Monday, January 13, 2025
5 changes · saas-18.1
Resolved issues and error corrections
The checkout helper now points to the updated script location after a previous update left it referencing an old path. This helps keep IoT box setup and maintenance processes running reliably without manual correction.
Original PR description
Forward-porting [this PR](https://github.com/odoo/odoo/pull/191928) resulted in setting path for checkout script to old path. The path is now set to the new location (in `iot_box_image` module).
Keyboard navigation in dropdown menus now clearly shows the currently selected option again. This restores expected behavior for users who rely on arrow keys, improving usability and accessibility when choosing records.
Original PR description
- Previously, navigating through dropdown options using the keyboard's up and down arrow keys would highlight the selected value in the dropdown. However, this functionality was inadvertently removed in this commit https://github.com/odoo/odoo/commit/6d77fb2d823688fcdd3085cd15c7a28771e783b6, resulting in the selected record not being visible during keyboard navigation. - This fix restores the original behavior, ensuring that the selected option is properly highlighted and visible when navigating with the keyboard. Task-4402580 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where selecting a Point of Sale preset by name could fail if no customer was linked. This prevents an unexpected error during checkout setup and keeps the sales flow uninterrupted.
Original PR description
Since https://github.com/odoo/odoo/pull/192154, selecting a preset indentified by name without a partner raise a traceback as we try to access the name of the partner which is undefined. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The web test timeout has been reduced now that the underlying browser-related slowdown has been fixed. This helps failed or unhealthy builds stop sooner, making regressions such as memory problems visible more quickly without affecting end users.
Original PR description
This timeout has been recently increased [1] because builds sometimes reached it. It was indicating that something was wrong, but until we figured it out, the correct thing to do was to increase it. PR [2] just fixed the underlying issue, which was coming from the update to from chrome 123 to chrome 126 on runbots. Indeed, as of chrome 124, the instruction to force a garbage collect after each test had to be slightly adapted. Now that this is done, this suite generally lasts 20-22 minutes, so we can safely decrease the timeout to 30 minutes, which allows us to kill the test earlier when something's wrong, and which will indicate regressions (like memory leaks) faster. [1] odoo/odoo#191456 [2] odoo/odoo#193332 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
Selecting a document record in mobile view no longer triggers an error after reloading the page. This improves reliability for users managing documents on phones or narrow screens.
Original PR description
**Steps to reproduce:** Switch to mobile view Reload the page Select any record Traceback occurs **Technical:** After commit https://github.com/odoo/odoo/commit/ef3656e3468ba6dab207c8df65d12fbb75ae4c77, the 'isPageSelected' condition was removed for the ALL button in the "web.list.selection" template. As a result, the first two conditions will be true, and the system will then check for model.root.isRecordCountTrustable. However, at that point, the model is not available. Previously, the false value of isPageSelected would prevent the check for the model from occurring. **After this commit:** The user will not encounter any traceback when selecting a record in mobile view. Task-4402442