The mail app’s emoji picker has been renamed from “emojis popover” to “emoji list” in the underlying code and related tests. This makes the feature naming clearer and more consistent for future maintenance without changing how users interact with emojis.

Task-2694206

Odoo now avoids storing the same website and interface view data in two separate caches. This should reduce memory use and unnecessary cache refreshes without changing how users experience the system.

QWeb views are cached two times, first in _compile who itself calls _read_template that is
also cached. The result is a 0% HIT rate on _read_template, and all frontend views are two
times stored in the cache.

Note that _read_template is only used by _compile, and another one in web_studio (that does
not need to be cached). So, removing this cache won't impact the CPU performance, but will
reuce memory usage and LRU invalidations.



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

This change updates the Mail/Discuss internals to prepare for a newer version of the underlying interface framework. It is a low-risk maintenance improvement intended to keep messaging features compatible and easier to evolve, with no expected change for day-to-day users.

In preparation for using OWL v2 in discuss code.
(`shouldUpdateBasedOnProps` will be removed)

Task-2695743

The mail module now detects when record creation includes information that does not match a real field, instead of silently ignoring it. This helps catch configuration or integration mistakes earlier and reduces the risk of hidden data issues, while also removing unused code uncovered by the change.

Invalid data provided at record creation were silently skipped by the framework without triggering an error. This commit ensures that data are no longer accidentally filtered and therefore that an error will be raised if a key that does not match an actual field is provided.

This commit also removes the dead code that was detected thanks to these changes.

Website editors can now apply transparency effects to mega menus as intended. This improves visual consistency for site designs that use transparent navigation areas, while keeping existing mega menus non-transparent by default.

Make the transparency effect work on mega menus.
This effect was not working because the container that contains the mega menu was not transparent.

This comes with an upgrade script, see https://github.com/odoo/upgrade/pull/2929

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

This update changes how Odoo imports records with nested line items so existing linked lines are not unnecessarily removed and recreated. It helps prevent important tax report tags from being wiped during module updates, reducing the risk of incorrect tax and journal item data after localization updates.

if there is the child then write vals is created like {'field_o2m_name': None} so it removes lines and adds them again by sub_records

so in this commit, we do not add f_name in vals if there is a child of o2m

this give a big effect on account.tax.report to check just update any localization module where account.tax.report is there, after the update all tag is removed from taxes and journal items(account.move.line)


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

Those were not accounted for, leading to fstrings passing through unflagged. Also update the SQL checker to be stricter but smarter: The previous version would "fail open", unknown nodes would be allowed through hence f-strings not being flagged when they started appearing in arg0 position, should now fail-closed, anything that's not allowed is forbidden. This flags a few more cases, all of which seem acceptable upon review. However the previous version would also only resolve ar