Opened 12 years ago

Closed 12 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)

Menupatch.patch (1.2 KB) - added by guest 12 years ago.
Patch to fix the problem in 0.9beta
Checkbox.patch (1.4 KB) - added by guest 12 years ago.
unmatched <input> tag in dijit.Checkbox

Download all attachments as: .zip

Change History (7)

Changed 12 years ago by guest

Attachment: Menupatch.patch added

Patch to fix the problem in 0.9beta

Changed 12 years ago by guest

Attachment: Checkbox.patch added

unmatched <input> tag in dijit.Checkbox

comment:1 Changed 12 years ago by guest

Also there is a similar problem in dijit.form.Checkbox

comment:2 Changed 12 years ago by Adam Peller

Owner: changed from bill to Douglas Hays

comment:3 Changed 12 years ago by Douglas Hays

Resolution: fixed
Status: newclosed

(In [10421]) Fixes #3932. Add terminating / to <input> tags and enclosed attributes in quotes.

comment:4 Changed 12 years ago by bill

Resolution: fixed
Status: closedreopened

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 12 years ago by bill

Resolution: fixed
Status: reopenedclosed

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.

Note: See TracTickets for help on using tickets.