Original PR description

Problem:
On website > shop > product page, when trying to edit the link of "Terms and conditions", a traceback occurs.

Cause:
When applying changes on "Terms and conditions" in `shop/product`, `ColorPlugin.removeAllColor()` is called on the `a` element. Its color was applied by the `text-muted` class.
This case in color removal was not properly handled.

Solution:
In `getFonts`, consider elements that have those special classes (e.g., `text-muted`) when processing color removal.

Steps to reproduce:
1. Open website/shop.
2. Open any product page.
3. Open the editor.
4. Select the "Terms and conditions" text.
5. Click edit in the link popover.
6. Click apply.
7. Traceback occurs.

opw-5130016

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

Forward-Port-Of: odoo/odoo#229725

Original PR description

This commit fixes a test that sometimes failed, because we didn't wait for an animationFrame after the macro was complete. As a consequence, there was no guarantee that the form view had been updated before the check.

runbot error~226829

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

Forward-Port-Of: odoo/odoo#233153

Original PR description

Before this commit, after selecting a field containing the char "|"
for conditional display, the field on which the condition is set will
never appear again.

This commit enable the use of any characters in form fields

Steps to reproduce the bug:
- Add a form
- Add two fields (A and B)
- Rename the field A with a string that contains "|"
- Set the field B visibility to "Visible only if"
- Set the field A as the visibility condition for field B
(field B visible only if field A contains 'hello', for example)
- Save the changes
- Complete the field A according to the visibility condition
(The second field does not appear)

task-3893749

Forward-Port-Of: odoo/odoo#181275

Original PR description

### Steps to reproduce:

- In the settings enable "Product Packaging"
- Create a product and set its `uom_id` (next to sales price) to "pack of 6"
- In the sales tab click on Packagings
> This opens a list view of units with convertions
#### > The "Units" is converted to "1 Undefined"

### Cause of the issue:

The "Units" uom does not have any set `relative_uom_id` so that `record.relative_uom_id[1] ` is undefined:
https://github.com/odoo/odoo/blob/e44ea4adbe56586349b78ae4796803777d8a782a/addons/uom/static/src/components/many2x_uom_tags/many2x_uom_tags.js#L74

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

Original PR description

Problem:
The CSS selector `li *` was applied globally, affecting all list content on pages where the editor is loaded — including frontend content outside the editor.

Cause:
The selector was not scoped to the editor context, so its styling leaked into non-editor elements.

Solution:
Restrict the `li *` selector to apply only within headers inside the editor to prevent unwanted global styling.

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

Original PR description

Problem introduced at [1] (see [2]). In stable, this comments the code to explain the dead code presence. In master, that snippet will be removed, as nobody seemed to have missed him for 4+ major versions and its structure is not perfect (overflow hidden...). Thankfully it should not come with any compatibility issue as it was not associated with any JS/CSS). Maybe a new equivalent will be introduced in master later on.

[1]: https://github.com/odoo/odoo/commit/b5c87d86cad1aa2b44f805da0b2d6635aeb85b96
[2]: https://github.com/odoo/odoo/pull/68644#discussion_r903721785

task-4084801

Forward-Port-Of: odoo/odoo#233203