normalize handling of "value" attribute in the parser

[bill]

Ideally the parser should differentiate between <input> and <input value="">, as the latter (but not the former) should override a default value defined in the widget's prototype like value:"default".

However, on IE we haven't figured out a way to differentiate these two cases without parsing outerHTML, so maybe it's best to just normalize all browsers to interpret <input> as <input value="">

[bill]

doug's patch to use outerHTML

[bill]

parser test w/test case added for value attribute

[bill]

(In [10005]) Write total parse time to console. Refs #4033 (lets us try various algorithms and test their performance)

[Douglas Hays]

IE patch to parser to parse outerHTML and only process attributres found

[bill]

Looks good to me. I don't see any performance differences on IE7. IE6 has a bunch of performance issues that we need to look but unrelated to this change.

[bill]

OK, the patch above turned out not to work, weird stuff like losing checked status for an <input type="checkbox" checked>. Punting to 1.0. We think the current workaround is good enough. (The limitation is that the default value must be "" for all widgets except checkbox, where the default value must be "on")

[Douglas Hays]

Deferring since the current workaround is still holding its own...

[bill]

Let's just close this. The current "workaround" requires that the default value of "value" is "", but I'm willing to consider that as a known (and accepted) limitation of the dojo parser.

[alex]

Milestone 2.0 deleted