The project settings page has been reorganized with a new grouping area so related options can be placed more clearly on the right side. This supports a cleaner setup experience and prepares the layout for additional enterprise settings.

Add a new group in the settings page, allowing to put some others
settings on the right side of the page (needed in enterprise).

Task-1942377 Closes #31212

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Chat and Discuss autocomplete lists now automatically highlight the first suggestion. This makes it faster for users to navigate and select contacts or channels using the keyboard.

Task:https://www.odoo.com/web#id=1894447&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
Pad:https://pad.odoo.com/p/r.11840c36adae746affa5f56b44d4612a


--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This change makes Odoo's browser-based automated tests look for clear success and failure messages instead of generic words that can appear during normal use. It reduces false test failures and improves diagnostic logging, helping teams maintain quality with fewer misleading test results.

When evaluating js tests using the browser_js method, they are
considered a success when 'ok' is found in the console log and a failure
if 'error' is found instead.

This is not very robust and recently failed with this commit : 7410de111fe
It adds a filter named 'Error' in a view, when the 'click_all' test
clicks on this filter, a message with the name of the filter is written
in the console, wrongly leading to a test failure.

With this commit, the browser_js method expects a log message in the
browser console with the explicit text "test successful".
On the other hand, any error in the console log will lead to a test
failure but a test can be forced to fail with the explicit error message
in the browser console "test failed".

As a bonus, the python logger should now also log browser js trace messages.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This update makes an internal online learning method private, reducing the chance it is used incorrectly by other parts of the system. The change is technical housekeeping and should not affect how users create, manage, or view eLearning content.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:



@odony 
Another conflict for @Elkasitu 


--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Adds demo payroll data so the Belgian individual account report can be tested more easily for a full year. This helps ensure the report works reliably when all yearly payslips are required.

The website opportunity form now uses the same “Expected Closing” wording as the backend instead of calling the field “Deadline.” This reduces confusion for users moving between the website and internal CRM screens.

In the backend interface, lead/opportunity date_deadline is named
"Expected Closing" or sometime "Expected Closing Date" but on the
frontend it was named "Deadline" for opportunity.

opw-1941273

This fixes an issue where users could only open the link editor by double-clicking directly on a link itself. Double-clicking text inside linked buttons, such as call-to-action snippets, now opens the link editor as expected while media items still open their own editor.

The link modal only opened on double-click directly on an anchor,
meaning that double-clicking text in a span node within the button (as
is the case in the call-to-action snippet for instance) wouldn't open
the modal.
Now it opens as long as we have an ancestor that is an anchor, unless
the double-click occurs on a media (eg: a pictogram), in which case it
should open the media's modal.

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This fixes a visual issue in the product configurator where the grey image editing handle did not stay correctly positioned when users scrolled. The change helps keep image editing controls predictable and avoids confusion during product configuration.

The image handle (grey overlay over the image) was not properly
repositioning on scroll in the product configurator (a side effect of
not having a popover).

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This fix prevents selected text inside links from being incorrectly wrapped as a new paragraph when deleted or replaced. It improves editing behavior in the website editor, especially for accordion titles where typing could appear to add an unwanted newline.

This notably fixes a bug with the accordion snippet (website) where selecting a title and typing seemed to add a newline.

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The website editor now avoids adding hidden spacing characters around media in areas that are not meant to be directly edited, such as navigation bars. This prevents unwanted invisible content from appearing in protected layout areas while keeping media replacement behavior intact.

The web editor inserts zero-width characters (unicode 200B) around media
when inserting them in the DOM so as to be able to edit before and after
said media (contenteditable caveat). It should however not do so in fake
not-editable nodes - such as the navbar - given that we do not expect to
edit in them but only to replace the media. This ensures that behaviour.

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This update fixes issues that caused documentation builds to fail or show confusing warnings. It also improves how the documentation system loads matching source code, helping keep published developer documentation accurate and reliable.