Thursday, September 12, 2024
10 changes · master
Resolved issues and error corrections
The Install App button was adjusted to remove its icon, keeping it visually consistent with other areas of the product. In Events, the button label was restored from “Kiosk Mode” to “Registration Desk,” making the wording clearer and familiar for users.
Original PR description
*: events To stay consistent with the lack of icons in other areas, we remove the icon that was added in this button. We also rename the "Kiosk Mode" button to "Registration Desk" in events, as it was named before. task-4160938
This fix removes a rule that could hide content inside Masonry website blocks when elements extended beyond the box, such as while editing or typing text. It preserves users' ability to see and edit their content, while leaving a separate visual issue with rounded image filters to be solved later.
Original PR description
A new CSS `overflow: hidden` rule was added by [1] to hide an issue about background layers which can be reproduced that way: - Drag and drop a Masonry snippet. - Select any item of the snippet. -…
A new CSS `overflow: hidden` rule was added by [1] to hide an issue about background layers which can be reproduced that way: - Drag and drop a Masonry snippet. - Select any item of the snippet. - Through the inner item's options, add an image. - Set a border radius and apply a color filter. - Color filter extends beyond the rounded corners of the block. This is a known bug, which unfortunately has no acceptable solution yet. PR such as [2] is trying to solve that issue. Meanwhile, using the `overflow: hidden` CSS rule is not a solution at the moment: indeed, it means that anything you put inside those masonry boxes will not be visible as soon as it overflows the box. Including typing text. Anyways, we have future development plans meant to improve that grid mode behavior but using `overflow: hidden` is a bad practice anyway. Let's remove it and find a solution for the long-existing issue described above later. Note: there are also many other `overflow: hidden` rules in the codebase that we might want to remove in the future. But those are older and more complicated, and not so easily breaking things as in grid mode. [1]: https://github.com/odoo/odoo/commit/4660f06e6835347769d925cedd4bd5035b609c7b [2]: https://github.com/odoo/odoo/pull/163466 task-3358501
This fixes a display issue where editor popups or overlays could appear in the wrong place when the editor was used inside an embedded frame. Users editing content in those embedded contexts should now see selection-related controls positioned correctly, improving usability and reducing confusion.
Original PR description
Before this commit, the overlay positioning was not correctly calculated when the editor was mounted in an iframe. This commit makes sure that: - the target element for the usePosition hook representing the selected range is attached to the editable's document, so that the usePosition hook can detect it in case it is in an iframe and adjust the overlay's position accordingly. - the container for overlay positioning is updated when a scroll event takes place in the top document.
The timesheet timer now appears on a single line for a cleaner, more consistent look. This makes the timer easier to read and helps align the timesheet interface with the rest of the system.
Original PR description
Modified the timesheet timer display to use a single line format for consistency. This change ensures that the timer is now presented in a more streamlined manner. task-4146841
This update replaces an outdated internal password hashing call with the currently supported method. It helps keep user authentication code maintainable and aligned with supported security libraries, with no expected change for end users.
Original PR description
*: website `crypt_context.encrypt` is deprecated since passlib 1.7. We don't support passlib 1.6 and lower anymore, so this commit changes all usages of `encrypt` to `hash` and removes the `encrypt` method in the wrapper class. task-4179594
Fixed an issue in the HTML editor where the formatting toolbar could appear even when no content was actually selected, such as after double-clicking at the end of a line. This makes editing feel cleaner and prevents confusing toolbar behavior for users.
Original PR description
Before this commit, it was possible to have an empty-looking selection that opened the toolbar. For example, when double-clicking at the end of a line. Solution: The toolbar is only opened if there is at least 1 traversedNode. 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
Using the pager in list and kanban views now resets the content back to the top. This prevents users from landing mid-page after moving between result pages, making navigation clearer and less confusing.
Original PR description
This commit fixes an issue where using the pager in list and kanban view would'nt reset the scroll value of the list view. This is due to the fact that the code which was supposed to handle this functionality in list view was targeting the wrong HTML element and there was no equivalent in kanban. task-4134026
Corrects a broken filter used to find liquidity journals after credit card journals were introduced. This helps accounting users see the right journal records when filtering, avoiding confusion in day-to-day financial setup and review.
Original PR description
With the introduction of the [credit card journal](https://github.com/odoo/odoo/pull/175315) the liquidity filter broke. No task
This fix aligns asset-related screens with the newer "list" view naming instead of the older "tree" wording. It helps keep the interface and configuration consistent with recent platform changes, reducing small display or compatibility issues.
Original PR description
[FIX] base/ir.ui.view: fix use 'list' instead of 'tree' see: https://github.com/odoo/odoo/pull/159909
Fixed a visual issue where WhatsApp partner message bubbles appeared unnecessarily faded. This keeps message bubbles easier to read and consistent with the intended conversation styling.
Original PR description
The WhatsApp partner message bubble had an unnecessary `opacity-25` class assigned. The original purpose of the line was to apply a `light-green` background to the bubble. However, as this would conflict with the existing color formatting for message bubbles, this line has now become redundant.  