diff options
| author | qsm-odoo <qsm@odoo.com> | 2017-12-28 14:41:25 +0100 |
|---|---|---|
| committer | qsm-odoo <qsm@odoo.com> | 2018-08-13 18:42:52 +0200 |
| commit | b56e647f2c540d34860cdee8a6adf0785ce3b8ef (patch) | |
| tree | 1991522bc27e7c2ee2b80236bd967590f75c16f8 /odoo/addons/base/data | |
| parent | 4dce6cc98b2b95a00249ac29245305e08f288e6c (diff) | |
[REF] web_editor, website: improve animations' restart
- Before this commit, when we asked to (re)start animations on an
element, we checked the animations to be started on the element
and started them after destroying the animations with the same
name which were already running on that element. This is in fact
not correct. Indeed, if an animation was running on element but
that the conditions that made the animation start are now gone,
asking to restart the animations on that element should destroy
the deprecated ones. (e.g. an animation "A" is to be started on
all elements which have a class "a", if we remove the class "a"
on an element then restart animations, the animation "A" should
be destroy). The implementation is in fact even simpler: when
asking a restart, a full stop is performed then a simple start.
Note: this does not need to be a fix as multiple animations on
a same element was recently introduced and the described case
never occurs with current features.
- When stopping the animations on an element, stops the animations
of all its descendants too.
- Add an helper method in the `SnippetOption` class to restart the
animations running on the `$target` element.
Diffstat (limited to 'odoo/addons/base/data')
0 files changed, 0 insertions, 0 deletions
