Opened 12 years ago
Closed 10 years ago
#9153 closed defect (worksforme)
Behavior when not passing a second argument to dojo.query for child queries differs across browsers
| Reported by: | Shane O'Sullivan | Owned by: | Kris Zyp |
|---|---|---|---|
| Priority: | high | Milestone: | future |
| Component: | Query | Version: | 1.3.0 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description (last modified by )
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 (12)
comment:1 Changed 12 years ago by
| Milestone: | 1.3.1 → tbd |
|---|---|
| Owner: | changed from anonymous to alex |
comment:2 Changed 12 years ago by
| Milestone: | tbd → 1.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 12 years ago by
| Description: | modified (diff) |
|---|---|
| Milestone: | 1.3.1 → tbd |
| Summary: | [regression] Behavior when not passing a second argument to dojo.query for child queries differs across browsers → Behavior 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.)
comment:4 Changed 12 years ago by
| Component: | General → Query |
|---|
comment:6 Changed 11 years ago by
| Milestone: | tbd → 1.5 |
|---|
comment:7 Changed 11 years ago by
| Milestone: | 1.5 → 1.6 |
|---|
comment:8 Changed 10 years ago by
| Milestone: | 1.6 → future |
|---|
(sadly) punting seemingly abandoned ticket and meta tickets to future
comment:10 Changed 10 years ago by
| Owner: | changed from dylan to kriszyp |
|---|
comment:11 Changed 10 years ago by
| Owner: | changed from kriszyp to Kris Zyp |
|---|
comment:12 Changed 10 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Was this fixed already? I can't reproduce this.
Note: See
TracTickets for help on using
tickets.
is this a regression?