


In this version, new features continue to be introduced to help WebĪpplication authors, new elements continue to be introduced based on research Language of the World Wide Web: the Hypertext Markup Language This specification defines the 5th major version, first minor revision of the core © 2013 W3C ® ( MIT, ERCIM, Keio, Beihang), All Rights Reserved. This specification is also available as a single page HTML document. Silvia Pfeiffer WHATWG Editor: Ian Hickson, Google, Inc. Warnings for authors not to rely on this feature yet are in the specification.A vocabulary and associated APIs for HTML and XHTMLĮditor's Draft Latest Published Version: Latest Editor's Draft: Previous Versions: W3C Editors: Robin Berjon, W3C Steve Faulkner, The Paciello Group Travis Leithead, Microsoft Erika Doyle Navara, Microsoft Edward O'Connor, Apple Inc.

In the HTML specification, it is mentioned in an algorithm, to take account of any implementation, in a way that means partial implementation does not introduce an interoperability problem. CSP hooks for inline events and styles This part of CSP does not appear to have implementation, but seems likely to be implemented in the near future. A warning for authors not to rely on this feature is in the specification. Use close() blob from File API This method does not appear to have implementation, and may in future be removed from File API. A warning for authors not to rely on this feature yet is in the specification. No known implementations probablySupportsContext This convenience function for canvas has no known implementation. Promise rejection handling with rejectionhandled and unhandledrejection events This features is currently only known to be implemented in blink, and a warning to authors that it is not yet reliable is in the specification. There is poor interoperability of this in general, so it is unlikely to affect Web Compatibility, but this change matches a similar one in the WHATWG specification. createTFoot to always insert at the end Only in Firefox. A warning for authors not to rely on this feature yet is in the specification.tFoot and. This defines how a CSS selector works with HTML when implemented, so the lack of implementation doesn't cause interop problems for browsers. Uncertain implementations One known implementation :dir CSS selector matching Only in Firefox. Implementation detail: conceptual storage of HTTPS State. Move "https state" from Window to Document Much of this change is Not Testable, except for nonce support IDL (on style/script) Script/style-src 'unsafe-inline' applies to elementĪdd hooks for CSP and Realms from ECMASCript Not testable implementation detail to support CSP. In SVG embedded in HTML, Firefox and Safari expose the first child title element as a tooltipĬhanges relating to other specifications Isolated integrationsĭefer some encoding specifics to WHATWG Encoding specĭefine enqueueJob() and nextJob() monkeypatching ECMAScriptĮxplains Promise resolution in terms of Microtasks - tests Promises use Microtask timing Yandex, Firefox, Chrome and Safari all expose the first title child in raw SVG. Non-scaling-stroke for vector-effect - testĪllow ARIA attributes - demonstrated by multiple examples Reference namedItem method from HTMLCollection not HTMLOptionsCollectionĭescribe SVG versions implemented in browsers no longer utilises HTMLFormControlsCollection Let FrameElement return null in cross-origin situationsĬhange ImageBitmap to allow cross-origin content The bugfix was in one piece of the spec that covers both cases. Make meta refresh parsing reflect realityįirefox doesn't seem to show the captions, despite loading them.ĮventSource appears to work cross-origin with the correct headers in related testing of Blink (Yandex) and Gecko, but this feature may not have been tested thoroughly. Manually checked if document.createElement('canvas').toBlob(null) throws…

Make 's event and htmlFor IDL attributes reflect the content attributes Make stepup/down algorithm reflect reality test caseĪccording to - which has a test that could be adapted. Modify header/footer content model to allow and descendants Search engines, RDFa validators - Google, Yandex, … Implementation information is documented in the relevant Github issue, Pull Request (PR), or documentation for developers. This report outlines known implementations for the features added between HTML 5.0 and HTML 5.1.
