Thursday, July 22, 2021
4 changes · master
Resolved issues and error corrections
This fixes internal developer documentation for web notifications and popovers by restoring that certain callbacks do not return a value. It helps prevent confusion for future maintenance without changing how users experience the system.
Original PR description
odoo/odoo#74003 updated a few docstrings, half of them being the typing of callbacks to not use the TypeScript syntax / extension. However in doing so it dropped critical parts of the signature (namely the specific type of the return value -- or the lack thereof). Update this error to restore the information that the callbacks have no return value.
This update rewrites a web interface color definition into a more widely supported format. It helps avoid styling issues in environments where some stylesheet tools could not process the previous color format.
Original PR description
Some scss compilers are not supporting the colors written in hexadecimal with 8 digits. So to keep the the color and transparency, we have re-written the color in rgba. Issue introduced in: https://github.com/odoo/odoo/commit/a1c983250e9547c383ef677fb411b0bc589efa89 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
Helpdesk analysis reports now keep the user's chosen measurement when filters are applied. This prevents reports from unexpectedly switching back to Count, making analysis more consistent and reducing rework.
Original PR description
Current behaviour:
* In the analysis report, after having set a measure other than Count,
the measure is reset to Count after having applied a filter.
Expected behaviour:
* In the analysis report, after having set a measure other than Count,
the measure remains selected after having applied a filter.Financial reports now correctly stop listening for window resize events after users navigate away. This prevents crashes when another action is opened on top of a report, improving stability without changing report functionality.
Original PR description
When on the "account_report" client action, do an action on top of it with the actionService You should have the "account_report" as a breadcrumb Trigger the resize event on window Before this commit, the handler defined by the "account_report" client action was executed eventhough the client action was not here anymore, resulting in a crash because the DOM was not as expected After this commit, there is no crash anymore, since we disable the resize handler at the right time This follows the refactoring at: 0573acae2306bf5da2005852da9323ddc59e5431