Tuesday, May 2, 2023
8 changes · master
Resolved issues and error corrections
This change stabilizes an automated test for advanced search date comparisons by using a fixed date. It helps prevent false test failures when the calendar month changes, supporting smoother development and release validation without changing user-facing behavior.
Original PR description
This commit adds a patchDate to the "Several date filters and a comparison" test. The patchDate will allow the date to be fixed and prevent the test from being invalidated when the month changes in the real world. 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
List views now apply warning or status colors consistently to many2one fields, such as customer or product links. This makes highlighted rows easier to read and prevents important visual cues from being missed.
Original PR description
Before this commit, in a list view, the style of a decoration on a m2o widget was ignored. For example, when applying the danger decoration, we want the m2o field to be in red. How to reproduce: Go to a list view with a field having the many2one widget and a danger-decoration. Have a line that respects the decoration condition. Before this commit: All text on the line is red except the many2one text After this commit: All text on the line is in red 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 change makes Odoo field components correctly respect read-only rules when the same field appears multiple times in a view. This helps prevent fields from being editable or locked incorrectly, improving consistency for users working with complex forms and lists.
Original PR description
In many field composents, we need to know if the field modifier is readonly or not. So we use the function record.isReadonly(fieldname) to get the information. This one is false if we have several times the same <field> defined in a view. We will only listen to the modfier.readonly of the last occurrence. To solve this problem and allow the use of several fields in the same view with different modifiers, we will have to extract the readonlyModifiers and evaluate it in the field component. Part of task: 3179751 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
Fixed an issue where short chatter message areas could show a large, unnecessary scrollbar even when there was little content. This makes the message panel cleaner and easier to use, especially when only one or a few messages are present.
Original PR description
Before this commit, when chatter message list was lower than 2500px, the message-list had scrollable of 2500px of height. This happens because the area detecting present time was always 2500px. thus making the content have this value as scrollheight. This commit fixes the issue by making presence area not go above the conversation height. So if message list is 250px of height, then presence area is 250px, not 2500px. This chatter, before commit, when it had a single message: <img width="1029" alt="Screenshot 2023-04-28 at 18 47 55" src="https://user-images.githubusercontent.com/6569390/235206760-33c8f012-fac3-4070-9bbf-c8d3132e2dcf.png"> With commit, no longer has scrollbar: <img width="1033" alt="Screenshot 2023-04-28 at 18 49 56" src="https://user-images.githubusercontent.com/6569390/235206912-5ae9d876-6398-42ea-b5d2-dd162cc564ad.png">
This update corrects how dynamic numbers and values are inserted into on-screen messages across payment, website editing, web views, and slide discussions. It helps prevent confusing or incorrectly formatted text from appearing to users.
Original PR description
*: web, web_editor, payment Before this commit, templates with %d was given to sprintf but it was not interpreted by the function After the commit, %d are replaced by %s in templates for sprintf Also this commit converts a last _.str.sprintf into sprintf
This change stabilizes an automated test for mail message replies by waiting for the page update more precisely before checking the result. It helps reduce false test failures in the development pipeline, supporting smoother and more reliable releases.
Original PR description
Before this PR, the `Updating the parent message of a reply also updates the visual of the reply` test was failing in a non-deterministic fashion. This PR fixes this issue by replacing the `nextTick` by a specific `waitUntil` in order to ensure the DOM is properly updated before asserting. Fixes 20829 runbot issue.
This update fixes version numbers in several localization-related modules so they align with the expected release information. It helps avoid confusion during upgrades, app management, or support checks without changing business functionality.
Original PR description
See odoo/odoo#118420
This update makes fields correctly respect read-only rules when the same field appears multiple times in a view. It helps prevent incorrect editing behavior in the timesheet grid and improves consistency for users.
Original PR description
In many field composents, we need to know if the field modifier is readonly or not. So we use the function record.isReadonly(fieldname) to get the information. This one is false if we have several times the same <field> defined in a view. We will only listen to the modfier.readonly of the last occurrence. To solve this problem and allow the use of several fields in the same view with different modifiers, we will have to extract the readonlyModifiers and evaluate it in the field component. Part of task: 3179751