The popover was set to bg-100 during darkmode redesign but it creates more issue than having it at 300. The initial issue was the button light behavior inside popover, but setting it to 100 doesn't solve the button light and breaks the elevation. Steps to reproduce (any popover): - Apply the Dark Mode - Go in CRM app - Open a lead - Clic the cog in the control panel next to the breadcrumb - Select "Add Properties" (it opens the popover) task-3593302 Forward-Port-Of: odoo/enterpris

The popover was set to bg-100 during darkmode redesign but it creates
more issue than having it at 300. The initial issue was the button light
behavior inside popover, but setting it to 100 doesn't solve the button
light and breaks the elevation.

Steps to reproduce (any popover):
- Apply the Dark Mode
- Go in CRM app
- Open a lead
- Clic the cog in the control panel next to the breadcrumb
- Select "Add Properties" (it opens the popover)

task-3593302

Forward-Port-Of: odoo/enterprise#51664

There's no refresh when closing a MO on the 'All MO' tab of the shopfloor. Because of that, the MO fades away but the total count is still the same. This PR forces a refresh to make sure that the count is corresponding to the number of MOs shown. When marking a workorder as done with the timer running, the timer doesn't stop and the value registered contains the time it takes to fade away. E.g. if you mark a WO as done at 1 min 33 sec, the real duration registered will be around 1 min

There's no refresh when closing a MO on the 'All MO' tab of the shopfloor.
Because of that, the MO fades away but the total count is still the same.
This PR forces a refresh to make sure that the count is corresponding to
the number of MOs shown.

When marking a workorder as done with the timer running, the timer
doesn't stop and the value registered contains the time it takes to
fade away.
E.g. if you mark a WO as done at 1 min 33 sec, the real duration
registered will be around 1 min 36-37 sec.
This fix ensures the timer stop effectively and visually when closing
a WO.

Forward-Port-Of: odoo/enterprise#71548

Steps to reproduce: - Install subscription and pos_sale_subscription - Create a sale order with a recurring product (a subscription) - Settle the sale order in the point of sale - The date of the next invoice is not updated To fix this issue, when the pos_order is paid, we will update the next invoice date of all sale orders in lines that are of type subscription. opw-4072950 Forward-Port-Of: odoo/enterprise#71204

Steps to reproduce:
- Install subscription and pos_sale_subscription
- Create a sale order with a recurring product (a subscription)
- Settle the sale order in the point of sale
- The date of the next invoice is not updated

To fix this issue, when the pos_order is paid, we will update the next invoice date of all sale orders in lines that are of type subscription.

opw-4072950

Forward-Port-Of: odoo/enterprise#71204

**Steps to reproduce:** - Install Accounting and l10n_de_reports - Switch to a German company - Create a 19% included tax - Create an invoice with the following line: * Product: [any] * Quantity: 1.00 * Price: 19.95 * Taxes: [the 19% included tax] - Confirm the invoice - Go to "Accounting / Reporting / Audit Reports / General Ledger" - Download "DATEV DATA (ZIP)" and check "EXTF_accounting_entries.csv" **Issue:** The line for the created invoice has an amount of 19.94 inst

**Steps to reproduce:**
- Install Accounting and l10n_de_reports
- Switch to a German company
- Create a 19% included tax
- Create an invoice with the following line:
  * Product: [any]
  * Quantity: 1.00
  * Price: 19.95
  * Taxes: [the 19% included tax]
- Confirm the invoice
- Go to "Accounting / Reporting / Audit Reports / General Ledger"
- Download "DATEV DATA (ZIP)" and check "EXTF_accounting_entries.csv"

**Issue:**
The line for the created invoice has an amount of 19.94 instead of 19.95.

**Cause:**
As the tax is included, the balance on the line is computed and rounded. When the report is generated, "compute_all" is executed with the rounded balance to retrieve the total price with the taxes. Because the balance used in "compute_all" has been rounded and therefore is not exactly the same than the original computed value, there can be a 0.01 difference.

**Solution:**
Use directly "price_total" field when available.

opw-4191876

Forward-Port-Of: odoo/enterprise#71654
Forward-Port-Of: odoo/enterprise#70801

