diff options
| author | Robot Odoo <xmo+roboto@odoo.com> | 2019-01-15 15:30:01 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-01-15 15:30:01 +0100 |
| commit | dc12f7e06c4c7d10f17aa56e4ba482a9b126a0ce (patch) | |
| tree | 398a414edd3ff9434ea463e57154e5c946e22d89 /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js | |
| parent | e24ab17d38fb049404f04112990e8b2fe1dd7727 (diff) | |
| parent | 070bd40f64da3b16fbfce42de867aaf9e149d64a (diff) | |
[MERGE/FIX] web_tour,*: remove step delay in tests
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). It also adapts some tours that didn't pass
anymore without the delay, and it fixes a bug in the kanban view that
has been spotted thanks to the delay removal.
closes odoo/odoo#30106
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions
