A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Why no script implements"

From WHATWG Wiki
Jump to: navigation, search
 
Line 7: Line 7:
 
Basically, the warning about how imprecise and unreliable DOM feature testing can be (
 
Basically, the warning about how imprecise and unreliable DOM feature testing can be (
 
http://dev.w3.org/html5/spec/Overview.html#dom-feature-strings ) would also apply to @implements.
 
http://dev.w3.org/html5/spec/Overview.html#dom-feature-strings ) would also apply to @implements.
 +
 +
[[Category:Justifications]]

Latest revision as of 14:34, 9 July 2013

Adding the implements attribute to scripts would allow user agents to recognize the purpose of a script, and not bother to download scripts it already had in cache, or for which it provided a native implementation.

Toby Inkster provided a pretty good argument for including it in http://lists.w3.org/Archives/Public/public-html/2009Sep/0538.html

Simon Pieters provided the more subtle counterargument in http://lists.w3.org/Archives/Public/public-html/2009Sep/0540.html

Basically, the warning about how imprecise and unreliable DOM feature testing can be ( http://dev.w3.org/html5/spec/Overview.html#dom-feature-strings ) would also apply to @implements.