### Steps to reproduce the issue: 1. Activate Mexican localization 2. Create multiple Invoices in USD with different amounts (add the Invoice Date) 3. Send and Print them for the CFDI 4. Register a grouped Payment in MXN for those invoices 5. Go to one of the Invoices and click on Update Payments 6. Go to the CFDI tab and, on the Payment line, click on Force CFDI 7. On the Payment line, you should now be able to Download an XML document 8. In the document, the EquivalenciaDR attributes

### Steps to reproduce the issue:

1. Activate Mexican localization
2. Create multiple Invoices in USD with different amounts (add the Invoice Date)
3. Send and Print them for the CFDI
4. Register a grouped Payment in MXN for those invoices
5. Go to one of the Invoices and click on Update Payments
6. Go to the CFDI tab and, on the Payment line, click on Force CFDI
7. On the Payment line, you should now be able to Download an XML document
8. In the document, the EquivalenciaDR attributes should have the same values, which is not the case

### Explanation:

When calculating the rate (which then is used in EquivalenciaDR) in `_l10n_mx_edi_add_payment_cfdi_values`, we are using amounts that have been rounded out, leading to rates that differ when aiming for certain decimal precisions.

### Fix reasoning:

While `_get_conversion_rate` can be used to avoid the inconsistencies of the rounded amounts, it should not be used if the values do not match once they are converted, since the rate would then be wrong.

opw-4090269

Forward-Port-Of: odoo/enterprise#70083

Reproduce the issue: - Turn on inter-company transactions to sync Sales and Purchases - Create an SO in one company for the second company - Chatter displays an incorrect message noting the record was created from the current company instead of the triggering company The issue: In the sale_order.py model of sale_purchase_inter_company_rules.py, the field of the current company was used instead of the field of the order's company. opw-4199979 Forward-Port-Of: odoo/enterprise#71624

Reproduce the issue:
- Turn on inter-company transactions to sync Sales and Purchases
- Create an SO in one company for the second company
- Chatter displays an incorrect message noting the record was created from the current company instead of the triggering company

The issue:
In the sale_order.py model of sale_purchase_inter_company_rules.py, the field of the current company was used instead of the field of the order's company.

opw-4199979

Forward-Port-Of: odoo/enterprise#71624

- Set up Avatax Credentials - In Fiscal Position "Automatic Tax Mapping (AvaTax)" enable "Automatic Detection" - Create an invoice with avatax product and register payment - Open payment entry and duplicate it Issue: Validation Error will raise "The following customer(s) need to have a zip, state and country when using Avatax:" This occurs because the system checks for customer data validity when duplicating the payment record but it should not occur opw-4119958 Forward-Port-Of: od

- Set up Avatax Credentials
- In Fiscal Position "Automatic Tax Mapping (AvaTax)" enable "Automatic Detection"
- Create an invoice with avatax product and register payment
- Open payment entry and duplicate it

Issue: Validation Error will raise
"The following customer(s) need to have a zip, state and country when using Avatax:"

This occurs because the system checks for customer data validity when duplicating the payment record but it should not occur

opw-4119958

Forward-Port-Of: odoo/enterprise#69757

