Sunday, September 20, 2026
3 changes · saas-19.4
Resolved issues and error corrections
Users adding reactions in Discuss can now hold Shift when choosing an emoji from the quick reaction menu to keep the picker open. This makes it easier to add multiple reactions in a row without repeatedly reopening the picker.
Original PR description
When adding a reaction to a message in Discuss, selecting an emoji adds the reaction and closes the emoji picker. This can be inconvenient when adding multiple reactions in a row, as the picker has to be reopened every time. To address this problem, the emoji picker remains open when the user holds Shift while selecting an emoji. However, this behavior was overlooked when implementing the Quick Reaction Menu, which therefore closes the emoji picker upon emoji selection, regardless of whether Shift is pressed. This commit fixes the Quick Reaction Menu so that holding Shift while selecting an emoji once again prevents the emoji picker from closing. [Task-6575382](https://www.odoo.com/odoo/project/1519/tasks/6575382) Forward-Port-Of: odoo/odoo#289352 Forward-Port-Of: odoo/odoo#288336
The attendance kiosk now shows the weekday in the same language as the rest of the interface. This avoids confusing mixed-language date displays for companies using Odoo in languages other than English.
Original PR description
Problem:
The weekday displayed in the attendance kiosk header is always shown in English, even when the comapany contact's language is changed.
This happens because `DateTime.toFormat("cccc")` uses Luxon's locale, but the `DateTime` instance is created without setting the current UI locale.
Steps to reproduce:
1. Install `hr_attendance`.
2. Change the company contact language to a language other than English (e.g. French).
3. Open the Kiosk Mode.
4. Observe that the date and UI are translated, but the weekday remains in English (e.g. "Monday" instead of "Lundi").
Fix:
Set the Luxon locale from the document language before formatting the weekday. This ensures `toFormat("cccc")` returns the weekday in the active Company contact language.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#289173
Forward-Port-Of: odoo/odoo#274655Color options without a manually selected color now appear consistently in the product configurator and Add to Cart popup. This prevents customers from seeing misleading gray swatches and makes product option selection clearer.
Original PR description
Issue: Color attribute values without an explicit html_color show correctly on the product page but render as a plain gray circle in the "Add to cart" popup / product configurator, even though selecting them still works. Steps to reproduce: 1. Create a Color attribute value without picking a color (leave the Color field unset) and add it to a published product. 2. Open the product page: the swatch shows fine. 3. Click Add to Cart to open the popup: the swatch is a plain gray circle instead. Cause: product_template_attribute_line.xml (sale.ptav_color) used `ptav.html_color` directly with no fallback, producing the invalid CSS "background-color:false" when html_color is unset. Fix: Apply the same `html_color or name` fallback in the configurator's color-swatch template. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#288582