[FIXED][2.2.1/3.0rc2] Ext.DomQuery returns invalid results when parsing XML in Opera

[xpuu]

This is wrong only when using "parent > child" syntax...
Btw. when using this syntax on normal DOM tree everything works just perfect...

Javascript

Ext.Ajax.request({
        url: 'test.xml',
        success: function (response) {
            // should display 2, but displays 0 in Opera
            alert(Ext.DomQuery.select('data > item', response.responseXML).length);
        }
});

XML file

<data>
    <item>1</item>
    <item>2</item>
</data>

[xpuu]

Broken in latest 2 and in RC 3 as well...

[evant]

This is fixed in both SVN versions. I don't see why it would be broken for RC2 though, since it was fixed a while back. Perhaps we need to look at how it's being built.

[xpuu]

Thanks very much for checking this for me. It would be nice to have always a chance to download (or to reach using cachefly) latest ext-all.js and ext-all-debug.js with latest fixes from SVN.

[tryanDLS]

Thanks very much for checking this for me. It would be nice to have always a chance to download (or to reach using cachefly) latest ext-all.js and ext-all-debug.js with latest fixes from SVN.

You can purchase a support subscription or wait til the next RC.