Daily updates from Odoo
Tuesday, October 14, 2025
5 changes · 18.0
Enhancements to existing features
Opening the Point of Sale configuration page on tablets and phones no longer automatically brings up the on-screen keyboard. This makes navigation smoother by preventing an unwanted keyboard pop-up when users simply want to view or select a POS configuration.
Original PR description
Task: [#5016943](https://www.odoo.com/odoo/project/1737/tasks/5016943)
---
On tablets and phones, the search bar was autofocus when opening the POS config kanban view. This was causing the keyboard to open automatically, which was not a good user experience.
Now the search bar is not autofocus on touch devices for the POS config kanban view ('view_pos_config_kanban').The POS booking screen no longer automatically opens the device keyboard on tablets and phones. This makes the booking flow smoother for staff using touch devices by avoiding an unwanted interruption when the screen loads.
Original PR description
Task: [#5016943](https://www.odoo.com/odoo/project/1737/tasks/5016943) --- On tablets and phones, the search bar was autofocus when opening the booking screen in the POS frontend. This was causing the keyboard to open automatically, which was not a good user experience. Now the search bar is not autofocus on touch devices for the booking screen by creating a new controller to manage this.
A new automated test was added to confirm that matching India tax configurations produce equal tax amounts. This helps reduce the risk of future tax calculation regressions in accounting scenarios.
Original PR description
Added a missing test case in India tax computation, where both taxes have the same configuration as below: - amount: same for both taxes - price_include: True - include_base_amount: True - is_base_affected: False In this case, both tax amounts should be equal. This commit ensures that scenario is properly covered in the test suite.
Updates Odoo's point of sale and related event/customer display flows so local IoT device connections continue to work as Chrome introduces stricter local network access rules. This helps avoid disruption for businesses using IoT hardware such as printers or displays from secure browser sessions.
Original PR description
Enterprise PR: https://github.com/odoo/enterprise/pull/96850 Local Network Access restrictions will start shipping by default in Chrome 142. As part of this change, local requests will be allowed to use HTTP in an HTTPS context (gated by a browser permission prompt). This will work automatically when the IP is provided directly, however in the case of IoT we often use the odoo-iot DNS domain to resolve the IP. In this case, you must specify the option `targetAddressSpace: "local"` in the `fetch` request. This commit simply adds this change where appropriate. task-5157145 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#231014
This update prepares Odoo IoT and Point of Sale IoT connections for upcoming Chrome browser changes. It helps ensure local IoT devices can still be reached reliably when users access Odoo over HTTPS.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/231014 Local Network Access restrictions will start shipping by default in Chrome 142. As part of this change, local requests will be allowed to use HTTP in an HTTPS context (gated by a browser permission prompt). This will work automatically when the IP is provided directly, however in the case of IoT we often use the odoo-iot DNS domain to resolve the IP. In this case, you must specify the option `targetAddressSpace: "local"` in the `fetch` request. This PR simply adds this change where appropriate. As part of this we have also backported the change from jquery -> fetch. task-5157145 Forward-Port-Of: odoo/enterprise#96850