Success! Looks like we've fixed this one. According to our records the fix was applied for
a recent build.
[ST 2.2.1] Ext.DomQuery.is multiple bugsUnfortunately fix of&nbsp;<b style="ma
Unfortunately fix for TOUCH-4126 introduced additional problems, making behavior of Ext.DomQuery.is in some cases extremely destructive.
Following things do not work:
Here comes my fiddle illustrating all these problems and tests for them
- passing element id will result in that element being removed from DOM
- checking elements outside DOM is still broken in some cases
- function do not support Array as first argument as specified in documentation
Also this fiddle includes fix for all of them: first two are errors in code - we shouldn't query parentNode before we convert el from string to element and we should pass root to this.select if we have any
Last one was implemented on my own, trying to keep code close to framework style
Thanks for the report! I have opened a bug in our bug tracker.