From 63f09a6180111d421d9a190647b9918bb27ca4f1 Mon Sep 17 00:00:00 2001 From: Joseph Caburnay Date: Thu, 12 Aug 2021 09:57:20 +0000 Subject: [PATCH] [FIX] point_of_sale: call the configureGui before calling start The chrome.comp.start() call also involves iot device loading which is dependent on Gui to show error when there is any. In this fix, we call configureGui when the Chrome instance is available and before calling start. Part-of: odoo/odoo#73725 --- addons/point_of_sale/static/src/js/chrome_adapter.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/addons/point_of_sale/static/src/js/chrome_adapter.js b/addons/point_of_sale/static/src/js/chrome_adapter.js index 0cc6a4652b7..12ee15f055f 100644 --- a/addons/point_of_sale/static/src/js/chrome_adapter.js +++ b/addons/point_of_sale/static/src/js/chrome_adapter.js @@ -33,9 +33,9 @@ export class ChromeAdapter extends Component { // Little trick to avoid displaying the block ui during the POS models loading const BlockUiFromRegistry = registry.category("main_components").get("BlockUI"); registry.category("main_components").remove("BlockUI"); + configureGui({ component: chrome.comp }); await chrome.comp.start(); registry.category("main_components").add("BlockUI", BlockUiFromRegistry); - configureGui({ component: chrome.comp }); setupResponsivePlugin(this.env); }); }