dojo.attr() cannot retrieve value="" attributes on form elements in IE 6

[paulprince]

Returns null value instead.

Retrieving other attributes seems to work.

Not sure in what other situations this bug might be triggered.

phiggins tested against trunk... attaching his modifications to my test case.

[paulprince]

phiggins'-provided simple test case

[bill]

FYI I assume this is why CheckBox?.js has the code:

if(this.value == ""){
	this.value = "on";
}

(because the parser is reporting that the user has specified a value initialization parameter when really they haven't)

[david]

The problem seems to be with the IE's getAttributeNode. When you ask it for the attribute node value, the specified property is set to false (which is wrong because value is set to a non-default value). It gets called from hasAttr which gets called by attr on line 1254:

return (typeof attrValue == 'boolean' || typeof attrValue == 'function') ? attrValue
   : (d.hasAttr(node, name) ? node.getAttribute(name) : null);

I don't know if it is necessary to call d.hasAttr(...) in this case. Is there some advantage over changing it to:

return (typeof attrValue == 'boolean' || typeof attrValue == 'function') ? attrValue
   : node.getAttribute(name);

Please advise.

[bill]

as per today's meeting, punting these core bugs

[dylan]

I haven't had time to tackle this one... no obvious solution in my eyes, so marking as future unless there are objections.

[Eugene Lazutkin]

Related to #8991.

[Eugene Lazutkin]

(In [17931]) html: cleaning dojo.attr() according to James' suggestions (thx, James Burke!), removing the "whitelist" of attributes, adding a test for "value", updating tests to account for non-standard IE6/7 behavior, !strict, fixes #8991, fixes #7355.