Login Register
Home » Support » Forums » Dojo Core (dojo.*, 0.9+) » Dojo Core Support » dojo.query('E[a]') broken on IE7?

dojo.query('E[a]') broken on IE7?

Submitted by rfong_trpz on Sat, 10/04/2008 - 16:31.

Using dojo 1.2, I have a DOM document with something like this:

When I run dojo.query('CHERRY[color]', myDoc) I get back the CHERRY element on Fx3. On IE7, I get nothing. I have to remove the attribute selector on IE7 to get this node, but this is less-specific.

Have other people noticed this problem too? Thanks.

‹ Source code debugging and enabling logging for custom build Problem with custom build and extra module ›

Darn form removed my xml

Submitted by rfong_trpz on Sun, 10/05/2008 - 20:48.

Darn form removed my xml again. :) Here is what I wrote as a sample.

<FRUIT>
    <CHERRY color="red"/>
</FRUIT>

dojo.query('E[a="v"]',

Submitted by rfong_trpz on Sun, 10/05/2008 - 21:11.

dojo.query('E[a="v"]', myDoc); doesn't work on IE7 either. I get a JS error "line 17, char 59013; Wrong number of arguments or invalid property assignment" when it is executed. In this example this is equivalent to calling dojo.query('CHERRY[color="red"]');

verified

Submitted by alex on Sun, 10/05/2008 - 23:12.

I've verified this issue and filed it as bug # 7796. Sorry for the inconvenience. Depending on when the fix gets in, this will be resolved for either Dojo 1.2.0 or (at the latest) 1.2.1.

Regards

--
President, The Dojo Foundation

To clarify, this won't make

Submitted by dante on Mon, 10/06/2008 - 01:18.

To clarify, this won't make it into 1.2, as the patch landed post-1.2-snapshot. It will be 1.3, or potentially 1.2.1 depending on the severity of the bug. 1.3 is not far off, and this isn't a regression per sae, so it will likely be 1.3 when the fix is ok.

1.2 dojo.query('*', myDoc) also fails on IE7

Submitted by rfong_trpz on Mon, 10/06/2008 - 21:22.

I found another bug in dojo.query. I have newline text nodes and a real element within part of my XML. A call to dojo.query('*', cherryNode); in Fx3 works fine & returns the only proper child node, such as PITTED in my sample below. The call in IE7 returns 0 nodes though.

<FRUIT>
    <CHERRY color="red">\n<PITTED state="true"/>\n</CHERRY>
</FRUIT>

Dante & Alex, thank you for logging bug 7796 for my prior-posted issue!