Odoo Changelog — 2026-01-03

Saturday, January 3, 2026

4 changes · saas-19.1

Bug Fixes(4)

Resolved issues and error corrections

[FIX] website_forum: fix void description on post submission

PR #241930

Coresaas-19.1website_forum

This update resolves an issue where submitting a forum post with an empty description would cause a server error. The fix resets a key setting to prevent a problematic form submission process. Users can now successfully post questions with descriptions.

Original PR description

Steps to reproduce
===================
1. Go to Forum.
2. Select any forum and Click on New Post.
3. Add a title and keep description empty.
4. Post Your Question.
=> The title is marked as invalid.
5. Now add a description.
6. Post Your Question.
=> Error page: Bad Request
7. Go back or open any forum page
=> Will receive error on each page until you clear sessionStorage

Technical
============
The commit [1] updates the website forum interaction to use
the html_editor `Wysiwyg` instead of `loadWysiwygFromTextarea`.
The textarea is hidden and populated through `WebsiteForumWysiwyg`.

When the description is left empty and the form is submitted,
`WebsiteForumWysiwyg.onSubmitButtonClick` populates empty content
into the textarea, sets the `readyToSubmit` property to true, and
resubmits the form to trigger the interaction logic. The editor
container is then validated as empty, marked invalid, and the
submission is prevented.

After the description is refilled and the form is submitted again,
the `readyToSubmit` is already true, causing an early return from
`onSubmitButtonClick`. This skips populating the textarea from the
editor container. Since validation is performed against the editor
container, the form is submitted successfully.

As we use form action that relies on named inputs, including the hidden
textarea, the submitted payload contains an empty textarea value.
As a result, the request fails with a bad request error due to empty content.

[1] https://github.com/odoo/odoo/commit/6bd3d1b557f82475f0a78ef8ff0529528e5f2b29

After this commit
======================

This commit fix the issue by resetting `readyToSubmit` property to false.

Task-5400394

Forward-Port-Of: odoo/odoo#241544

#forum#post#error

[FIX] website_forum: fix forum post form validation

PR #241942

Coresaas-19.1website_forum

This update corrects a bug in the forum post form where fields were incorrectly marked as invalid, even after being filled in. The change, triggered by a refactoring of user interactions, now properly highlights invalid fields, ensuring users receive accurate feedback when creating forum posts. This improves the overall user experience and data integrity.

Original PR description

Steps to reproduce
===================
1. Go to Forum.
2. Select any forum and Click on New Post.
3. Add a title and keep description empty.
4. Post Your Question.
=> The title is marked as invalid.
6. Now add a description.
7. Post Your Question.
=> Both the title and description are marked as invalid, yet form is submitted successfully.

After commit [1], refactoring public widgets to Interactions, the `is-invalid` class toggle for forum post title and description used an incorrect condition, leading to improper highlighting of these fields.

[1] https://github.com/odoo/odoo/commit/22e777c046521f3f89b62caa5876680beb7f5aba

Task-5400394

Forward-Port-Of: odoo/odoo#241540

#forum#validation#user experience

[FIX] mail: jump to present not working in non-aside chatter

PR #241900

Coresaas-19.1mail

This update resolves an issue where the 'Jump to Present' button in non-aside chatters was unreliable, causing flickering and incorrect scrolling. By disabling a browser feature that interfered with scrolling, this fix ensures users can reliably access the latest messages in chatters.

Original PR description

**Description of the issue this PR addresses:**
------------------------------------------------
In non-aside chatter, the **Jump to Present** action did not work reliably. When users clicked it, the view flickered and the scroll position jumped back, preventing users from reaching the latest message.

This happened because the browser’s native scroll anchoring interfered with the scroll-to-bottom behavior when messages were reloaded.

**Current behavior before PR:**
---------------------------------
- In non-aside chatter, clicking **Jump to Present** caused flickering.
- The view jumped back instead of staying on the latest message.
- Users could not reliably reach the most recent messages.

**Desired behavior after PR is merged:**
-----------------------------------------
- Clicking **Jump to Present** in non-aside chatter scrolls directly to the
  latest message without flickering.
- The scroll position remains stable and does not jump back.
- The **Jump to Present** button works consistently.

**Task:** 5264332

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#240934

[FIX] point_of_sale: prevent leftpane from shrinking below its width

PR #241954

Coresaas-19.1point_of_sale

This update fixes an issue where the left pane in the Point of Sale interface was sometimes obscured by its right-hand content, making text difficult to read. The fix ensures the left pane maintains its intended width, improving the user experience. The problem was intermittent and resolved by adjusting the layout's flexibility.

Original PR description

In some scenarios, although not fully deterministic, the left pane is being pushed by its right pane sibling (i.e. the products grid), making it go below its specified with of `left-pane-width`, and making text non readable.

By setting `flex-shrink: 0` on this element, we tell the browser to respect the specified width, and not allow its siblings to shrink it.

We could have also set `min-width: $left-pane-width;`, but it's less descriptive. The problem happens because we are in a flex container, hencer we use `flex-shrink: 0`.

### Notes:
This issue only happened from time to time for the client, and it seems non deterministic. 
If we disable showing the product images, the issue stops happening.

The below before vs after screenshots are taken on MacBook Pro 14 inches.

