> Actually, the compelling reason is that the specified attribute height
> will quickly lose sync with the actual height of the element.
>
> <iframe height="100".../>
>
> $("iframe").height( 1 ).attr("height")
> // 100... but it's height isn't 100 any more.
>
> Getting the current, "computed", value is much more useful and
> practical to everyday users. height attributes are simply a bit of
> legacy left over from ancient documents (as is bgcolor and inline
> onTYPE event handlers). If we cut the crufty legacy code we can build
> APIs that are much more cohesive and match the intentions and
> expectations of the user better.An alternative that might work here - and one that would go together with a mapping of the available attributes - is to simply deprecate the use of certain attributes (height, width, bgcolor, onTYPE, etc. come to mind off hand). It's pretty easy to do if we just point people towards the alternatives that we already provide. Then we can focus all of our energy on just making the remaining set of attributes work identically (and expectedly) across all platforms. --John -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
