Tuesday, May 2, 2023
36 changes · master
Enhancements to existing features
Odoo now enforces clearer version number formats for modules and upgrade scripts to avoid ambiguity during upgrades. This helps reduce the risk of upgrade scripts being interpreted as the wrong version and adds warnings when invalid version numbers are detected.
The wording around neutralized databases has been improved to reduce confusion about what the neutralization process does. This helps users better understand that the database is made safe for testing or staging, rather than being automatically destroyed.
Original PR description
Improve the copywriting around neutralize that can be confusing (will it auto-destroy?) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website editor now applies sensible default sizing when users choose a repeat-pattern background. This makes the selected background style visibly take effect across relevant page snippets, improving the editing experience without changing business workflows.
Original PR description
Description of the issue/feature this PR addresses: --- When a user chooses "Repeat Pattern" as the background image position, nothing happens. Current behavior before PR: --- As the background size is set to auto, for background-position `repeat-pattern` no [effect](https://bit.ly/3MM31Ac) can be seen in the background size. Desired behavior after PR is merged: --- Not a bug but can be considered an improvement in features by setting some [default width or height](https://bit.ly/3GbGIBo) for a repeat-pattern option for all relevant snippets." PR [102995](https://github.com/odoo/odoo/pull/102995) TaskID: 2862510 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Helpdesk team labels have been renamed to “Helpdesk Team” across screens, reports, and related settings. This helps users distinguish helpdesk teams from other team concepts in Odoo, such as sales or maintenance teams.
Original PR description
Several apps in odoo have the notion of team (crm/sales, maintenance, quality...). We need to differentiate helpdesk teams from the other kind of teams. task-3251737
The Helpdesk ticket activity view has been adjusted to remove an unnecessary blank space between the customer and name fields. This creates a cleaner, more compact layout for users reviewing ticket activities.
Original PR description
Before this commit there is a extra space between partner field and name in activity view of ticket. This commit move partner field to proper place to remove extra space. task-3178619
Resolved issues and error corrections
This change stabilizes an automated test for advanced search date comparisons by using a fixed date. It helps prevent false test failures when the calendar month changes, supporting smoother development and release validation without changing user-facing behavior.
Original PR description
This commit adds a patchDate to the "Several date filters and a comparison" test. The patchDate will allow the date to be fixed and prevent the test from being invalidated when the month changes in the real world. 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
Code cleanup and technical improvements
This update tidies the Sales Loyalty module by reorganizing files, improving naming, and standardizing formatting. It does not change business functionality, but makes the module easier to maintain and reduces the risk of future errors.
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Description of the issue/feature this PR addresses: _should_be_valued should always return a bool. Current behavior before PR: Currently, when it's False, it returns False. However, when it's True, it returns self.company_id. Desired behavior after PR is merged: After this fix, it returns True instead of self.company_id. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#120123
Original PR description
Description of the issue/feature this PR addresses: _should_be_valued should always return a bool. Current behavior before PR: Currently, when it's False, it returns False. However, when it's True, it returns self.company_id. Desired behavior after PR is merged: After this fix, it returns True instead of self.company_id. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#120123
List views now apply warning or status colors consistently to many2one fields, such as customer or product links. This makes highlighted rows easier to read and prevents important visual cues from being missed.
Original PR description
Before this commit, in a list view, the style of a decoration on a m2o widget was ignored. For example, when applying the danger decoration, we want the m2o field to be in red. How to reproduce: Go to a list view with a field having the many2one widget and a danger-decoration. Have a line that respects the decoration condition. Before this commit: All text on the line is red except the many2one text After this commit: All text on the line is in red 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
Fixed an issue where short chatter message areas could show a large, unnecessary scrollbar even when there was little content. This makes the message panel cleaner and easier to use, especially when only one or a few messages are present.
Original PR description
Before this commit, when chatter message list was lower than 2500px, the message-list had scrollable of 2500px of height. This happens because the area detecting present time was always 2500px. thus making the content have this value as scrollheight. This commit fixes the issue by making presence area not go above the conversation height. So if message list is 250px of height, then presence area is 250px, not 2500px. This chatter, before commit, when it had a single message: <img width="1029" alt="Screenshot 2023-04-28 at 18 47 55" src="https://user-images.githubusercontent.com/6569390/235206760-33c8f012-fac3-4070-9bbf-c8d3132e2dcf.png"> With commit, no longer has scrollbar: <img width="1033" alt="Screenshot 2023-04-28 at 18 49 56" src="https://user-images.githubusercontent.com/6569390/235206912-5ae9d876-6398-42ea-b5d2-dd162cc564ad.png">
This update corrects how dynamic numbers and values are inserted into on-screen messages across payment, website editing, web views, and slide discussions. It helps prevent confusing or incorrectly formatted text from appearing to users.
Original PR description
*: web, web_editor, payment Before this commit, templates with %d was given to sprintf but it was not interpreted by the function After the commit, %d are replaced by %s in templates for sprintf Also this commit converts a last _.str.sprintf into sprintf
This change stabilizes an automated test for mail message replies by waiting for the page update more precisely before checking the result. It helps reduce false test failures in the development pipeline, supporting smoother and more reliable releases.
Original PR description
Before this PR, the `Updating the parent message of a reply also updates the visual of the reply` test was failing in a non-deterministic fashion. This PR fixes this issue by replacing the `nextTick` by a specific `waitUntil` in order to ensure the DOM is properly updated before asserting. Fixes 20829 runbot issue.
This update fixes version numbers in several localization-related modules so they align with the expected release information. It helps avoid confusion during upgrades, app management, or support checks without changing business functionality.
Original PR description
See odoo/odoo#118420
This update makes fields correctly respect read-only rules when the same field appears multiple times in a view. It helps prevent incorrect editing behavior in the timesheet grid and improves consistency for users.
Original PR description
In many field composents, we need to know if the field modifier is readonly or not. So we use the function record.isReadonly(fieldname) to get the information. This one is false if we have several times the same <field> defined in a view. We will only listen to the modfier.readonly of the last occurrence. To solve this problem and allow the use of several fields in the same view with different modifiers, we will have to extract the readonlyModifiers and evaluate it in the field component. Part of task: 3179751
This update reorganizes several internal Discuss components into the Discuss area of the Mail module. It does not introduce new business features, but it helps keep the codebase cleaner and easier to maintain for future improvements.
Original PR description
Part of task-3265211
Task: 30336 Description of the issue/feature this PR addresses: In a payment when selecting checks it is allowed to select checks belonging to different companies but it is necessary to allow only to select companies from the same company (the company of the payment). Current behavior before PR: In a payment when selecting checks it is allowed to select checks belonging to different companies. Desired behavior after PR is merged: In a payment not allow to select checks belonging to d
Original PR description
Task: 30336 Description of the issue/feature this PR addresses: In a payment when selecting checks it is allowed to select checks belonging to different companies but it is necessary to allow only to select companies from the same company (the company of the payment). Current behavior before PR: In a payment when selecting checks it is allowed to select checks belonging to different companies. Desired behavior after PR is merged: In a payment not allow to select checks belonging to different companies --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#118683
With the BS5 upgrade script of 16.0, countdowns' data-display may have been converted to data-bs-display by mistake. This will fix the DOM at page load for good measures, maybe even allowing to remove this code in a few years as hopefully all current countdowns will have been removed or edited (or when a proper upgrade script in a future version of Odoo will be made, if necessary). opw-3240041 opw-3240532 opw-3258751 opw-3272731 Forward-Port-Of: odoo/odoo#119661
Original PR description
With the BS5 upgrade script of 16.0, countdowns' data-display may have been converted to data-bs-display by mistake. This will fix the DOM at page load for good measures, maybe even allowing to remove this code in a few years as hopefully all current countdowns will have been removed or edited (or when a proper upgrade script in a future version of Odoo will be made, if necessary). opw-3240041 opw-3240532 opw-3258751 opw-3272731 Forward-Port-Of: odoo/odoo#119661
Scenario: - set a quotation template on a quotation that adds lines ordered with a sequence (eg. 3 lines with sequences 10, 11, 12) - add lines in this quotation - save Issue: The added lines have sequence 10 and the seen order changes. This is caused by 6f11060d6afd9edce904dd34a2d415a2a2461108 that tries to mitigate a more rare issue when there is more than one page of lines. Solution: Reverting the previous fix, and setting the sequence of the first line to -99: - when resequencing th
Original PR description
Scenario: - set a quotation template on a quotation that adds lines ordered with a sequence (eg. 3 lines with sequences 10, 11, 12) - add lines in this quotation - save Issue: The added lines have…
Scenario: - set a quotation template on a quotation that adds lines ordered with a sequence (eg. 3 lines with sequences 10, 11, 12) - add lines in this quotation - save Issue: The added lines have sequence 10 and the seen order changes. This is caused by 6f11060d6afd9edce904dd34a2d415a2a2461108 that tries to mitigate a more rare issue when there is more than one page of lines. Solution: Reverting the previous fix, and setting the sequence of the first line to -99: - when resequencing the first page, the sequence will be -99 to -60 => records from the second page will not get in the first page - new lines will be added at the end Issues still present: - when resequencing the second page, item from 3 pages get into it (it was already the case before 6f11060d6afd9edce904dd34a2d415a2a2461108) - when adding a new line (without resequencing), it is added at the end and not at the beginning of the next page But those are just behavior in any list view (as is the original issue of 6f11060d6afd9edce904dd34a2d415a2a2461108, but since it was partially fixed for a year, this patch try to give an in-between solution instead of just reverting it). opw-2833913 Forward-Port-Of: odoo/odoo#119890 Forward-Port-Of: odoo/odoo#119231
Fixed incorrect use of the popup add function. Since version saas-16.2, the first parameter must be the chosen popup component and not the name of the popup as a string. Forward-Port-Of: odoo/odoo#120073
Original PR description
Fixed incorrect use of the popup add function. Since version saas-16.2, the first parameter must be the chosen popup component and not the name of the popup as a string. Forward-Port-Of: odoo/odoo#120073
Starting with Firefox 109, a widget element prototype that is put inside an iframe will not be instanceof its original constructor. See: https://github.com/webcompat/web-bugs/issues/118350 This is because a node that is adopted by an iframe will have its prototype changed to match the constructor from within the iframe instead of its original one. This has been the case for a long time. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1470017 It largely went unnoticed because of another
Original PR description
Starting with Firefox 109, a widget element prototype that is put inside an iframe will not be instanceof its original constructor. See: https://github.com/webcompat/web-bugs/issues/118350 This is…
Starting with Firefox 109, a widget element prototype that is put inside an iframe will not be instanceof its original constructor. See: https://github.com/webcompat/web-bugs/issues/118350 This is because a node that is adopted by an iframe will have its prototype changed to match the constructor from within the iframe instead of its original one. This has been the case for a long time. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1470017 It largely went unnoticed because of another quirk of Firefox related to the use of instanceof which was fixed in version 109. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1360715 Since this bug was fixed it became apparent, in the form of a traceback, that the wrong instance of ClipboardJS was being used in the case of Firefox, due to the forced prototype change. This commit could be reverted once Firefox is fixed. Steps to reproduce the issue in Firefox > 109: - Create a new mass mailing. - Choose the third template with "Thank you for joining us!". - Click on the "LOGIN" button link inside the email. - Get a traceback about a paremeter not being the right type. Task-3186513 OPW-3172914 Forward-Port-Of: odoo/odoo#120003
Steps to reproduce: - create a product; - disable the continue selling option for the out-of-stock; - do not have a stock quantity for this product. - go to ecommerce; - without click on the product, add it in the cart with the cart icon (on the picture). Issue: It is possible to add the product to the cart. If we repeat this several times, we will create quotations. Solution: Hide the button if the product is a storable product and we don't want to sell it if we have no stock. We
Original PR description
Steps to reproduce: - create a product; - disable the continue selling option for the out-of-stock; - do not have a stock quantity for this product. - go to ecommerce; - without click on the product, add it in the cart with the cart icon (on the picture). Issue: It is possible to add the product to the cart. If we repeat this several times, we will create quotations. Solution: Hide the button if the product is a storable product and we don't want to sell it if we have no stock. We also check the quantity available. opw-3148069 Forward-Port-Of: odoo/odoo#119982 Forward-Port-Of: odoo/odoo#112172
[FIX] stock: allow multi-picking validation w/show reception report Steps to reproduce: - activate `group_stock_reception_report` in settings - activate `auto_show_reception_report` for the "Receipts" operation type - create a receipt w/ any product + confirm - create a return w/any product + confirm - select both the receipt + return in the (Operations > Transfers) list view > action > Validate Expected result: both pickings are validated Actual result: stacktrace due to expecte
Original PR description
[FIX] stock: allow multi-picking validation w/show reception report Steps to reproduce: - activate `group_stock_reception_report` in settings - activate `auto_show_reception_report` for the "Receipts" operation type - create a receipt w/ any product + confirm - create a return w/any product + confirm - select both the receipt + return in the (Operations > Transfers) list view > action > Validate Expected result: both pickings are validated Actual result: stacktrace due to expected singleton ValueError task-3204596 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#113628
Was missing in the export Forward-Port-Of: odoo/odoo#120258
Original PR description
Was missing in the export Forward-Port-Of: odoo/odoo#120258
The call was made with the old method `showPopup`. The call is now made with the new .add method on the popup service. Forward-Port-Of: odoo/odoo#120239
Original PR description
The call was made with the old method `showPopup`. The call is now made with the new .add method on the popup service. Forward-Port-Of: odoo/odoo#120239
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#119775
Original PR description
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#119775
Corporate CLA for Le Filament --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#120015
Original PR description
Corporate CLA for Le Filament --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#120015
Deleting a kit BoM will lead to an error if the kit is in the middle of a sale process To reproduce the issue: 1. In Settings, enable UoM 2. Create a product category PC: - AVCO - Auto 3. Create three storable products P_kit, P_01, P_02 - UoM of P_01: `m` - UoM of P_02: `kg` 4. Create a BoM: - Product: P_kit - Type: kit - Components: - 1 x P_01 - 1 x P_02 5. Create and confirm a SO with 1 x P_kit 6. Force the delivery 7. Delete the BoM 8. Creat
Original PR description
Deleting a kit BoM will lead to an error if the kit is in the middle of a sale process To reproduce the issue: 1. In Settings, enable UoM 2. Create a product category PC: - AVCO - Auto 3. Create…
Deleting a kit BoM will lead to an error if the kit is in the middle
of a sale process
To reproduce the issue:
1. In Settings, enable UoM
2. Create a product category PC:
- AVCO
- Auto
3. Create three storable products P_kit, P_01, P_02
- UoM of P_01: `m`
- UoM of P_02: `kg`
4. Create a BoM:
- Product: P_kit
- Type: kit
- Components:
- 1 x P_01
- 1 x P_02
5. Create and confirm a SO with 1 x P_kit
6. Force the delivery
7. Delete the BoM
8. Create and confirm the SO's invoice
Error: a traceback appears "ValueError: Expected singleton: uom.uom..."
Because of the configuration, when posting the invoice, we compute
the COGS. During that process, we need the average price of P_kit
https://github.com/odoo/odoo/blob/640907ec1852c4e477957c865549a87d3ae840dd/addons/sale_stock/models/account_move.py#L133
We give to that method the components' SMs. In
`_compute_average_price`, since we don't find a BoM, we will bypass
the mrp override
https://github.com/odoo/odoo/blob/419e42132d9526e9d98c2126158d4f88716d17c4/addons/mrp_account/models/product.py#L48-L50
As a result, it leads to
https://github.com/odoo/odoo/blob/640907ec1852c4e477957c865549a87d3ae840dd/addons/stock_account/models/product.py#L680-L684
Where we will have the candidates of all components (i.e., several
different products). But that method is not designed for such a
situation. This is the reason why, when calling `_consume_all`, it
will fail:
https://github.com/odoo/odoo/blob/858d24a611c4c8af0dcae82a6eb4077e391398ed/addons/stock_account/models/stock_valuation_layer.py#L85
We try to get the rounding of the product, but there are actually
two of them (the two components) -> singleton error
OPW-3218141
Forward-Port-Of: odoo/odoo#120251
Forward-Port-Of: odoo/odoo#119944In the Invoicing dashboard, the "Average Invoice" scorecoard displays the wrong amount of invoices. It displays the number of "account.invoice.report" lines. This commit fixes the issue by displaying the count_unique measure of "move_id" task 3180524 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:
Original PR description
In the Invoicing dashboard, the "Average Invoice" scorecoard displays the wrong amount of invoices. It displays the number of "account.invoice.report" lines. This commit fixes the issue by displaying the count_unique measure of "move_id" task 3180524 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#120253
Current behavior: When you try to open the pos as a demo user, you get an error message. Steps to reproduce: - Install pos and loyalty modules - Log in as demo user - Try to open the pos - You get an error message opw-3297341 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#120262
Original PR description
Current behavior: When you try to open the pos as a demo user, you get an error message. Steps to reproduce: - Install pos and loyalty modules - Log in as demo user - Try to open the pos - You get an error message opw-3297341 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#120262
Commit [1] adapted the code to remove a python route. However, it forgot to adapt its enterprise counter-part. This leads to a crash when clicking on the button to install `website_appointment`. This commit fixes that by also adapting website_enterprise. Steps to reproduce: - Install website enterprise edition - Click on +New in the website app - Click on Appointment From => TB [1]: https://github.com/odoo/odoo/commit/7f83e398b68d7c7544753e2b8bb1b334fb5f7036 opw-3261873 Forward
Original PR description
Commit [1] adapted the code to remove a python route. However, it forgot to adapt its enterprise counter-part. This leads to a crash when clicking on the button to install `website_appointment`. This commit fixes that by also adapting website_enterprise. Steps to reproduce: - Install website enterprise edition - Click on +New in the website app - Click on Appointment From => TB [1]: https://github.com/odoo/odoo/commit/7f83e398b68d7c7544753e2b8bb1b334fb5f7036 opw-3261873 Forward-Port-Of: odoo/enterprise#40580
Steps to reproduce the bug: - Go to the mrp settings and print work order barcode commands - Create a storable product “P1”: - Add a BoM: - Add an Operation - Create a MO to produce 10 units of “P1” - Confirm the MO - Open the tablet view - Set the qty done to 1 - Scan “Mark as Done” barcode Problem: A traceback is triggered: “This._super is not a function” `this._super` is reassigned after each patched function is called, so as we use an asynchronous function in t
Original PR description
Steps to reproduce the bug:
- Go to the mrp settings and print work order barcode commands
- Create a storable product “P1”:
- Add a BoM:
- Add an Operation
- Create a MO to produce 10 units of “P1”
- Confirm the MO
- Open the tablet view
- Set the qty done to 1
- Scan “Mark as Done” barcode
Problem:
A traceback is triggered: “This._super is not a function”
`this._super` is reassigned after each patched function is called, so
as we use an asynchronous function in this patch, then we cannot call
`this._super` after an await because it will be undefined, therefore we
have to keep a reference to the initial _super method
opw-3185355
Forward-Port-Of: odoo/enterprise#40539
Forward-Port-Of: odoo/enterprise#37392Before this commit, in case of a rounding error in the calculation of monetary value of a commodity, we get an error from UPS: `Invalid or missing product unit value for product number 1. Valid length is 1 to 19 numeric and it can hold up to 6 decimal places` To avoid this, we need to round the unit price before sending it to the UPS. We are rounding to 2 decimal places because there is not a straight-forward way to get the number of decimal places of the currency and it covers most cases.
Original PR description
Before this commit, in case of a rounding error in the calculation of monetary value of a commodity, we get an error from UPS: `Invalid or missing product unit value for product number 1. Valid length is 1 to 19 numeric and it can hold up to 6 decimal places` To avoid this, we need to round the unit price before sending it to the UPS. We are rounding to 2 decimal places because there is not a straight-forward way to get the number of decimal places of the currency and it covers most cases. opw-3289042 Forward-Port-Of: odoo/enterprise#40536
This commit's purpose is to add a test to ensure the 'mark as done' button is working correctly for tasks when multiple deliveries are validated through the button and the show_report option is activated, the deliveries are correctly validated and marked as 'done'. task-3204596 Forward-Port-Of: odoo/enterprise#37518
Original PR description
This commit's purpose is to add a test to ensure the 'mark as done' button is working correctly for tasks when multiple deliveries are validated through the button and the show_report option is activated, the deliveries are correctly validated and marked as 'done'. task-3204596 Forward-Port-Of: odoo/enterprise#37518
In v15 when going to the closing entry of the belgium tax report you could close entry and when you post it, a wizard appeared and the options selected were displayed in the pdf. But in v16 with reportalypse, the options were ignored in the export_to_pdf function (more precisely the print_options ignored those options). By adding in the init_custom_options the missing options they are not ignored anymore. task-id: 3247369 Forward-Port-Of: odoo/enterprise#39008
Original PR description
In v15 when going to the closing entry of the belgium tax report you could close entry and when you post it, a wizard appeared and the options selected were displayed in the pdf. But in v16 with reportalypse, the options were ignored in the export_to_pdf function (more precisely the print_options ignored those options). By adding in the init_custom_options the missing options they are not ignored anymore. task-id: 3247369 Forward-Port-Of: odoo/enterprise#39008
According to the XSD definition `DTE_v10.xsd`, the Discount Percentage field ('DescuentoPct') of invoice lines should be rounded to 2 decimal places. This should be the case both in the invoice DTE and in the DTE of the Guía de Despacho. With this commit, we use float_repr to truncate this field to 2 decimal places. opw-3202045  Forward-Port-Of: odoo/enterprise#40319 Forwar
Original PR description
According to the XSD definition `DTE_v10.xsd`, the Discount Percentage field ('DescuentoPct') of invoice lines should be rounded to 2 decimal places.
This should be the case both in the invoice DTE and in the DTE of the Guía de Despacho.
With this commit, we use float_repr to truncate this field to 2 decimal places.
opw-3202045
Forward-Port-Of: odoo/enterprise#40319
Forward-Port-Of: odoo/enterprise#40192Propagate debug param from host to iframe to allow in browser iframe js debug. Forward-Port-Of: odoo/enterprise#40569 Forward-Port-Of: odoo/enterprise#39555
Original PR description
Propagate debug param from host to iframe to allow in browser iframe js debug. Forward-Port-Of: odoo/enterprise#40569 Forward-Port-Of: odoo/enterprise#39555