Open IPTV Forum
Feature Package Specification
Volume 5a - Web Standards TV profile
[V1.0.0] - [2013-04-29]
Postal Address
Open IPTV Forum support office
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 43 83
Fax: +33 4 92 38 52 90
Internet
http://www.oipf.tv
Disclaimer
The Open IPTV Forum accepts no liability whatsoever for any use of this document.
Copyright Notification
No part may be reproduced except as authorized by written permission.
Any form of reproduction and/or distribution of these works is prohibited.
Copyright 2013 © Open IPTV Forum e.V.
All rights reserved.
This document is a profile of HTML, CSS and other related web technologies aimed to connected TV services and devices. Its goal is to describe a common profile that can be relied on by content and service providers and implemented by manufacturers. It does not describe extensions or modification to any of the referenced technologies but only tries to define a subset of web standards that are suitable and useful for TV deployments and at the same time stable enough to provide a good degree of confidence that real interoperability can be achieved. It may add clarifications and/or additional constraints where these are needed due to the nature of target deployment environment.
This document only describe a minimum subset of web technology that a Terminal compliant with this profile is required to support. This does not preclude terminals to support more technologies than the ones described in this profile.
This document will be updated over time, as maturity of different standards (now work in progress) increase and/or new web standards are defined.
This section is non-normative.
This specification is aimed to TV terminals that implement a browser based application environment. Applications running in such environment are authored using a set of languages commonly referred to as "web technologies" or "web standards". This document lists the minimum set of languages that shall be supported by a Terminal conforming to this specification. A terminal may support more languages than the ones listed in this document.
To avoid fragmentation and enhance interoperability with other web technologies-based devices and eco-systems, this specification tries not to diverge from any of the referenced specifications it relays on. In some exceptional cases though, this specification may decide to intentionally diverge from the referenced specifications. Such differences will be explicitly noted throughout the document.
This document is organized as follows: the main body includes a list of references to specifications that this profile relies on and that are considered necessary to enable an enhanced user experience. Annex A contains instead a detailed list of which features for each specification are considered stable enough and therefore can be safely supported by terminals and used by application developers. Such tables will be updated in future revisions of this document as maturity of the various specification evolve. Support tables are omitted for those specifications that are required to be fully supported.
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this specification are to be interpreted as described in [RFC2119].
This document references specification that some times are still work in progress. All features marked as "at risk" in such referenced specification SHALL be considered as OPTIONAL to support unless this profile explicitly mandate support for them.
The HTML5 [HTML5-20121217] specification defines conformance requirements for user-agents and documents. Applications and Authoring tools SHALL comply with conformance requirements for documents unless differently specified in section A.1 HTML5 profile. Terminals SHALL comply with conformance requirements for user agents unless differently specified in section A.1 HTML5 profile; in particular a Terminal SHALL support the HTML syntax and the XHTML syntax for HTML documents as defined in [HTML5-20121217].
Terminals SHALL support CSS Basic User Interface [CSS3UI-20120117] as profiled in section section B.1 CSS Basic User Interface
Terminals SHALL support CSS 2.1 [CSS21-20110607]
Terminals SHALL support CSS Color Module Level 3 [CSS3COLOR-20110607].
Terminals SHALL support CSS Image Values and Replaced Content [CSS3-IMAGES-20120417] as profiled in section section B.2 CSS Image Values and Replaced Content
Terminals SHALL support CSS Backgrounds and Borders [CSS3-BG-20120724] as profiled in section section B.3 CSS Backgrounds and Borders
Terminals SHALL support CSS Selectors Level 3 [SELECTORS-LEVEL-3-20110929].
Terminals SHALL support CSS Media Queries [CSS3-MEDIAQUERIES-20120619].
Terminals SHALL support CSS Multi-column Layout [CSS3COL-20110412].
Terminals SHALL support CSS Flexible Box Layout [FLEXBOX-20120918]
Terminals SHOULD support CSS Conditional Rules Module Level 3 [CSS3-CONDITIONAL-20121213]
Terminals SHALL support the [CSS3-FONTS-20130212] as profiled in section section B.4 CSS Fonts Module Level 3
Terminals SHALL support the Web Open Font Format [WOFF-20121213].
Applications can link to [WOFF-20121213] fonts via a @font-face
rule ([CSS3-FONTS-20130212]).
Terminals SHALL support CSS Text [CSS3TEXT-20121113] as profiled in section section B.5 CSS Text Level 3
Terminals SHALL support the CSS Transforms [CSS3-TRANSFORMS-20120911] as profiled in section section B.6 CSS Transforms
Terminals SHALL support CSS Transitions [CSS3-TRANSITIONS-20130212] as profiled in section section B.7 CSS Transitions
Terminals SHALL support CSS Animations [CSS3-ANIMATIONS-20130219]
Terminals SHALL support Canvas 2D [CANVAS-2D-20121217] as profiled in section section C.3 Canvas 2D.
Terminals SHALL support the event model defined in [DOM-LEVEL-3-EVENTS-20120906].
In order to support legacy content, Terminals SHALL support also the legacy attributeskeyCode
and charCode
as defined in Appendix B of [DOM-LEVEL-3-EVENTS-20120906].
Applications SHALL NOT rely on these attributes and SHALL use the new event model as defined in DOM3 Events. Values used for the keyCode
property are implementation specific, but SHALL be exposed to the application through the constants below defined on the KeyboardEvent
interface.
These constants SHALL also be available via a KeyEvent
interface. For example VK_OK can be accessed as KeyEvent
.VK_OK.
Virtual Keycode Constants |
---|
VK_UNDEFINED |
VK_CANCEL |
VK_BACK_SPACE |
VK_TAB |
VK_CLEAR |
VK_ENTER |
VK_SHIFT |
VK_CONTROL |
VK_ALT |
VK_PAUSE |
VK_CAPS_LOCK |
VK_KANA |
VK_FINAL |
VK_KANJI |
VK_ESCAPE |
VK_CONVERT |
VK_NONCONVERT |
VK_ACCEPT |
VK_MODECHANGE |
VK_SPACE |
VK_PAGE_UP |
VK_PAGE_DOWN |
VK_END |
VK_HOME |
VK_LEFT |
VK_UP |
VK_RIGHT |
VK_DOWN |
VK_COMMA |
VK_PERIOD |
VK_SLASH |
VK_0 |
VK_1 |
VK_2 |
VK_3 |
VK_4 |
VK_5 |
VK_6 |
VK_7 |
VK_8 |
VK_9 |
VK_SEMICOLON |
VK_EQUALS |
VK_A |
VK_B |
VK_C |
VK_D |
VK_E |
VK_F |
VK_G |
VK_H |
VK_I |
VK_J |
VK_K |
VK_L |
VK_M |
VK_N |
VK_O |
VK_P |
VK_Q |
VK_R |
VK_S |
VK_T |
VK_U |
VK_V |
VK_W |
VK_X |
VK_Y |
VK_Z |
VK_OPEN_BRACKET |
VK_BACK_SLASH |
VK_CLOSE_BRACKET |
VK_NUMPAD0 |
VK_NUMPAD1 |
VK_NUMPAD2 |
VK_NUMPAD3 |
VK_NUMPAD4 |
VK_NUMPAD5 |
VK_NUMPAD6 |
VK_NUMPAD7 |
VK_NUMPAD8 |
VK_NUMPAD9 |
VK_MULTIPLY |
VK_ADD |
VK_SEPARATER |
VK_SUBTRACT |
VK_DECIMAL |
VK_DIVIDE |
VK_F1 |
VK_F2 |
VK_F3 |
VK_F4 |
VK_F5 |
VK_F6 |
VK_F7 |
VK_F8 |
VK_F9 |
VK_F10 |
VK_F11 |
VK_F12 |
VK_DELETE |
VK_NUM_LOCK |
VK_SCROLL_LOCK |
VK_PRINTSCREEN |
VK_INSERT |
VK_HELP |
VK_META |
VK_BACK_QUOTE |
VK_QUOTE |
VK_RED |
VK_GREEN |
VK_YELLOW |
VK_BLUE |
VK_GREY |
VK_BROWN |
VK_POWER |
VK_DIMMER |
VK_WINK |
VK_REWIND |
VK_STOP |
VK_EJECT_TOGGLE |
VK_PLAY |
VK_RECORD |
VK_FAST_FWD |
VK_PLAY_SPEED_UP |
VK_PLAY_SPEED_DOWN |
VK_PLAY_SPEED_RESET |
VK_RECORD_SPEED_NEXT |
VK_GO_TO_START |
VK_GO_TO_END |
VK_TRACK_PREV |
VK_TRACK_NEXT |
VK_RANDOM_TOGGLE |
VK_CHANNEL_UP |
VK_CHANNEL_DOWN |
VK_STORE_FAVORITE_0 |
VK_STORE_FAVORITE_1 |
VK_STORE_FAVORITE_2 |
VK_STORE_FAVORITE_3 |
VK_RECALL_FAVORITE_0 |
VK_RECALL_FAVORITE_1 |
VK_RECALL_FAVORITE_2 |
VK_RECALL_FAVORITE_3 |
VK_CLEAR_FAVORITE_0 |
VK_CLEAR_FAVORITE_1 |
VK_CLEAR_FAVORITE_2 |
VK_CLEAR_FAVORITE_3 |
VK_SCAN_CHANNELS_TOGGLE |
VK_PINP_TOGGLE |
VK_SPLIT_SCREEN_TOGGLE |
VK_DISPLAY_SWAP |
VK_SCREEN_MODE_NEXT |
VK_VIDEO_MODE_NEXT |
VK_VOLUME_UP |
VK_VOLUME_DOWN |
VK_MUTE |
VK_SURROUND_MODE_NEXT |
VK_BALANCE_RIGHT |
VK_BALANCE_LEFT |
VK_FADER_FRONT |
VK_FADER_REAR |
VK_BASS_BOOST_UP |
VK_BASS_BOOST_DOWN |
VK_INFO |
VK_GUIDE |
VK_TELETEXT |
VK_SUBTITLE |
VK_BACK |
VK_MENU |
VK_PLAY_PAUSE |
Screen
interface or extensions to the Window
interface to obtain the width of the viewport through script. Future versions of this profile may mandate support for this specification, once it reaches an higher level of maturity.Terminals SHALL support the XMLHttpRequest API [XHR-20121206] as profiled in section section C.1 XMLHttpRequest
Terminals SHALL support the Web Messaging API [POSTMSG-20120501].
Terminals SHALL support the Web Socket API [WEBSOCKETS-API-20120920].
Terminals SHALL support the Web Workers API [WEBWORKERS-20120501] as profiled in section section C.2 Web Workers
Terminals SHALL support the Server-Sent Events API [SSE-20121211].
Terminals SHALL support the Web Storage API [WEBSTORAGE-20111208].
src
attribute of the <video>
element), it MAY include a Fragment Identifier [RFC3986]. The semantics of such fragments for resources of type audio/*, image/* and video/* are defined in [MEDIA-FRAGS-20120925].
Terminals SHALL support temporal clipping based on Normal Play Time as defined in section 4.2.1 of the Media Fragments URI specification [MEDIA-FRAGS-20120925].
This section is non-normative.
This section provides some guidelines about the recommended minimum memory requirements of some of the specifications referenced by this document.
Feature | Memory requirement | Comment |
---|---|---|
Downloadable fonts [WOFF-20121213] |
|
It is recommended to cache WOFF packages for for a better user experience. |
Web Storage [WEBSTORAGE-20111208] |
|
Terminals may provide methods to free-up memory as described in [WEBSTORAGE-20111208] |
Cookies [COOKIES] |
|
Terminals SHALL support all features marked as "Yes" in the "Mandatory" column; if restrictions apply, the feature support is indicated as "Partial" and the "Comment" column provide a description of the normative requirements. Support for all features marked as "No" is OPTIONAL.
Note that specifications that are required to be fully supported don't have a related support table in this section.
This section lists HTML elements that are either new HTML5 elements or elements already defined in HTML4 and now re-defined in HTML5. Some of the HTML4 elements have a slightly modified meanings in HTML5 to better reflect how they are used on the Web or to make them more useful.
Element name | Description (INFORMATIVE) | Mandatory | Comment |
---|---|---|---|
<body>
|
The body element of a document is the first child of the html element that is either a body element or a frameset element. If there is no such element, it is null.
|
Yes | |
<base>
|
The base element allows authors to specify the document base URL for the purposes of resolving relative URLs, and the name of the default browsing context for the purposes of following hyperlinks. The element does not represent any content beyond this information.
|
Yes | |
<meta>
|
The meta element represents various kinds of metadata that cannot be expressed using the title , base , link , style , and script elements.
|
Yes | |
<style>
|
The style element allows authors to embed style information in their documents.
|
Partial |
Support for the scoped attribute is OPTIONAL.
|
<br>
|
The br element represents a line break.
|
Yes | |
<div>
|
The div element has no special meaning at all. It represents its children. It can be used with the class , lang , and title attributes to mark up semantics common to a group of consecutive elements.
|
Yes | |
<h1>
<h2>
<h3>
<h4>
<h5>
<h6>
|
The div element has no special meaning at all. It represents its children. It can be used with the class, lang, and title attributes to mark up semantics common to a group of consecutive elements. | Yes | |
<html>
|
The html element represents the root of an HTML document.
|
Yes | |
<iframe>
|
The iframe element represents a nested browsing context.
|
Partial |
Support for the sandbox , srcdoc and seamless attributes is OPTIONAL.
|
<img>
|
An img element represents an image.
|
Yes | |
<li>
|
The li element represents a list item.
|
Yes | |
<link>
|
The link element allows authors to link their document to other resources.
|
Partial |
|
<ol>
|
The ol element represents a list of items, where the items have been intentionally ordered, such that changing the order would change the meaning of the document.
|
Yes | |
<option>
|
The option element represents an option in a select element or as part of a list of suggestions in a datalist element.
|
Yes | |
<p>
|
The p element represents a paragraph.
|
Yes | |
<pre>
|
The pre element represents a block of preformatted text, in which structure is represented by typographic conventions rather than by elements.
|
Yes | |
<dl>
|
The dl element represents an association list consisting of zero or more name-value groups (a description list).
|
Yes | |
<dt>
|
The dt element represents the term, or name, part of a term-description group in a description list (dl element).
|
Yes | |
<dd>
|
The dd element represents the description, definition, or value, part of a term-description group in a description list (dl element).
|
Yes | |
<em>
|
The em element represents stress emphasis of its contents.
|
Yes | |
<s>
|
The s element represents contents that are no longer accurate or no longer relevant.
|
Yes | |
<q>
|
The q element represents some phrasing content quoted from another source.
|
Yes | |
<dfn>
|
The dfn element represents the defining instance of a term.
|
Yes | |
<abbr>
|
The abbr element represents an abbreviation or acronym, optionally with its expansion.
|
Yes | |
<code>
|
The code element represents a fragment of computer code.
|
Yes | |
<samp>
|
The samp element represents (sample) output from a program or computing system.
|
Yes | |
<var>
|
The var element represents a variable
|
Yes | |
<kbd>
|
The kbd element represents user input (typically keyboard input, although it may also be used to represent other input, such as voice commands).
|
Yes | |
<sub>,<sub>
|
The sup element represents a superscript and the sub element represents a subscript.
|
Yes | |
<u>
|
The u element represents a span of text with an unarticulated, though explicitly rendered, non-textual annotation, such as labeling the text as being a proper name in Chinese text (a Chinese proper name mark), or labeling the text as being misspelt.
|
Yes | |
<bdi>
|
The bdi element represents a span of text that is to be isolated from its surroundings for the purposes of bidirectional text formatting.
|
No | |
<bdo>
|
The bdo element represents explicit text directionality formatting control for its children. It allows authors to override the Unicode bidirectional algorithm by explicitly specifying a direction override.
|
Yes | |
<ins>
|
The ins element represents an addition to the document.
|
Yes | |
<del>
|
The del element represents a removal from the document.
|
Yes | |
<object>
|
The object element can represent an external resource, which, depending on the type of the resource, will either be treated as an image, as a nested browsing context, or as an external resource to be processed by a plugin.
|
Yes | |
<param>
|
The param element defines parameters for plugins invoked by object elements. It does not represent anything on its own.
|
Yes | |
<map>
|
The map element, in conjunction with any area element descendants, defines an image map. The element represents its children.
|
Yes | |
<area>
|
The area element represents either a hyperlink with some text and a corresponding area on an image map, or a dead area on an image map.
|
Partial | Support for the IDL attribute relList is OPTIONAL |
<caption>
|
The caption element represents the title of the table that is its parent, if it has a parent and that is a table element.
|
Yes | |
<table>
|
The table element represents data with more than one dimension, in the form of a table.
|
Partial |
Support for the summary attribute is OPTIONAL;
|
<colgroup>
|
The colgroup element represents a group of one or more columns in the table that is its parent, if it has a parent and that is a table element.
|
Yes | |
<col>
|
If a col element has a parent and that is a colgroup element that itself has a parent that is a table element, then the col element represents one or more columns in the column group represented by that colgroup .
|
Yes | |
<tbody>
|
The tbody element represents a block of rows that consist of a body of data for the parent table element, if the tbody element has a parent and it is a table .
|
Yes | |
<thead>
|
The thead element represents the block of rows that consist of the column labels (headers) for the parent table element, if the thead element has a parent and it is a table .
|
Yes | |
<tfoot>
|
The tfoot element represents the block of rows that consist of the column summaries (footers) for the parent table element, if the tfoot element has a parent and it is a table .
|
Yes | |
<tr>
|
Yes | ||
<td>
|
The tr element represents a row of cells in a table .
|
Yes | |
<th>
|
The th element represents a header cell in a table .
|
Yes | |
<form>
|
The form element represents a collection of form-associated elements, some of which can represent editable values that can be submitted to a server for processing.
|
Yes | |
<fieldset>
|
The fieldset element represents a set of form controls optionally grouped under a common name.
|
Yes | |
<legend>
|
The legend element represents a caption for the rest of the contents of the legend element's parent fieldset element, if any.
|
Yes | |
<button>
|
The button element represents a button.
|
Yes | |
<optgroup>
|
The optgroup element represents a group of option elements with a common label.
|
Yes | |
<script>
|
The script element allows authors to include dynamic script and data blocks in their documents. The element does not represent content for the user.
|
Partial |
Support for the async attribute is OPTIONAL |
<noscript>
|
The noscript element represents nothing if scripting is enabled, and represents its children if scripting is disabled. It is used to present different markup to user agents that support scripting and those that don't support scripting, by affecting how the document is parsed.
|
No | Since support for scripting is mandated by this profile, support for this element is not needed. |
<span>
|
The span element doesn't mean anything on its own, but can be useful when used together with the global attributes, e.g. class , lang , or dir . It represents its children.
|
Yes | |
<title>
|
The title element represents the document's title or name.
|
Yes | |
<ul>
|
The ul element represents a list of items, where the order of the items is not important — that is, where changing the order would not materially change the meaning of the document.
|
Yes | |
<section>
|
Represents a generic document or application section. It can be used together with the h1, h2, h3, h4, h5, and h6 elements to indicate the document structure. | Yes | |
<article>
|
Represents an independent piece of content of a document, such as a blog entry or newspaper article. | Yes | |
<aside>
|
Represents a piece of content that is only slightly related to the rest of the page. | Yes | |
<hgroup>
|
Represents the header of a section. | Yes | |
<header>
|
Represents a group of introductory or navigational aids. | Yes | |
<footer>
|
Represents a footer for a section and can contain information about the author, copyright information, etc. | Yes | |
<nav>
|
Represents a section of the document intended for navigation. | Yes | |
<figure>
|
Can be used to associate a caption together with some embedded content, such as a graphic or video: | Yes | |
<figcaption>
|
Provides the caption for the <figure> element's contents.
|
Yes | |
<video>
|
Represents a video or movie. It is a media element whose media data is ostensibly video data, possibly with associated audio data. | Partial |
Support for crossorigin , mediagroup , and controls content attributes is OPTIONAL.
|
<audio>
|
Represents a sound or audio stream. It is a media element whose media data is ostensibly audio data. | Partial | Support for crossorigin , mediagroup , and controls content attributes is OPTIONAL. |
<track>
|
The track element allows authors to specify explicit external timed text tracks for media elements. It does not represent anything on its own. | No | Not required as only support for in-band tracks is required |
<source>
|
Allows authors to specify multiple media resources for media elements. It does not represent anything on its own. | Yes | |
<embed>
|
It is is used for plug-in content. It represents an integration point for an external (typically non-HTML) applications or interactive content. | Yes | |
<mark>
|
Represents a run of text in one document marked or highlighted for reference purposes, due to its relevance in another context. | Yes | |
<progress>
|
Represents a completion of a task such as downloading, or when performing a series of expensive operations. | Yes | |
<meter>
|
Represents a scalar measurement within a known range, or a fractional value; for example:
|
Yes | |
<time>
|
Represents either a time on a 24 hour clock, or a precise date in the proleptic Gregorian calendar, optionally with a time and a time zone. It provides an API for accessing the date/time as a Date object. | No | |
<ruby>
|
Allows one or more spans of phrasing content to be marked with ruby annotations. Ruby annotations are short runs of text presented alongside base text, primarily used in East Asian typography as a guide for pronunciation or to include other annotations. In Japanese, this form of typography is also known as furigana. | No | |
<rt>
|
Marks the ruby text component of a ruby annotation. | No | |
<rp>
|
Can be used to provide parentheses around a ruby text component of a ruby annotation, to be shown by user agents that do not support ruby annotations. | No | |
<wbr>
|
Represents a line-break opportunity where phrasing content is expected. For example, someone is quoted as saying something
which, for effect, is written as one long word. However, to ensure that the text can be wrapped in a readable fashion, the
individual words in the quote are separated using a <wbr> element.
|
Yes | |
<canvas>
|
Represents a resolution-dependent bitmap canvas, which can be used for rendering graphs, game graphics, or other visual images on the fly. | Partial | For details on support of Canvas APIs, see section C.3 Canvas 2D |
<command>
|
Represents a command that the user can invoke. | No | |
<details>
|
Represents additional information or controls which the user can obtain on demand. | No | |
<summary>
|
Represents a summary, caption, or legend for the rest of the contents of the summary element's parent details element, if any. | Yes | |
<datalist>
|
Represents a set of <option> elements that represent predefined options for other controls. The contents
of the element represents fallback content for legacy user agents, intermixed with <option> elements
that represent the predefined options. In the rendering, the <datalist> element represents nothing and
it, along with its children, should be hidden. The <datalist> element together with the new list
attribute for input can be used to make comboboxes.
|
Yes | |
<keygen>
|
Represents a key pair generator control. When the control's form is submitted, the private key is stored in the local keystore, and the public key is packaged and sent to the server. | Yes | |
<output>
|
Represents some type of output, as from a calculation done through scripting. | Yes | |
<textarea>
|
Represents a multiline plain text edit control for the element's raw value | Yes | |
<select>
|
Represents a control for selecting amongst a set of options. | Yes | |
<fieldset>
|
Represents a set of form controls optionally grouped under a common name. | Yes | |
<input>
|
The <input> element represents a typed data field, usually with a form control to allow the user to edit the data.
The <input> element type attribute has the following values.
|
Partial |
|
<a>
|
The <a> element without an href attribute now represents a "placeholder link".
It can also contain flow content rather than being restricted to phrase content.
|
Partial | Support for the IDL attribute relList is OPTIONAL |
<address>
|
The <address> element is now scoped by the new concept of sectioning. It represents the contact information
for its nearest article or body element ancestor. If that is the body element, then the contact information applies to the
document as a whole.
|
Yes | |
<b>
|
The <b> element represents a span of text to be stylistically offset from the normal prose without conveying
any extra importance, such as key words in a document abstract, product names in a review, or other spans of text whose
typical typographic presentation is boldened.
|
Yes | |
<cite>
|
The <cite> element now solely represents the title of a work (e.g. a book, a paper, an essay, a poem,
a score, a song, a script, a film, a TV show, a game, a sculpture, a painting, a theatre production, a play, an opera, a
musical, an exhibition, a legal case report, etc). Specifically the example in HTML4 where it is used to mark up the name
of a person is no longer considered conforming.
|
Yes | |
<hr>
|
The <hr> element represents a paragraph-level thematic break, e.g. a scene change in a story, or a transition
to another topic within a section of a reference book.
|
Yes | |
<i>
|
The <i> element represents a span of text in an alternate voice or mood, or otherwise offset from the
normal prose, such as a taxonomic designation, a technical term, an idiomatic phrase from another language, a thought, a
ship name, or some other prose whose typical typographic presentation is italicized.
|
Yes | |
<label>
|
For the <label> element the browser should no longer move focus from the label to the control
unless such behavior is standard for the underlying platform user interface.
|
Yes | |
<menu>
|
The <menu> element represents a list of commands and is redefined to be useful for toolbars and context
menus.
|
Partial |
|
<small>
|
The <small> element now represents small print (for side comments and legal print).
|
Yes | |
<strong>
|
The <strong> element now represents importance rather than strong emphasis.
|
Yes | |
<head>
|
The <head> element no longer allows the object element as child.
|
Yes |
Attribute name | Description (INFORMATIVE) | Mandatory | Comment |
---|---|---|---|
accessKey
|
The accesskey attribute's value is used by the user agent as a guide for creating a keyboard shortcut that activates or focuses the element. | No | |
class
|
Every HTML element may have a class attribute specified. The attribute, if specified, must have a value that is an unordered set of unique space-separated tokens representing the various classes that the element belongs to. The classes that an HTML element has assigned to it consists of all the classes returned when the value of the class attribute is split on spaces. | Yes | |
dir
|
The dir attribute specifies the element's text directionality (left-to-right, or right-to-left). The attribute
is an enumerated attribute with the keyword ltr ((left-to-right) mapping to the state ltr , and
the keyword rtl (right-to-left) mapping to the state rtl . The attribute has no defaults.
|
Yes | |
id
|
The id attribute represents its element's unique identifier. The value must be unique in the element's home
subtree and must contain at least one character. The value must not contain any space characters.
|
Yes | |
lang
|
The lang attribute (in no namespace) specifies the primary language for the element's contents and for any
of the element's attributes that contain text. Its value must be a valid BCP 47 language code, or the empty string.
|
Yes | |
style
|
All HTML elements may have the style content attribute set. If specified, the attribute must contain only a
list of zero or more semicolon-separated (;) CSS declarations. In user agents that support CSS, the attribute's value must
be parsed when the attribute is added or has its value changed, with its value treated as the body (the part inside the
curly brackets) of a declaration block in a rule whose selector matches just the element on which the attribute is set.
All URLs in the value must be resolved relative to the element when the attribute is parsed. For the purposes of the CSS
cascade, the attribute must be considered to be a style attribute at the author level. Documents that use
style attributes on any of their elements must still be comprehensible and usable if those attributes were removed.
|
Yes | |
tabindex
|
The tabindex content attribute specifies :
|
Yes | |
title
|
The title attribute represents advisory information:
|
Yes | |
contenteditable / isContentEditable
|
The contenteditable attribute is an enumerated attribute whose keywords are the empty string ,
true , and false . The empty string and the true keyword map to the true state. The false keyword
maps to the false state. In addition, there is a third state, the inherit state, which is the missing value
default (and the invalid value default).
|
No | |
designMode
|
Documents have a designMode, which can be either enabled or disabled. When enabled, the document is editable. | No | |
contextmenu
|
The contextmenu attribute gives the element's context menu. The value must be the ID of a menu element in the
DOM. If the node that would be obtained by the invoking the getElementById() method using the attribute's value
as the only argument is null or not a menu element, then the element has no assigned context menu. Otherwise,
the element's assigned context menu is the element so identified.
|
No | |
data-*
|
A custom data attribute is an attribute in no namespace whose name starts with the string "data- ",
has at least one character after the hyphen, is XML-compatible, and contains no characters in the range U+0041 .. U+005A
(LATIN CAPITAL LETTER A .. LATIN CAPITAL LETTER Z). Custom data attributes are intended to store custom data private to
the page or application, for which there are no more appropriate attributes or elements. These attributes are not intended
for use by software that is independent of the site that uses the attributes. Every HTML element may have any number of
custom data attributes specified, with any value. They refer to the DOM Dataset API.
|
Yes | |
draggable
|
All HTML elements may have the draggable content attribute set. It is an enumerated attribute, and has three
states:
|
No | |
dropzone
|
All HTML elements may have the dropzone content attribute set. | No | |
hidden
|
All HTML elements may have the hidden content attribute set. The hidden attribute is a boolean attribute.
When specified on an element, it indicates that the element is not yet, or is no longer, relevant. User agents should not
render elements that have the hidden attribute specified.
|
Yes | |
spellcheck
|
The spellcheck attribute is an enumerated attribute whose keywords are the empty string , true
and false . The empty string and the true keyword map to the true state. The false
keyword maps to the false state. Please note that the "default" state has been removed.
|
No |
HTML5 introduces a number of APIs that help creating applications.
API name | Description (INFORMATIVE) | Mandatory | Comment |
---|---|---|---|
Media elements
|
An API for playing of video and audio which can be used with the new <video> and <audio> elements.
|
Partial | See profile in section section A.1.3.1 Media APIs |
Application cache
|
An API that enables offline Web applications. | No | This feature is potentially useful but marked as feature at risk in [HTML5-20121217] and likely to change in the near future. |
Custom scheme and content handlers
|
An API that allows a Web application to register itself for certain protocols or media types. | No | Not relevant for this profile. Also, marked as feature at risk in [HTML5-20121217] |
Custom search provider
|
An API that allows a Web application to register itself for certain search provider. | No | Not relevant for this profile. Also, marked as feature at risk in [HTML5-20121217] |
Drag and drop
|
This API works in combination with a draggable attribute.
|
No | |
History
|
An API that exposes the history and allows pages to add to it to prevent breaking the back button. | Yes | |
Base64 utility methods
|
An API that allow authors to transform content to and from the base64 encoding. | Yes |
HTML Media APIs SHALL be supported as profiled below
Interface | Attribute Name | Mandatory | Comment |
---|---|---|---|
HTMLVideoElement |
|||
width | Yes | ||
height | Yes | ||
videoWidth | Yes | ||
videoHeight | Yes | ||
poster | Yes | ||
HTMLAudioElement |
Yes | ||
HTMLSourceElement |
|||
src | Yes | ||
type | Yes | ||
media | Yes | ||
HTMLTrackElement |
No | ||
HTMLMediaElement |
|||
error | Yes | ||
src | Yes | ||
currentSrc | Yes | ||
crossOrigin | No | ||
networkState | Yes | ||
preload | Yes | ||
buffered | Yes | ||
load() | Yes | ||
canPlayType() | Yes | ||
readyState | Yes | ||
seeking | Yes | ||
currentTime | Yes | ||
duration | Yes | ||
startDate | No | ||
paused | Yes | ||
defaultPlaybackRate | Yes | ||
playbackRate | Yes | ||
played | Yes | ||
seekable | Yes | ||
ended | Yes | ||
autoplay | Yes | ||
loop | Yes | ||
play() | Yes | ||
pause() | Yes | ||
mediaGroup | No | ||
controller | No | ||
controls | No | ||
volume | Yes | ||
muted | Yes | ||
defaultMuted | Yes | ||
videoTracks | No | ||
audioTracks | Yes | ||
textTracks | Yes | Only support for in-band tracks is required | |
addTextTrack() | No | ||
MediaError |
|||
code | Yes | ||
AudioTrackList |
|||
length | Yes | ||
getter(index) | Yes | ||
getTrackByID() | Yes | ||
onchange | Yes | ||
onaddtrack | No | ||
onremovetrack | No | ||
AudioTrack |
|||
id | Yes | ||
kind | Yes | ||
label | Yes | ||
language | Yes | ||
enabled | Yes | ||
VideoTrackList |
No | ||
VideoTrack |
No | ||
TextTrackList |
Yes | ||
TextTrack |
|||
kind | Yes | ||
label | Yes | ||
language | Yes | ||
onMetadataTrackDispatchType | Yes | ||
mode | Yes | ||
cues | No | ||
activeCues | No | ||
addCue | No | ||
removeCue | No | ||
oncuechange | No | ||
TextTrackCueList |
No | ||
TextTrackCue |
No | ||
MediaController |
No | ||
TimeRange |
|||
length | Yes | ||
start | Yes | ||
end | Yes | ||
TrackEvent |
Yes |
Events | Mandatory |
---|---|
loadstart | Yes |
progress | Yes |
suspend | Yes |
abort | Yes |
error | Yes |
emptied | Yes |
stalled | Yes |
loadedmetadata | Yes |
loadeddata | Yes |
canplay | Yes |
canplaythrough | Yes |
playing | Yes |
waiting | Yes |
seeking | Yes |
seeked | Yes |
ended | Yes |
durationchange | Yes |
timeupdate | Yes |
play | Yes |
pause | Yes |
ratechange | Yes |
volumechange | Yes |
Property | Values | Description | Mandatory | Comment |
---|---|---|---|---|
appearance
|
normal | <appearance> | inherit | This property can be used to make an element look like a standard user interface element on the platform. It is a shorthand for "appearance", "color", "font", and "cursor". | No | |
box-sizing
|
padding-box | content-box | border-box | inherit | This property specifies a border/padding value in relation to a fluid length element. | Partial |
Support for property value padding-box is OPTIONAL (marked as feature at risk in [HTML5-20121217])
|
content
|
icon | This property is used with the :before and :after pseudo-elements to generate content in a document. | No | Marked as feature at risk in [HTML5-20121217] |
cursor
|
[ [<uri> [<x> <y>]?,]* [ auto | default | none | context-menu | help | pointer | progress | wait | cell | crosshair | text | vertical-text | alias | copy | move | no-drop | not-allowed | e-resize | n-resize | ne-resize | nw-resize | s-resize | se-resize | sw-resize | w-resize | ew-resize | ns-resize | nesw-resize | nwse-resize | col-resize | row-resize | all-scroll | zoom-in | zoom-out ] ] | inherit | This property specifies the type of cursor to be displayed for the pointing device. | Yes | |
font
|
<appearance> | status-bar | message-box | caption | small-caption | inherit | The shorthand "font" property has the effect of setting all of the elemental "font-*" properties. | Yes | |
icon
|
auto | <uri> [, <uri>]* | inherit | The "icon" property give the author the ability to style any arbitrary element with an iconic equivalent. | No | Feature at risk in [HTML5-20121217] |
nav-index
|
auto | <number> | inherit | This property is an input-method-neutral way of specifying the sequential navigation order, also known as "tabbing order". | Yes | |
nav-up
|
auto | <id> [ current | root | <target-name> ]? | inherit | This property allows User agents for devices with directional navigation keys to respond by navigating the nav-up focus. | Yes | |
nav-right
|
auto | <id> [ current | root | <target-name> ]? | inherit | This property allows User agents for devices with directional navigation keys to respond by navigating the nav-right focus. | Yes | |
nav-down
|
auto | <id> [ current | root | <target-name> ]? | inherit | This property allows User agents for devices with directional navigation keys to respond by navigating the nav-down focus. | Yes | |
nav-left
|
auto | <id> [ current | root | <target-name> ]? | inherit | This property allows User agents for devices with directional navigation keys to respond by navigating the nav-left focus. | Yes | |
outline
|
[ <"outline-color"> || <"outline-style"> || <"outline-width"> ] | inherit | This property allows authors who want to create outlines around visual objects such as buttons, active form fields, image maps, etc., to make them stand out. | Yes | |
outline-color
|
<color> | invert | inherit | This property controls the border color of a dynamic outline. | Yes | |
outline-offset
|
<length> | inherit | This property controls the border offset of a dynamic outline. | Yes | |
outline-style
|
auto | <border-style> | inherit | This property controls the border style of a dynamic outline. | Partial |
At this time outline-style SHALL be supported as defined by CSS2.1 specification, so support for value auto is not required.
|
outline-width
|
<border-width> | inherit | This property controls the border width of a dynamic outline. | Yes | |
resize
|
none | both | horizontal | vertical | inherit | This property allows an author to specify whether or not an element is resizable by the user, and if so, along which axis/axes. | No | |
ime-mode
|
auto | normal | active | inactive | disabled | inherit | The ‘ime-mode’ CSS property controls the state of the input method editor for text fields. | No | Feature at risk in [HTML5-20121217] |
text-overflow
|
( clip | ellipsis | |
This property specifies rendering when inline content overflows its block container element ("the block") in its inline progression direction that has ‘overflow’ other than ‘visible’ | Partial | Support for the text-overflow property value <string> and the text-overflow property 2-value syntax and definition is OPTIONAL (marked as feature at risk in [CSS3UI-20120117]).
|
Pseudo class | Mandatory | Comment |
---|---|---|
:active
|
Yes | |
:checked
|
Yes | |
:default
|
Yes | |
:disabled
|
Yes | |
:enabled
|
Yes | |
:focus
|
Yes | |
:hover
|
Yes | |
:in-range
|
Yes | |
:indeterminate
|
Yes | |
:invalid
|
Yes | |
:optional
|
Yes | |
:out-of-range
|
Yes | |
:read-only
|
Yes | |
:read-write
|
Yes | |
:required
|
Yes | |
:valid
|
Yes | |
:visited
|
Yes | |
:visited
|
Yes |
Terminals SHALL support Gradients as defined in CSS Image Values and Replaced Content [CSS3-IMAGES-20120417]. Support for other features is OPTIONAL.
Terminals SHALL support all features in CSS Backgrounds and Borders [CSS3-BG-20120724] with the exception of the border-image
set of properties
Terminals SHALL support the [CSS3-FONTS-20130212] specification as profiled below:
font-family
, font-weight
, font-style
, font-size
and font
properties SHALL be supported. Support for other properties is OPTIONAL.font
property is OPTIONAL.@font-face
rule SHALL be supported. Support for other rules is OPTIONAL.@font-face
rule SHALL be supported. Support for other descriptors is OPTIONAL.text-shadow
, text-align
, word-spacing
, letter-spacing
, text-indent
.
transform
and transform-origin
properties is requiredmatrix()
, translate()
, translateX()
, translateY()
, scale()
, scaleX()
, scaleY()
, rotate()
, skewX()
, skewY()
transform functions is required.Support for the pseudoElement
field on the TransitionEvent
interface is OPTIONAL
Support for the pseudoElementArg
argument for the initTransitionEvent
method is OPTIONAL
Support for animatable properties SHALL be as indicated below
Property Name | Type | Madatory |
---|---|---|
background-color
|
color | Yes |
background-image
|
only gradients | No |
background-position
|
percentage, length | No |
border-bottom-color
|
color | No |
border-bottom-width
|
length | Yes |
border-color
|
color | No |
border-left-color
|
color | No |
border-left-width
|
length | Yes |
border-right-color
|
color | No |
border-right-width
|
length | Yes |
border-spacing
|
length | Yes |
border-top-color
|
color | No |
border-top-width
|
length | Yes |
border-width
|
length | Yes |
bottom
|
length, percentage | Yes |
color
|
color | Yes |
crop
|
rectangle | No |
font-size
|
length, percentage | Yes |
font-weight
|
number | Yes |
grid-*
|
various | No |
height
|
length, percentage | Yes |
left
|
length, percentage | Yes |
letter-spacing
|
length | Yes |
line-height
|
number, length, percentage | Yes |
margin-bottom
|
length | Yes |
margin-left
|
length | Yes |
margin-right
|
length | Yes |
margin-top
|
length | Yes |
max-height
|
length, percentage | Yes |
max-width
|
length, percentage | Yes |
min-height
|
length, percentage | Yes |
min-width
|
length, percentage | Yes |
opacity
|
number | Yes |
outline-color
|
color | Yes |
outline-offset
|
integer | Yes |
outline-width
|
length | Yes |
padding-bottom
|
length | Yes |
padding-left
|
length | Yes |
padding-right
|
length | Yes |
padding-top
|
length | Yes |
right
|
length, percentage | Yes |
text-indent
|
length, percentage | Yes |
text-shadow
|
shadow | No |
top
|
length, percentage | Yes |
vertical-align
|
keywords, length, percentage | Yes |
visibility
|
visibility | Yes |
width
|
length, percentage | Yes |
word-spacing
|
length, percentage | Yes |
z-index
|
integer | Yes |
zoom
|
number | No |
Support for Document
response type is OPTIONAL. All other features SHALL be supported.
Path
DrawingStyle
HitRegionOptions
Member | Support | Comment |
---|---|---|
width
|
Yes | |
height
|
Yes | |
toDataURL()
|
Yes | |
getContext(context)
|
Yes |
Member | Mandatory | Comment |
---|---|---|
width
|
Yes | |
actualBoundingBoxLeft
|
No | |
actualBoundingBoxRight
|
No | |
fontBoundingBoxAscent
|
No | |
fontBoundingBoxDescent
|
No | |
actualBoundingBoxAscent
|
No | |
actualBoundingBoxDescent
|
No | |
emHeightAscent
|
No | |
emHeightDescent
|
No | |
hangingBaseline
|
No | |
alphabeticBaseline
|
No | |
ideographicBaseline
|
No |
Member | Mandatory | Comment |
---|---|---|
addColorStop(offset, color)
|
Yes |
Member | Mandatory | Comment |
---|---|---|
canvas
|
Yes | |
save()
|
Yes | |
restore()
|
Yes | |
scale(x, y)
|
Yes | |
rotate(angle)
|
Yes | |
translate(x, y)
|
Yes | |
transform(m11, m12, m21, m22, dx, dy)
|
No | |
setTransform(m11, m12, m21, m22, dx, dy)
|
No | |
globalAlpha
|
Yes | |
globalCompositeOperation
|
Yes |
The value source-over for this property SHALL be supported.
Support for other values is OPTIONAL.
|
strokeStyle
|
Yes | |
fillStyle
|
Yes | |
createImageData(sw, sh)
|
Yes | |
createImageData(imagedata)
|
Yes | |
createLinearGradient(x0, y0, x1, y1)
|
Yes | If this feature is not hardware accelerated, performance will be limited |
createRadialGradient(x0, y0, r0, x1, y1, r1)
|
Yes | If this feature is not hardware accelerated, performance will be limited |
createPattern(image, repetition)
|
Yes | |
lineWidth
|
Yes | |
lineCap
|
Yes | If this feature is not hardware accelerated, performance will be limited |
lineJoin
|
Yes | |
miterLimit
|
Yes | |
shadowOffsetX
|
Yes | |
shadowOffsetY
|
Yes | |
shadowBlur
|
Yes | If this feature is not hardware accelerated, performance will be limited |
shadowColor
|
Yes | |
clearRect(x, y, w, h)
|
Yes | |
fillRect(x, y, w, h)
|
Yes | |
strokeRect(x, y, w, h)
|
Yes | If this feature is not hardware accelerated, performance will be limited |
beginPath()
|
Yes | |
closePath()
|
Yes | |
moveTo(x, y)
|
Yes | |
lineTo(x, y)
|
Yes | |
quadraticCurveTo(cpx, cpy, x, y)
|
No | |
bezierCurveTo(cp1x, cp1y, cp2x, cp2y, x, y)
|
No | |
arcTo(x1, y1, x2, y2, radius)
|
No | |
rect(x, y, w, h)
|
Yes | |
arc(x, y, radius, startAngle, endAngle, anticlockwise)
|
No | |
ellipse(x, y, radiusX, radiusY, rotation, startAngle, endAngle, anticlockwise);
|
No | |
fill()
|
Yes | |
fill(path)
|
No | |
stroke()
|
Yes | |
stroke(path)
|
No | |
clip()
|
No | |
clip(path)
|
No | |
isPointInPath(x, y)
|
Yes | |
isPointInPath(path, x, y)
|
No | |
drawImage(image, dx, dy)
|
Yes | |
drawImage(image, dx, dy, dw, dh)
|
Yes | |
drawImage(image, sx, sy, sw, sh, dx, dy, dw, dh)
|
Yes | |
getImageData(sx, sy, sw, sh)
|
Yes | |
putImageData(image, dx, dy)
|
Yes | |
putImageData(image, dx, dy, dirtyX, dirtyY, dirtyWidth, dirtyHeight)
|
No | |
font
|
Yes | |
textAlign
|
Yes | |
textBaseline
|
Yes | |
fillText
|
Yes | |
strokeText
|
Yes | |
measureText
|
Yes | |
setLineDash(segments)
|
No | |
getLineDash()
|
No | |
lineDashOffset
|
No | |
drawSystemFocusRing(element)
|
No | |
drawSystemFocusRing(path,element)
|
No | |
drawCustomFocusRing(element)
|
No | |
drawCustomFocusRing(path,element)
|
No | |
scrollPathIntoView
|
No | |
scrollPathIntoView(path)
|
No | |
addHitRegion(options)
|
No | |
removeHitRegion(options)
|
No |