Added base localization package for Iraq 🇮🇶. It inludes the following: - Chart of Accounts - Taxes [task-3927924](https://www.odoo.com/web#model=project.task&id=3927924) Forward-Port-Of: odoo/enterprise#70457

Added base localization package for Iraq 🇮🇶. It inludes the following:
- Chart of Accounts
- Taxes

[task-3927924](https://www.odoo.com/web#model=project.task&id=3927924)

Forward-Port-Of: odoo/enterprise#70457

Problem: When the user enables allow_material on a project, they encounter a ValidationError when adding products on a task that has no sale order. Odoo tries to create a sale order for the task, but there is no company_id passed into the values. Solution: The company_id should be required when allow_material is enabled and the company should be computed once enabled. Steps to Reproduce on Runbot: 1. Install Sales, Field Service, Projects 2. Create a project and enable "Products on Task"

Problem: When the user enables allow_material on a project, they encounter a ValidationError when adding products on a task that has no sale order. Odoo tries to create a sale order for the task, but there is no company_id passed into the values.

Solution: The company_id should be required when allow_material is enabled and the company should be computed once enabled.

Steps to Reproduce on Runbot:
1. Install Sales, Field Service, Projects
2. Create a project and enable "Products on Task"
3. Create a task and assign a customer that has no sales order
4. Add products on the task and the ValidationError occurs

opw-4000580

Forward-Port-Of: odoo/enterprise#68493

Before this commit: The information of message sender using email alias was not shown, instead only mail subject with name Odoobot was displayed in chatter. After this commit: The information of sender such as email address, name, subject of email and email body is not displayed in chatter along with the attachment. Task - 4008634 Forward-Port-Of: odoo/enterprise#66503

Before this commit:
The information of message sender using email alias was not shown, instead only mail subject with name Odoobot was displayed in chatter.

After this commit:
The information of sender such as email address, name, subject of email and email body is not displayed in chatter along with the attachment.

Task - 4008634

Forward-Port-Of: odoo/enterprise#66503

Steps to reproduce the bug: - Create two Storable product: - “P1” -> product category A - “P2” -> product category B - Create a quality point: - picking type: receipt - product category: Cat A & Cat B - Measure: by quantity - Create a second quality point: - picking type: receipt - product category: Cat A - Measure: by quantity - Create a receipt of one unit of P1 and P2 - Confirm Problem: Four quality checks are created instead of three bec

Steps to reproduce the bug:
- Create two Storable product:
    - “P1” -> product category A
    - “P2” -> product category B

- Create a quality point:
    - picking type: receipt
    - product category: Cat A & Cat B
    - Measure: by quantity

- Create a second quality point:
    - picking type: receipt
    - product category: Cat A
    - Measure: by quantity

- Create a receipt of one unit of P1 and P2
- Confirm

Problem:
Four quality checks are created instead of three because we check if the quality point corresponds to the picking type and if the quality point has no product selected. However, we don't verify if a product category is also not set.

opw-4240859

Forward-Port-Of: odoo/enterprise#71453

Open General Ledger Search for a non existing account/aline (ex. "1111111111111") Issue: All lines are shown This occurs because we update matched lines only if there is a match, otherwise we reset the filter opw-4160605 Forward-Port-Of: odoo/enterprise#69424

Open General Ledger
Search for a non existing account/aline (ex. "1111111111111")

Issue: All lines are shown
This occurs because we update matched lines only if there is a match, otherwise we reset the filter

opw-4160605

Forward-Port-Of: odoo/enterprise#69424

This commit adds support for the Bank of Italy currency rates. The Bank of Italy publishes the currency rates on its APIs, of which the most recent one is available at https://tassidicambio.bancaditalia.it/terzevalute-wf-web/rest/v1.0/latestRates. Documentation can be found at https://tassidicambio.bancaditalia.it/terzevalute-wf-ui-web/assets/files/Istruzioni_tecnico-operative.pdf. This is necessary for Italian law compliance, as the Bank of Italy is the only institution allowed to publis

This commit adds support for the Bank of Italy currency rates. The Bank of Italy publishes the currency rates on its APIs, of which the most recent one is available at https://tassidicambio.bancaditalia.it/terzevalute-wf-web/rest/v1.0/latestRates.

Documentation can be found at https://tassidicambio.bancaditalia.it/terzevalute-wf-ui-web/assets/files/Istruzioni_tecnico-operative.pdf. 

This is necessary for Italian law compliance, as the Bank of Italy is the only institution allowed to publish currency rates in Italy.

Forward-Port-Of: odoo/enterprise#55502

In this PR: - Simplified tax detail retrieval using Odoo ORM instead of complex SQL queries. - Directly mapped tax amounts from tax lines to improve accuracy. - Enhanced handling of journal items with 0% tax or no tax. Task ID: 4032825 Forward-Port-Of: odoo/enterprise#65983

In this PR:
- Simplified tax detail retrieval using Odoo ORM instead of complex SQL queries.
- Directly mapped tax amounts from tax lines to improve accuracy.
- Enhanced handling of journal items with 0% tax or no tax.

Task ID: 4032825

Forward-Port-Of: odoo/enterprise#65983

**Steps to reproduce:** - Install Accounting and l10n_cl_edi_boletas - Switch to a Chilean company (e.g. CL Company) - Create a branch company for it - Create a product with a tax from "ILA" group - Switch to the branch company - Create an invoice with the created product - Confirm it **Issue:** A traceback is raised while trying to fetch some tax groups: - self.env.ref(f'account.{cid}_tax_group_ila') - self.env.ref(f'account.{cid}_tax_group_retenciones') where {cid} is the id of th

**Steps to reproduce:**
- Install Accounting and l10n_cl_edi_boletas
- Switch to a Chilean company (e.g. CL Company)
- Create a branch company for it
- Create a product with a tax from "ILA" group
- Switch to the branch company
- Create an invoice with the created product
- Confirm it

**Issue:**
A traceback is raised while trying to fetch some tax groups:
- self.env.ref(f'account.{cid}_tax_group_ila')
- self.env.ref(f'account.{cid}_tax_group_retenciones') where {cid} is the id of the branch company.

**Cause:**
There is no tax group defined in the branch company. The taxes and the tax groups are defined in the parent company.

**Solution:**
Do not raise an error if the XMLID cannot be found and also check tax groups from parent companies as the taxes could come from them.
Use the "ref" method defined in "account.chart.template" model that is doing it.

opw-4227241


Related comminity PR: https://github.com/odoo/odoo/pull/182798

Forward-Port-Of: odoo/enterprise#71476

Currently, a traceback occurs when the user creates a link tracker having no scheme in the URL. To reproduce this issue: 1) Install website_link, email marketing 2) Create a new link tracker with a target URL from email marketing/configuration 3) Now remove the `http://` from the target URL 4) Navigate to website/site/link tracker Error:- ``` AttributeError: 'str' object has no attribute 'to_url' ``` This is because when the target URL has no `http://` the URL scheme will be

