[thelist] Workaround for setAttribute bug in IE7?
Matt Warden
mwarden at gmail.com
Wed Dec 13 16:23:37 CST 2006
On 12/13/06, Lee kowalkowski <lee.kowalkowski at googlemail.com> wrote:
> On 13/12/06, Matt Warden <mwarden at gmail.com> wrote:
> > See my domnode.length example. It was in the message you replied to,
> > but just in case:
> > http://lists.evolt.org/archive/Week-of-Mon-20061211/186779.html
>
> :-) Your example doesn't illustrate how using setAttribute("length",
> 4) is any better than length=4 (which I think was your original
> assertion). Because on HTML DOM objects that actually have a length
> attribute, they are read-only, both methods will fail! If it isn't
> read only, both methods would work, and yes, both methods would result
> in the creation of an attribute. Hardly the fault of a design
> decision.
Again, missing the entire point. The fact that you have to know this:
> Because on HTML DOM objects that actually have a length
> attribute, they are read-only, both methods will fail!
is my point. And here is a real-world example:
http://mwarden.f2o.org/sandbox/attributetest.htm
--
Matt Warden
Cleveland, OH, USA
http://mattwarden.com
This email proudly and graciously contributes to entropy.
More information about the thelist
mailing list