Opened 13 years ago

Last modified 11 years ago

#9153 closed defect

Behavior when not passing a second argument to dojo.query for child queries differs across browsers — at Version 3

Reported by: Shane O'Sullivan Owned by: alex
Priority: high Milestone: future
Component: Query Version: 1.3.0
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by bill)

When a query for direct descendents is executed, e.g.

dojo.query("> .someClass")

is executed, and a second argument is not passed, the behavior is not consistent across broswers.

In FF3, an empty NodeList? is returned, as would be expected. However in IE7 an Error is thrown.

Change History (3)

comment:1 Changed 13 years ago by Adam Peller

Milestone: 1.3.1tbd
Owner: changed from anonymous to alex

is this a regression?

comment:2 Changed 13 years ago by bill

Milestone: tbd1.3.1
Summary: Behavior when not passing a second argument to dojo.query for child queries differs across browsers[regression] Behavior when not passing a second argument to dojo.query for child queries differs across browsers

Yes. This works in 1.2, fails in 1.3 (and trunk).

comment:3 Changed 13 years ago by bill

Description: modified (diff)
Milestone: 1.3.1tbd
Summary: [regression] Behavior when not passing a second argument to dojo.query for child queries differs across browsersBehavior when not passing a second argument to dojo.query for child queries differs across browsers

Oops, I actually meant to write the above comment into #9071, not this ticket.

This isn't a regression, it failed on IE even in 1.2.

(I tested by loading dojo/tests/_base/query.html and running the above command in the firebug lite console.)

Note: See TracTickets for help on using tickets.