### Adjust `oi-stack-*` icons
Since the introduction of the new Material Icons library, we also introduced the `oi-stack-*` classes to allow stacking multiple icons.
Prior to this PR, the vertical alignment was incorrect when stacking a 1x icon with a 2x icon.
This commit adjusts the vertical alignment to ensure that stacked icons are properly aligned.

### Adapt drop zone layout
Prior to this PR, there was a layout issue where the upload icon was positioned on top of the drop zone, making the content difficult to read.
This PR adjusts the icon position and fine-tunes the layout to better match the new Frost design.

task-6591717

---

Example using 
```xml
<div class="oi-stack oi-4x">
   <i class="oi oi-stack-2x" data-icon="circle"></i>
   <i class="oi oi-stack-1x" data-icon="star"></i>
</div>
```

| Before | After |
|--------|--------|
| <img width="149" height="141" alt="Screenshot 2026-09-23 at 09 00 00" src="https://github.com/user-attachments/assets/9d343dc5-6f83-4f1e-8548-47cfec00272a" /> | <img width="146" height="142" alt="Screenshot 2026-09-23 at 09 00 25" src="https://github.com/user-attachments/assets/c67fdc1d-d29f-494d-9646-04014bd68d8f" /> |

Adapt drop zone layout
| Before | After |
|--------|--------|
| <img width="1668" height="698" alt="Screenshot 2026-09-23 at 08 51 30" src="https://github.com/user-attachments/assets/d92d5aee-9046-4a35-892e-ba11994d8e4b" /> | <img width="1671" height="698" alt="Screenshot 2026-09-23 at 08 51 22" src="https://github.com/user-attachments/assets/532a0625-5f04-4a52-a113-442ad3c58357" /> |







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

Forward-Port-Of: odoo/odoo#289893

Steps to reproduce:
1. Install Sign.
2. Open the form view of a document.
3. Select a model in the "Link to" (Reference) field, but leave the record empty.
4. Save and refresh the page.

Issue:
- After refreshing, the selected model is cleared because the reference value is invalid.

Cause:
- A reference field is only valid when it contains both a model and a record ID. However, the record selector has no placeholder, making it easy to overlook and save an incomplete value.

Solution:
- Add a default placeholder to the record selector of reference fields to make it more visible.

<table>
  <tr>
    <th>Before</th>
  </tr>
  <tr>
    <td>
      <img src="https://github.com/user-attachments/assets/3ba34b77-f901-4d3e-9768-5acaf2e673b8" alt="Before" width="100%">
    </td>
  </tr>
  <tr>
    <th>After</th>
  </tr>
  <tr>
    <td>
      <img src="https://github.com/user-attachments/assets/1fe54b89-221f-4d28-bd2b-0a3c706d5746" alt="After" width="100%">
    </td>
  </tr>
</table>


opw-6426339

Forward-Port-Of: odoo/odoo#280266

### Steps to Reproduce:
1. Go to Sales > Products and select a product
2. Upload an image for the product
3. Go to Settings > Technical > Attachments
4. Click on one of the image attachments
5. Observe the Client Error: "Uncaught Promise > Invalid props for
component 'Many2One': 'domain' is not a function"

