Opened 10 years ago
Closed 5 years ago
#13738 closed defect (patchwelcome)
dojo.attr(node, 'required') inconsistent in different browsers
Reported by: | tanneman | Owned by: | Eugene Lazutkin |
---|---|---|---|
Priority: | high | Milestone: | 1.13 |
Component: | HTML | Version: | 1.6.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
The command: dojo.attr(node, 'required') has different results on browsers, FF6 always returns a boolean while IE8/9 returns a string. See the table below for the output.
IE8-IE9 | FF6 | |
<input required="true"> | 'true' | true |
<input required="false"> | 'false' | true |
<input> | null | false |
Change History (4)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
Component: | General → HTML |
---|---|
Owner: | set to Eugene Lazutkin |
Summary: | dojo.attr inconsistent in different browsers → dojo.attr(node, 'required') inconsistent in different browsers |
comment:3 Changed 9 years ago by
We may need to introduce a pre/post-processors for dojo.attr()
to handle this and similar tickets. My point is it will be a bigger change under the hood than expected.
comment:4 Changed 5 years ago by
Milestone: | tbd → 1.12 |
---|---|
Resolution: | → patchwelcome |
Status: | new → closed |
Given that no one has shown interest in creating a patch in the past 4+ years, I'm closing this as patchwelcome.
Note: See
TracTickets for help on using
tickets.
Note that the behavior is correct for other attributes, it only occurs if its the 'required' attribute