Opened 14 years ago
Closed 14 years ago
#3932 closed defect (fixed)
dijit.Menu has X-HTML incompatibilites
Reported by: | guest | Owned by: | Douglas Hays |
---|---|---|---|
Priority: | high | Milestone: | 1.0 |
Component: | Dijit | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
When using Firefox 2.0.6 with a content type of "application/xhtml+xml" and working with X-HTML the dijit.MenuItem? and dijit.MenuSeparator? fail to parse, both problems a very simple changes to the templateString.
Attachments (2)
Change History (7)
Changed 14 years ago by
Attachment: | Menupatch.patch added |
---|
comment:2 Changed 14 years ago by
Owner: | changed from bill to Douglas Hays |
---|
comment:3 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 Changed 14 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
The change to convert
<input>
to
<input/>
is causing two input tags to show up on IE (use IE Dom Inspector to see). Unfortunately
<input> </input>
also causes an extra tag to show up. Not sure what to do about that but let's be careful not to break IE just to support the relatively rare xhtml+xml type.
comment:5 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Hmm, sorry, my mistake, <input/> doesn't seem to cause any ill effects (although<input></input> does make a second node on IE). Got confused by the hidden node for canonical vs. displayed value.
Patch to fix the problem in 0.9beta