#8102 closed defect (fixed)
dojo.query broken in Safari3.2
| Reported by: | virsir | Owned by: | alex |
|---|---|---|---|
| Priority: | high | Milestone: | 1.2.3 |
| Component: | Query | Version: | 1.2.1 |
| Keywords: | Cc: | phiggins, Adam Peller, James Burke, alex | |
| Blocked By: | Blocking: |
Description
It looks like it can not handle upperclass className properly. I am not sure whether there is other issues in safari 3.2 when querying dom nodes.
try below simple html in Safari3.2:
<script type="text/javascript" src="dojo/dojo.js">
</script>
<body>
<div class="hahaA"></div>
</body>
<script type="text/javascript">
dojo.addOnLoad(function(){
var a = dojo.query(".hahaA")[0];
alert(a)
})
</script>
Change History (7)
comment:1 Changed 11 years ago by
| Owner: | changed from anonymous to alex |
|---|
comment:2 Changed 11 years ago by
comment:3 Changed 11 years ago by
Seems suspiciously related to our fix for Safari 3.1: http://bugs.dojotoolkit.org/ticket/6252
comment:4 Changed 11 years ago by
A little more info, Safari 3.2 was just pushed to my machine (thanks, Apple) -- Several dojo.query unit tests failing in trunk:
mostly saying: SYNTAX_ERR: DOM Exception 12
eg:
dojo.is(1, dojo.query("#foo ~").length);
Also, NodeList.concat, place, splice, and orphan tests failing. Not sure if that should be a new ticket, or it is all related to some underlying thing.
comment:5 Changed 11 years ago by
| Cc: | phiggins Adam Peller James Burke alex added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:6 Changed 11 years ago by
| Milestone: | 1.3 → 1.2.3 |
|---|
comment:7 Changed 11 years ago by
| Component: | Core → Query |
|---|
Note: See
TracTickets for help on using
tickets.
Just to update on this, it seems the parser is affected by this too?
From dijit/layout/tests/test_AccordionPane.html:
dojo.query("[dojotype]").length; 15 dojo.query("[dojoType]").length; 0Though my testing comes from discovering the parser not working at all in Safari4 "dev" release. The _prog version of the above test works as expected.
Tested Safari4/dev, so not necessarily a bug yet, but seems identical to this ticket (mixed case query selections?)