Currently, a traceback occurs when the user creates a link tracker having no scheme in the URL.

To reproduce this issue:

1) Install website_link, email marketing
2) Create a new link tracker with a target URL from email marketing/configuration
3) Now remove the `http://` from the target URL
4) Navigate to  website/site/link tracker

Error:- 
```
AttributeError: 'str' object has no attribute 'to_url'
```

This is because when the target URL has no `http://` the URL scheme will be an empty string. 
So it executes the else block in the below line.

https://github.com/odoo/odoo/blob/8a1e6bef82fdaa98c60ef1e3fa519a03206a6788/addons/link_tracker/models/link_tracker.py#L54-L58

Clearly in the else block the value of `tracker.get_base_url()` is the string, when joining the `url` and `tracker.get_base_url()` it becomes a string.

which leads to a traceback when `to_url()` is accessed from the string.

sentry-5925121505

Forward-Port-Of: odoo/odoo#182556

**Steps to reproduce:** - Install Accounting, POS and l10n_cl - Switch to a Chilean company (e.g. CL Company) - Create a branch company for it - Create a product with a tax from "ILA" group - Switch to the branch company - Open a POS session - Sell the created product - When processing payment, select a Chilean customer and the invoice option **Issue:** A traceback is raised while trying to fetch some tax groups: - self.env.ref(f'account.{cid}_tax_group_ila') - self.env.ref(f'accou

**Steps to reproduce:**
- Install Accounting, POS and l10n_cl
- Switch to a Chilean company (e.g. CL Company)
- Create a branch company for it
- Create a product with a tax from "ILA" group
- Switch to the branch company
- Open a POS session
- Sell the created product
- When processing payment, select a Chilean customer and the invoice option

**Issue:**
A traceback is raised while trying to fetch some tax groups:
- self.env.ref(f'account.{cid}_tax_group_ila')
- self.env.ref(f'account.{cid}_tax_group_retenciones') where {cid} is the id of the branch company.

**Cause:**
There is no tax group defined in the branch company. The taxes and the tax groups are defined in the parent company.

**Solution:**
Do not raise an error if the XMLID cannot be found and also check tax groups from parent companies as the taxes could come from them.
Use the "ref" method defined in "account.chart.template" model that is doing it.

opw-4227241


Related enterprise PR: https://github.com/odoo/enterprise/pull/71476

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

Forward-Port-Of: odoo/odoo#182798

In the new IoT image we use Chromium instead of Firefox, however it comes bundled with some extensions, namely uBlock, which use up disk space in the background. This leads to the `/tmp` directory getting full, which causes various errors and instability. After this change, the `/tmp` directory only reaches around 50% capacity, even after many restarts and webpage visits. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/

In the new IoT image we use Chromium instead of
Firefox, however it comes bundled with some
extensions, namely uBlock, which use up disk space in the background. This leads to the `/tmp`
directory getting full, which causes various
errors and instability.

After this change, the `/tmp` directory only
reaches around 50% capacity, even after many
restarts and webpage visits.

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

Forward-Port-Of: odoo/odoo#182883

Issue 1: Previously, the chart was being overlapped by the navigation on smaller screen sizes. This commit fixes the issue by limiting the max-width for navigations and also hiding the button text for smaller screens. Issue 2: Previously, after a certain amount of data, the bar colors defaulted to black as the dataIndex exceeded the colors array. This commit fixes the issue by using the modulo operation on dataIndex with the colors array to repeat the colors, and also added additional color

Issue 1:
Previously, the chart was being overlapped by the navigation on smaller screen sizes. This commit fixes the issue by limiting the max-width for navigations and also hiding the button text for smaller screens.

Issue 2:
Previously, after a certain amount of data, the bar colors defaulted to black as the dataIndex exceeded the colors array. This commit fixes the issue by using the modulo operation on dataIndex with the colors array to repeat the colors, and also added additional colors referenced from reporting.

Task-4089537

Forward-Port-Of: odoo/odoo#175704

Steps to reproduce: 1. Create a live session for a 'Quiz about your company' survey 2. Add images to your answers 2. Complete it with one user 3. Review your answer in the last 4. The images are getting overlap Technical Reason: on the user-side results page, images that were not properly handled were displayed at their default size. After this commit: it should be perfectly aligned. Task-4208130 Forward-Port-Of: odoo/odoo#181386

Steps to reproduce:
1. Create a live session for a 'Quiz about your company' survey
2. Add images to your answers
2. Complete it with one user
3. Review your answer in the last
4. The images are getting overlap

Technical Reason:
on the user-side results page, images that were not properly handled were displayed at their default size.

After this commit:
it should be perfectly aligned.

Task-4208130

Forward-Port-Of: odoo/odoo#181386

Steps to reproduce: - Install serbian (latin) language - Add a keyword in serbian via SEO optimize menu - Traceback occurs This fix ensures that language variants, such as "sr@latin", are properly handled when making requests to the Google Autocomplete API for SEO suggestions. A test has been added. task-4210707 Forward-Port-Of: odoo/odoo#181400

Steps to reproduce:

- Install serbian (latin) language
- Add a keyword in serbian via SEO optimize menu
- Traceback occurs

This fix ensures that language variants, such as "sr@latin", are properly handled when making requests to the Google Autocomplete API for SEO suggestions.
A test has been added.

task-4210707

Forward-Port-Of: odoo/odoo#181400

Steps to reproduce the bug: - In Website edit mode. - click on the navbar. - For the "Format" option of the navbar, open the color picker. - Select any colors of the theme colors or any grayscale color. - Bug: the color is not applied to the navbar links. The bug has existed since commit [1], which added the feature to set a custom text color for the header. Two problems were there from the start: - First, the variable wasn't saved inside quotes like it should have been. - Seco

Steps to reproduce the bug:

- In Website edit mode.
- click on the navbar.
- For the "Format" option of the navbar, open the
color picker.
- Select any colors of the theme colors or any grayscale color.
- Bug: the color is not applied to the navbar links.

The bug has existed since commit [1], which added the feature to set a
custom text color for the header. Two problems were there from the
start:

- First, the variable wasn't saved inside quotes like it should have
been.
- Second, there was no function to convert theme colors (e.g.,
"o-color-1") into hexadecimal values when generating the CSS.

Because of this, only non-theme colors worked with this option. This
commit fixes the issue but ensures that it doesn't change anything for
users who already applied a color that didn’t work before. This way,
their navbar text color won't suddenly change after the fix without
them understanding why.

[1]: https://github.com/odoo/odoo/commit/d54028e5ed33a0258d3f2aeeaea338ac04f8d402

opw-4065019

Forward-Port-Of: odoo/odoo#182570

When you made a downpayment on an order that contained product with fixed amount taxes, the tax would be paid multiple times. Steps to reproduce: ------------------- * Create a tax T1 with a fixed amount of 10€ * Create a product P1 using the tax T1 * Make a sale order and add the product P1 to it * Open PoS and make a downpayment for the sale order (e.g 50%) * You will already pay the 10€ of tax * Now if you make a second downpayment (e.g. 10%) > Observation: You still have the 10€ t

When you made a downpayment on an order that contained product with fixed amount taxes, the tax would be paid multiple times.

Steps to reproduce:
-------------------
* Create a tax T1 with a fixed amount of 10€
* Create a product P1 using the tax T1
* Make a sale order and add the product P1 to it
* Open PoS and make a downpayment for the sale order (e.g 50%)
* You will already pay the 10€ of tax
* Now if you make a second downpayment (e.g. 10%)
> Observation: You still have the 10€ tax to pay

Why the fix:
------------
We match the behavior of sales app, and ignore the fixed price taxes when creating the downpayment lines.

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

Forward-Port-Of: odoo/odoo#182380

To avoid confusion, the field previously labeled as 'Purchase Order' has been renamed to 'Purchase Order Warning'. This clarifies that the field relates to triggering purchase warnings, not managing purchase orders themselves. This change only affects the field label, ensuring consistency in user expectations without altering the filter content or behavior. OPW-4141054 Forward-Port-Of: odoo/odoo#180176

To avoid confusion, the field previously labeled as 'Purchase Order' has been renamed to 'Purchase Order Warning'. This clarifies that the field relates to triggering purchase warnings, not managing purchase orders themselves.

This change only affects the field label, ensuring consistency in user expectations without altering the filter content or behavior.

OPW-4141054

Forward-Port-Of: odoo/odoo#180176

With this commit, the test test_ui is imported and runs smoothly. task-4143417 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#182832 Forward-Port-Of: odoo/odoo#181761

With this commit, the test test_ui is imported and runs smoothly.

task-4143417

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#182832
Forward-Port-Of: odoo/odoo#181761

Fix the code at [1], Where the system tries to update the payment method, Modify the code to handle this issue where the network value might not exist. This can be done by providing a default value for ```payment_method_type``` if the network value is not present. Link [1]: https://github.com/odoo/odoo/blob/d30f41a49f614456c71a0a6974325030f552a0db/addons/payment_razorpay/models/payment_transaction.py#L391-L392 Sentry-5950544641 --- I confirm I have signed the CLA and read the PR guidel

Fix the code at [1], Where the system tries to update the payment method, Modify the code to handle this issue where the network value might not exist. This can be done by providing a default value for ```payment_method_type``` if the network value is not present.

Link [1]: https://github.com/odoo/odoo/blob/d30f41a49f614456c71a0a6974325030f552a0db/addons/payment_razorpay/models/payment_transaction.py#L391-L392

Sentry-5950544641

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

Forward-Port-Of: odoo/odoo#182617

Before this commit, when users added a description to a pickup shipping method, the algorithm to prevent the payment button from being enabled when no pickup location was selected failed. Now, the payment button will be disabled when no pickup is selected even if the shipping method has a description. opw-4040317 Forward-Port-Of: odoo/odoo#183222

Before this commit, when users added a description to a pickup shipping method, the algorithm to prevent the payment button from being enabled when no pickup location was selected failed.

Now, the payment button will be disabled when no pickup is selected even if the shipping method has a description.

opw-4040317

Forward-Port-Of: odoo/odoo#183222

Before this commit, when some extension in chrome threw an unhandledrejection event, Chrome apparently redacts it. The error popped into Odoo as very generic one. The error Dialog was spawned, intempestively. After this commit, we use a heuristic to block that kind of errors: Apparently, the error event is a CustomEvent, with no `reason`. opw-4246402 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I

Before this commit, when some extension in chrome threw an unhandledrejection event, Chrome apparently redacts it. The error popped into Odoo as very generic one. The error Dialog was spawned, intempestively.

After this commit, we use a heuristic to block that kind of errors: Apparently, the error event is a CustomEvent, with no `reason`.

opw-4246402

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#183327