dijit.Menu has X-HTML incompatibilites

[guest]

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.

[guest]

Patch to fix the problem in 0.9beta

[guest]

unmatched <input> tag in dijit.Checkbox

[guest]

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

[Douglas Hays]

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

[bill]

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.

[bill]

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.