Thursday, July 29, 2021
3 changes · master
Resolved issues and error corrections
Odoo keyboard shortcuts now use the physical key being pressed instead of the character produced by the user's current keyboard layout. This means shortcuts such as Alt+S work consistently for users typing with non-Latin layouts, reducing frustration and layout switching.
Original PR description
Description of the issue/feature this PR addresses: When users work with odoo with local keyboard layout most of shortcuts don't work. This is happened because of hotkey_service uses `event.key` to…
Description of the issue/feature this PR addresses: When users work with odoo with local keyboard layout most of shortcuts don't work. This is happened because of hotkey_service uses `event.key` to determine shortcut. But with non-latin keyboard layout `event.key` is localized. Non-english users have to switch keyboard layout to english to use shortcut, then they have to switch back to enter text. It's annoying. Some users just think that shortcuts in odoo doesn't work at all because they use english layout very rarely. This PR changes hostkey_service so it uses `event.code` to determine pressed key. Current behavior before PR: With non-latin keyboard layout most of shotcuts don't work. F.x. `Alt+S` doesn't work for russian keyboard layout becase hotkey_service interprets this shortcut as `Alt+Ы`. Desired behavior after PR is merged: Shortcuts registered in hotkey_service don't depend on keyboard layout. So pressing `Alt+S` on any keyboard layout will trigger appropriate event listener. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures prices shown in the website shop autocomplete search appear as intended instead of displaying visible HTML formatting text. Customers see cleaner, correctly formatted price information while browsing products through search suggestions.
Original PR description
/shop/products/autocomplete return price already rendered with monetary
widget, so it is plain html like:
"$ <span class=\"oe_currency_value\">12.00</span>"
It need to be marked MarkupSafe to avoid the escaping.
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-prThe Analysis button is restored on worksheet template forms after it disappeared during a module restructuring. The change moves this behavior into the shared worksheet module so Field Service and Quality can both use it consistently.
Original PR description
Before this commit: The 'analysis' button is missing when going to field service > configuration > worksheet templates > open the form view This is happening after introducing the new worksheet module from industry_fsm_report to allow other modules to create their worksheet. see: 0324acc After this commit: The 'analysis' button will be displayed. Also, move that part in the worksheet module as we also want the 'analysis' button in Quality. Hence make it generic. Task-2555286