Changes
This section summarises substantial changes since the HTML 5.1 Recommendation.
Full details of all changes since 12 January 2016 are available from the commit log of the w3c/html github repository, including various editorial and linking fixes.
New features
-
The
dialogelement. -
Integration with the JavaScript module system of [ECMA-262].
-
Update ARIA reference to [wai-aria-1.1], which introduces new features to improve accessibility.
-
The
nonceattribute forlinkas used in Content Security Policy [CSP3]. -
The
allowpaymentrequestattribute ofiframe, for integration with the Payment Request API [PAYMENT-REQUEST]. -
The allow-presentation value for the
sandboxattribute ofiframe, for integration with the Presentation API [PRESENTATION-API]. -
The
noreferrerlink type value for [SECURE-CONTEXTS]. -
The apple-touch-icon value for the
relattribute to allow the use of thesizeattribute in thelinkelement. -
The
registerContentHandler(),isContentHandlerRegistered()andisProtocolHandlerRegistered()methods. -
The
innerTextIDL attribute forHTMLElement. -
Define the
about:html-kindURL for MP4 media track integration. -
Integrate the Should element be blocked a priori by Content Security Policy? of [CSP3]
Features removed
-
The
keygen,menuandmenuitemelements. -
The
inputmodeattribute for textualinputelements, and thedropzoneattributes. -
The
showModalDialogmethod. -
The Plugin API has been marked as obsolete.
Fixing bugs and matching reality better
-
Stop media resource requests from non-network sources delaying the
loadevent. -
Remove arbitrary upper limits on refresh rates.
-
Coordinates for
ismapno longer include the image’s border in calculation. -
Update
accesskeydefinition to require a single printable character. -
Fix the activation algorithm for
summaryto match reality. -
Fix the algorithm to determine row and column headers for
table. -
Update the rendering of
summary -
Reflecting a broken URL returns the unparsed value
-
currentScriptmay returnSVGScriptElement. -
Resetting a
textarearesets its dirty value flag. -
document.open()anddocument.close()check for XML document. -
HashChangeEventURLs areUSVStringinstead ofDOMString. -
Selection members' types are nullable.
-
data:URLs are treated as a separate origin. -
Sadly, elements that are only focusable because they have a
tabindexattribute generally will not fire aclickevent when activated with a non-pointer device. -
Navigation for sandboxed contexts
-
Updated allowable
rolevalues in line with [html-aria]
- The following constructions are now valid HTML:
stylewithin thebody.- Multiple
mainelements in the DOM, so long as only one is visible to the user. - The presentation for the
imgelement. divas a child of adlelement.dfnas a descendent of anlielement that contains a definition of the term defined.- Headings within
legendin afieldset. - Empty
optionelement as a child ofdatalist. - Comments containing two consecutive hyphens, or ending with a hyphen, in the HTML syntax.
- Remove restrictions on BiDi algorithm section
- The following constructions are no longer valid HTML:
rolevalues for acaptionelement.- Inline blocks, inline tables, or floated and positioned block-level elements as children of a
pelement. - Content with the HTML4 or XHTML1 strict doctype.
New concepts
-
Added serialized state and creator context security.
-
Added an algorithm to determine whether content is allowed to use certain powerful, hence potentially risky, features.
-
Added the
WindowOrWorkerGlobalScopemixin as a convenience.
Editorial clarifications
-
Browsers should represent punycode addresses as natural unicode text for the
emailinputtype. -
Clarify the concept of last frame time for the
seekableIDL attribute -
Browsers that use the the suggestions source element to filter suggestions should implement substring matching on the
labelattribute. -
Users should be able to interact with
areaelements whether or not they use a pointing device.