W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2010

hixie: Make it clear that disabling a feature should truly remove it, not just stub it out. (whatwg r4693)

From: poot <cvsmail@w3.org>
Date: Fri, 12 Feb 2010 22:09:44 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100212130944.8200B2BBFD@toro.w3.mag.keio.ac.jp>
hixie: Make it clear that disabling a feature should truly remove it,
not just stub it out. (whatwg r4693)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3744&r2=1.3745&f=h
http://html5.org/tools/web-apps-tracker?from=4692&to=4693

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3744
retrieving revision 1.3745
diff -u -d -r1.3744 -r1.3745
--- Overview.html	12 Feb 2010 09:50:32 -0000	1.3744
+++ Overview.html	12 Feb 2010 13:09:27 -0000	1.3745
@@ -2171,6 +2171,16 @@
 
   </div>
 
+  <p>When support for a feature is disabled (e.g. as an emergency
+  measure to mitigate a security problem, or to aid in development, or
+  for performance reasons), user agents must act as if they had no
+  support for the feature whatsoever, and as if the feature was not
+  mentioned in this specification. For example, if a particular
+  feature is accessed via an attribute in a Web IDL interface, the
+  attribute itself would be omitted from the objects that implement
+  that interface &mdash; leaving the attribute on the object but
+  making it return null or throw an exception is insufficient.</p>
+
   <hr><p>When vendor-neutral extensions to this specification are needed,
   either this specification can be updated accordingly, or an
   extension specification can be written that overrides the
Received on Friday, 12 February 2010 13:10:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:17 GMT