Opened 14 years ago
Closed 14 years ago
#3438 closed defect (fixed)
0.9: dojoType versus dojotype browser oddness.
Reported by: | Jared Jurkiewicz | Owned by: | alex |
---|---|---|---|
Priority: | high | Milestone: | 0.9beta |
Component: | General | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
0.9: dojoType versus dojotype browser oddness.
In Firefox, if you accidentally type dojotype= instead of dojoType=, the widgets still work. If you do the same in IE, the widget never instantiates. It appears the query/parser behaves differently with case senstivity between the browsers. It would be good if this didn't matter, as I spent an hour just now tracking this down in a simple app.
Change History (2)
comment:1 Changed 14 years ago by
Component: | Dijit → General |
---|---|
Owner: | changed from bill to alex |
comment:2 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Hmm, I agree that it would be good if that were consistent but I'm not sure if it's practical. In any case the only two calls related to dojoType are node.getAttribute() and dojo.query(). Passing to Alex to see what he thinks. I thought that attribute names are supposed to be case insensitive (except for XHTML).