### Issue:
In `attachment_patch.js`, the domain for the `Many2OneReferenceField` is overridden when an attachment is linked to another attachment. The patch calculates the domain and incorrectly assigns a static Array (using `.toList()`) to `props.domain`. In Odoo 19, the `Many2One` component enforces strict prop validation (caught when Owl's debug mode is enabled during testing), causing a crash because it expects the domain prop to be a function.

### Solution:
We can just wrap the resulting domain Array in an arrow function so that it evaluates dynamically when the `Many2One` component mounts. Also added a unit test to explicitly cover this patched scenario. The test manually applies a local patch to `Many2OneReferenceField.prototype` to accurately replicate the environment and verify the fix.

opw-6563954

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

Forward-Port-Of: odoo/odoo#289772
Forward-Port-Of: odoo/odoo#287951

Currently, an error occurs when a user opens the website and Live Chat is initialized with an invalid URL regex.

Steps to Reproduce:
 - Install `website_livechat` without demo data.
 - Open `Live Chat` and, in the `YourWebsite.com` channel, click the 
   `three-dot` menu and select `Configure Channel`.
 - Go to the `Rules` tab.
 - Add a rule, select `Welcome Bot` in `Chatbot`, and set an invalid regex such as 
   `*` in `URL Regex` and save.
- Click `Join Channel`.
- Open the `website`.

`re.PatternError: nothing to repeat at position 0
when serializing dict item 'result'
`
 - when `URL Regex is '['`

`re.error: unterminated character set at position 0 when serializing dict item 'result'`

When a user opens the website, Live Chat is initialized by checking operator availability and 
finding the matching country/URL rule [1]. The rule matching checks whether `regex_url` matches 
the current page URL. It uses `re.search()` [2], which compiles the regex pattern before searching. 
If `regex_url` contains an invalid pattern such as `*`, `re.search()` raises `nothing to repeat at position 0` 
because `*` must follow a preceding regex element. Similarly, `[` starts a character set (`[...]`) 
but has no closing `]`, causing `unterminated character set at position 0`.

This commit adds a constraint to validate `regex_url` and reject invalid regex patterns 
when creating or updating Live Chat rules.

[1]- https://github.com/odoo/odoo/blob/f962f1eccecfdbc95375f795174c8f687459b521/addons/im_livechat/controllers/main.py#L87

[2]- https://github.com/odoo/odoo/blob/f962f1eccecfdbc95375f795174c8f687459b521/addons/im_livechat/models/im_livechat_channel.py#L387

sentry-7679767396


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

Forward-Port-Of: odoo/odoo#283545

Problem:
When a link's metadata contains whitespace-only strings for `og_title`, `og_description`, or `og_image` (e.g. `og_title: "   "`), the link popover displays an empty clickable preview area.

Cause:
`LinkPopover` assigned raw metadata values directly. Non-empty whitespace strings evaluate to truthy values in JavaScript (`"   "` is truthy), preventing fallback to the default URL or empty string.

Solution:
Trim the metadata values (`og_title`, `og_description`, `og_image`) when populating state so that whitespace-only values evaluate to empty strings and trigger appropriate fallbacks.

Steps to reproduce:
- Open HTML editor.
- Add a link with URL `https://netorg4182089.sharepoint.com/:v:/s/projects/IQD72ajP3WOBT4jcAu_1qLfIAamL9lvrq4ls1Bs9XCyXJvw?e=vQ9wH3`.
- Open the link popover. => Observe that the popover title falls back to the URL instead of showing an empty clickable space.

opw-6564118

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

Forward-Port-Of: odoo/odoo#288188

**Steps to reproduce:**
- Receive a mail with an embedded code block
- Open a chatter containing this message
- Error: "Cannot mount a component on a detached dom node"

**Issue:**
Mail message are rendered with a shadow dom body and isolated from surrounding styling.
```xml
<div class="o-mail-Message-shadowBody overflow-x-auto" t-if="this.message.message_type and this.message.message_type.includes('email')" t-custom-ref="shadowBody"/>
```
Then in `useLayoutEffect` parent element is created for the shadow root and the message body is created:
```js
const bodyEl = createElementWithContent(
    "span",
    this.message.showTranslation
        ? this.message.richTranslationValue
        : this.props.messageSearch?.highlight(this.message.richBody) ??
                this.message.richBody
);
const roots = this.prepareMessageBody(bodyEl) ?? [];
this.shadowRoot.appendChild(bodyEl);
```
But after [1] we have `return this.renderEmbeddedCodeBlocks(bodyEl);` which calls:
```js
const { root, mountPromise } = mountComponent(...);
```
And root creation fails as the element is not on the shadow root yet (due to `validateTarget` and `isAttachedToDocument`).
```js
const root = app.createRoot(Component, { props, env });
```

But even if we have the element directly added on the `shadowRoot` the highlighting styling won't be applied properly without all the needed assets.

**Fix:**
Prevent `ReadonlySyntaxHighlightingComponent` for incoming email body.

Doesn't seem worth to try to load the needed css/style elements in the shadow root.

[1] https://github.com/odoo/odoo/commit/8fa3cc31e8b81645d40b5d09c925b57d2c0558ab

opw-6463735

Forward-Port-Of: odoo/odoo#288136
Forward-Port-Of: odoo/odoo#287977

eproduction steps:
 - MRP subcontracting + purchase
 - Subcontracted product with BOM
 - Create PO with a qty > 1 for this product
 - Go into barcode
 - Scan > 0 and < all of the expected quantity
 - Back out of barcode
 - Click validate -> Error **OR** Go back into barcode, attempt to validate -> Error

Added the StockMove and StockPicking classes to stock_barcode_mrp_subcontracting
to extend functions `_subcontracted_produce`, `_clean_merged`, and `split_uncompleted_moves`
to use a new context flag, `keep_subcontract_production`. When this flag
is set, the move Barcode creates from the split keeps the MO of the move
it was split from rather than splitting the MO in two, gives that link up
before it is merged away so its cancellation does not cancel the MO, and
the MO quantity is resynced with the merged move afterwards.

Error thrown here:
https://github.com/odoo/odoo/blob/f84eeb3ed1421e0cc07c906ff6444734dc01d35f/addons/mrp_subcontracting/models/stock_move.py#L248

opw-6428928

Forward-Port-Of: odoo/enterprise#131459

https://github.com/odoo/enterprise/commit/11cd136b2d222fd53dfeb07a611e14d14918009f introduced a margin to prevent Kanban cards from being too close to the top banner.
Commit https://github.com/odoo/enterprise/commit/c33e82717c4862a32f1feadd9d333f7237c59103 unintentionally removed this margin.
This commit restores the missing margin in BarcodeView.

| Before | After |
|--------|--------|
| <img width="1277" height="465" alt="Screenshot 2026-09-22 at 16 25 13" src="https://github.com/user-attachments/assets/9917112b-d503-432f-95f0-aec14033c10d" /> | <img width="1279" height="460" alt="Screenshot 2026-09-22 at 16 24 42" src="https://github.com/user-attachments/assets/80de37dd-500f-45f1-9720-118a6d991836" /> |
| <img width="1281" height="610" alt="Screenshot 2026-09-22 at 16 25 15" src="https://github.com/user-attachments/assets/e0c67c37-367b-4bcb-a451-6edbb91e4fd2" /> | <img width="1279" height="559" alt="Screenshot 2026-09-22 at 16 24 51" src="https://github.com/user-attachments/assets/dc550a73-0c33-404c-9d18-8d06d3d2d8f8" /> |

Forward-Port-Of: odoo/enterprise#132612

Circular 99/2025/TT-BTC (effective FY2026) replaces Circular
200/2014/TT-BTC. The Profit & Loss statement (Mẫu B02-DN) gains a
new mandatory line, "Lãi/lỗ của hoạt động bán, thanh lý bất động sản
đầu tư" (mã số 21), computed from the new 5117/6327 sub-accounts
(see the paired l10n_vn commit). Financial income, financial
expenses and the interest memo line shift to mã số 22/23/24
accordingly, the "Net profit from operating activities" formula is
updated to include the new line, and all following line
numbers/labels are renumbered to match the printed form. The
interest memo line itself is renamed from "Chi phí lãi vay" to
"Chi phí đi vay" (Borrowing costs), per the gazette text.

Also, per revised guidance:
- Revenue and cost of goods sold now exclude the new investment
  property sub-accounts (5117/6327), so those amounts aren't
  double-counted between the main lines and the new gain/loss line.
- Other income is now computed from the "income_other" account type
  instead of a hardcoded account code, matching how the chart of
  accounts already classifies it.

Both the Balance Sheet and Profit and Loss VN reports also declare
an extra "Code" string column (for the printed-form mã số) alongside
"Balance". Core's growth-comparison heuristic only turns on the auto
growth-% column when there are exactly 2 total columns; with
Code+Balance that becomes 4 once a comparison period is added, so
the % never renders even though the underlying side-by-side
comparison values are fine. account.report exposes
filter_growth_comparison as a toggle independent from
filter_period_comparison for exactly this case (see Trial Balance
and the Deferred reports), so both reports set it to False: period
comparison stays available, only the auto growth-% column is
suppressed.

Task-6518304

Forward-Port-Of: odoo/enterprise#132715
Forward-Port-Of: odoo/enterprise#131085

Steps to reproduce:
- Ecuadorian company, PoS with a preparation printer (or use the "Back" button on the feedback screen)
- Open a session, add a product, go to the payment screen
- Select a customer, uncheck "Invoice", pay in cash and validate

Issue:
An invoice is created and sent to the SRI although "Invoice" was unchecked.

Cause:
l10n_ec_edi_pos patches PosOrder.setup() to force to_invoice = true. setup() runs not only on creation but every time the record is reloaded from the server, so the sync done at validation flips the flag back to true in the browser. Since the paid order can now be re-synced after validation (kitchen printer, "Back" on the feedback screen), the server processes it in process_saved_payments, writes to_invoice = True and generates the invoice.

Fix:
Only apply the Ecuadorian default when the loaded values carry no to_invoice, i.e. for a newly created order. Reloaded records keep the value the user chose.

opw-6572987

Forward-Port-Of: odoo/enterprise#131612

[FIX] ai_website: save custom css scoped

Before this commit, if you had multiple websites, AI wouldn't save
custom css in the correct website's bundles, which caused the following
broken flow:
- open css editor, make any changes, and save it
- open the AI website builder agent and ask it to make all buttons red,
  writing a custom css for that

=> you get a traceback, and after reloading your website is broken.

Note that this isn't an issue in 20.0 as this behavior has been changed.

Related to task-6578231

---

 [FIX] ai_website: validate custom SCSS with bundle url rewriting

When AI used url($var) in scss, it would break the style compilation and
display an error. This happened because compiling replaced relative urls
with the absolute path. It wasn't caught before saving the custom css,
because we preprocessed css content inline, which doesn't rewrite
relative url()s.

To directly check it, you can just ask it to save this custom css:
`'$img: "a.png"; #test { background: url($img); }'`
=> Style compilation will fail.

Also, this commit updates some already present nested `with` statements
in tests to remove Ruff warnings.

task-6578231

Forward-Port-Of: odoo/enterprise#132463
Forward-Port-Of: odoo/enterprise#131954

**Steps to reproduce:**
- Install Appointment app
- Create an appointment type based on resources, auto-assigned, with two shareable resources linked together
- Set the first resource's capacity to 3 and the second resource's capacity to 4
- From the backend Gantt view, create a booking for 2 people on the first resource
- Create a second booking for 2 people on the same resource, at the same date and time
- First resource is now overbooked with reserved capacity of 4 out of 3
- Try to create an appointment from the website
- Error: "The capacity reserved should be positive."

**Issue:**
When bookings are created from the backend gantt view, the selected resource can be overbooked even if another linked resource still has available capacity.

Then when trying to book an appointment the new booking lines will trigger this constraint:
```py
_check_capacity_reserved = models.Constraint(
    'CHECK(capacity_reserved >= 0)',
    "The capacity reserved should be positive.",
)
```
This is caused by the negative values in:
```py
booking_line_values = []
if appointment_type.schedule_based_on == 'resources':
    capacity_to_assign = asked_capacity
    for resource in resources:
        resource_remaining_capacity = resources_remaining_capacity.get(resource)
        new_capacity_reserved = min(resource_remaining_capacity, capacity_to_assign, resource.capacity)
        capacity_to_assign -= new_capacity_reserved
        booking_line_values.append({
            'appointment_resource_id': resource.id,
            'capacity_reserved': new_capacity_reserved,
            'capacity_used': new_capacity_reserved if resource.shareable and appointment_type.resource_manage_capacity else resource.capacity,
        })
```

**Fix:**
Avoid negative remaining value in resource booking when computing available slots.

Note: Tried to take the capacity already used by overlapping bookings into account when assigning resource booking lines from the backend gantt view. And also force linked_resources booking when trying to book more
than the total capacity to properly dispatch as many slots as possible. But it was breaking `appointment_google_reserve` tests.

opw-6503147

Forward-Port-Of: odoo/enterprise#132484
Forward-Port-Of: odoo/enterprise#130520

Issue Before This Commit:
=========================
Currently, the Purchase Order Line field on the vendor bill line allows users to 
select purchase order lines regardless of the purchase order state. As a result,
lines from purchase orders that are not confirmed can also be selected and 
linked to vendor bill lines.

Steps to Reproduce:
===================
- Install Purchase and create an RFQ.
- Create a vendor bill for the same vendor.
- Add a bill line and enable the Purchase Order column.
- Open the dropdown of the Purchase Order Line field.
- Observe that lines from unconfirmed purchase orders are available
  for selection.

Cause of the Issue:
====================
This [PR](https://github.com/odoo/odoo/pull/266003) made Purchase Order lines selectable directly on bill lines, 
but the selection domain did not restrict the lines to confirmed purchase orders. 
Therefore, lines from unconfirmed purchase orders remained available for selection.

After This Commit:
==================
Only Purchase Order lines from confirmed purchase orders are selectable
on vendor bill lines.

Forward-Port-Of: odoo/odoo#288858

When a translatable field is displayed in the multi create popover (e.g. in a calendar view with a `multi_create_view`), the rendering of the popover crashes when the props are validated (in debug mode) with "Invalid component props (TranslationButton)", `resId` being reported as a missing key of the `record` prop.

The `TranslationButton` indeed requires a `resId` on the record it receives, which must be `false` when the record doesn't exist yet. The record of the popover is produced by the `Record` component (`@web/model/record`), which forwards its `resId` prop as is to the config of the standalone model. As no `resId` is given for that new record, the datapoint ends up with an `undefined` `resId`, which is considered as a missing prop by the props validation.

Normalize the `resId` in the model, such that a mono record config always has a `resId`, which is `false` when the record is new, as the `FormController` and the datapoints created by the lists already do. `_getNextConfig` is the single entry point of every load, so every root datapoint is covered, whatever the caller.

The next props are normalized as well in the `Record` component, otherwise each re-render of the parent would trigger a useless reload (`undefined !== false`).

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

Forward-Port-Of: odoo/odoo#289585

Steps to reproduce:
--------------------------------------
1. Install the mail module
2. Allow push notification permissions from the site settings
3. Open Discuss > Go to Channels
4. Click Join on a channel where the current user is not a member

Observation:
--------------------------------------
The current user receives a push notification saying: 'User has invited you to this channel.'

This is incorrect; the user joined voluntarily. Nobody invited them

Issue:
--------------------------------------
The commit https://github.com/odoo/odoo/pull/255052/changes/cddd9491c28e9c949efb24d2330c58e35144af12 Adds a push notification when a user is invited to a channel

`_add_members` creates the new member and sends a push notification to all newly added members' partner IDs without checking whether a member joined by themselves or was invited by someone else.

https://github.com/odoo/odoo/blob/e9cfa0fd65d234bcff8130a2c790cd80ee443595/addons/mail/models/discuss/discuss_channel.py#L830-L853

Interestingly, the bus notification code just a few lines above already makes this distinction using `member.is_self` but the web push block doesn't apply the same filter.

https://github.com/odoo/odoo/blob/e9cfa0fd65d234bcff8130a2c790cd80ee443595/addons/mail/models/discuss/discuss_channel.py#L810-L811

Solution:
--------------------------------------
Filter out self-joined members from the web push notification recipients. The push notification should only target members who were invited.

OPW-6527691

Forward-Port-Of: odoo/odoo#289796
Forward-Port-Of: odoo/odoo#286421

Issue Before this Commit:
=====================
Clicking on the rescheduling popover widget on the picking form leads to a page
crash.

Steps to Reproduce:
=====================
1. Install the `stock` module.
2. Create a storable product, then create a delivery order for it
3. Create a receipt for the same product, and `set its Scheduled Date to a date later than the delivery order's Scheduled Date`.
4. Open the Allocation Report from the receipt and assign the received quantity to the delivery order.
5. Open the delivery order and click the Danger icon next to the Scheduled Date. Observe that the page crashes with the following error:
`Uncaught Promise > Invalid loop expression: "undefined" is not iterable`

Cause of the Issue:
=====================
The `late_elements` is not defined in `useProps` of
`StockRescheculingPopoverComponent`, even though it was used by the
`stock.PopoverStockRescheduling` template. As a result, the template tried to
iterate over `undefined`, leading to a page crash.

After this Commit:
=====================
This commit defines the `late_elements` and `delay_alert_date` in useProps so
that the values are correctly available in the component and the rescheduling
popover renders without crashing.

Forward-Port-Of: odoo/odoo#288895

Step to reproduce:
------------------
- Install `pos_sale_stock` and `mrp` module.
- Go to the setting enable "Replenish on Order (MTO)"
- Create a storable product with the MTO route
- Create a Bill of Materials for the product with a storable component
- Now Create Sale order for the Product and confirm it.
- Open POS Store and settel Created sale order.
- Process toward payment and try to validate it.

Issue:
------

`AssertionError: Invalid falsy real id`

Cause:
------
When an MTO product with a manufacturing Bill of Materials is added to a Sale Order and the SO is confirmed, Odoo creates two distinct sets of stock.move records that share the same stock.reference group:

1. **Delivery moves** (picking_id → stock.picking) Created by the outgoing stock rule triggered by the MTO route. These moves are assigned to a delivery picking and have a valid picking_id.

2. **Manufacturing component moves** (picking_id = False) Created by the Manufacture route's procurement rule, which spawns an mrp.production. The raw-material moves inside an MO belong to the production order, not to any stock.picking. Their picking_id field is intentionally False by design.

Both sets of moves are linked to the same stock.reference record through the stock_reference_move_rel many2many table. This means that traversing:

    so_line.move_ids          → delivery move(s)
    .reference_ids            → shared stock.reference
    .move_ids                 → ALL moves in the group (delivery + MRP)

every move in the reference group, including MRP component moves whose picking_id is False.

- Then In PosOrder.sync_from_ui(), the code collected the IDs of all related pickings into a set for later cancellation:

https://github.com/odoo/odoo/blob/a0cdf9c33ed464b4ec8bd520e4d0523afb8dbd28/addons/pos_sale/models/pos_order.py#L111

https://github.com/odoo/odoo/blob/a0cdf9c33ed464b4ec8bd520e4d0523afb8dbd28/addons/pos_sale/models/pos_order.py#L130-L133

        waiting_picking_ids.add(move.picking_id.id)   # ← adds False for MRP moves

Because MRP moves pass the state filter ('confirmed') but have picking_id = False, `move.picking_id.id` evaluates to False (the empty recordset's falsy id), which was silently added to the waiting_picking_ids set.

Issue occur from this [commit](https://github.com/odoo/odoo/commit/515eb5ba0892a759dde32a9b2923d8ecc1e4bf74?debug=1), the ORM assertion in browse() rejects falsy IDs:

https://github.com/odoo/odoo/blob/a0cdf9c33ed464b4ec8bd520e4d0523afb8dbd28/addons/pos_sale/models/pos_order.py#L139

https://github.com/odoo/odoo/blob/9e02922f821a3b4e891e90bf9bd18448a08e66fa/odoo/orm/models.py#L5297

Fix:
---
Add guards in `sync_from_ui()`
*Inner filtered() guard* — add `m.picking_id` as the first condition so
   that MRP component moves (picking_id = False) are never iterated, preventing
   `False` from ever entering the set

---

opw-6486681

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

Forward-Port-Of: odoo/odoo#289890
Forward-Port-Of: odoo/odoo#284103