Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Animated Dataview creates two DOM elements with same ID #1632
Found: 4.8.0 (prior to release)
The animated dataview UX plugin now throws an exception while the store filter causes items to be redrawn. The fade-out animation's callback attempt to get the faded out element results in a query returning two different DOM elements, and an error is triggered because the fetched ID DOM element differs from which one is cached in ExtJS (during
The temporary double-ID DOM element should be avoided, or the animation callback should reliably fetch the target that needs to be removed from DOM to address the issue; being the former preferred, the latter alternative is known to be feasible at this moment.
The drawback of changing how the animated/faded DOM element is that it will require replacing the whole
Unfortunately the most feasible way was to just fix how the animation fetched the target dom element; meant just one line change in the code, although the whole
The way the plugin is written allows little to no advantage on overriding. Keeping the original file instead of fully replacing it will allow to identify whenever Sencha fixes their version of the plug in.
Notice: Sencha's examples have one for the animated dataview which has not been working since, at least, version 6.0.0 release. The URL for 6.7.0 would be: https://examples.sencha.com/extjs/6.7.0/examples/classic/view/animated-dataview.html
It breaks because it makes references to several non-existing resources; before it failed during
Without that example working, there's little to do as to create a new Sencha forum thread. An existing thread was found and bumped but it was a little unrelated, and also for Ext JS 5. A new thread has been created for Ext JS 6, and specific to this issue: Ext.ux.DataView.Animated example broken and UX issue.