Wednesday, April 17, 2024
4 changes
2 changes
Enhancements to existing features
This update removes style settings that were defined but not actually used across several Odoo Enterprise areas. It helps keep the codebase cleaner and easier to maintain, with no expected change to how users see or use the product.
Original PR description
This commit removes assigned but never used SCSS variables.
Argentine electronic invoicing and VAT reporting now use the shared invoice currency rate stored on accounting entries. This keeps enterprise localization aligned with the main accounting changes and helps ensure consistent currency conversion data across reports and documents.
Original PR description
*: l10n_ar_edi,l10n_ar_reports In the related community PR the field 'l10n_ar_currency_rate' was removed in favor of the new stored 'currency_rate' field on account.move . This commit does the necessary changes in enterprise. task-3634224 see odoo/odoo#147910 see odoo/upgrade#5496
2 changes
Enhancements to existing features
The system now uses more precise targeting to locate the fiscal position field in invoice forms, making the code more reliable and easier to maintain. This change fixes compatibility issues with customizations while improving how the system identifies and modifies form fields.
Original PR description
Currently, an inherited view for `account.view_move_form` targets field `fiscal_position_id` directly with an xpath. While that works for standard modules, it is a very broad xpath that only succeeds in selecting the correct field because it appears before other ocurrences of identically named fields. This commit narrows down the xpath to make it explicit that we target the field located in `account.move`'s "Other Info" page. This fixes an ongoing issue with a customization (described in the task) while improving readability and extensability of `account_invoice_form_inherit`. Task link: [odoo/task#3837027](https://www.odoo.com/web#model=project.task&id=3837027) Task-3837027 Forward-Port-Of: odoo/enterprise#60358
This update improves the documentation and testing of the throttleForAnimation function to help developers understand how to properly handle browser events that lose their context during asynchronous operations. The change includes better guidance and test cases showing how to track scroll event targets in Chrome, preventing potential issues when animations are throttled.
Original PR description
This is a followup on [1]. In Chrome the event's currentTarget is cleared after events such as "scroll" are handled. For asynchronously called methods to be able to access it, the current value of currentTarget needs to be kept. To help developers that might stumble on this issue when using `throttleForAnimation`, this commit emphasizes the fact that usage of that function is not limited to event handlers, and it adds a test case that illustrates a solution for tracking the lost scroll event target. No scenario was identified in 15.0, but this could be used as an alternative solution for [1]. [1]: https://github.com/odoo/odoo/commit/0ba601d2ef5c4e2f846818e78dcd23966d6f563d task-3449843 Forward-Port-Of: odoo/odoo#160969 Forward-Port-Of: odoo/odoo#131259