Monday, January 28, 2019
6 changes · master
Enhancements to existing features
This update standardizes selection field values so they are stored and handled as text across affected business apps. It reduces inconsistencies and future compatibility issues without introducing a visible workflow change for most users.
Original PR description
odoo/odoo#29039
Resolved issues and error corrections
This fix makes automated browser tests wait for the actual page to finish loading instead of sometimes mistaking a blank startup page as ready. It reduces rare, misleading test failures and helps keep development validation more stable.
Original PR description
cherry-pick of 03a88196525 In an HttpCase test, when the browser_js method is used, an optional javascript code can be used to check that the page is ready to execute the test. When no 'ready' code is given it defaults to check the 'document.readyState' status. In some rare cases (discovered by @Xavier-Do) this status is checked on the 'about:blank' page. As the page seems ready, the test code is evaluated and fails. With this commit, when no specific ready code is provided, the test will wait for a chrome devtools event that ensure the page is fully loaded before starting the test.
This fix removes duplicate field entries that appeared in website sales and eLearning configuration views after a previous update. It helps keep the interface cleaner and avoids confusion for users managing products or course channels.
This change prevents automated browser tests from checking readiness too early, before the intended page has loaded. It reduces rare, hard-to-reproduce test failures and improves confidence in build results without changing user-facing behavior.
Original PR description
In some rare case the _wait_ready was executed before the expected page was loaded This should be impossible since navigate_to should ensure that the url is loaded, but since this bug is difficult to reproduce, this fix should be enough waiting for a better solution. This bug was leading to some test failling, especially the test_01_js_interpretation (a + b + c === 6) Side note: The only way to reproduce this bug 100% of the time was to reboot, and only the very first build was failling. Killing chrome wasn't enough. Installing only test_assetsbundle was enough, using chrome version 71.0.3578.98 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
This update fixes misspellings in website snippet text. It improves the professionalism and clarity of website content for users and visitors without changing functionality.
Original PR description
opw-1931844 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
This fixes a visual glitch that occurred when users liked or disliked slides on the website learning pages. The change makes the interaction look more reliable and polished for visitors using slide content.
Original PR description
Description of the issue/feature this PR addresses: Issue: https://youtu.be/1XKl4Zf016A 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