Benoit Socias
abbc068dbe
Before this commit tips could be revived after being destroyed if a resize event occurred, because the resize was being debounced and could trigger a request to rebuild the bubble mode of the tip. After this commit the resize debounce is cancelled if the tip was destroyed in the meantime. However another unidentified reason still manages to trigger an asynchronous re-creation of the tip after destroy() is called, even though all timeouts are cleared. The following remaining sequence has been identified: - mouseenter.anchor is triggered: but this is disabled during destroy - it calls _to_info_mode() which registers the timer_in timeout: but this timeout is cleared during destroy - it calls _build_info_mode() which registers the _transitionEndTimer timeout: but this timeout is cleared during destroy - it calls _onTransitionEnd() which calls _updatePosition() which revives the tip Therefore an additional guard is added to prevent _updatePosition() from being executed if destroy() was called. Note that the mouseleave > to_bubble_mode chain being symmetrical to this one, it is likely that it could also happen. task-2728994 (was task-2675252) X-original-commit: 635675398c153e123e62dd30a35ba23a29503c70 Part-of: odoo/odoo#83692
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials