The live chat and mail areas now use Odoo's standard text formatting tool instead of an older external helper. This is a small internal cleanup that improves consistency and maintainability without changing the user experience.

**Current behavior before PR:**

`_.str.sprintf` was being used

**Desired behavior after PR is merged:**

replaced `_.str.sprintf` with `sprintf`

Task-2810721

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

This update renames an internal device-size label from “mobile” to “small” across messaging-related screens. It helps keep the product terminology consistent for upcoming Discuss improvements without changing user-facing behavior.

*: sms, snailmail.

In order to reduce the noise in the new discuss env PR, all the
messaging.device.isMobile occurences have been renamed to isSmall
in order to match the new env terminology.

task-2582313

enterprise: https://github.com/odoo/enterprise/pull/26597

Industry labels have been cleaned up to better match NACE naming conventions. This improves consistency and clarity for users selecting or reviewing partner industry classifications.

In the current version, some industries are named things like `Administrative`,
`Food`, and `Transportation`, and do not have the proper space and dash after
the first alphabet in full name.

This commit renames the above industries to `Administrative/Utilities`,
`Food/Hospitality`, and `Transportation/Logistic` respectively, and also adds
 space after comma and semicolon according to `NACE` rules, and also adds a dash
 after the first alphabet in the full name.

task-2674365

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 prepares several Odoo modules for an upcoming messaging environment change by aligning internal test server method names. It is a behind-the-scenes cleanup that should reduce future development complexity without changing day-to-day user behavior.

*: calendar, hr_holidays, im_livechat, note, website_livechat.

This PR helps reducing the noise in the discuss new env PR. Indeed,
the new mockServer has the same method except that they are not prefixed
by any underscore. All calls have been changed, and the corresponding
methods created. They will be deleted later.

task-2582313

enterprise: https://github.com/odoo/enterprise/pull/26603

The mail plugin now shows a clearer message when a contact or company email address is invalid. This helps users understand what needs to be corrected and reduces confusion during email-related workflows.

Purpose
=======
Improve the error message when the email
of the contact / company is not valid.

Task-2601837

The mail module was reorganized so key interface pieces are backed by clearer internal models. This should make future mail features easier to maintain and evolve without directly changing the user experience today.

This commit introduces models that define records being 1:1 map with components,
as a step to move further to having essentially all business code in models.

Having code in models is desirable to have very maintainable code, thanks to
robust and declarative code with an ORM-like architecture.

Task-2831082

enterprise: https://github.com/odoo/enterprise/pull/26637

The mail composer suggestion list was simplified by removing an unnecessary positioning option. This is a small internal cleanup that helps keep the messaging interface easier to maintain without changing the user experience.

Task-2831082

A small unused part of the mail dialog code was removed. This helps keep the product codebase cleaner and easier to maintain, with no expected change for end users.

Task-2831082

The mail module now centralizes how dialogs respond to global keyboard actions. This makes dialog behavior more consistent and easier to maintain, with limited direct impact for everyday users.

Task-2831082

This update improves how mail-related pop-up windows respond to clicks outside the window. It helps create more consistent and predictable behavior when users interact with dialogs in the messaging interface.

Task-2831082

This update improves the Mail follower interface by adding a clearer remove action for followers. It helps users manage who follows conversations or records more smoothly, reducing friction in day-to-day communication management.

Task-2831082

The mail app’s chat window header has been reorganized into its own reusable view. This makes the chat interface easier to maintain and supports more consistent behavior across chat windows without changing core business workflows.

Task-2831082

The mail follow button now uses a dedicated view to better manage interactions such as leaving an unfollow action. This makes the follow/unfollow experience more consistent and easier to maintain, reducing small usability issues for users following conversations or records.

Task-2831082

The mail follow button now has a dedicated interface component to better manage hover behavior when users are about to unfollow. This makes the follow/unfollow interaction clearer and more consistent for users in messaging-related screens.

Task-2831082

This update improves how the mail chatter top bar receives internal context, helping it work more reliably within the chatter interface. The change is minor and supports smoother maintenance of the messaging area without introducing visible workflow changes for users.

Task-2831082

This change adjusts the mail app's test setup so timing controls are returned in a cleaner way. It is mainly preparation for upcoming Discuss app environment changes and should not affect day-to-day users.

This PR prepares the ground for the introduction of the new environment in the discuss
app. For now, the start method adds the advanceTime function to the environment. The issue
is that the new env is not extendable. This change makes a lot of noise hence the prep PR.

task-2582313

The mail module’s user interface code was reorganized to make it easier to maintain and evolve. This internal improvement supports more reliable future updates to chat, chatter, attachments, and composer features without changing day-to-day user workflows.

This commit introduces models that define records being 1:1 map with components,
as a step to move further to having essentially all business code in models.

Having code in models is desirable to have very maintainable code, thanks to
robust and declarative code with an ORM-like architecture.

Task-2831082

This update reorganizes parts of the Approvals and Sign apps so their screens are backed by clearer internal view models. It should not change day-to-day behavior for users, but it helps the product team maintain and evolve these apps more reliably over time.

This commit introduces models that define records being 1:1 map with components,
as a step to move further to having essentially all business code in models.

Having code in models is desirable to have very maintainable code, thanks to
robust and declarative code with an ORM-like architecture.

Task-2831082

community: https://github.com/odoo/odoo/pull/89735

This update adjusts internal approval app test helpers so they match a newer mock server structure. It is a behind-the-scenes preparation that reduces future migration effort and should not change the user experience.

This PR helps reducing the noise in the discuss new env PR. Indeed,
the new mockServer has the same method except that they are not prefixed
by any underscore. All calls have been changed, and the corresponding
methods created. They will be deleted later.

task-2582313

community: https://github.com/odoo/odoo/pull/89659

A new debug-only menu option lets administrators request a fresh spreadsheet snapshot when a file is slow to load. This improves loading performance by clearing the current undo and redo history for that spreadsheet session.

The purpose of this commit is to add a menu item in the file menu
(only visible in debug mode) in order to request a snapshot. Requesting
a snapshot will imply to clear the revisions of the current session, so
the history (undo/redo) will be lost, but loading time will be reduce.
So this button should be used when a spreadsheet takes long time to load.

In an ideal world, we should be able to clearly identify when a session
should be closed (when there is no more active users).

The mail enterprise code now uses the newer “isSmall” naming instead of “isMobile” when adapting Discuss views to smaller screens. This is an internal cleanup that makes future Discuss improvements easier to integrate without changing visible behavior for users.

In order to reduce the noise in the new discuss env PR, all the
messaging.device.isMobile occurences have been renamed to isSmall
in order to match the new env terminology.

task-2582313

community: https://github.com/odoo/odoo/pull/89655