### Before:
<img width="1493" height="868" alt="image" src="https://github.com/user-attachments/assets/70bc5a70-34a6-48c9-a60a-ab1de1fa0b9b" />

<img width="1496" height="867" alt="image" src="https://github.com/user-attachments/assets/e8ae9b25-3525-439b-93dd-18dc825613c7" />


### After:
<img width="1495" height="866" alt="Capture d’écran 2025-12-31 à 11 28 38" src="https://github.com/user-attachments/assets/23585d3d-b0bf-4316-8749-b39a56fc8cda" />

<img width="1497" height="866" alt="image" src="https://github.com/user-attachments/assets/f5654163-1dd3-4ff9-bb12-d8cd8fbc497b" />


opw-5392359

Forward-Port-Of: odoo/odoo#241941
Forward-Port-Of: odoo/odoo#241731

Steps to reproduce =================== 1. Go to Forum. 2. Select any forum and Click on New Post. 3. Add a title and keep description empty. 4. Post Your Question. => The title is marked as invalid. 5. Now add a description. 6. Post Your Question. => Error page: Bad Request 7. Go back or open any forum page => Will receive error on each page until you clear sessionStorage Technical ============ The commit [1] updates the website forum interaction to use the html_editor `Wysiwyg` instead of `loadWysiwygFromTextarea`. The textarea is hidden and populated through `WebsiteForumWysiwyg`. When the description is left empty and the form is submitted, `WebsiteForumWysiwyg.onSubmitButtonClick` populates empty content into the textarea, sets the `readyToSubmit` property to true, and resubmits the form to trigger the interaction logic. The editor container is then validated as empty, marked invalid, and the submission is prevented. After the description is refilled and the form is submitted again, the `readyToSubmit` is already true, causing an early return from `onSubmitButtonClick`. This skips populating the textarea from the editor container. Since validation is performed against the editor container, the form is submitted successfully. As we use form action that relies on named inputs, including the hidden textarea, the submitted payload contains an empty textarea value. As a result, the request fails with a bad request error due to empty content. [1] https://github.com/odoo/odoo/commit/6bd3d1b557f82475f0a78ef8ff0529528e5f2b29 After this commit ====================== This commit fix the issue by resetting `readyToSubmit` property to false. Task-5400394 Forward-Port-Of: odoo/odoo#241544

Steps to reproduce =================== 1. Go to Forum. 2. Select any forum and Click on New Post. 3. Add a title and keep description empty. 4. Post Your Question. => The title is marked as invalid. 6. Now add a description. 7. Post Your Question. => Both the title and description are marked as invalid, yet form is submitted successfully. After commit [1], refactoring public widgets to Interactions, the `is-invalid` class toggle for forum post title and description used an incorrect condition, leading to improper highlighting of these fields. [1] https://github.com/odoo/odoo/commit/22e777c046521f3f89b62caa5876680beb7f5aba Task-5400394 Forward-Port-Of: odoo/odoo#241540

**Description of the issue this PR addresses:** ------------------------------------------------ In non-aside chatter, the **Jump to Present** action did not work reliably. When users clicked it, the view flickered and the scroll position jumped back, preventing users from reaching the latest message. This happened because the browser’s native scroll anchoring interfered with the scroll-to-bottom behavior when messages were reloaded. **Current behavior before PR:** --------------------------------- - In non-aside chatter, clicking **Jump to Present** caused flickering. - The view jumped back instead of staying on the latest message. - Users could not reliably reach the most recent messages. **Desired behavior after PR is merged:** ----------------------------------------- - Clicking **Jump to Present** in non-aside chatter scrolls directly to the latest message without flickering. - The scroll position remains stable and does not jump back. - The **Jump to Present** button works consistently. **Task:** 5264332 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#240934

In some scenarios, although not fully deterministic, the left pane is being pushed by its right pane sibling (i.e. the products grid), making it go below its specified with of `left-pane-width`, and making text non readable. By setting `flex-shrink: 0` on this element, we tell the browser to respect the specified width, and not allow its siblings to shrink it. We could have also set `min-width: $left-pane-width;`, but it's less descriptive. The problem happens because we are in a flex container, hencer we use `flex-shrink: 0`. ### Notes: This issue only happened from time to time for the client, and it seems non deterministic. If we disable showing the product images, the issue stops happening. The below before vs after screenshots are taken on MacBook Pro 14 inches. ### Before: <img width="1493" height="868" alt="image" src="https://github.com/user-attachments/assets/70bc5a70-34a6-48c9-a60a-ab1de1fa0b9b" /> <img width="1496" height="867" alt="image" src="https://github.com/user-attachments/assets/e8ae9b25-3525-439b-93dd-18dc825613c7" /> ### After: <img width="1495" height="866" alt="Capture d’écran 2025-12-31 à 11 28 38" src="https://github.com/user-attachments/assets/23585d3d-b0bf-4316-8749-b39a56fc8cda" /> <img width="1497" height="866" alt="image" src="https://github.com/user-attachments/assets/f5654163-1dd3-4ff9-bb12-d8cd8fbc497b" /> opw-5392359 Forward-Port-Of: odoo/odoo#241941 Forward-Port-Of: odoo/odoo#241731