Thursday, November 6, 2025
4 changes · 19.0
Enhancements to existing features
The POS pre-ticket now shows a suggested tip for Chilean restaurants when early receipt printing is enabled. It also removes fiscal details from this pre-payment receipt so the printed information matches what is available at that stage and stays compliant with local requirements.
Original PR description
**PURPOSE** - Comply with Chilean [law](https://blog.nubox.com/contadores/ley-de-propinas-en-chile) requiring restaurants to print a 'suggested tip' on the pre-ticket (before payment). - Ensure the LATAM tip flow behaves correctly in POS. - Prevent fiscal data from being printed in the pre-ticket since it’s not required and cannot be generated accurately at that stage. **SPECIFICATION** - When Early Receipt Printing is enabled: - Exclude fiscal elements from pre-ticket in l10n_cl_edi_pos. - Add a 'Suggested Tip' line showing 10% of the order subtotal (before taxes) task-5060967
This pull request mainly updates accounting and localization content, including new tax report codes for Finland and translation refreshes. It also fixes several smaller issues in accounting-related flows, point of sale, online payments, email templates, and website donations to improve reliability and avoid errors in everyday use.
Original PR description
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 update improves the way return-related reporting items are displayed and checked, making the workflow clearer for users. It also updates several country-specific reporting modules so return handling stays consistent across localized reports.
Original PR description
This update makes embedded content inside the editor work more reliably, especially for components with editable areas. It also adds a way for actions to run right after an embedded component finishes loading, which helps keep inserted content behaving correctly.
Original PR description
### Automatically preserve selection in editable descendants Prior to this work, to make use of the automatic selection restoration feature hidden in `useEditableDescendants` hook for editable…
### Automatically preserve selection in editable descendants Prior to this work, to make use of the automatic selection restoration feature hidden in `useEditableDescendants` hook for editable descendants of embedded components, one had to define a new env property: `editorShared` and populate it with the selection plugin shared functions. This process was pretty obscure and is always the same, therefore it makes a lot more sense to automatically populate the `env` with the selection shared functions. This work refines the concept of `env.editorShared`: it is now always present in the `env` of embedded components that are inside an editor, and can be populated using the `mount_component_handlers` resource. The idea is that a plugin can assign some of its dependencies in that shared Object for its related embedded components. Embedded components using editable descendants will now always have the `selection` plugin shared functions in `env.editorShared.selection`. ### Introduce renderBlueprintToElement Prior to this work, it was pretty difficult to execute an operation in a Plugin related to an embedded Component after inserting the blueprint, because the Plugin has no way of knowing when the embedded component finishes its async mount operation. This work introduces a new shared function `renderBlueprintToElement`, which allows one to define a callback (associated with the rendered blueprint) which will be executed after the first mount of its related embedded component when it was just inserted in the DOM. That function will not be executed if the blueprint is removed from the DOM before the first mount nor if the component is mounted again afterwards. task-5189453
task-5155703