04.02.2013 Views

HTML 5 Draft Standard - 30 July 2009 - Huihoo

HTML 5 Draft Standard - 30 July 2009 - Huihoo

HTML 5 Draft Standard - 30 July 2009 - Huihoo

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

40<br />

Web IDL<br />

The IDL fragments in this specification must be interpreted as required for conforming IDL<br />

fragments, as described in the Web IDL specification. [WEBIDL]<br />

Unless otherwise specified, if a DOM attribute that is a floating point number type (float) is<br />

assigned an Infinity or Not-a-Number value, a NOT_SUPPORTED_ERR exception must be<br />

raised.<br />

Unless otherwise specified, if a method with an argument that is a floating point number<br />

type (float) is passed an Infinity or Not-a-Number value, a NOT_SUPPORTED_ERR exception<br />

must be raised.<br />

JavaScript<br />

Some parts of the language described by this specification only support JavaScript as the<br />

underlying scripting language. [ECMA262]<br />

Media Queries<br />

Note: The term "JavaScript" is used to refer to ECMA262, rather than the<br />

official term ECMAScript, since the term JavaScript is more widely known.<br />

Similarly, the MIME type used to refer to JavaScript in this specification is<br />

text/javascript, since that is the most commonly used type, despite it<br />

being an officially obsoleted type (page 24) according to RFC 4329.<br />

[RFC4329]<br />

Implementations must support some version of the Media Queries language. [MQ]<br />

This specification does not require support of any particular network transport protocols, style<br />

sheet language, scripting language, or any of the DOM and WebAPI specifications beyond those<br />

described above. However, the language described by this specification is biased towards CSS<br />

as the styling language, JavaScript as the scripting language, and HTTP as the network protocol,<br />

and several features assume that those languages and protocols are in use.<br />

Note: This specification might have certain additional requirements on<br />

character encodings, image formats, audio formats, and video formats in the<br />

respective sections.<br />

2.2.2 Extensibility<br />

Vendor-specific proprietary extensions to this specification are strongly discouraged. Documents<br />

must not use such extensions, as doing so reduces interoperability and fragments the user base,<br />

allowing only users of specific user agents to access the content in question.<br />

If markup extensions are needed, they should be done using XML, with elements or attributes<br />

from custom namespaces. If DOM extensions are needed, the members should be prefixed by<br />

vendor-specific strings to prevent clashes with future versions of this specification. Extensions<br />

must be defined so that the use of extensions does not contradict nor cause the<br />

non-conformance of functionality defined in the specification.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!