Sunday, November 16, 2025
4 changes · saas-18.4
Resolved issues and error corrections
This update improves automated web tests by making sure unfinished drag actions are properly canceled at the end of each test. It prevents leftover test actions from causing delayed errors after a test has already completed, making the test suite more stable and reliable.
Original PR description
Before this commit, when initiating an unfinished drag sequence (i.e. calling `drag` without `drop` or `cancel`), the drag sequence was ended by destroying the component, which could throw asynchronous errors after the test finished. One possible fix would be to wait for these errors upon ending a test, but this process is handled by Owl and through a possible chain of promises, which would have to be accounted for by an arbitrary amount of 'animationFrame' or 'advanceTime' calls. Instead, the `contains...drag` and `contains...dragAndDrop` now handle a single drag sequence at a time, with a systematic cleanup after each test in case a drag sequence has been left pending. In such cases, the sequence is canceled. Enterprise: https://github.com/odoo/enterprise/pull/99369 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#235593 Forward-Port-Of: odoo/odoo#235359
This fix makes sure kanban views return to their normal record limit after a user removes grouping and switches back from another view. It prevents the page from trying to load too many records at once, which could slow down the interface or cause it to crash.
Original PR description
Steps to reproduce ================== - Add a group by in the kanban product view - Switch to the list view - Remove the group by - Switch back to the kanban view -> No limit is applied, and the webclient can crash if too many records are returned. Cause of the issue ================== The groupsLimit is set as MAX_SAFE_INTEGER in the kanban view https://github.com/odoo/odoo/blob/df959e05ac9cf3136d1724bc80b7597a70932225/addons/web/static/src/views/kanban/kanban_controller.js#L168 Which is then reused as the limit https://github.com/odoo/odoo/blob/df959e05ac9cf3136d1724bc80b7597a70932225/addons/web/static/src/model/relational_model/relational_model.js#L368 Solution ======== There is already a code path to reset the limit when switching from grouped to ungrouped, but is wasn't called on the first load (when this.root isn't set yet) opw-5167769 Forward-Port-Of: odoo/odoo#235794 Forward-Port-Of: odoo/odoo#235232
This update makes automated drag-and-drop tests finish their cancel or drop actions before the test ends. It helps prevent flaky test results and makes the test suite more reliable.
Original PR description
Since drag sequences are automatically canceled at the end of tests, 'cancel' or 'drop' calls should be properly awaited before the end of a test. This commit ensures that these actions are properly finished before a test ends. Community: https://github.com/odoo/odoo/pull/235359 Forward-Port-Of: odoo/enterprise#99449 Forward-Port-Of: odoo/enterprise#99369
This change prevents product review cards from appearing through the portal chatter area when viewed on mobile. It restores the correct background in the sticky section so the page looks clean and readable while scrolling.
Original PR description
To reproduce: ============= 1- Enable product reviews on the website 2- Add a few reviews 3- Switch to mobile view -> Scroll to see the behavior Why: ==== This commit did the problem https://github.com/odoo/odoo/commit/f13ee41a4a62f7fedbddc4245e52ee8e9dce9e0e Specifically this change: https://github.com/odoo/odoo/commit/f13ee41a4a62f7fedbddc4245e52ee8e9dce9e0e#diff-6e5197b652583a0032baba5d873fb639b7567600f54b58acce137945ca072b03L23-R24 So the value of the background-color for the portal Chatter is no longer getting background-color of the body. Solution: ========= Apply the body background-color to the sticky part. opw-5098372 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#229272