Wednesday, December 4, 2024
4 changes · 18.0
Resolved issues and error corrections
Clearing formatting in the HTML editor now works correctly for fully selected tables with colored cells. This prevents the editor from freezing and ensures table cell background colors can be removed as expected.
Original PR description
Description of the issue this PR addresses: I. Removing formatting on text with a background color inside a fully selected table triggers an infinite loop in `removeAllColor`. This happened because applying background color to selected table cells filtered out child nodes in each `<td>` to apply background color directly to the cell. However, this filtering should be skipped when there is no color to apply, such as when removing background color. II. This PR fixes an issue where the background color of a table cell could not be removed when clearing formatting. task-4333327 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures products created by Purchase users keep matching sales and purchase units of measure, even when some unit fields are hidden by access rights. It prevents products from accidentally defaulting purchase units to “Units,” reducing order and inventory mismatches.
Original PR description
Steps to reproduce: - User permission on purchase - Create a product with a specific uom_id - The uom_po_id is set to the default "Units" since the user has no access to the uom_po_id due to visibility restriction. Issue: The error occurs when users without admin rights on Purchase do not have visibility into uom_po_id. this leads to uom_po_id defaulting to "Units" during product creation. Consequently, there is a mismatch between uom_id and uom_po_id. Fix: The fix has been [implemented](https://github.com/odoo/odoo/commit/c6fd91d61b2f62cab4) .This commits aims to add a test to ensure alignement between the different uom (purchase and sales). opw-4286165 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The salary configurator dropdown now groups choices by category again, making options easier for users to browse and select. This restores expected behavior from the previous version and adds spacing below the dropdown for a cleaner experience.
Original PR description
Problem ---------- In th salary configurator, The display "group by category" for dropdown is broken in 18.0 due to framework task. Objective ---------- Make it works again like in 17.4. Group options by optgroup Solution ---------- add groups in the state and fill it with label of groups (attribute in optgroup) and all the choices (options inside optgroup) task-4350875
Users can once again add comments inside list items in Knowledge articles when using the new editor. This fixes an unintended limitation and helps teams keep feedback tied to the exact content they are discussing.
Original PR description
`position_plugin` does not share methods, but it offers features through resources that are pretty much essential for other plugins. In these cases, it makes sense to add them as a dependency. Prior to this PR, it was not possible to comment inside a list item (comment beacons were not allowed inside) in the new editor. It is not intended, and this commits allows it again. task-4331264