When buying a gift card from a POS, the gift card is created without a partner. This is an issue for users who want to see who bought a specific gift card.

In [`pos_loyalty/models/pos_order.py`](https://github.com/odoo/odoo/blob/0bf53e6b2ab8c4c1705ebbb776102d493ac7445c/addons/pos_loyalty/models/pos_order.py), the `coupon_data` passed to the `confirm_coupon_programs` method does not contain the `partner_id`. This happens because the *Gift Card* program is not considered "nominative", failing the following condition from `pos_loyalty/static/src/overrides/models/pos_store.js`:

https://github.com/odoo/odoo/blob/0bf53e6b2ab8c4c1705ebbb776102d493ac7445c/addons/pos_loyalty/static/src/overrides/models/pos_store.js#L795-L801

In fact, the conditions for nominative programs are defined in the `loyalty` module:

https://github.com/odoo/odoo/blob/0bf53e6b2ab8c4c1705ebbb776102d493ac7445c/addons/loyalty/models/loyalty_program.py#L196-L200

This fix uses the customer's id when there's no `partner_id` in the `coupon_data` coming from the Javascript side. If there's no customer selected when buying the gift card from the POS, `self.partner_id.id` evaluates to `False`, leading to the original behavior: a gift card with no partner.

### Steps to reproduce:
1. Install Point of Sale (`point_of_sale`)
2. In Settings > Point of Sale, toggle *Promotions, Coupons, Gift Card & Loyalty Program*
3. In the POS, open a register
4. On the product screen, select the *"Gift Card"* product and click *Payment*
5. On the payment screen, set the Customer to any customer, pay, and click *Validate*
6. In the POS backend, go to Products > Gift cards & eWallet, click the *Gift Cards* program, and click the *Gift Cards (1)* smart button
7. The gift card we just sold in the POS appears in the list, but there's no Partner assigned to it.

opw-5261991

Forward-Port-Of: odoo/odoo#237807

**Description of the issue/feature this PR addresses:**
----------------------------------------------
In saas-18.2, the unread message separator can visually overlap with the
message jump/highlight animation when navigating to unread messages.
This issue was not present in 18.0 and results from reduced vertical spacing
between the unread separator and the first unread message.

**Current behavior before PR:**
----------------------------------------------
- Clicking the “X new messages” banner triggers a jump highlight animation
- The highlighted message overlaps the unread red separator line
- The separator becomes partially or fully obscured during the animation

**Desired behavior after PR is merged:**
----------------------------------------------
- The unread separator remains clearly visible during message jump/highlight
- No overlap occurs between the separator and the highlighted message
- Highlight animation behavior remains unchanged
- Visual behavior matches the stable experience observed in 18.0

This PR restores sufficient vertical spacing for the unread separator line,
preventing overlap without altering message animation or interaction logic.

Task-5420965

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

Steps to reproduce:
===================
-  Add a product categories block with a search bar in the inner content of the block, like "s_product_list".
- Drag a "Search" snippet inside of the block in top of products categories
- Change the layout to "Grid" & Save.
- Type in the search bar to trigger autocomplete suggestions. -> The suggestions appear behind the product categories and are not visible.

Cause:
======
When a searchbar snippet is placed inside a section using grid mode, the autocomplete dropdown was hidden behind sibling grid items. This occurred because the grid layout applies inline z-index to each column (via `_placeColumns` `in grid_layout_utils.js` (See [1])), creating stacking contexts that trapped the dropdown.
So once you change to grid mode layout `_toggleGridMode` function will be triggered which will call  `_placeColumns` that will assign z-index; (See [2])

Solution:
=========
Override the inline z-index on grid items containing a searchbar

[1]: https://github.com/odoo/odoo/blob/d4411c27b469e5dcc526b5b1f8ea4498f2b08567/addons/web_editor/static/src/js/common/grid_layout_utils.js#L225

[2]: https://github.com/odoo/odoo/blob/d4411c27b469e5dcc526b5b1f8ea4498f2b08567/addons/web_editor/static/src/js/common/grid_layout_utils.js#L138

opw-5392011

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

Forward-Port-Of: odoo/odoo#239607

Tour "knowledge_calendar_command_tour" fails since Chrome 143 with an error "Cannot read properties of null (reading 'querySelectorAll')".

This is due to the fix in Chromium "Fix target/relatedTarget clearing logic during dispatch" [^1] introduced in Chrome 143, to actually match the spec [^2].

To quote the Chromium commit message:
> According to the spec, only if the top node is in a shadow tree, both
> the target and relatedTarget should be cleared.
> However, if the top node is not in a shadow tree and not a document,
> the target and relatedTarget are always cleared. Because the current
> implementation only checks whether the top node is not a document.
> So, this patch fixes the bug by checking whether the top node is in a
> shadow tree.

In practice, this means that events are now properly dispatched when the FullCalendar container's element is not connected to the document but still to the shadow tree. As a result, the OWL reference to this container can not exist anymore when the event handler is called but FullCalendar's API still has the right reference to this element.

Note: Firefox and Safari already implemented the spec properly (aka. it was already broken for them...)

[^1]: https://chromium.googlesource.com/chromium/src/+/63178146cd776eae2b466983f0835e86c314d051%5E%21/
[^2]: https://dom.spec.whatwg.org/#concept-event-dispatch

Forward-Port-Of: odoo/odoo#240920

Currently an error occurs when user tries to remove end date on slot.

Steps to replicate:
- Install `planning`.
- Create a new planning slot and click on a slot template at the top.
- Remove the end date (rightmost) and click elsewhere.

Error:
```
 File /home/odoo/odoo18/enterprise/planning/models/planning.py, line 423, in _compute_template_id
    if slot._different_than_template():
 File /home/odoo/odoo18/enterprise/planning/models/planning.py, line 439, in _different_than_template
    slot_time = self[slot_field].astimezone(pytz.timezone(self._get_tz()))
AttributeError: 'bool' object has no attribute 'astimezone'
```
Cause:
- When the end date was removed, [compute] was triggered, calling the `_different_than_template()` method, which iterates through the fields in the slot template.
- Since the user removed `end_datetime`, `self['end_datetime']` became false and caused the error at line [1].

Solution:
- Returned from the function call when `end_datetime` is false.

[compute]: https://github.com/odoo/enterprise/blob/745c1cc0e06f5e0578ec4383439f8be2419adb6b/planning/models/planning.py#L418-L426

[1]: https://github.com/odoo/enterprise/blob/745c1cc0e06f5e0578ec4383439f8be2419adb6b/planning/models/planning.py#L438

No ID

Forward-Port-Of: odoo/enterprise#102762