Sunday, April 20, 2025
4 changes · saas-18.2
Resolved issues and error corrections
Users can now scroll through pivot dimensions in the spreadsheet side panel when it is in readonly mode. This fixes a usability issue that prevented viewing all available pivot details without enabling editing.
Original PR description
The `pointer-events: none;` property prevents elements (and their children) from receiving any pointer events, including scroll gestures. As a result, scrolling the pivot dimensions in readonly mode was not possible. To fix this, we removed `pointer-events: none;` from the main container and applied it only to the child elements of the pivot dimensions. Task: 4655830
Miscellaneous changes
Reproduce: - Switch to mobile view - Go to Project module - Click on the gear icon next to a task or project - Click the Start (or Launch) button in the dropdown - Try tapping anywhere on the button (not just on the text) Description of the issue/feature this PR addresses: In the mobile view of the Project module, clicking the Start button from the dropdown menu only works if the user taps directly on the text. Tapping on the surrounding area within the button does not trigger the actio
Original PR description
Reproduce: - Switch to mobile view - Go to Project module - Click on the gear icon next to a task or project - Click the Start (or Launch) button in the dropdown - Try tapping anywhere on the button…
Reproduce: - Switch to mobile view - Go to Project module - Click on the gear icon next to a task or project - Click the Start (or Launch) button in the dropdown - Try tapping anywhere on the button (not just on the text) Description of the issue/feature this PR addresses: In the mobile view of the Project module, clicking the Start button from the dropdown menu only works if the user taps directly on the text. Tapping on the surrounding area within the button does not trigger the action—instead, it closes the menu without starting the timer. Root cause: The button inside the dropdown is wrapped in a `<span>` element, but its width does not extend across the entire span. As a result, only the text area is interactive, which causes usability issues on mobile where precise tapping is harder. Solution: Ensure the button inside the dropdown item spans the full width of its container by setting `width: 100%`. This allows the entire area of the button to be clickable, improving usability on mobile devices. Desired behavior after PR is merged: Tapping anywhere on the button (not just the text) now consistently triggers the timer as expected. opw-4561724 Forward-Port-Of: odoo/odoo#205660
Before thos commit, the next invoice date was updated at post invoice based on the order line properties. pre paid lines are will use the last deferred end date of the linked account move lines and post paid line simply increment the next invoice date. Before this commit, the post paid detection was faulty: we checked that all line were postpaid but if line notes or non recurring lines existed, they would not have the postpaid property. As a result, the next invoice date would be incremented
Original PR description
Before thos commit, the next invoice date was updated at post invoice based on the order line properties. pre paid lines are will use the last deferred end date of the linked account move lines and post paid line simply increment the next invoice date. Before this commit, the post paid detection was faulty: we checked that all line were postpaid but if line notes or non recurring lines existed, they would not have the postpaid property. As a result, the next invoice date would be incremented with the prepaid condition. As a result, the next invoice date would only be incremented by one day and the cron would run on these contracts every day. opw-4618947 opw-4668741 opw-4686930 Forward-Port-Of: odoo/enterprise#83701 Forward-Port-Of: odoo/enterprise#83438
This commit slightly adapts a Gantt test to accommodate adjustments made in Chrome 135 to some rounding done during painting. To do so, and to avoid a purely arbitrary value, the related assert is modified to check the visibility of the "today" column and that there is an actual scroll applied instead of an arbitrary scroll of 762px. References (not exhaustive): - https://chromium.googlesource.com/chromium/src.git/+/a629cc4312019dfa43b686bdb2d9418a625f9bc6 - https://chromium.googlesource.co
Original PR description
This commit slightly adapts a Gantt test to accommodate adjustments made in Chrome 135 to some rounding done during painting. To do so, and to avoid a purely arbitrary value, the related assert is modified to check the visibility of the "today" column and that there is an actual scroll applied instead of an arbitrary scroll of 762px. References (not exhaustive): - https://chromium.googlesource.com/chromium/src.git/+/a629cc4312019dfa43b686bdb2d9418a625f9bc6 - https://chromium.googlesource.com/chromium/src.git/+/2efdf2a6f8e184ece09acca4677d1ce9eb7a43ea - https://chromium.googlesource.com/chromium/src.git/+/ce7a5f6b60b175c780fb39e2f751d82abb8b011b Forward-Port-Of: odoo/enterprise#83639 Forward-Port-Of: odoo/enterprise#83587