summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_controller.js
diff options
context:
space:
mode:
authorAaron Bohy <aab@odoo.com>2019-01-08 11:06:50 +0000
committerAaron Bohy <aab@odoo.com>2019-01-14 11:29:53 +0000
commit6f7f235799128dc650b3f94994aa9a1a55a1f033 (patch)
tree33981603d48eb04e08fe6a0f9fddfbba92c88808 /addons/web/static/src/js/views/basic/basic_controller.js
parente24ab17d38fb049404f04112990e8b2fe1dd7727 (diff)
[FIX] web_tour: remove delay in test mode
For historical reasons, the tour manager executed each step of tour in a setTimeout (10ms). When a step could be executed (i.e. when its trigger selector has a match in the DOM), the element matching its trigger was saved as a jQuery element (the $anchor), and in the setTimeout, the action (e.g. click) was performed on that element. However, it could happen that, after the delay, the $anchor was no longer in the DOM, either because 1) the tip selector had no match anymore, meaning that the element had been removed from the DOM meanwhile 2) the tip selector still had a match in the DOM, but that element had been rerendered meanwhile Case 2) occured sometimes when the main_flow_tour was executed in community, when trying to open a Manufacturing Order after having reloaded the Manufacturing Order list view (because the row of the order to open that was saved as $anchor was the one of the list before the reload, and that list was re-rendered during the delay). This rev. removes the default delay of 10ms, but the feature is kept such that one can still manually run a tour slowly (e.g. to debug or to make a demo).
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions