Clicking a record in the Employee Skills pie chart report currently triggers a traceback.

Steps to reproduce the error:
- Install ``hr_skills`` module with demo data
- Open any employee > In Resume tab, Click on TIMELINE
- Switch to Pie chart > click on any record

Traceback:
```py
UndefinedColumn: column hr_employee_skill_history_report.id does not exist
LINE 1: SELECT "hr_employee_skill_history_report"."id" FROM "hr_empl...
```

``hr.employee.skill.history.report`` model is ``_auto=False``,
meaning that no database table is created for this model.
In earlier versions, clicking on the record opens the list view.
In the [commit](https://github.com/odoo/odoo/commit/341fe890d2b7001dab1e3cd65ecb0c3bb4ed327e), list view was removed.
So, now clicking on the record will lead to the above traceback.

[1]: https://github.com/odoo/odoo/commit/341fe890d2b7001dab1e3cd65ecb0c3bb4ed327e

sentry-7099766240

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

Forward-Port-Of: odoo/odoo#239416

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

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

**Description of the issue/feature this PR addresses:**
----------------------------------------------
Currently, when requesting microphone permission in video calls, the "Use microphone and camera" button is shown even though only microphone access is needed, or vice-versa. This creates confusion as users see an option to request permissions that aren't relevant to their current action.

**Current behavior before PR:**
----------------------------------------------
- When clicking the microphone button in a video call, the "Use microphone and camera" button is shown if camera permission is not explicitly denied.
- Users see permission options that don't match what they're actually trying to do (e.g., microphone button shows camera options).

**Desired behavior after PR is merged:**
----------------------------------------------
- The "Use microphone and camera" button is only shown when neither camera nor microphone permissions have been granted yet.
- When users click the microphone button, they only see microphone-related options unless they also need camera permissions.
- When users click the camera button, they only see camera-related options unless they also need microphone permissions.
- Permission dialogs are contextual and only show relevant options for the action being performed.

Task-5367786

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

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

An error occurs when a user with `Employee Management` rights, but without any appraisal rights, tries to open an employee’s appraisals.

**Steps to Reproduce:**
1) Install Appraisals App.(with Demo).
2) Log in as admin, open Marc Demo in Settings > Users & Companies > Users,
   and set `Employees: Officer (Manage all employees)` under HR section.
3) Log in as Marc Demo and open any employee profile (e.g., Anita Oliver).
 4) Click on `Appraisals smart button`.

**Error:**
`IndexError: tuple index out of range`

**Root Cause:**
When a user has only employee management rights, `self.appraisal_ids` received in the method at [1] becomes an empty tuple. Accessing `self.appraisal_ids[0].id` therefore raises an `IndexError`.

**FIX:**
If no `appraisal_ids` are available, return the list view of appraisals, matching the behavior from previous versions.

[1]- https://github.com/odoo/enterprise/blob/3ee1df0b806f9c73d79b8b55fcc7d55b530d9e6b/hr_appraisal/models/hr_employee.py#L169-L180

sentry-7032734789