Now Stable

"New on the Web": For a given set of browsers, what APIs became stable and when, ordered reverse chronologically.

It's a great source of information for posts like this

Example Comparisons
Browsers
Features

Stable APIs

Below is a list of features that are in Firefox, Safari, and Edge, ordered reverse chronologically by when they became stable (i.e, available in the last browser).

2026/3

API First Browser Date Last Browser Date Days Notes
html.elements.template.shadowrootreferencetarget Edge2/6/2025 Firefox3/24/2026411
css.properties.text-indent.each-line πŸ“‹Safari9/20/2021 Edge3/12/20261634
css.properties.text-indent.hanging πŸ“‹Safari9/20/2021 Edge3/12/20261634

2026/2

API First Browser Date Last Browser Date Days Notes
css.properties.position-area.block-end πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.block-start πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.bottom πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.end πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.inline-end πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.inline-start πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.left πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.right πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-block-end πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-block-start πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-end πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-inline-end πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-inline-start πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-start πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-x-end πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-x-start πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-y-end πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-y-start πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.top πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.x-end πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.x-start πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.y-end πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.y-start πŸ“‹Safari9/15/2025 Firefox2/24/2026162
Chrome: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-x-end πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-x-start πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-y-end πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-y-start πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-x-end πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-x-start πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-y-end πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-y-start πŸ“‹Safari12/12/2025 Firefox2/24/202674
Chrome: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-order πŸ“‹Edge5/17/2024 Firefox2/24/2026648
css.properties.position-try-order.most-block-size πŸ“‹Edge5/17/2024 Firefox2/24/2026648
css.properties.position-try-order.most-height πŸ“‹Edge5/17/2024 Firefox2/24/2026648
css.properties.position-try-order.most-inline-size πŸ“‹Edge5/17/2024 Firefox2/24/2026648
css.properties.position-try-order.most-width πŸ“‹Edge5/17/2024 Firefox2/24/2026648
css.properties.position-try-order.normal πŸ“‹Edge5/17/2024 Firefox2/24/2026648
css.types.basic-shape.shape πŸ“‹Safari3/31/2025 Firefox2/24/2026330
html.elements.details.search_match_opens Edge1/6/2022 Firefox2/24/20261510
Firefox: The browser does not correctly scroll to the matching text. See bug 2006040.Firefox for Android: The browser does not correctly scroll to the matching text. See bug 2006040.Safari: The browser does not correctly scroll to the matching text. See bug 304174.Safari on iOS: The browser does not correctly scroll to the matching text. See bug 304174.WebView on iOS: The browser does not correctly scroll to the matching text. See bug 304174.
html.global_attributes.hidden.until-found πŸ“‹Edge5/31/2022 Firefox2/24/20261365
Firefox: The browser does not correctly scroll to the matching text. See bug 2006040.Firefox for Android: The browser does not correctly scroll to the matching text. See bug 2006040.Safari: The browser does not correctly scroll to the matching text. See bug 304174.Safari on iOS: The browser does not correctly scroll to the matching text. See bug 304174.WebView on iOS: The browser does not correctly scroll to the matching text. See bug 304174.
css.properties.word-spacing.percentages Safari10/22/2013 Edge2/14/20264498

2026/1

API First Browser Date Last Browser Date Days Notes
css.properties.background-position-x.side-relative_values Firefox9/20/2016 Edge1/21/20263410
css.properties.background-position-y.side-relative_values Firefox9/20/2016 Edge1/21/20263410
css.properties.position-area.span-all πŸ“‹Safari9/15/2025 Edge1/21/2026128
Chrome: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.flip-x πŸ“‹Safari12/12/2025 Edge1/21/202640
css.properties.position-try.flip-y πŸ“‹Safari12/12/2025 Edge1/21/202640
css.properties.position-try-fallbacks.flip-x πŸ“‹Safari12/12/2025 Edge1/21/202640
css.properties.position-try-fallbacks.flip-y πŸ“‹Safari12/12/2025 Edge1/21/202640
css.types.color.color.colorSpace_parameter_accepts_display-p3-linear_value πŸ“‹Firefox12/9/2025 Edge1/21/202643
css.at-rules.position-try πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.align-items.anchor-center πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.align-self.anchor-center πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.anchor-name πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.anchor-name.none πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.anchor-scope πŸ“‹Edge11/14/2024 Firefox1/13/2026425
css.properties.anchor-scope.all πŸ“‹Edge11/14/2024 Firefox1/13/2026425
css.properties.anchor-scope.none πŸ“‹Edge11/14/2024 Firefox1/13/2026425
css.properties.block-size.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.bottom.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.bottom.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.height.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inline-size.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inset.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inset.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.inset-block.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inset-block.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.inset-block-end.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inset-block-end.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.inset-block-start.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inset-block-start.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.inset-inline.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inset-inline.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.inset-inline-end.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inset-inline-end.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.inset-inline-start.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.inset-inline-start.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.justify-items.anchor-center πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.justify-self.anchor-center πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.left.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.left.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-block.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-block-end.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-block-start.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-bottom.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-inline.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-inline-end.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-inline-start.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-left.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-right.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.margin-top.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.max-block-size.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.max-height.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.max-inline-size.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.max-width.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.min-block-size.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.min-height.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.min-inline-size.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.min-width.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.place-items.anchor-center πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.place-self.anchor-center πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-anchor.auto πŸ“‹Edge5/17/2024 Firefox1/13/2026606
Chrome: The generic auto value exists, but it does not yet have the effect described in the spec.Chrome Android: The generic auto value exists, but it does not yet have the effect described in the spec.Edge: The generic auto value exists, but it does not yet have the effect described in the spec.Opera: The generic auto value exists, but it does not yet have the effect described in the spec.Opera Android: The generic auto value exists, but it does not yet have the effect described in the spec.Samsung Internet: The generic auto value exists, but it does not yet have the effect described in the spec.WebView Android: The generic auto value exists, but it does not yet have the effect described in the spec.
css.properties.position-area πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.center πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.none πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-bottom πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-left πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-right πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-self-block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-self-block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-self-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-self-inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-self-inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-self-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-self-x-end πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-area.span-self-x-start πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-area.span-self-y-end πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-area.span-self-y-start πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-area.span-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-top πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-x-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-x-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-y-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.span-y-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-area.start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-try.block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.bottom πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.center πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.flip-block πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-try.flip-inline πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-try.flip-start πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-try.inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.left πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.none πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-try.right πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.self-block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.self-block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.self-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.self-inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.self-inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.self-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-all πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-bottom πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-left πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-right πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-self-block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-self-block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-self-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-self-inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-self-inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-self-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-self-x-end πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-try.span-self-x-start πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-try.span-self-y-end πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-try.span-self-y-start πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-try.span-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-top πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-x-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-x-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-y-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.span-y-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.top πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.x-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.x-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.y-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try.y-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks πŸ“‹Edge8/22/2024 Firefox1/13/2026509
css.properties.position-try-fallbacks.block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.bottom πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.center πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.flip-block πŸ“‹Edge8/22/2024 Firefox1/13/2026509
css.properties.position-try-fallbacks.flip-inline πŸ“‹Edge8/22/2024 Firefox1/13/2026509
css.properties.position-try-fallbacks.flip-start πŸ“‹Edge8/22/2024 Firefox1/13/2026509
css.properties.position-try-fallbacks.inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.left πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.none πŸ“‹Edge8/22/2024 Firefox1/13/2026509
css.properties.position-try-fallbacks.position-area πŸ“‹Edge8/22/2024 Firefox1/13/2026509
Chrome: inset-area values had to be wrapped inside an inset-area() function.Chrome Android: inset-area values had to be wrapped inside an inset-area() function.Edge: inset-area values had to be wrapped inside an inset-area() function.Opera: inset-area values had to be wrapped inside an inset-area() function.Opera Android: inset-area values had to be wrapped inside an inset-area() function.Samsung Internet: inset-area values had to be wrapped inside an inset-area() function.WebView Android: inset-area values had to be wrapped inside an inset-area() function.
css.properties.position-try-fallbacks.right πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.self-block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.self-block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.self-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.self-inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.self-inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.self-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-all πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-bottom πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-left πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-right πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-self-block-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-self-block-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-self-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-self-inline-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-self-inline-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-self-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-self-x-end πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-try-fallbacks.span-self-x-start πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-try-fallbacks.span-self-y-end πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-try-fallbacks.span-self-y-start πŸ“‹Edge12/5/2025 Firefox1/13/202639
css.properties.position-try-fallbacks.span-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-top πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-x-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-x-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-y-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.span-y-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.top πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.x-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.x-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.y-end πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-try-fallbacks.y-start πŸ“‹Edge9/19/2024 Firefox1/13/2026481
css.properties.position-visibility πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-visibility.always πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-visibility.anchors-visible πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.position-visibility.no-overflow πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.right.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.right.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.top.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.properties.top.anchor-size πŸ“‹Edge1/17/2025 Firefox1/13/2026361
css.properties.width.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.selectors.active-view-transition-type πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.types.anchor πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.types.anchor-size πŸ“‹Edge5/17/2024 Firefox1/13/2026606
css.types.length.rcap πŸ“‹Edge10/13/2023 Firefox1/13/2026823
css.types.length.rch πŸ“‹Edge3/13/2023 Firefox1/13/20261037
css.types.length.rex πŸ“‹Edge3/13/2023 Firefox1/13/20261037
css.types.length.ric πŸ“‹Edge3/13/2023 Firefox1/13/20261037
html.elements.button.commandfor.implicit_anchor_reference πŸ“‹Edge4/4/2025 Firefox1/13/2026284
html.elements.button.popovertarget.implicit_anchor_reference πŸ“‹Edge2/6/2025 Firefox1/13/2026341
html.elements.input.popovertarget.implicit_anchor_reference πŸ“‹Edge2/6/2025 Firefox1/13/2026341

2025/12

API First Browser Date Last Browser Date Days Notes
css.properties.font-family.math Edge1/12/2023 Safari12/12/20251065
css.properties.math-shift πŸ“‹Edge1/12/2023 Safari12/12/20251065
css.properties.math-shift.compact πŸ“‹Edge1/12/2023 Safari12/12/20251065
css.properties.math-shift.normal πŸ“‹Edge1/12/2023 Safari12/12/20251065
css.properties.scrollbar-color πŸ“‹Firefox12/11/2018 Safari12/12/20252558
css.properties.scrollbar-color.auto πŸ“‹Firefox12/11/2018 Safari12/12/20252558
css.properties.text-decoration.auto πŸ“‹Firefox10/22/2019 Safari12/12/20252243
css.properties.text-decoration.currentColor πŸ“‹Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.dashed πŸ“‹Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.dotted πŸ“‹Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.double πŸ“‹Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.from-font πŸ“‹Firefox10/22/2019 Safari12/12/20252243
css.properties.text-decoration.grammar-error πŸ“‹Edge1/25/2024 Safari12/12/2025687
css.properties.text-decoration.includes_color-and-style Firefox8/16/2011 Safari12/12/20255232
css.properties.text-decoration.includes_thickness Firefox10/22/2019 Safari12/12/20252243
css.properties.text-decoration.solid πŸ“‹Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.spelling-error πŸ“‹Edge1/25/2024 Safari12/12/2025687
css.properties.text-decoration.transparent πŸ“‹Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.wavy πŸ“‹Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration-line.grammar-error πŸ“‹Edge1/25/2024 Safari12/12/2025687
css.properties.text-decoration-line.spelling-error πŸ“‹Edge1/25/2024 Safari12/12/2025687
css.selectors.nesting.at-scope Firefox8/19/2025 Safari12/12/2025115
html.elements.button.command πŸ“‹Edge4/4/2025 Safari12/12/2025252
html.elements.button.command.request-close πŸ“‹Edge8/7/2025 Safari12/12/2025127
html.elements.button.commandfor πŸ“‹Edge4/4/2025 Safari12/12/2025252
css.at-rules.scope πŸ“‹Edge10/13/2023 Firefox12/9/2025788
css.properties.height.stretch πŸ“‹Safari9/30/2015 Firefox12/9/20253723
css.properties.width.stretch πŸ“‹Safari10/22/2013 Firefox12/9/20254431

2025/11

API First Browser Date Last Browser Date Days Notes
css.properties.text-autospace πŸ“‹Safari3/31/2025 Firefox11/11/2025225
css.properties.text-autospace.no-autospace πŸ“‹Safari3/31/2025 Firefox11/11/2025225
css.properties.text-autospace.normal πŸ“‹Safari3/31/2025 Firefox11/11/2025225

2025/10

API First Browser Date Last Browser Date Days Notes
css.properties.view-transition-class πŸ“‹Edge5/17/2024 Firefox10/14/2025515
css.properties.view-transition-class.none πŸ“‹Edge5/17/2024 Firefox10/14/2025515
css.properties.view-transition-name πŸ“‹Edge3/13/2023 Firefox10/14/2025946
css.properties.view-transition-name.match-element πŸ“‹Safari3/31/2025 Firefox10/14/2025197
css.properties.view-transition-name.none πŸ“‹Edge3/13/2023 Firefox10/14/2025946
css.selectors.active-view-transition πŸ“‹Edge5/17/2024 Firefox10/14/2025515
css.selectors.view-transition πŸ“‹Edge1/12/2023 Firefox10/14/20251006
css.selectors.view-transition-group πŸ“‹Edge1/12/2023 Firefox10/14/20251006
css.selectors.view-transition-image-pair πŸ“‹Edge1/12/2023 Firefox10/14/20251006
css.selectors.view-transition-new πŸ“‹Edge1/12/2023 Firefox10/14/20251006
css.selectors.view-transition-old πŸ“‹Edge1/12/2023 Firefox10/14/20251006
html.elements.iframe.cross-origin-top-navigation-by-user-activation Safari9/19/2019 Firefox10/14/20252217
Chrome: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Chrome Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Edge: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Firefox: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Firefox for Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Quest Browser: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Opera: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Opera Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Safari: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.Safari on iOS: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.Samsung Internet: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.WebView Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.WebView on iOS: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.

2025/9

API First Browser Date Last Browser Date Days Notes
css.selectors.details-content πŸ“‹Edge11/14/2024 Firefox9/16/2025306
Safari: Does not support chaining pseudo-elements after ::details-content. See bug 283446.Safari on iOS: Does not support chaining pseudo-elements after ::details-content. See bug 283446.WebView on iOS: Does not support chaining pseudo-elements after ::details-content. See bug 283446.
css.properties.animation-timeline πŸ“‹Firefox2/14/2023 Safari9/15/2025944
css.properties.animation-timeline.scroll πŸ“‹Firefox2/14/2023 Safari9/15/2025944
Firefox: Zero scroll range is treated as 100% but should be 0% (see bug 1780865).Firefox: Supports the deprecated horizontal and vertical axis values, and not the x and y values.
css.properties.animation-timeline.view πŸ“‹Firefox6/6/2023 Safari9/15/2025832
css.properties.content-visibility.auto πŸ“‹Edge8/27/2020 Safari9/15/20251845
Safari: Skipped content is not findable via find-in-page.Safari on iOS: Skipped content is not findable via find-in-page.WebView on iOS: Skipped content is not findable via find-in-page.
css.properties.overflow-block πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-block.auto πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-block.clip πŸ“‹Firefox9/22/2020 Safari9/15/20251819
css.properties.overflow-block.hidden πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-block.scroll πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-block.visible πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline.auto πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline.clip πŸ“‹Firefox9/22/2020 Safari9/15/20251819
css.properties.overflow-inline.hidden πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline.scroll πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline.visible πŸ“‹Firefox9/3/2019 Safari9/15/20252204
css.properties.scroll-timeline πŸ“‹Firefox3/14/2023 Safari9/15/2025916
Firefox: The syntax of the shorthand property uses the fixed order of name and then the axis.Firefox: Supports the deprecated horizontal and vertical axis values, and not the x and y values.Firefox: The @scroll-timeline at-rule is replaced with the longhand properties scroll-timeline-name and scroll-timeline-axis and the shorthand property scroll-timeline.
css.properties.scroll-timeline-axis πŸ“‹Firefox3/14/2023 Safari9/15/2025916
Firefox: The syntax of the shorthand property uses the fixed order of name and then the axis.Firefox: Supports the deprecated horizontal and vertical values, and not the x and y values.Firefox: The @scroll-timeline at-rule is replaced with the longhand properties scroll-timeline-name and scroll-timeline-axis and the shorthand property scroll-timeline.
css.properties.scroll-timeline-name πŸ“‹Firefox3/14/2023 Safari9/15/2025916
Firefox: The syntax of the shorthand property uses the fixed order of name and then the axis.Firefox: The @scroll-timeline at-rule is replaced with the longhand properties scroll-timeline-name and scroll-timeline-axis and the shorthand property scroll-timeline.
css.properties.view-timeline πŸ“‹Firefox6/6/2023 Safari9/15/2025832
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline-axis πŸ“‹Firefox6/6/2023 Safari9/15/2025832
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline-name πŸ“‹Firefox3/14/2023 Safari9/15/2025916
css.at-rules.font-face.font-feature-settings πŸ“‹Firefox12/1/2014 Edge9/5/20253931
Firefox: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox: From Firefox 4 to Firefox 14 (inclusive), Firefox supported an older, slightly different syntax. See OpenType Font Feature support in Firefox 4.Firefox for Android: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox for Android 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox for Android 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox for Android: From Firefox for Android 4 to Firefox for Android 14 (inclusive), Firefox for Android supported an older, slightly different syntax. See OpenType Font Feature support in Firefox for Android 4.

2025/7

API First Browser Date Last Browser Date Days Notes
css.properties.font-variant-emoji πŸ“‹Safari5/13/2024 Firefox7/22/2025435

2025/6

API First Browser Date Last Browser Date Days Notes
css.types.abs πŸ“‹Safari3/14/2022 Edge6/26/20251200
css.types.sign πŸ“‹Safari3/14/2022 Edge6/26/20251200
css.selectors.highlight πŸ“‹Edge9/1/2022 Firefox6/24/20251027
Firefox: Cannot yet be used with text-shadow. See bug 1845447.Firefox: Before Firefox 146, cannot be used with text-decoration. See bug 1845446.Firefox for Android: Cannot yet be used with text-shadow. See bug 1845447.Firefox for Android: Before Firefox for Android 146, cannot be used with text-decoration. See bug 1845446.Safari: The style is ignored when combined with user-select: none. See bug 278455.Safari on iOS: The style is ignored when combined with user-select: none. See bug 278455.WebView on iOS: The style is ignored when combined with user-select: none. See bug 278455.

2025/5

API First Browser Date Last Browser Date Days Notes
css.properties.print-color-adjust πŸ“‹Firefox2/8/2022 Edge5/1/20251178
Chrome: Chrome does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Chrome: Before version 26, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Chrome Android: Chrome Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Chrome Android: Before version 26, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Edge: Edge does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Edge: Before version 79, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Quest Browser: Quest Browser does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Quest Browser: Before version 5.0, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Opera: Opera does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Opera: Before version 15, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Opera Android: Opera Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Opera Android: Before version 14, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Safari: Safari does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Safari on iOS: Safari on iOS does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Samsung Internet: Samsung Internet does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Samsung Internet: Before version 1.5, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.WebView Android: WebView Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.WebView Android: Before version 4.4, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.WebView on iOS: WebView on iOS does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.
css.properties.print-color-adjust.economy πŸ“‹Safari7/25/2012 Edge5/1/20254663
css.properties.print-color-adjust.exact πŸ“‹Safari7/25/2012 Edge5/1/20254663

2025/4

API First Browser Date Last Browser Date Days Notes
html.elements.script.type.importmap.integrity πŸ“‹Edge7/25/2024 Firefox4/29/2025278
css.types.gradient.conic-gradient.single_color_stop πŸ“‹Firefox3/4/2025 Edge4/4/202531
css.types.gradient.linear-gradient.single_color_stop πŸ“‹Firefox3/4/2025 Edge4/4/202531
css.types.gradient.radial-gradient.single_color_stop πŸ“‹Firefox3/4/2025 Edge4/4/202531
css.types.gradient.repeating-conic-gradient.single_color_stop πŸ“‹Firefox3/4/2025 Edge4/4/202531
css.types.gradient.repeating-linear-gradient.single_color_stop πŸ“‹Firefox3/4/2025 Edge4/4/202531
css.types.gradient.repeating-radial-gradient.single_color_stop πŸ“‹Firefox3/4/2025 Edge4/4/202531

2025/3

API First Browser Date Last Browser Date Days Notes
css.properties.container-type.weak_containment πŸ“‹Edge9/19/2024 Safari3/31/2025193
css.properties.writing-mode.sideways-lr Firefox12/15/2015 Safari3/31/20253394
css.properties.writing-mode.sideways-rl Firefox12/15/2015 Safari3/31/20253394
css.types.attr.declaration-value πŸ“‹Firefox10/24/2023 Safari3/31/2025524
html.global_attributes.contenteditable.plaintext-only Safari6/7/2010 Firefox3/4/20255384

2024/12

API First Browser Date Last Browser Date Days Notes
css.at-rules.page πŸ“‹Firefox2/19/2013 Safari12/11/20244313
css.at-rules.page.size πŸ“‹Edge1/15/2020 Safari12/11/20241792
css.at-rules.page.size.jis-b4 πŸ“‹Edge5/21/2020 Safari12/11/20241665
css.at-rules.page.size.jis-b5 πŸ“‹Edge5/21/2020 Safari12/11/20241665
css.properties.ruby-align πŸ“‹Firefox5/12/2015 Safari12/11/20243501
Internet Explorer: Internet Explorer 9 and later supports an earlier draft of CSS Ruby with non-standard values for this property: auto, left, center, right, distribute-letter, distribute-space, and line-edge.
css.properties.ruby-align.center πŸ“‹Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-align.space-around πŸ“‹Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-align.space-between πŸ“‹Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-align.start πŸ“‹Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-position πŸ“‹Firefox5/12/2015 Safari12/11/20243501
Chrome: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).Chrome Android: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).Edge: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).Internet Explorer: Internet Explorer 9 and later support an old draft values: inline (equivalent of having display: inline on the ruby), and above (synonym of the modern over).Quest Browser: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).Opera: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).Opera Android: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).Safari: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).Safari on iOS: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).WebView Android: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).WebView on iOS: Implemented as a non-standard, prefixed, version of ruby-position, -webkit-ruby-position: it has two properties: before and after (both equivalent, for ltr and rtl scripts to the standard over value used with ruby-align: start).
css.properties.ruby-position.over Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-position.under Firefox5/12/2015 Safari12/11/20243501
css.properties.scrollbar-gutter πŸ“‹Edge9/24/2021 Safari12/11/20241174
css.properties.scrollbar-gutter.auto πŸ“‹Edge9/24/2021 Safari12/11/20241174
css.properties.scrollbar-gutter.stable πŸ“‹Edge9/24/2021 Safari12/11/20241174
css.properties.scrollbar-width πŸ“‹Firefox12/11/2018 Safari12/11/20242192
css.properties.scrollbar-width.auto πŸ“‹Firefox12/11/2018 Safari12/11/20242192
css.properties.scrollbar-width.none πŸ“‹Firefox12/11/2018 Safari12/11/20242192
css.properties.scrollbar-width.thin πŸ“‹Firefox12/11/2018 Safari12/11/20242192
css.properties.text-underline-offset.percentage πŸ“‹Firefox3/10/2020 Safari12/11/20241737
css.properties.text-underline-position.left πŸ“‹Edge1/15/2020 Safari12/11/20241792
css.properties.text-underline-position.right πŸ“‹Edge1/15/2020 Safari12/11/20241792
css.selectors.target-text πŸ“‹Edge3/4/2021 Safari12/11/20241378

2024/10

API First Browser Date Last Browser Date Days Notes
html.elements.img.fetchpriority πŸ“‹Edge4/28/2022 Firefox10/29/2024915
html.elements.link.fetchpriority πŸ“‹Edge4/28/2022 Firefox10/29/2024915
html.elements.script.fetchpriority πŸ“‹Edge4/28/2022 Firefox10/29/2024915
css.properties.box-decoration-break πŸ“‹Safari10/22/2013 Edge10/17/20244013
Chrome: This property is only supported for inline elements.Chrome Android: This property is only supported for inline elements.Edge: This property is only supported for inline elements.Quest Browser: This property is only supported for inline elements.Safari: This property is only supported for inline elements.Safari on iOS: This property is only supported for inline elements.Samsung Internet: This property is only supported for inline elements.WebView Android: This property is only supported for inline elements.WebView on iOS: This property is only supported for inline elements.
css.properties.box-decoration-break.clone πŸ“‹Safari10/22/2013 Edge10/17/20244013
Chrome: This value was only supported with the -webkit- prefix.Chrome Android: This value was only supported with the -webkit- prefix.Edge: This value was only supported with the -webkit- prefix.Quest Browser: This value was only supported with the -webkit- prefix.Opera: This value was only supported with the -webkit- prefix.Opera Android: This value was only supported with the -webkit- prefix.Samsung Internet: This value was only supported with the -webkit- prefix.WebView Android: This value was only supported with the -webkit- prefix.
css.properties.box-decoration-break.slice πŸ“‹Safari10/22/2013 Edge10/17/20244013
Chrome: This value was only supported with the -webkit- prefix.Chrome Android: This value was only supported with the -webkit- prefix.Edge: This value was only supported with the -webkit- prefix.Quest Browser: This value was only supported with the -webkit- prefix.Opera: This value was only supported with the -webkit- prefix.Opera Android: This value was only supported with the -webkit- prefix.Samsung Internet: This value was only supported with the -webkit- prefix.WebView Android: This value was only supported with the -webkit- prefix.
css.properties.text-wrap.auto πŸ“‹Firefox12/19/2023 Edge10/17/2024303
css.properties.text-wrap.stable πŸ“‹Firefox12/19/2023 Edge10/17/2024303
css.properties.text-wrap-mode πŸ“‹Safari3/5/2024 Edge10/17/2024226
css.properties.text-wrap-mode.nowrap Safari3/5/2024 Edge10/17/2024226
css.properties.text-wrap-mode.wrap Safari3/5/2024 Edge10/17/2024226
css.properties.text-wrap-style πŸ“‹Firefox3/19/2024 Edge10/17/2024212
css.properties.text-wrap-style.auto πŸ“‹Firefox3/19/2024 Edge10/17/2024212
css.properties.text-wrap-style.balance πŸ“‹Firefox3/19/2024 Edge10/17/2024212
css.properties.text-wrap-style.stable πŸ“‹Firefox3/19/2024 Edge10/17/2024212
html.elements.a.text_fragments Edge2/7/2020 Firefox10/1/20241698

2024/9

API First Browser Date Last Browser Date Days Notes
css.properties.backdrop-filter πŸ“‹Edge1/15/2020 Safari9/16/20241706
Firefox: Before Firefox 123, the property was not supported on systems with unknown GPU vendor (see bug 1868737).Firefox for Android: Before Firefox for Android 123, the property was not supported on systems with unknown GPU vendor (see bug 1868737).
css.properties.content-visibility πŸ“‹Edge8/27/2020 Safari9/16/20241481
css.properties.content-visibility.hidden πŸ“‹Edge8/27/2020 Safari9/16/20241481
css.properties.content-visibility.visible πŸ“‹Edge8/27/2020 Safari9/16/20241481
css.properties.offset-path.basic_shape πŸ“‹Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.border-box πŸ“‹Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.content-box πŸ“‹Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.fill-box πŸ“‹Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.none πŸ“‹Firefox1/7/2020 Safari9/16/20241714
css.properties.offset-path.padding-box πŸ“‹Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.stroke-box πŸ“‹Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.view-box πŸ“‹Edge8/21/2023 Safari9/16/2024392
css.properties.white-space.collapse πŸ“‹Edge6/2/2023 Safari9/16/2024472
css.properties.white-space.preserve πŸ“‹Edge6/2/2023 Safari9/16/2024472
css.properties.white-space.preserve-breaks πŸ“‹Edge6/2/2023 Safari9/16/2024472
css.properties.white-space.wrap πŸ“‹Edge6/2/2023 Safari9/16/2024472
css.types.color.color.relative_syntax πŸ“‹Edge11/2/2023 Safari9/16/2024319
Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).
css.types.color.hsl.mixed_type_parameters Firefox1/23/2024 Safari9/16/2024237
css.types.color.hsl.relative_syntax πŸ“‹Edge5/17/2024 Safari9/16/2024122
Chrome: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Chrome Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Edge: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).Samsung Internet: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).
css.types.color.hwb.mixed_type_parameters Firefox1/23/2024 Safari9/16/2024237
css.types.color.hwb.relative_syntax πŸ“‹Edge5/17/2024 Safari9/16/2024122
Chrome: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Chrome Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Edge: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).Samsung Internet: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).
css.types.color.lch.relative_syntax πŸ“‹Edge11/2/2023 Safari9/16/2024319
Safari: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Safari on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).WebView on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).
css.types.color.oklch.relative_syntax πŸ“‹Edge2/23/2024 Safari9/16/2024206
Chrome: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Chrome Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Edge: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Opera: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Opera Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Safari: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Safari on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Samsung Internet: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.WebView Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.WebView on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).
css.types.color.rgb.mixed_type_parameters Firefox5/9/2023 Safari9/16/2024496
css.types.color.rgb.relative_syntax πŸ“‹Edge2/23/2024 Safari9/16/2024206
Chrome: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Chrome Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Edge: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Opera: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Opera Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Safari: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.Safari on iOS: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.Samsung Internet: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.WebView Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.WebView on iOS: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.
css.properties.hyphens.language_czech Safari3/21/2016 Firefox9/3/20243088
html.elements.details.name Edge12/7/2023 Firefox9/3/2024271

2024/8

API First Browser Date Last Browser Date Days Notes
css.at-rules.starting-style πŸ“‹Edge9/15/2023 Firefox8/6/2024326
css.properties.transition.transition-behavior Edge9/15/2023 Firefox8/6/2024326
css.properties.transition-behavior πŸ“‹Edge9/15/2023 Firefox8/6/2024326
css.properties.transition-behavior.allow-discrete πŸ“‹Edge9/15/2023 Firefox8/6/2024326
css.properties.transition-behavior.normal πŸ“‹Edge9/15/2023 Firefox8/6/2024326

2024/7

API First Browser Date Last Browser Date Days Notes
css.properties.align-content.flex_context.safe_unsafe Firefox10/23/2018 Safari7/29/20242106
Chrome: Before version 115, this value is recognized, but has no effect.Chrome Android: Before version 115, this value is recognized, but has no effect.Edge: Before version 115, this value is recognized, but has no effect.Opera: Before version 101, this value is recognized, but has no effect.Opera Android: Before version 77, this value is recognized, but has no effect.Samsung Internet: Before version 23.0, this value is recognized, but has no effect.WebView Android: Before version 115, this value is recognized, but has no effect.
css.properties.align-items.flex_context.safe_unsafe Firefox10/23/2018 Safari7/29/20242106
Chrome: Before version 115, this value is recognized, but has no effect.Chrome Android: Before version 115, this value is recognized, but has no effect.Edge: Before version 115, this value is recognized, but has no effect.Opera: Before version 101, this value is recognized, but has no effect.Opera Android: Before version 77, this value is recognized, but has no effect.Samsung Internet: Before version 23.0, this value is recognized, but has no effect.WebView Android: Before version 115, this value is recognized, but has no effect.
css.properties.align-self.flex_context.safe_unsafe Firefox10/23/2018 Safari7/29/20242106
Chrome: Before version 115, this value is recognized, but has no effect.Chrome Android: Before version 115, this value is recognized, but has no effect.Edge: Before version 115, this value is recognized, but has no effect.Opera: Before version 101, this value is recognized, but has no effect.Opera Android: Before version 77, this value is recognized, but has no effect.Samsung Internet: Before version 23.0, this value is recognized, but has no effect.WebView Android: Before version 115, this value is recognized, but has no effect.
css.properties.justify-content.flex_context.safe_unsafe Firefox10/23/2018 Safari7/29/20242106
Chrome: Before version 115, this value is recognized, but has no effect.Chrome Android: Before version 115, this value is recognized, but has no effect.Edge: Before version 115, this value is recognized, but has no effect.Opera: Before version 101, this value is recognized, but has no effect.Opera Android: Before version 77, this value is recognized, but has no effect.Samsung Internet: Before version 23.0, this value is recognized, but has no effect.WebView Android: Before version 115, this value is recognized, but has no effect.
css.properties.font-size-adjust πŸ“‹Firefox6/17/2008 Edge7/25/20245882
Firefox: Before Firefox 40, font-size-adjust: 0 was incorrectly interpreted as font-size-adjust: none (bug 1144885).Firefox: Only supported on Windows.Firefox for Android: Before Firefox for Android 40, font-size-adjust: 0 was incorrectly interpreted as font-size-adjust: none (bug 1144885).
css.properties.font-size-adjust.from-font πŸ“‹Safari9/18/2023 Edge7/25/2024311
css.properties.font-size-adjust.none πŸ“‹Firefox6/17/2008 Edge7/25/20245882
css.properties.font-size-adjust.two-values Firefox9/7/2021 Edge7/25/20241052
css.at-rules.property πŸ“‹Edge8/27/2020 Firefox7/9/20241412
css.at-rules.property.inherits πŸ“‹Edge8/27/2020 Firefox7/9/20241412
css.at-rules.property.initial-value πŸ“‹Edge8/27/2020 Firefox7/9/20241412
css.at-rules.property.syntax πŸ“‹Edge8/27/2020 Firefox7/9/20241412
css.properties.content.alt_text Edge1/15/2020 Firefox7/9/20241637
css.types.calc.color_component Safari3/27/2023 Firefox7/9/2024470
css.types.color.lab.relative_syntax πŸ“‹Safari3/27/2023 Firefox7/9/2024470
css.types.color.oklab.relative_syntax πŸ“‹Safari3/27/2023 Firefox7/9/2024470
Chrome: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Chrome Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Edge: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Opera: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Opera Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Samsung Internet: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.WebView Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.

2024/6

API First Browser Date Last Browser Date Days Notes
css.types.gradient.conic-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.conic-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.linear-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.linear-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.radial-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.radial-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-conic-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-conic-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-linear-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-linear-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-radial-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-radial-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
html.elements.base.href.forbid_data_javascript_urls Edge1/15/2020 Firefox6/11/20241609
html.elements.link.rel.dns-prefetch πŸ“‹Safari6/7/2010 Firefox6/11/20245118
Firefox: Only HTTP pages were supported.Firefox for Android: Only HTTP pages were supported.

2024/5

API First Browser Date Last Browser Date Days Notes
css.selectors.state πŸ“‹Safari3/5/2024 Edge5/17/202473
Chrome: Uses a dashed-ident (such as :--foo) instead of :state().Chrome Android: Uses a dashed-ident (such as :--foo) instead of :state().Edge: Uses a dashed-ident (such as :--foo) instead of :state().Quest Browser: Uses a dashed-ident (such as :--foo) instead of :state().Opera: Uses a dashed-ident (such as :--foo) instead of :state().Opera Android: Uses a dashed-ident (such as :--foo) instead of :state().Samsung Internet: Uses a dashed-ident (such as :--foo) instead of :state().WebView Android: Uses a dashed-ident (such as :--foo) instead of :state().
css.types.mod πŸ“‹Safari3/14/2022 Edge5/17/2024795
css.types.mod.mixed_type_parameters πŸ“‹Firefox9/26/2023 Edge5/17/2024234
css.types.rem πŸ“‹Safari3/14/2022 Edge5/17/2024795
css.types.rem.mixed_type_parameters πŸ“‹Firefox9/26/2023 Edge5/17/2024234
css.types.round πŸ“‹Safari3/14/2022 Edge5/17/2024795
css.types.round.mixed_type_parameters πŸ“‹Firefox9/26/2023 Edge5/17/2024234
css.properties.zoom πŸ“‹Safari3/18/2008 Firefox5/14/20245901
Firefox: Before Firefox 131, SVG elements are not zoomed properly. See bug 1905023 and bug 878346.Firefox for Android: Before Firefox for Android 131, SVG elements are not zoomed properly. See bug 1905023 and bug 878346.
html.elements.iframe.allow.screen-wake-lock πŸ“‹Edge7/16/2020 Firefox5/14/20241398
css.at-rules.import.supports πŸ“‹Firefox7/4/2023 Safari5/13/2024314
css.properties.text-wrap.balance πŸ“‹Edge6/2/2023 Safari5/13/2024346
css.types.color.light-dark πŸ“‹Firefox11/21/2023 Safari5/13/2024174
html.elements.template.shadowrootclonable πŸ“‹Firefox4/16/2024 Safari5/13/202427

2024/4

API First Browser Date Last Browser Date Days Notes
css.properties.direction.vertical_slider_direction Safari5/18/2023 Edge4/18/2024336
Firefox: Only supported for vertical range sliders.Firefox for Android: Only supported for vertical range sliders.Safari: Only supported for vertical range sliders.Safari on iOS: Only supported for vertical range sliders.WebView on iOS: Only supported for vertical range sliders.
css.properties.writing-mode.vertical_oriented_form_controls Firefox11/21/2023 Edge4/18/2024149
Chrome: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Chrome: Supported for select, button, textarea and textual input elements.Chrome: Only supported for select and button elements.Chrome Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Chrome Android: Supported for select, button, textarea and textual input elements.Chrome Android: Only supported for select and button elements.Edge: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Edge: Supported for select, button, textarea and textual input elements.Edge: Only supported for select and button elements.Opera: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Opera: Supported for select, button, textarea and textual input elements.Opera: Only supported for select and button elements.Opera Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Opera Android: Supported for select, button, textarea and textual input elements.Opera Android: Only supported for select and button elements.Safari: Support for range sliders, textual inputs, and textareas onlySafari on iOS: Support for range sliders, textual inputs, and textareas onlySamsung Internet: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Samsung Internet: Supported for select, button, textarea and textual input elements.WebView Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.WebView Android: Supported for select, button, textarea and textual input elements.WebView Android: Only supported for select and button elements.WebView on iOS: Support for range sliders, textual inputs, and textareas only
css.properties.align-content.block_context πŸ“‹Safari3/5/2024 Firefox4/16/202442
css.properties.transform-box.content-box πŸ“‹Safari3/24/2020 Firefox4/16/20241484
css.properties.transform-box.stroke-box πŸ“‹Safari3/24/2020 Firefox4/16/20241484
css.selectors.backdrop.popover Edge6/2/2023 Firefox4/16/2024319
css.selectors.popover-open πŸ“‹Edge6/2/2023 Firefox4/16/2024319
html.elements.button.popovertarget πŸ“‹Edge6/2/2023 Firefox4/16/2024319
html.elements.button.popovertargetaction πŸ“‹Edge6/2/2023 Firefox4/16/2024319
html.elements.input.popovertarget πŸ“‹Edge6/2/2023 Firefox4/16/2024319
html.elements.input.popovertargetaction πŸ“‹Edge6/2/2023 Firefox4/16/2024319
html.global_attributes.popover πŸ“‹Edge6/2/2023 Firefox4/16/2024319

2024/3

API First Browser Date Last Browser Date Days Notes
css.properties.paint-order πŸ“‹Safari9/19/2017 Edge3/22/20242376
Chrome: Does not affect stroked HTML text, see bug 41372165Chrome Android: Does not affect stroked HTML text, see bug 41372165Edge: Does not affect stroked HTML text, see bug 41372165Quest Browser: Does not affect stroked HTML text, see bug 41372165Opera: Does not affect stroked HTML text, see bug 41372165Opera Android: Does not affect stroked HTML text, see bug 41372165Safari: Does not affect stroked HTML text, see bug 168601Safari on iOS: Does not affect stroked HTML text, see bug 168601Samsung Internet: Does not affect stroked HTML text, see bug 41372165WebView Android: Does not affect stroked HTML text, see bug 41372165WebView on iOS: Does not affect stroked HTML text, see bug 168601
html.elements.template.shadowrootdelegatesfocus πŸ“‹Safari3/27/2023 Edge3/22/2024361
css.properties.text-wrap.nowrap πŸ“‹Edge6/2/2023 Firefox3/19/2024291
css.properties.text-wrap.wrap πŸ“‹Edge6/2/2023 Firefox3/19/2024291
css.properties.white-space-collapse πŸ“‹Edge6/2/2023 Firefox3/19/2024291
css.properties.white-space-collapse.break-spaces πŸ“‹Edge6/2/2023 Firefox3/19/2024291
css.properties.white-space-collapse.collapse πŸ“‹Edge6/2/2023 Firefox3/19/2024291
css.properties.white-space-collapse.preserve πŸ“‹Edge6/2/2023 Firefox3/19/2024291
css.properties.white-space-collapse.preserve-breaks πŸ“‹Edge6/2/2023 Firefox3/19/2024291
css.properties.rx πŸ“‹Firefox9/3/2019 Safari3/5/20241645
Safari: Before Safari 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.Safari on iOS: Before Safari on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.WebView on iOS: Before WebView on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.
css.properties.rx.auto πŸ“‹Firefox9/3/2019 Safari3/5/20241645
css.properties.ry πŸ“‹Firefox9/3/2019 Safari3/5/20241645
Safari: Before Safari 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.Safari on iOS: Before Safari on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.WebView on iOS: Before WebView on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.
css.properties.ry.auto πŸ“‹Firefox9/3/2019 Safari3/5/20241645
css.properties.text-decoration-thickness.percentage Firefox3/10/2020 Safari3/5/20241456
css.properties.text-wrap πŸ“‹Edge6/2/2023 Safari3/5/2024277
css.selectors.backdrop.inherit_from_originating_element Firefox11/21/2023 Safari3/5/2024105

2024/2

API First Browser Date Last Browser Date Days Notes
html.elements.template.shadowrootmode πŸ“‹Edge3/13/2023 Firefox2/20/2024344

2024/1

API First Browser Date Last Browser Date Days Notes
css.properties.offset.auto πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.border-box πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.bottom πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.center πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.content-box πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.fill-box πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.left πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.normal πŸ“‹Edge8/21/2023 Firefox1/23/2024155
css.properties.offset.padding-box πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.right πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.stroke-box πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.top πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.view-box πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-path.ray πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-path.url πŸ“‹Edge8/21/2023 Firefox1/23/2024155
css.properties.offset-position πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.auto πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.bottom πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.center πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.left πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.normal πŸ“‹Edge8/21/2023 Firefox1/23/2024155
css.properties.offset-position.right πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.top πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.types.basic-shape.rect πŸ“‹Edge11/2/2023 Firefox1/23/202482
Chrome: Only supported on the offset-path property.Chrome Android: Only supported on the offset-path property.Edge: Only supported on the offset-path property.Opera: Only supported on the offset-path property.Opera Android: Only supported on the offset-path property.Samsung Internet: Only supported on the offset-path property.WebView Android: Only supported on the offset-path property.
css.types.basic-shape.xywh πŸ“‹Edge11/2/2023 Firefox1/23/202482
Chrome: Only supported on the offset-path property.Chrome Android: Only supported on the offset-path property.Edge: Only supported on the offset-path property.Opera: Only supported on the offset-path property.Opera Android: Only supported on the offset-path property.Samsung Internet: Only supported on the offset-path property.WebView Android: Only supported on the offset-path property.
css.types.ray πŸ“‹Safari9/12/2022 Firefox1/23/2024498
css.types.ray.position Edge8/21/2023 Firefox1/23/2024155
css.types.ray.size Edge8/21/2023 Firefox1/23/2024155
html.elements.form.autocomplete.webauthn πŸ“‹Edge12/5/2022 Firefox1/23/2024414
html.elements.hr.hr_in_select Safari9/18/2023 Firefox1/23/2024127
Chrome: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Chrome: Does not expose the <hr> in the accessibility tree.Edge: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Edge: Does not expose the <hr> in the accessibility tree.Firefox: Does not expose the <hr> in the accessibility tree.Opera: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Opera: Does not expose the <hr> in the accessibility tree.Safari: Does not expose the <hr> in the accessibility tree.Safari on iOS: Does not expose the <hr> in the accessibility tree.WebView on iOS: Does not expose the <hr> in the accessibility tree.
html.elements.select.hr_in_select Safari9/18/2023 Firefox1/23/2024127
Chrome: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Chrome: Does not expose the <hr> in the accessibility tree.Edge: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Edge: Does not expose the <hr> in the accessibility tree.Firefox: Does not expose the <hr> in the accessibility tree.Opera: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Opera: Does not expose the <hr> in the accessibility tree.Safari: Does not expose the <hr> in the accessibility tree.Safari on iOS: Does not expose the <hr> in the accessibility tree.WebView on iOS: Does not expose the <hr> in the accessibility tree.
html.elements.video.disablepictureinpicture πŸ“‹Edge1/15/2020 Firefox1/23/20241469
Firefox: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox for Android: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox for Android: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.

2023/12

API First Browser Date Last Browser Date Days Notes
css.selectors.has πŸ“‹Safari3/14/2022 Firefox12/19/2023645
html.elements.iframe.loading πŸ“‹Edge1/15/2020 Firefox12/19/20231434
css.properties.counter-set πŸ“‹Firefox7/9/2019 Safari12/11/20231616
css.properties.counter-set.list-item πŸ“‹Firefox7/9/2019 Safari12/11/20231616
css.properties.counter-set.none πŸ“‹Firefox7/9/2019 Safari12/11/20231616
css.selectors.nesting πŸ“‹Firefox8/29/2023 Safari12/11/2023104
Chrome: Does not support nested rules that start with a type selector.Chrome Android: Does not support nested rules that start with a type selector.Edge: Does not support nested rules that start with a type selector.Opera: Does not support nested rules that start with a type selector.Opera Android: Does not support nested rules that start with a type selector.Safari: Does not support nested rules that start with a type selector.Safari on iOS: Does not support nested rules that start with a type selector.Samsung Internet: Does not support nested rules that start with a type selector.WebView Android: Does not support nested rules that start with a type selector.WebView on iOS: Does not support nested rules that start with a type selector.
css.types.easing-function.linear-function πŸ“‹Firefox4/11/2023 Safari12/11/2023244
css.types.length.cap Firefox2/8/2022 Safari12/11/2023671
html.elements.link.imagesizes πŸ“‹Edge1/15/2020 Safari12/11/20231426
html.elements.link.imagesrcset πŸ“‹Edge1/15/2020 Safari12/11/20231426
css.at-rules.media.scripting πŸ“‹Firefox5/9/2023 Edge12/7/2023212
css.properties.background-clip.text πŸ“‹Firefox9/20/2016 Edge12/7/20232634
Chrome: The text value is only supported by -webkit-background-clip (and not by background-clip; see bug 40229927).Chrome Android: The text value is only supported by -webkit-background-clip (and not by background-clip; see bug 40229927).Edge: The text value is only supported by -webkit-background-clip (and not by background-clip; see bug 40229927).Edge: Before Edge 15, this value was supported with the prefixed version of the property only.Firefox: Does not work with background-attachment: fixed (bug 1313757), in multi-layer backgrounds with other values (bug 1481498), and in some other special cases (see bug 1656784).Firefox for Android: Does not work with background-attachment: fixed (bug 1313757), in multi-layer backgrounds with other values (bug 1481498), and in some other special cases (see bug 1656784).Quest Browser: The text value is only supported by -webkit-background-clip (and not by background-clip; see bug 40229927).Opera: The text value is only supported by -webkit-background-clip (and not by background-clip; see bug 40229927).Opera Android: The text value is only supported by -webkit-background-clip (and not by background-clip; see bug 40229927).Safari: The text value is only supported by -webkit-background-clip (and not by background-clip).Safari on iOS: The text value is only supported by -webkit-background-clip (and not by background-clip).Samsung Internet: The text value is only supported by -webkit-background-clip (and not by background-clip; see bug 40229927).WebView Android: The text value is only supported by -webkit-background-clip (and not by background-clip; see bug 40229927).WebView on iOS: The text value is only supported by -webkit-background-clip (and not by background-clip).
css.properties.mask πŸ“‹Firefox4/19/2017 Edge12/7/20232423
Chrome: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Chrome: While the property is recognized, values applied to it don't have any effect.Chrome Android: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Chrome Android: While the property is recognized, values applied to it don't have any effect.Edge: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Edge: While the property is recognized, values applied to it don't have any effect.Firefox: Only supports mask: url(file.svg#mask_id) or mask: url(#mask_id), where the URL is a reference to an SVG <mask> element.Firefox for Android: Only supports mask: url(file.svg#mask_id) or mask: url(#mask_id), where the URL is a reference to an SVG <mask> element.Quest Browser: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Quest Browser: While the property is recognized, values applied to it don't have any effect.Opera: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Opera: While the property is recognized, values applied to it don't have any effect.Opera Android: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Opera Android: While the property is recognized, values applied to it don't have any effect.Safari: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Safari: While the property is recognized, values applied to it don't have any effect.Safari on iOS: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Safari on iOS: While the property is recognized, values applied to it don't have any effect.Samsung Internet: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Samsung Internet: While the property is recognized, values applied to it don't have any effect.WebView Android: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.WebView Android: While the property is recognized, values applied to it don't have any effect.WebView on iOS: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.WebView on iOS: While the property is recognized, values applied to it don't have any effect.
css.properties.mask-clip πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-composite πŸ“‹Firefox4/19/2017 Edge12/7/20232423
Chrome: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Chrome Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Edge: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Opera: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Opera Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Safari: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Safari on iOS: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Samsung Internet: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.WebView Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.WebView on iOS: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.
css.properties.mask-composite.add πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-composite.exclude πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-composite.intersect πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-composite.subtract πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-image πŸ“‹Firefox4/19/2017 Edge12/7/20232423
Chrome: From version 8, Chrome added support for gradient values. Initially, Chrome supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Chrome Android: From version 18, Chrome Android added support for gradient values. Initially, Chrome Android supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Quest Browser: From version 5.0, Quest Browser added support for gradient values. Initially, Quest Browser supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Safari: Initially, Safari supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Safari on iOS: Initially, Safari on iOS supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Samsung Internet: From version 1.0, Samsung Internet added support for gradient values. Initially, Samsung Internet supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.WebView Android: Initially, Android supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.WebView on iOS: Initially, WebView on iOS supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.
css.properties.mask-mode πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-mode.alpha πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-mode.luminance πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-mode.match-source πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-origin πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-position πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-repeat πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-size πŸ“‹Firefox4/19/2017 Edge12/7/20232423
css.selectors.dir πŸ“‹Firefox9/20/2016 Edge12/7/20232634
css.types.exp πŸ“‹Safari3/14/2022 Edge12/7/2023633
css.types.hypot πŸ“‹Safari3/14/2022 Edge12/7/2023633
css.types.log πŸ“‹Safari3/14/2022 Edge12/7/2023633
css.types.pow πŸ“‹Safari3/14/2022 Edge12/7/2023633
css.types.sqrt πŸ“‹Safari3/14/2022 Edge12/7/2023633

2023/11

API First Browser Date Last Browser Date Days Notes
css.types.length.lh πŸ“‹Edge1/12/2023 Firefox11/21/2023313
css.types.length.rlh πŸ“‹Edge3/13/2023 Firefox11/21/2023253
html.elements.input.type_range.vertical_orientation Edge7/29/2015 Firefox11/21/20233037
Chrome: Vertical orientation available via the writing-mode property (see Creating vertical controls).Chrome: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Chrome Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Chrome Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Edge: Vertical orientation available by setting the writing-mode: bt-lr style on the input element.Firefox: Vertical orientation available via the writing-mode property (see Creating vertical controls).Firefox: Supported using the non-standard orient="vertical" attribute.Firefox for Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Firefox for Android: Supported using the non-standard orient="vertical" attribute.Internet Explorer: Vertical orientation available by setting the writing-mode: bt-lr style on the input element.Quest Browser: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Opera: Vertical orientation available via the writing-mode property (see Creating vertical controls).Opera: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Opera Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Opera Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Safari: Vertical orientation available via the writing-mode property (see Creating vertical controls).Safari: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Safari on iOS: Vertical orientation available via the writing-mode property (see Creating vertical controls).Safari on iOS: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Samsung Internet: Vertical orientation available via the writing-mode property (see Creating vertical controls).Samsung Internet: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.WebView Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).WebView Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.WebView on iOS: Vertical orientation available via the writing-mode property (see Creating vertical controls).WebView on iOS: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.
css.properties.clip-path.border-box πŸ“‹Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-path.content-box πŸ“‹Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-path.fill-box πŸ“‹Firefox1/24/2017 Edge11/2/20232473
Firefox: This value was supported before Firefox 51, but as an alias to border-box.Firefox for Android: This value was supported before Firefox for Android 51, but as an alias to border-box.
css.properties.clip-path.margin-box πŸ“‹Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-path.padding-box πŸ“‹Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-path.stroke-box πŸ“‹Firefox1/24/2017 Edge11/2/20232473
Firefox: This value was supported before Firefox 51, but as an alias to border-box.Firefox for Android: This value was supported before Firefox for Android 51, but as an alias to border-box.
css.properties.clip-path.view-box πŸ“‹Firefox6/13/2017 Edge11/2/20232333
css.selectors.user-invalid πŸ“‹Firefox4/19/2021 Edge11/2/2023927
css.selectors.user-valid πŸ“‹Firefox4/19/2021 Edge11/2/2023927

2023/10

API First Browser Date Last Browser Date Days Notes
css.properties.clear.inline-end πŸ“‹Firefox8/8/2017 Edge10/13/20232257
css.properties.clear.inline-start πŸ“‹Firefox8/8/2017 Edge10/13/20232257
css.properties.float.inline-end πŸ“‹Firefox8/8/2017 Edge10/13/20232257
css.properties.float.inline-start πŸ“‹Firefox8/8/2017 Edge10/13/20232257
css.properties.resize.block Firefox10/23/2018 Edge10/13/20231816
css.properties.resize.inline Firefox10/23/2018 Edge10/13/20231816
css.properties.transform-box.border-box πŸ“‹Firefox8/8/2017 Edge10/13/20232257
html.elements.search πŸ“‹Safari9/18/2023 Edge10/13/202325

2023/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.counter-style πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.additive-symbols πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.fallback πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.negative πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.pad πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.prefix πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.range πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.suffix πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.symbols πŸ“‹Firefox10/14/2014 Safari9/18/20233261
Chrome: Does not support <image> as a value for the symbols descriptor.Chrome Android: Does not support <image> as a value for the symbols descriptor.Edge: Does not support <image> as a value for the symbols descriptor.Firefox: Does not support <image> as a value for the symbols descriptor.Firefox for Android: Does not support <image> as a value for the symbols descriptor.Quest Browser: Does not support <image> as a value for the symbols descriptor.Opera: Does not support <image> as a value for the symbols descriptor.Opera Android: Does not support <image> as a value for the symbols descriptor.Samsung Internet: Does not support <image> as a value for the symbols descriptor.WebView Android: Does not support <image> as a value for the symbols descriptor.
css.at-rules.counter-style.system πŸ“‹Firefox10/14/2014 Safari9/18/20233261
css.at-rules.font-face.size-adjust πŸ“‹Edge7/22/2021 Safari9/18/2023788
css.at-rules.font-face.src.tech_keyword Firefox11/15/2022 Safari9/18/2023307
css.at-rules.media.overflow-block πŸ“‹Firefox3/19/2019 Safari9/18/20231644
css.at-rules.media.overflow-inline πŸ“‹Firefox3/19/2019 Safari9/18/20231644
css.at-rules.media.update πŸ“‹Firefox6/28/2022 Safari9/18/2023447
css.at-rules.supports.font-format Firefox10/18/2022 Safari9/18/2023335
css.at-rules.supports.font-tech Firefox10/18/2022 Safari9/18/2023335
css.properties.background-image.image-set πŸ“‹Firefox6/1/2021 Safari9/18/2023839
Chrome: Support for url images only and x is the only supported resolution unit.Chrome Android: Support for url images only and x is the only supported resolution unit.Edge: Support for url images only and x is the only supported resolution unit.Firefox: The type() function is not supported as an argument to image-set().Firefox for Android: The type() function is not supported as an argument to image-set().Quest Browser: Support for url images only and x is the only supported resolution unit.Opera: Support for url images only and x is the only supported resolution unit.Opera Android: Support for url images only and x is the only supported resolution unit.Safari: The type() function is not supported as an argument to image-set().Safari: The type() function is not supported as an argument to image-set().Safari: Support for url images only and x is the only supported resolution unit.Safari: Support for url images only and x is the only supported resolution unit.Safari on iOS: The type() function is not supported as an argument to image-set().Safari on iOS: The type() function is not supported as an argument to image-set().Safari on iOS: Support for url images only and x is the only supported resolution unit.Safari on iOS: Support for url images only and x is the only supported resolution unit.Samsung Internet: Support for url images only and x is the only supported resolution unit.WebView Android: Support for url images only and x is the only supported resolution unit.WebView on iOS: The type() function is not supported as an argument to image-set().WebView on iOS: The type() function is not supported as an argument to image-set().WebView on iOS: Support for url images only and x is the only supported resolution unit.WebView on iOS: Support for url images only and x is the only supported resolution unit.
css.properties.contain-intrinsic-block-size πŸ“‹Edge10/21/2021 Safari9/18/2023697
css.properties.contain-intrinsic-block-size.none πŸ“‹Edge2/3/2022 Safari9/18/2023592
css.properties.contain-intrinsic-height πŸ“‹Edge10/21/2021 Safari9/18/2023697
css.properties.contain-intrinsic-height.none πŸ“‹Edge2/3/2022 Safari9/18/2023592
css.properties.contain-intrinsic-inline-size πŸ“‹Edge10/21/2021 Safari9/18/2023697
css.properties.contain-intrinsic-inline-size.none πŸ“‹Edge2/3/2022 Safari9/18/2023592
css.properties.contain-intrinsic-size πŸ“‹Edge5/21/2020 Safari9/18/20231215
css.properties.contain-intrinsic-size.auto_none Firefox8/29/2023 Safari9/18/202320
css.properties.contain-intrinsic-size.none πŸ“‹Edge2/3/2022 Safari9/18/2023592
css.properties.contain-intrinsic-width πŸ“‹Edge10/21/2021 Safari9/18/2023697
css.properties.contain-intrinsic-width.none πŸ“‹Edge2/3/2022 Safari9/18/2023592
css.properties.content.image-set πŸ“‹Firefox6/1/2021 Safari9/18/2023839
Chrome: Support for url images only and x is the only supported resolution unit.Chrome Android: Support for url images only and x is the only supported resolution unit.Edge: Support for url images only and x is the only supported resolution unit.Firefox: The type() function is not supported as an argument to image-set().Firefox for Android: The type() function is not supported as an argument to image-set().Quest Browser: Support for url images only and x is the only supported resolution unit.Opera: Support for url images only and x is the only supported resolution unit.Opera Android: Support for url images only and x is the only supported resolution unit.Safari: The type() function is not supported as an argument to image-set().Safari: The type() function is not supported as an argument to image-set().Safari: Support for url images only and x is the only supported resolution unit.Safari: Support for url images only and x is the only supported resolution unit.Safari on iOS: The type() function is not supported as an argument to image-set().Safari on iOS: The type() function is not supported as an argument to image-set().Safari on iOS: Support for url images only and x is the only supported resolution unit.Safari on iOS: Support for url images only and x is the only supported resolution unit.Samsung Internet: Support for url images only and x is the only supported resolution unit.WebView Android: Support for url images only and x is the only supported resolution unit.WebView on iOS: The type() function is not supported as an argument to image-set().WebView on iOS: The type() function is not supported as an argument to image-set().WebView on iOS: Support for url images only and x is the only supported resolution unit.WebView on iOS: Support for url images only and x is the only supported resolution unit.
css.properties.hyphenate-character πŸ“‹Firefox3/8/2022 Safari9/18/2023559
css.properties.hyphens πŸ“‹Firefox12/15/2015 Safari9/18/20232834
Edge: Only works if the specified language is the same as the language of the underlying OS.Internet Explorer: Only works if the specified language is the same as the language of the underlying OS.
css.properties.list-style-type.ethiopic-halehame Firefox11/9/2004 Safari9/18/20236887
css.properties.list-style-type.ethiopic-halehame-am Firefox11/9/2004 Safari9/18/20236887
css.selectors.only-child.no_parent_required Firefox3/7/2017 Safari9/18/20232386
css.types.image.image-set πŸ“‹Firefox6/1/2021 Safari9/18/2023839
Chrome: Support for url images only and x is the only supported resolution unit.Chrome Android: Support for url images only and x is the only supported resolution unit.Edge: Support for url images only and x is the only supported resolution unit.Firefox: The type() function is not supported as an argument to image-set().Firefox for Android: The type() function is not supported as an argument to image-set().Quest Browser: Support for url images only and x is the only supported resolution unit.Opera: Support for url images only and x is the only supported resolution unit.Opera Android: Support for url images only and x is the only supported resolution unit.Safari: The type() function is not supported as an argument to image-set().Safari: The type() function is not supported as an argument to image-set().Safari: Support for url images only and x is the only supported resolution unit.Safari: Support for url images only and x is the only supported resolution unit.Safari on iOS: The type() function is not supported as an argument to image-set().Safari on iOS: The type() function is not supported as an argument to image-set().Safari on iOS: Support for url images only and x is the only supported resolution unit.Safari on iOS: Support for url images only and x is the only supported resolution unit.Samsung Internet: Support for url images only and x is the only supported resolution unit.WebView Android: Support for url images only and x is the only supported resolution unit.WebView on iOS: The type() function is not supported as an argument to image-set().WebView on iOS: The type() function is not supported as an argument to image-set().WebView on iOS: Support for url images only and x is the only supported resolution unit.WebView on iOS: Support for url images only and x is the only supported resolution unit.
html.elements.iframe.sandbox.allow-downloads πŸ“‹Edge5/21/2020 Safari9/18/20231215
html.elements.link.rel.modulepreload πŸ“‹Edge1/15/2020 Safari9/18/20231342
html.elements.link.rel.modulepreload.as-script πŸ“‹Edge1/15/2020 Safari9/18/20231342
css.properties.font-variant-position πŸ“‹Firefox12/1/2014 Edge9/15/20233210
css.properties.font-variant-position.normal πŸ“‹Firefox12/1/2014 Edge9/15/20233210
css.properties.font-variant-position.sub πŸ“‹Firefox12/1/2014 Edge9/15/20233210
Chrome: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Chrome Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Edge: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Opera: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Opera Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Safari: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).Safari on iOS: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).Samsung Internet: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).WebView Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).WebView on iOS: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).
css.properties.font-variant-position.super πŸ“‹Firefox12/1/2014 Edge9/15/20233210
Chrome: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 352218916).Chrome Android: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 352218916).Edge: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 352218916).Opera: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 352218916).Opera Android: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 352218916).Safari: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 151471).Safari on iOS: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 151471).Samsung Internet: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 352218916).WebView Android: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 352218916).WebView on iOS: If the font does not have superscript glyphs, then substitute characters are not synthesized (see bug 151471).
css.properties.grid-template-columns.subgrid πŸ“‹Firefox12/10/2019 Edge9/15/20231375
css.properties.grid-template-rows.subgrid πŸ“‹Firefox12/10/2019 Edge9/15/20231375

2023/8

API First Browser Date Last Browser Date Days Notes
css.properties.math-style πŸ“‹Safari4/26/2021 Firefox8/29/2023855
css.properties.math-style.compact πŸ“‹Safari4/26/2021 Firefox8/29/2023855
css.properties.math-style.normal πŸ“‹Safari4/26/2021 Firefox8/29/2023855
css.properties.offset-anchor πŸ“‹Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.auto πŸ“‹Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.bottom πŸ“‹Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.center πŸ“‹Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.left πŸ“‹Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.right πŸ“‹Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.top πŸ“‹Firefox1/7/2020 Edge8/21/20231322
css.types.color.lab.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.lch.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.oklab.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.oklch.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.selectors.first πŸ“‹Safari7/25/2012 Firefox8/1/20234024
html.elements.input.dirname πŸ“‹Safari7/25/2012 Firefox8/1/20234024
html.elements.textarea.dirname πŸ“‹Safari7/25/2012 Firefox8/1/20234024

2023/7

API First Browser Date Last Browser Date Days Notes
css.properties.display.multi-keyword_values Firefox10/22/2019 Edge7/21/20231368
css.types.color.system-color.accentcolor_accentcolortext πŸ“‹Firefox7/26/2022 Edge7/21/2023360
Safari: Only supports a fallback: The native color when accent colour (in macOS' appearance panel) is set to 'multicolour'. On iOS falls back to the blue accent colourSafari on iOS: Only supports a fallback: The native color when accent colour (in macOS' appearance panel) is set to 'multicolour'. On iOS falls back to the blue accent colourWebView on iOS: Only supports a fallback: The native color when accent colour (in macOS' appearance panel) is set to 'multicolour'. On iOS falls back to the blue accent colour
css.properties.animation-composition πŸ“‹Safari9/12/2022 Firefox7/4/2023295
css.properties.animation-composition.accumulate πŸ“‹Safari9/12/2022 Firefox7/4/2023295
css.properties.animation-composition.add πŸ“‹Safari9/12/2022 Firefox7/4/2023295
css.properties.animation-composition.replace πŸ“‹Safari9/12/2022 Firefox7/4/2023295

2023/6

API First Browser Date Last Browser Date Days Notes
css.properties.-webkit-text-security Safari10/26/2007 Firefox6/6/20235702
css.types.calc-keyword.NaN Edge3/3/2022 Firefox6/6/2023460
css.types.calc-keyword.infinity Edge3/3/2022 Firefox6/6/2023460
css.types.overflow.overlay Safari9/17/2018 Edge6/2/20231719
Chrome: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Chrome Android: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Edge: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Quest Browser: Before version false, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version false, the keyword aliases to the standard auto keyword. See bug 40444262.Opera: Before version 100, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 100, the keyword aliases to the standard auto keyword. See bug 40444262.Safari: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.Safari on iOS: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.WebView Android: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.WebView on iOS: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.

2023/5

API First Browser Date Last Browser Date Days Notes
css.properties.content.gradient πŸ“‹Safari10/22/2013 Firefox5/9/20233486
Firefox: content: <gradient> doesn't paint on ::before/::after pseudo elements. See bug 1832901.Firefox for Android: content: <gradient> doesn't paint on ::before/::after pseudo elements. See bug 1832901.
css.selectors.nth-child.of_syntax Safari9/30/2015 Firefox5/9/20232778
css.selectors.nth-last-child.of_syntax Safari9/30/2015 Firefox5/9/20232778
css.types.color.color πŸ“‹Safari9/20/2021 Firefox5/9/2023596
Safari: Only supports display-p3 and srgb predefined color profiles.Safari on iOS: Only supports display-p3 and srgb predefined color profiles.WebView on iOS: Only supports display-p3 and srgb predefined color profiles.
css.types.color.color.mixed_type_parameters Safari9/20/2021 Firefox5/9/2023596
css.types.color.color-mix πŸ“‹Safari12/13/2022 Firefox5/9/2023147
css.types.color.lab πŸ“‹Safari9/20/2021 Firefox5/9/2023596
css.types.color.lch πŸ“‹Safari9/20/2021 Firefox5/9/2023596
css.types.color.oklab πŸ“‹Safari3/14/2022 Firefox5/9/2023421
css.types.color.oklch πŸ“‹Safari3/14/2022 Firefox5/9/2023421
html.elements.iframe.sandbox.allow-storage-access-by-user-activation Safari4/12/2018 Edge5/5/20231849

2023/4

API First Browser Date Last Browser Date Days Notes
html.global_attributes.inert πŸ“‹Safari5/16/2022 Firefox4/11/2023330
css.properties.hyphens.language_dutch Safari7/20/2011 Edge4/6/20234278
css.properties.hyphens.language_italian Safari7/20/2011 Edge4/6/20234278
css.properties.hyphens.language_russian Safari7/20/2011 Edge4/6/20234278
css.properties.hyphens.language_swedish Safari7/20/2011 Edge4/6/20234278
css.properties.hyphens.language_ukrainian Firefox12/20/2011 Edge4/6/20234125

2023/3

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.or_syntax Firefox12/11/2018 Safari3/27/20231567
css.at-rules.media.range_syntax Firefox6/28/2022 Safari3/27/2023272
Firefox: Only supports range notations where the feature name comes before any value (width > 500px)Firefox for Android: Only supports range notations where the feature name comes before any value (width > 500px)
css.at-rules.media.scan πŸ“‹Firefox10/23/2018 Safari3/27/20231616
css.properties.font-size.xxx-large Firefox10/22/2019 Safari3/27/20231252
css.properties.font-synthesis-small-caps πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-small-caps.auto πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-small-caps.none πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-style πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-style.auto πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-style.none πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-weight πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-weight.auto πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-weight.none πŸ“‹Edge1/6/2022 Safari3/27/2023445
css.properties.outline πŸ“‹Firefox4/19/2021 Safari3/27/2023707
Chrome: Before Chrome 94, outline does not follow the shape of border-radius.Chrome Android: Before Chrome Android 94, outline does not follow the shape of border-radius.Edge: Before Edge 94, outline does not follow the shape of border-radius.Firefox: Before Firefox 88, outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, outline does not follow the shape of border-radius.Quest Browser: Before Quest Browser 18.0, outline does not follow the shape of border-radius.Opera: Before Opera 80, outline does not follow the shape of border-radius.Safari: Before Safari 16.4, outline does not follow the shape of border-radius. See bug 20807.Safari on iOS: Before Safari on iOS 16.4, outline does not follow the shape of border-radius. See bug 20807.WebView Android: Before Chrome 94, outline does not follow the shape of border-radius.WebView on iOS: Before WebView on iOS 16.4, outline does not follow the shape of border-radius. See bug 20807.
css.selectors.backdrop.fullscreen Edge7/29/2015 Safari3/27/20232798
css.selectors.fullscreen πŸ“‹Edge7/29/2015 Safari3/27/20232798
Safari on iOS: Only available on iPad, not on iPhone.Safari on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.Safari on iOS: Only available on iPad, not on iPhone.WebView on iOS: Only available on iPad, not on iPhone.WebView on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.WebView on iOS: Only available on iPad, not on iPhone.
html.elements.script.type.importmap πŸ“‹Edge3/4/2021 Safari3/27/2023753
html.elements.form.rel πŸ“‹Safari3/14/2022 Firefox3/14/2023365
html.global_attributes.translate πŸ“‹Safari7/25/2012 Firefox3/14/20233884
css.at-rules.font-feature-values πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.annotation Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.character-variant Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.historical-forms Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.ornaments Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.styleset Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.stylistic Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.swash Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant.historical-forms πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.annotation πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.character_variant πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.historical-forms πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.normal πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.ornaments πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.styleset πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.stylistic πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.swash πŸ“‹Firefox12/1/2014 Edge3/13/20233024
css.types.acos πŸ“‹Safari3/14/2022 Edge3/13/2023364
css.types.asin πŸ“‹Safari3/14/2022 Edge3/13/2023364
css.types.atan πŸ“‹Safari3/14/2022 Edge3/13/2023364
css.types.atan2 πŸ“‹Safari3/14/2022 Edge3/13/2023364
css.types.cos πŸ“‹Safari3/14/2022 Edge3/13/2023364
css.types.sin πŸ“‹Safari3/14/2022 Edge3/13/2023364
css.types.tan πŸ“‹Safari3/14/2022 Edge3/13/2023364

2023/2

API First Browser Date Last Browser Date Days Notes
css.at-rules.container πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.at-rules.media.color-gamut πŸ“‹Safari9/20/2016 Firefox2/14/20232338
css.at-rules.media.color-gamut.p3 πŸ“‹Safari9/20/2016 Firefox2/14/20232338
Firefox: color-gamut: p3 is always false because Firefox does not support wide-gamut color. See bug 1626624.Firefox for Android: color-gamut: p3 is always false because Firefox for Android does not support wide-gamut color. See bug 1626624.
css.at-rules.media.color-gamut.rec2020 πŸ“‹Safari9/20/2016 Firefox2/14/20232338
Firefox: color-gamut: rec2020 is always false because Firefox does not support wide-gamut color. See bug 1626624.Firefox for Android: color-gamut: rec2020 is always false because Firefox for Android does not support wide-gamut color. See bug 1626624.
css.at-rules.media.color-gamut.srgb πŸ“‹Safari9/20/2016 Firefox2/14/20232338
Firefox: color-gamut: srgb is always true because Firefox does not support wide-gamut color. See bug 1626624.Firefox for Android: color-gamut: srgb is always true because Firefox for Android does not support wide-gamut color. See bug 1626624.
css.properties.container πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container.inline-size πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container.none πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container.normal πŸ“‹Safari9/12/2022 Firefox2/14/2023155
css.properties.container.scroll-state πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container.size πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container-name πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container-name.none πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type.inline-size πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type.normal πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type.size πŸ“‹Edge9/1/2022 Firefox2/14/2023166
css.properties.page πŸ“‹Safari6/23/2003 Firefox2/14/20237176
css.properties.page.auto πŸ“‹Safari6/23/2003 Firefox2/14/20237176
css.types.length.container_query_length_units Edge9/1/2022 Firefox2/14/2023166
html.elements.datalist.input_type_range πŸ“‹Edge7/29/2015 Firefox2/14/20232757
html.elements.input.type_range.list πŸ“‹Edge7/29/2015 Firefox2/14/20232757
html.global_attributes.autofocus πŸ“‹Edge1/15/2020 Firefox2/14/20231126
Chrome: Supported for the <button>, <input>, <select>, and <textarea> elements.Chrome Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Edge: Supported for the <button>, <input>, <select>, and <textarea> elements.Firefox: Supported for the <button>, <input>, <select>, and <textarea> elements.Firefox for Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Internet Explorer: Supported for the <button>, <input>, <select>, and <textarea> elements.Quest Browser: Supported for the <button>, <input>, <select>, and <textarea> elements.Opera: Supported for the <button>, <input>, <select>, and <textarea> elements.Opera Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Safari: Supported for the <button>, <input>, <select>, and <textarea> elements.Safari on iOS: If there's no hardware keyboard connected, then the autofocus attribute has no effect (for example, the focus event doesn't fire and the element does not match the :focus selector).Samsung Internet: Supported for the <button>, <input>, <select>, and <textarea> elements.WebView Android: Supported for the <button>, <input>, <select>, and <textarea> elements.WebView on iOS: If there's no hardware keyboard connected, then the autofocus attribute has no effect (for example, the focus event doesn't fire and the element does not match the :focus selector).
css.properties.font-variant.sub πŸ“‹Firefox12/1/2014 Edge2/9/20232992
css.properties.font-variant.super πŸ“‹Firefox12/1/2014 Edge2/9/20232992
css.selectors.autofill πŸ“‹Firefox2/23/2021 Edge2/9/2023716
Firefox: The :autofill pseudo-class matches autofilled username and password fields, but not other autocompleted fields. See bug 1923525.Firefox: The :-webkit-autofill pseudo-class matches autofilled username and password fields, but not other autocompleted fields. See bug 1923525.Firefox for Android: The :autofill pseudo-class matches autofilled username and password fields, but not other autocompleted fields. See bug 1923525.Firefox for Android: The :-webkit-autofill pseudo-class matches autofilled username and password fields, but not other autocompleted fields. See bug 1923525.
css.types.calc-keyword.e Safari3/14/2022 Edge2/9/2023332

2023/1

API First Browser Date Last Browser Date Days Notes
html.elements.form.autocomplete.one-time-code Safari9/17/2018 Firefox1/17/20231583
html.elements.input.type_range.tick_marks Safari3/25/2019 Firefox1/17/20231394
html.elements.textarea.autocomplete.one-time-code Safari9/17/2018 Firefox1/17/20231583
css.types.calc-keyword.pi Safari3/14/2022 Edge1/12/2023304

2022/12

API First Browser Date Last Browser Date Days Notes
css.properties.align-items.flex_context.last_baseline Firefox3/7/2017 Safari12/13/20222107
css.properties.align-self.flex_context.last_baseline Firefox3/7/2017 Safari12/13/20222107
css.properties.text-emphasis-position.over Safari10/22/2013 Firefox12/13/20223339
css.properties.text-emphasis-position.under Safari10/22/2013 Firefox12/13/20223339
css.types.calc-keyword πŸ“‹Edge3/3/2022 Firefox12/13/2022285
html.elements.source.height πŸ“‹Edge4/15/2021 Firefox12/13/2022607
html.elements.source.width πŸ“‹Edge4/15/2021 Firefox12/13/2022607
css.at-rules.font-face.src.format_keyword Safari6/8/2009 Edge12/5/20224928
css.types.length.vb Safari3/14/2022 Edge12/5/2022266
css.types.length.vi Safari3/14/2022 Edge12/5/2022266
css.types.length.viewport_percentage_units_dynamic Safari3/14/2022 Edge12/5/2022266
css.types.length.viewport_percentage_units_large Safari3/14/2022 Edge12/5/2022266
css.types.length.viewport_percentage_units_small Safari3/14/2022 Edge12/5/2022266

2022/11

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-palette-values πŸ“‹Safari3/14/2022 Firefox11/15/2022246
css.at-rules.font-palette-values.base-palette πŸ“‹Safari3/14/2022 Firefox11/15/2022246
css.at-rules.font-palette-values.font-family πŸ“‹Safari3/14/2022 Firefox11/15/2022246
css.at-rules.font-palette-values.override-colors πŸ“‹Safari3/14/2022 Firefox11/15/2022246
css.properties.font-palette πŸ“‹Safari3/14/2022 Firefox11/15/2022246
css.properties.font-palette.dark πŸ“‹Safari3/14/2022 Firefox11/15/2022246
css.properties.font-palette.light πŸ“‹Safari3/14/2022 Firefox11/15/2022246
css.properties.font-palette.normal πŸ“‹Safari3/14/2022 Firefox11/15/2022246

2022/10

API First Browser Date Last Browser Date Days Notes
css.properties.grid-template-columns.animation Firefox3/19/2019 Edge10/27/20221318
css.properties.grid-template-rows.animation Firefox3/19/2019 Edge10/27/20221318
css.types.length.ic Firefox2/8/2022 Edge10/3/2022237

2022/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.forced-colors πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.at-rules.media.resolution πŸ“‹Firefox11/8/2011 Safari9/12/20223961
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.properties.contain.inline-size πŸ“‹Firefox5/31/2022 Safari9/12/2022104
css.properties.flex.fit-content πŸ“‹Edge9/24/2021 Safari9/12/2022353
css.properties.flex.max-content πŸ“‹Firefox3/19/2019 Safari9/12/20221273
css.properties.flex.min-content πŸ“‹Firefox3/19/2019 Safari9/12/20221273
css.properties.flex-basis.fit-content Edge9/24/2021 Safari9/12/2022353
css.properties.flex-basis.max-content Firefox3/19/2019 Safari9/12/20221273
css.properties.flex-basis.min-content Firefox3/19/2019 Safari9/12/20221273
css.properties.offset πŸ“‹Firefox1/7/2020 Safari9/12/2022979
css.properties.offset.none πŸ“‹Firefox1/7/2020 Safari9/12/2022979
css.properties.offset-distance πŸ“‹Firefox1/7/2020 Safari9/12/2022979
css.properties.offset-path.path Firefox1/7/2020 Safari9/12/2022979
css.properties.offset-rotate πŸ“‹Firefox1/7/2020 Safari9/12/2022979
css.properties.offset-rotate.auto πŸ“‹Firefox1/7/2020 Safari9/12/2022979
css.properties.offset-rotate.reverse πŸ“‹Firefox1/7/2020 Safari9/12/2022979
css.properties.overflow.clip πŸ“‹Firefox9/22/2020 Safari9/12/2022720
css.properties.overflow-x.clip πŸ“‹Firefox9/22/2020 Safari9/12/2022720
css.properties.overflow-y.clip πŸ“‹Firefox9/22/2020 Safari9/12/2022720
css.properties.overscroll-behavior πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior.auto πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior.contain πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior.none πŸ“‹Firefox3/13/2018 Safari9/12/20221644
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-block πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-block.auto πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-block.contain πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-block.none πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-inline πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-inline.auto πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-inline.contain πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-inline.none πŸ“‹Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-x πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior-x.auto πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior-x.contain πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior-x.none πŸ“‹Firefox3/13/2018 Safari9/12/20221644
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-y πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior-y.auto πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior-y.contain πŸ“‹Firefox3/13/2018 Safari9/12/20221644
css.properties.overscroll-behavior-y.none πŸ“‹Firefox3/13/2018 Safari9/12/20221644
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.text-align-last πŸ“‹Edge7/29/2015 Safari9/12/20222602
Internet Explorer: IE only supports text-align-last when text-align is set to justify.Internet Explorer: The start and end values are not supported.
css.properties.text-align-last.auto πŸ“‹Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.center πŸ“‹Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.end πŸ“‹Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.justify πŸ“‹Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.left πŸ“‹Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.right πŸ“‹Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.start πŸ“‹Firefox4/24/2012 Safari9/12/20223793
css.properties.user-select.all Firefox11/9/2004 Safari9/12/20226516
css.types.basic-shape.path.offset-path πŸ“‹Firefox1/7/2020 Safari9/12/2022979
css.types.overflow.clip Firefox9/22/2020 Safari9/12/2022720
css.types.resolution πŸ“‹Firefox11/8/2011 Safari9/12/20223961
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.types.resolution.dpcm Firefox11/8/2011 Safari9/12/20223961
css.types.resolution.dpi Firefox11/8/2011 Safari9/12/20223961
css.types.resolution.dppx Firefox10/9/2012 Safari9/12/20223625
css.types.resolution.x Firefox9/5/2018 Safari9/12/20221468
html.elements.textarea.placeholder.line_breaks Edge7/29/2015 Safari9/12/20222602
html.elements.video.autoplay.requires_muted_audio Firefox5/21/2019 Safari9/12/20221210
Firefox for Android: Between versions 79 and 91, the default behavior was to block videos from autoplaying, regardless of whether audio was muted.
css.selectors.modal πŸ“‹Safari7/20/2022 Edge9/1/202243

2022/8

API First Browser Date Last Browser Date Days Notes
css.properties.rotate πŸ“‹Firefox1/7/2020 Edge8/5/2022941
css.properties.rotate.none πŸ“‹Firefox1/7/2020 Edge8/5/2022941
css.properties.rotate.x_y_z_angle Firefox1/7/2020 Edge8/5/2022941
css.properties.scale πŸ“‹Firefox1/7/2020 Edge8/5/2022941
css.properties.scale.none πŸ“‹Firefox1/7/2020 Edge8/5/2022941
css.properties.translate πŸ“‹Firefox1/7/2020 Edge8/5/2022941
css.properties.translate.none πŸ“‹Firefox1/7/2020 Edge8/5/2022941

2022/7

API First Browser Date Last Browser Date Days Notes
css.properties.backdrop-filter.none πŸ“‹Safari9/30/2015 Firefox7/26/20222491
css.properties.contain.style πŸ“‹Edge1/15/2020 Firefox7/26/2022923
Chrome: Before Chrome 115, style containment did not affect quotes, see bug 40592922.Chrome Android: Before Chrome Android 115, style containment did not affect quotes, see bug 40592922.Edge: Before Edge 115, style containment did not affect quotes, see bug 40592922.Quest Browser: Before Quest Browser false, style containment did not affect quotes, see bug 40592922.Opera: Before Opera 101, style containment did not affect quotes, see bug 40592922.Opera Android: Before Opera Android 77, style containment did not affect quotes, see bug 40592922.Safari: Style containment does not affect quotes, see bug 232083.Safari on iOS: Style containment does not affect quotes, see bug 232083.Samsung Internet: Before Samsung Internet 23.0, style containment did not affect quotes, see bug 40592922.WebView Android: Before WebView Android 115, style containment did not affect quotes, see bug 40592922.WebView on iOS: Style containment does not affect quotes, see bug 232083.
css.properties.scroll-snap-stop πŸ“‹Edge1/15/2020 Firefox7/26/2022923
css.properties.scroll-snap-stop.always πŸ“‹Edge1/15/2020 Firefox7/26/2022923
css.properties.scroll-snap-stop.normal πŸ“‹Edge1/15/2020 Firefox7/26/2022923
css.properties.align-content.flex_context.start_end Firefox3/8/2016 Safari7/20/20222325
Opera: Before version 79, this value is recognized, but has no effect.Opera Android: This value is recognized, but has no effect.

2022/5

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.prefers-contrast πŸ“‹Safari4/26/2021 Firefox5/31/2022400
html.global_attributes.nonce πŸ“‹Edge1/15/2020 Safari5/16/2022852
Firefox: Firefox does not prevent nonce exfiltration through content attributes.Firefox for Android: Firefox for Android does not prevent nonce exfiltration through content attributes.Safari: Safari does not prevent nonce exfiltration through content attributes.Safari on iOS: Safari on iOS does not prevent nonce exfiltration through content attributes.WebView on iOS: WebView on iOS does not prevent nonce exfiltration through content attributes.
css.at-rules.media.dynamic-range πŸ“‹Safari3/24/2020 Firefox5/3/2022770

2022/4

API First Browser Date Last Browser Date Days Notes
css.types.color.hwb πŸ“‹Safari9/20/2021 Edge4/28/2022220
css.properties.mix-blend-mode.plus-lighter πŸ“‹Safari3/21/2016 Firefox4/5/20222206
css.properties.scroll-snap-type πŸ“‹Safari9/19/2017 Firefox4/5/20221659
Edge: Edge supports an earlier draft of CSS Scroll Snap without axis values.Firefox: On macOS Monterey, scroll snapping does not complete reliably. See bug 1749352.Firefox: An earlier draft of CSS Scroll Snap without axis values.Firefox for Android: An earlier draft of CSS Scroll Snap without axis values.Internet Explorer: Internet Explorer supports an earlier draft of CSS Scroll Snap without axis values.Safari: Older Safari versions support an earlier draft of CSS Scroll Snap without axis values.Safari on iOS: Older Safari on iOS versions support an earlier draft of CSS Scroll Snap without axis values.WebView on iOS: Older WebView on iOS versions support an earlier draft of CSS Scroll Snap without axis values.

2022/3

API First Browser Date Last Browser Date Days Notes
css.at-rules.import.layer πŸ“‹Firefox2/8/2022 Safari3/14/202234
css.at-rules.layer πŸ“‹Firefox2/8/2022 Safari3/14/202234
css.properties.accent-color πŸ“‹Edge9/2/2021 Safari3/14/2022193
Chrome Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Quest Browser: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Opera Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Safari: Safari does not maintain minimum contrast for legibility of the control. See bug 244233.Safari on iOS: Safari on iOS does not maintain minimum contrast for legibility of the control. See bug 244233.Samsung Internet: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.WebView Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.WebView on iOS: WebView on iOS does not maintain minimum contrast for legibility of the control. See bug 244233.
css.properties.accent-color.auto Edge9/2/2021 Safari3/14/2022193
css.properties.align-items.flex_context.start_end Firefox3/8/2016 Safari3/14/20222197
css.properties.align-self.flex_context.start_end Firefox3/8/2016 Safari3/14/20222197
Opera: Before version 79, this value is recognized, but has no effect.
css.properties.appearance πŸ“‹Edge7/16/2020 Safari3/14/2022606
css.properties.appearance.auto πŸ“‹Edge5/21/2020 Safari3/14/2022662
css.properties.backface-visibility πŸ“‹Firefox10/9/2012 Safari3/14/20223443
css.properties.background-attachment.fixed πŸ“‹Firefox10/24/2006 Safari3/14/20225620
Safari: fixed is recognized but has no effect. See related bug 219324.Safari on iOS: fixed is recognized but has no effect. See bug 275247.WebView on iOS: fixed is recognized but has no effect. See bug 275247.
css.properties.background-attachment.local πŸ“‹Firefox10/29/2013 Safari3/14/20223058
Safari: local is recognized but has no effect. See bug 219324.Safari on iOS: local is recognized but has no effect. See bug 219324.Safari on iOS: If -webkit-overflow-scrolling: touch is set, then local has no effect.WebView on iOS: local is recognized but has no effect. See bug 219324.WebView on iOS: If -webkit-overflow-scrolling: touch is set, then local has no effect.
css.properties.contain πŸ“‹Firefox9/3/2019 Safari3/14/2022923
css.properties.contain.content πŸ“‹Firefox9/3/2019 Safari3/14/2022923
css.properties.contain.layout πŸ“‹Firefox9/3/2019 Safari3/14/2022923
css.properties.contain.none πŸ“‹Firefox9/3/2019 Safari3/14/2022923
css.properties.contain.paint πŸ“‹Firefox9/3/2019 Safari3/14/2022923
css.properties.contain.size πŸ“‹Firefox9/3/2019 Safari3/14/2022923
css.properties.contain.strict πŸ“‹Firefox9/3/2019 Safari3/14/2022923
css.properties.flex-basis.content Firefox6/26/2018 Safari3/14/20221357
css.properties.justify-content.flex_context.start_end Firefox3/8/2016 Safari3/14/20222197
css.properties.offset-path πŸ“‹Firefox1/7/2020 Safari3/14/2022797
Samsung Internet: path() is the only value type supported.
css.properties.overflow-wrap.anywhere πŸ“‹Firefox1/29/2019 Safari3/14/20221140
css.properties.scroll-behavior πŸ“‹Firefox2/24/2015 Safari3/14/20222575
css.properties.scroll-behavior.auto πŸ“‹Firefox2/24/2015 Safari3/14/20222575
css.properties.scroll-behavior.smooth πŸ“‹Firefox2/24/2015 Safari3/14/20222575
css.properties.text-align.match-parent πŸ“‹Firefox8/11/2015 Safari3/14/20222407
css.properties.text-combine-upright πŸ“‹Firefox8/2/2016 Safari3/14/20222050
Chrome: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Chrome Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Firefox: Before version 81, Firefox implemented the property as animatable. This was corrected to spec in 81.Firefox for Android: Before version 81, Firefox for Android implemented the property as animatable. This was corrected to spec in 81.Quest Browser: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Opera: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Opera Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Safari: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Safari on iOS: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Samsung Internet: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.WebView Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.WebView on iOS: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.
css.properties.text-combine-upright.all πŸ“‹Firefox8/2/2016 Safari3/14/20222050
css.properties.text-combine-upright.none πŸ“‹Firefox8/2/2016 Safari3/14/20222050
css.properties.text-decoration-skip-ink πŸ“‹Firefox10/22/2019 Safari3/14/2022874
css.properties.text-decoration-skip-ink.auto πŸ“‹Firefox10/22/2019 Safari3/14/2022874
css.properties.text-decoration-skip-ink.none πŸ“‹Firefox10/22/2019 Safari3/14/2022874
css.selectors.backdrop πŸ“‹Firefox6/7/2016 Safari3/14/20222106
css.selectors.backdrop.dialog Edge1/15/2020 Safari3/14/2022789
css.selectors.focus-visible πŸ“‹Edge10/9/2020 Safari3/14/2022521
css.types.global_keywords.revert-layer πŸ“‹Firefox2/8/2022 Safari3/14/202234
css.types.transform-function.perspective.none πŸ“‹Firefox10/5/2021 Safari3/14/2022160
html.elements.dialog πŸ“‹Edge1/15/2020 Safari3/14/2022789
html.elements.dialog.open Edge1/15/2020 Safari3/14/2022789
html.elements.img.loading πŸ“‹Edge1/15/2020 Safari3/14/2022789
css.properties.hyphenate-character.auto πŸ“‹Safari7/20/2011 Firefox3/8/20223884
css.properties.text-emphasis πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-color πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-position πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.circle πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.dot πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.double-circle πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.filled πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.none πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.open πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.sesame πŸ“‹Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.triangle πŸ“‹Safari10/22/2013 Edge3/3/20223054

2022/2

API First Browser Date Last Browser Date Days Notes
css.properties.color-scheme.only Safari9/19/2019 Edge2/3/2022868

2022/1

API First Browser Date Last Browser Date Days Notes
css.properties.color-scheme πŸ“‹Safari9/19/2019 Firefox1/11/2022845
css.properties.color-scheme.dark Safari9/19/2019 Firefox1/11/2022845
css.properties.color-scheme.light Safari9/19/2019 Firefox1/11/2022845
css.properties.color-scheme.normal Safari9/19/2019 Firefox1/11/2022845
html.elements.meta.name.color-scheme πŸ“‹Safari3/25/2019 Firefox1/11/20221023
css.properties.font-synthesis πŸ“‹Firefox12/1/2014 Edge1/6/20222593
css.properties.font-synthesis.none πŸ“‹Firefox12/1/2014 Edge1/6/20222593
css.properties.font-synthesis.small-caps Safari3/27/2017 Edge1/6/20221746
css.properties.font-synthesis.style Firefox12/1/2014 Edge1/6/20222593
css.properties.font-synthesis.weight Firefox12/1/2014 Edge1/6/20222593

2021/12

API First Browser Date Last Browser Date Days Notes
html.global_attributes.inputmode πŸ“‹Safari3/25/2019 Firefox12/7/2021988
Safari on iOS: Before iOS 13, inputmode="none" had no effect.WebView on iOS: Before iOS 13, inputmode="none" had no effect.

2021/11

API First Browser Date Last Browser Date Days Notes
css.properties.block-size.fit-content πŸ“‹Safari3/25/2019 Firefox11/2/2021953
css.properties.height.fit-content πŸ“‹Safari9/19/2017 Firefox11/2/20211505
css.properties.inline-size.fit-content πŸ“‹Safari3/25/2019 Firefox11/2/2021953
css.properties.max-block-size.fit-content Safari3/25/2019 Firefox11/2/2021953
css.properties.max-height.fit-content πŸ“‹Safari9/19/2017 Firefox11/2/20211505
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.max-inline-size.fit-content Safari3/25/2019 Firefox11/2/2021953
css.properties.max-width.fit-content πŸ“‹Safari9/19/2017 Firefox11/2/20211505
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.min-block-size.fit-content Safari3/25/2019 Firefox11/2/2021953
css.properties.min-height.fit-content Safari9/19/2017 Firefox11/2/20211505
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.min-inline-size.fit-content Safari3/25/2019 Firefox11/2/2021953
css.properties.min-width.fit-content Safari9/19/2017 Firefox11/2/20211505
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.width.fit-content πŸ“‹Safari9/19/2017 Firefox11/2/20211505
html.global_attributes.enterkeyhint πŸ“‹Edge1/15/2020 Firefox11/2/2021657

2021/10

API First Browser Date Last Browser Date Days Notes
css.properties.image-rendering.pixelated πŸ“‹Safari9/20/2016 Firefox10/5/20211841
html.elements.input.type_datetime-local πŸ“‹Edge7/29/2015 Firefox10/5/20212260
Firefox: Only displays a date picker without a time picker, see bug 1726107 and bug 1726108.Firefox for Android: Only displays a date picker without a time picker, see bug 1726107 and bug 1726108.Safari: Safari only displays a date picker and does not display a time picker.

2021/9

API First Browser Date Last Browser Date Days Notes
css.properties.flex.content πŸ“‹Firefox6/26/2018 Edge9/24/20211186
html.elements.iframe.allow.display-capture πŸ“‹Safari9/19/2019 Edge9/24/2021736
css.properties.aspect-ratio πŸ“‹Edge1/21/2021 Safari9/20/2021242
css.properties.aspect-ratio.auto πŸ“‹Edge1/21/2021 Safari9/20/2021242
css.properties.border-end-end-radius πŸ“‹Firefox3/19/2019 Safari9/20/2021916
css.properties.border-end-start-radius πŸ“‹Firefox3/19/2019 Safari9/20/2021916
css.properties.border-start-end-radius πŸ“‹Firefox3/19/2019 Safari9/20/2021916
css.properties.border-start-start-radius πŸ“‹Firefox3/19/2019 Safari9/20/2021916
css.properties.list-style-type.cjk-decimal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.disclosure-closed πŸ“‹Firefox10/14/2014 Safari9/20/20212533
css.properties.list-style-type.disclosure-open πŸ“‹Firefox10/14/2014 Safari9/20/20212533
css.properties.list-style-type.ethiopic-numeric πŸ“‹Firefox10/14/2014 Safari9/20/20212533
Firefox: Before Firefox 38, Firefox added a dot as suffix of the number for ethiopic-numeric (for example, ፫. instead of ፫). The specification later defined the absence of a suffix, which Firefox 38 followed.Firefox for Android: Before Firefox for Android 38, Firefox for Android added a dot as suffix of the number for ethiopic-numeric (for example, ፫. instead of ፫). The specification later defined the absence of a suffix, which Firefox for Android 38 followed.
css.properties.list-style-type.japanese-formal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.japanese-informal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.korean-hangul-formal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.korean-hanja-formal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.korean-hanja-informal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.simp-chinese-formal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.simp-chinese-informal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.tamil πŸ“‹Firefox10/14/2014 Safari9/20/20212533
css.properties.list-style-type.trad-chinese-formal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.trad-chinese-informal πŸ“‹Firefox3/18/2014 Safari9/20/20212743
css.properties.scroll-margin-block πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-margin-block-end πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-margin-block-start πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-margin-inline πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-margin-inline-end πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-margin-inline-start πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-block πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-block.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-block-end πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-block-end.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-block-start πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-block-start.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-bottom.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-inline πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-inline.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-inline-end πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-inline-end.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-inline-start πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-inline-start.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-left.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-right.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-top.auto πŸ“‹Firefox7/9/2019 Safari9/20/2021804
css.selectors.any-link.not_match_link Edge1/15/2020 Safari9/20/2021614
css.selectors.link.not_match_link Edge7/29/2015 Safari9/20/20212245
css.selectors.visited.not_match_link Edge7/29/2015 Safari9/20/20212245
css.types.gradient.linear-gradient.premultiplied_gradients Firefox2/24/2015 Safari9/20/20212400
css.types.gradient.radial-gradient.premultiplied_gradients Firefox2/24/2015 Safari9/20/20212400
html.elements.img.aspect_ratio_computed_from_attributes Firefox12/10/2019 Safari9/20/2021650
Safari: Safari doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).Safari on iOS: Safari on iOS doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).WebView on iOS: WebView on iOS doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).
css.properties.break-inside.avoid-column Safari9/20/2016 Firefox9/7/20211813
css.properties.break-inside.avoid-page Safari9/20/2016 Firefox9/7/20211813
css.properties.break-inside.multicol_context.avoid-column Edge7/29/2015 Firefox9/7/20212232
css.properties.font-family.system-ui Safari9/19/2017 Firefox9/7/20211449
Firefox: Supported on macOS only.
css.properties.justify-content.flex_context.left_right Safari9/30/2015 Edge9/2/20212164
Internet Explorer: This value is recognized, but has no effect.Opera Android: This value is recognized, but has no effect.

2021/8

API First Browser Date Last Browser Date Days Notes
css.properties.tab-size πŸ“‹Safari10/22/2013 Firefox8/10/20212849
Chrome: This property is not yet animatable.Chrome Android: This property is not yet animatable.Edge: This property is not yet animatable.Firefox: Before Firefox 53, this property was not animatable.Firefox for Android: Before Firefox for Android 53, this property was not animatable.Quest Browser: This property is not yet animatable.Samsung Internet: This property is not yet animatable.

2021/7

API First Browser Date Last Browser Date Days Notes
css.properties.scroll-margin πŸ“‹Edge1/15/2020 Firefox7/13/2021545
Firefox: The scroll-margin property can cause an element's visibility to be incorrectly calculated for element.focus(). See bug 1708303.Firefox for Android: The scroll-margin property can cause an element's visibility to be incorrectly calculated for element.focus(). See bug 1708303.Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.

2021/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.supports.selector Firefox9/3/2019 Safari4/26/2021601
css.properties.border-block πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.currentColor πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.dashed πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.dotted πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.double πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.groove πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.hidden πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.inset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.medium πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.none πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.outset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.ridge πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.solid πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.thick πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.thin πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.transparent πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-color πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-color.currentColor πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-color.transparent πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.dashed πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.dotted πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.double πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.groove πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.hidden πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.inset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.none πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.outset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.ridge πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.solid πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-width πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-width.medium πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-width.thick πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-width.thin πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.currentColor πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.dashed πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.dotted πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.double πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.groove πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.hidden πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.inset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.medium πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.none πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.outset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.ridge πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.solid πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.thick πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.thin πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.transparent πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-color πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-color.currentColor πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-color.transparent πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.dashed πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.dotted πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.double πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.groove πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.hidden πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.inset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.none πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.outset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.ridge πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.solid πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-width πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-width.medium πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-width.thick πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-width.thin πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.column-gap.flex_context πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.gap.flex_context πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.gap.multicol_context πŸ“‹Edge10/17/2017 Safari4/26/20211287
css.properties.inset πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.inset.auto πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.inset-block πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-block.auto πŸ“‹Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-block-end πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-block-end.auto πŸ“‹Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-block-start πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-block-start.auto πŸ“‹Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-inline πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-inline.auto πŸ“‹Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-inline-end πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-inline-end.auto πŸ“‹Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-inline-start πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-inline-start.auto πŸ“‹Firefox9/22/2015 Safari4/26/20212043
css.properties.list-style-type.string Firefox7/2/2015 Safari4/26/20212125
css.properties.margin-block πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.margin-block.auto πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.margin-inline πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.margin-inline.auto πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.padding-block πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.padding-inline πŸ“‹Firefox3/19/2019 Safari4/26/2021769
css.properties.quotes.auto πŸ“‹Firefox10/22/2019 Safari4/26/2021552
Internet Explorer: This value is not supported, but the default browser behavior is to choose appropriate quotes for the user's language setting
css.properties.row-gap.flex_context πŸ“‹Firefox10/23/2018 Safari4/26/2021916
css.properties.scroll-margin-bottom πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-left πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-right πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-top πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-padding πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding-bottom πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding-left πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding-right πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding-top πŸ“‹Firefox7/9/2019 Safari4/26/2021657
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.selectors.file-selector-button πŸ“‹Firefox10/20/2020 Safari4/26/2021188
css.selectors.marker.animation_and_transition_support Firefox8/25/2020 Safari4/26/2021244
html.elements.input.type_date πŸ“‹Edge7/29/2015 Safari4/26/20212098
html.elements.input.type_date.disables_invalid_values_in_picker_ui Firefox11/14/2017 Safari4/26/20211259
html.elements.input.type_time πŸ“‹Edge7/29/2015 Safari4/26/20212098

2021/3

API First Browser Date Last Browser Date Days Notes
css.properties.text-decoration-thickness πŸ“‹Safari3/25/2019 Edge3/4/2021710
Chrome: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Chrome Android: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Edge: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Quest Browser: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Opera: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Opera Android: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Samsung Internet: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.WebView Android: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.

2021/1

API First Browser Date Last Browser Date Days Notes
css.properties.touch-action.pinch-zoom Edge7/29/2015 Firefox1/26/20212008
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.Firefox for Android: Not applicable to Firefox for Android platforms that support neither pointer nor touch events.
html.elements.link.rel.preload πŸ“‹Safari4/12/2018 Firefox1/26/20211020
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-fetch Safari4/12/2018 Firefox1/26/20211020
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-font Safari4/12/2018 Firefox1/26/20211020
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-image Safari4/12/2018 Firefox1/26/20211020
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-script Safari4/12/2018 Firefox1/26/20211020
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-style Safari4/12/2018 Firefox1/26/20211020
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
css.properties.clip-path.path Firefox12/10/2019 Edge1/21/2021408
css.properties.hyphens.auto Safari7/20/2011 Edge1/21/20213473
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.manual Safari7/20/2011 Edge1/21/20213473
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.none Safari7/20/2011 Edge1/21/20213473
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.selectors.is πŸ“‹Firefox6/30/2020 Edge1/21/2021205
Chrome: Doesn't support combinators.Chrome Android: Doesn't support combinators.Edge: Doesn't support combinators.Firefox: Doesn't support combinators.Firefox: See bug 906353.Firefox for Android: Doesn't support combinators.Firefox for Android: See bug 906353.Quest Browser: Doesn't support combinators.Opera: Doesn't support combinators.Opera Android: Doesn't support combinators.Safari: Doesn't support combinators.Safari on iOS: Doesn't support combinators.WebView Android: Doesn't support combinators.WebView on iOS: Doesn't support combinators.
css.selectors.is.forgiving_selector_list Safari9/16/2020 Edge1/21/2021127
css.selectors.not.selector_list Safari9/30/2015 Edge1/21/20211940
css.selectors.where πŸ“‹Firefox6/30/2020 Edge1/21/2021205
css.selectors.where.forgiving_selector_list Safari9/16/2020 Edge1/21/2021127
css.types.basic-shape.path.clip-path πŸ“‹Firefox1/7/2020 Edge1/21/2021380
html.elements.a.implicit_noopener Safari3/25/2019 Edge1/21/2021668
html.elements.area.implicit_noopener Safari3/25/2019 Edge1/21/2021668

2020/11

API First Browser Date Last Browser Date Days Notes
css.properties.hyphens.language_croatian Firefox11/8/2011 Edge11/19/20203299
css.properties.hyphens.language_danish Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_french Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_german_reformed_orthography Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_hungarian Firefox12/20/2011 Edge11/19/20203257
css.properties.hyphens.language_norwegian_no Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_portuguese Firefox11/8/2011 Edge11/19/20203299
css.properties.hyphens.language_spanish Safari7/20/2011 Edge11/19/20203410
css.properties.text-decoration-thickness.auto πŸ“‹Safari3/25/2019 Edge11/19/2020605
css.properties.text-decoration-thickness.from-font πŸ“‹Safari3/25/2019 Edge11/19/2020605
css.properties.text-underline-offset πŸ“‹Safari3/25/2019 Edge11/19/2020605
css.properties.text-underline-offset.auto πŸ“‹Safari3/25/2019 Edge11/19/2020605
css.properties.text-underline-position.from-font πŸ“‹Safari3/25/2019 Edge11/19/2020605
css.types.gradient.conic-gradient πŸ“‹Safari3/25/2019 Firefox11/17/2020603
css.types.gradient.conic-gradient.doubleposition Safari3/25/2019 Firefox11/17/2020603
css.types.gradient.repeating-conic-gradient πŸ“‹Safari3/25/2019 Firefox11/17/2020603

2020/10

API First Browser Date Last Browser Date Days Notes
css.selectors.marker πŸ“‹Safari4/12/2018 Edge10/9/2020911
Safari: Safari support is limited to color and font-size.Safari on iOS: Safari on iOS support is limited to color and font-size.WebView on iOS: WebView on iOS support is limited to color and font-size.

2020/9

API First Browser Date Last Browser Date Days Notes
css.properties.flex-direction.column-reverse πŸ“‹Safari10/22/2013 Firefox9/22/20202527
Firefox: Before Firefox 81, overflow with column-reverse was unsupported. See bug 1042151.Firefox for Android: Before Firefox for Android 81, overflow with column-reverse was unsupported. See bug 1042151.
css.properties.flex-direction.row-reverse πŸ“‹Safari10/22/2013 Firefox9/22/20202527
Firefox: Before Firefox 81, overflow with column-reverse was unsupported. See bug 1042151.Firefox for Android: Before Firefox for Android 81, overflow with column-reverse was unsupported. See bug 1042151.
css.properties.animation-timing-function.jump Firefox1/29/2019 Safari9/16/2020596
css.properties.text-orientation πŸ“‹Firefox9/22/2015 Safari9/16/20201821
css.properties.transition-timing-function.jump Firefox1/29/2019 Safari9/16/2020596
css.types.easing-function.steps.jump Firefox1/29/2019 Safari9/16/2020596
html.elements.a.referrerpolicy πŸ“‹Firefox11/15/2016 Safari9/16/20201401
html.elements.area.referrerpolicy πŸ“‹Firefox11/15/2016 Safari9/16/20201401
html.elements.iframe.referrerpolicy πŸ“‹Firefox11/15/2016 Safari9/16/20201401
html.elements.img.referrerpolicy πŸ“‹Firefox11/15/2016 Safari9/16/20201401
html.elements.link.referrerpolicy πŸ“‹Firefox11/15/2016 Safari9/16/20201401
html.elements.script.referrerpolicy πŸ“‹Firefox1/29/2019 Safari9/16/2020596
html.elements.video.aspect_ratio_computed_from_attributes Firefox12/10/2019 Safari9/16/2020281

2020/8

API First Browser Date Last Browser Date Days Notes
css.properties.appearance.menulist-button πŸ“‹Safari10/26/2007 Firefox8/25/20204687
Firefox: See bug 1481615.Firefox for Android: See bug 1481615.

2020/7

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.sandbox.allow-top-navigation-by-user-activation πŸ“‹Safari4/12/2018 Firefox7/28/2020838
css.types.global_keywords.revert πŸ“‹Safari3/21/2016 Edge7/16/20201578

2020/6

API First Browser Date Last Browser Date Days Notes
css.selectors.read-only πŸ“‹Safari6/8/2009 Firefox6/30/20204040
css.selectors.read-write πŸ“‹Safari6/8/2009 Firefox6/30/20204040

2020/5

API First Browser Date Last Browser Date Days Notes
css.properties.line-break.anywhere πŸ“‹Firefox9/3/2019 Edge5/21/2020261
css.properties.grid-template-columns.repeat πŸ“‹Safari3/27/2017 Firefox5/5/20201135
Firefox: repeat(auto-fill, ...) and repeat(auto-fit, ...) only support one repeated column (see bug 1341507).Firefox: calc() doesn't work in repeat() (see bug 1350069).Firefox for Android: repeat(auto-fill, ...) and repeat(auto-fit, ...) only support one repeated column (see bug 1341507).Firefox for Android: calc() doesn't work in repeat() (see bug 1350069).
css.properties.grid-template-rows.repeat πŸ“‹Safari3/27/2017 Firefox5/5/20201135
Firefox: repeat(auto-fill, ...) and repeat(auto-fit, ...) only support one repeated column (see bug 1341507).Firefox: calc() doesn't work in repeat() (see bug 1350069).Firefox for Android: repeat(auto-fill, ...) and repeat(auto-fit, ...) only support one repeated column (see bug 1341507).Firefox for Android: calc() doesn't work in repeat() (see bug 1350069).

2020/4

API First Browser Date Last Browser Date Days Notes
css.properties.image-orientation πŸ“‹Firefox12/10/2013 Edge4/13/20202316
css.properties.image-orientation.from-image πŸ“‹Firefox12/10/2013 Edge4/13/20202316
css.properties.image-orientation.none πŸ“‹Firefox12/10/2013 Edge4/13/20202316
css.types.clamp πŸ“‹Edge1/15/2020 Firefox4/7/202083
css.types.max πŸ“‹Safari4/12/2018 Firefox4/7/2020726
css.types.min πŸ“‹Safari4/12/2018 Firefox4/7/2020726

2020/3

API First Browser Date Last Browser Date Days Notes
css.properties.font-optical-sizing πŸ“‹Edge4/30/2018 Safari3/24/2020694
css.properties.font-optical-sizing.auto πŸ“‹Edge4/30/2018 Safari3/24/2020694
css.properties.font-optical-sizing.none πŸ“‹Edge4/30/2018 Safari3/24/2020694
css.properties.opacity.percentages Firefox10/22/2019 Safari3/24/2020154
css.properties.overflow.multiple_keywords Firefox6/26/2018 Safari3/24/2020637
css.properties.tab-size.length πŸ“‹Firefox4/19/2017 Safari3/24/20201070
css.properties.text-orientation.mixed πŸ“‹Firefox9/22/2015 Safari3/24/20201645
css.properties.text-orientation.upright πŸ“‹Firefox9/22/2015 Safari3/24/20201645
css.properties.white-space.break-spaces πŸ“‹Firefox9/3/2019 Safari3/24/2020203
css.selectors.part πŸ“‹Firefox1/7/2020 Safari3/24/202077
css.types.basic-shape.path πŸ“‹Firefox1/7/2020 Safari3/24/202077
css.types.length.Q Firefox9/20/2016 Safari3/24/20201281
html.elements.link.rel.prefetch πŸ“‹Firefox10/24/2006 Safari3/24/20204900
Chrome: Requires secure contextChrome Android: Requires secure contextEdge: Requires secure contextFirefox: Requires secure contextFirefox for Android: Requires secure contextQuest Browser: Requires secure contextOpera: Requires secure contextOpera Android: Requires secure contextSamsung Internet: Requires secure contextWebView Android: Requires secure context
html.global_attributes.exportparts πŸ“‹Firefox1/7/2020 Safari3/24/202077
html.global_attributes.part πŸ“‹Firefox1/7/2020 Safari3/24/202077
css.properties.text-underline-position πŸ“‹Edge7/29/2015 Firefox3/10/20201686
css.properties.text-underline-position.auto πŸ“‹Safari3/25/2019 Firefox3/10/2020351
css.properties.text-underline-position.under πŸ“‹Safari3/25/2019 Firefox3/10/2020351
html.elements.audio.crossorigin πŸ“‹Safari9/20/2016 Firefox3/10/20201267
Firefox: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.Firefox for Android: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.
html.elements.iframe.allow πŸ“‹Safari4/12/2018 Firefox3/10/2020698
html.elements.iframe.allow.camera πŸ“‹Safari4/12/2018 Firefox3/10/2020698
html.elements.iframe.allow.microphone πŸ“‹Safari4/12/2018 Firefox3/10/2020698
html.elements.video.crossorigin πŸ“‹Safari9/20/2016 Firefox3/10/20201267
Firefox: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.Firefox for Android: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.

2020/1

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.OpenType_COLRv0 Firefox7/22/2014 Edge1/15/20202003
css.at-rules.font-face.font-display πŸ“‹Firefox1/23/2018 Edge1/15/2020722
css.at-rules.keyframes.ignore_important_declarations Firefox2/19/2013 Edge1/15/20202521
css.at-rules.media.calc πŸ“‹Firefox3/13/2018 Edge1/15/2020673
css.at-rules.media.display-mode πŸ“‹Firefox6/7/2016 Edge1/15/20201317
css.at-rules.media.display-mode.browser πŸ“‹Firefox6/7/2016 Edge1/15/20201317
Firefox for Android: display-mode: browser is always true.Safari: In a Safari browser window, display-mode: browser is always true, even in a macOS Full Screen window or when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In the Safari app, display-mode: browser is always true, even when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).WebView on iOS: In the Safari app, display-mode: browser is always true, even when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).
css.at-rules.media.display-mode.fullscreen πŸ“‹Firefox6/7/2016 Edge1/15/20201317
Firefox: In Firefox's "Full Screen" user interface, browser tabs and other user interface appear but display-mode: fullscreen is true.Safari: In a Safari browser window, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In the Safari app, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In an installed web application with the display manifest member set to standalone, display-mode: fullscreen is true, even though the system status bar is visible. See bug 264218.WebView on iOS: In the Safari app, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).WebView on iOS: In an installed web application with the display manifest member set to standalone, display-mode: fullscreen is true, even though the system status bar is visible. See bug 264218.
css.at-rules.media.display-mode.minimal-ui πŸ“‹Firefox11/14/2017 Edge1/15/2020792
Firefox: display-mode: minimal-ui is never true.Safari: display-mode: minimal-ui is never true.Safari on iOS: display-mode: minimal-ui is never true.WebView on iOS: display-mode: minimal-ui is never true.
css.at-rules.media.display-mode.standalone πŸ“‹Firefox11/14/2017 Edge1/15/2020792
Firefox: display-mode: standalone is never true.Safari on iOS: In an installed web application with the display manifest member set to standalone, display-mode: standalone is false and display-mode: fullscreen is true. See bug 264218.WebView on iOS: In an installed web application with the display manifest member set to standalone, display-mode: standalone is false and display-mode: fullscreen is true. See bug 264218.
css.at-rules.media.monochrome πŸ“‹Firefox10/24/2006 Edge1/15/20204831
css.at-rules.media.prefers-color-scheme πŸ“‹Safari3/25/2019 Edge1/15/2020296
css.at-rules.media.prefers-reduced-motion πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.align-content.flex_context.baseline Safari9/30/2015 Edge1/15/20201568
css.properties.align-content.flex_context.first_baseline Firefox3/7/2017 Edge1/15/20201044
css.properties.align-content.flex_context.space-evenly Firefox3/7/2017 Edge1/15/20201044
css.properties.align-content.flex_context.stretch Safari9/30/2015 Edge1/15/20201568
css.properties.align-items.flex_context.baseline Safari10/22/2013 Edge1/15/20202276
css.properties.align-items.flex_context.first_baseline Firefox3/7/2017 Edge1/15/20201044
css.properties.align-items.grid_context.start_end Firefox3/7/2017 Edge1/15/20201044
css.properties.align-self.auto πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.align-self.flex_context.baseline πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.align-self.flex_context.first_baseline Firefox3/7/2017 Edge1/15/20201044
css.properties.align-self.flex_context.stretch πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.properties.align-self.normal πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.align-self.stretch πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.all πŸ“‹Firefox2/4/2014 Edge1/15/20202171
css.properties.animation.paused πŸ“‹Safari6/8/2009 Edge1/15/20203873
css.properties.animation.running πŸ“‹Safari6/8/2009 Edge1/15/20203873
css.properties.background-blend-mode πŸ“‹Firefox6/10/2014 Edge1/15/20202045
css.properties.background-position.bottom πŸ“‹Safari6/23/2003 Edge1/15/20206050
css.properties.background-position.center πŸ“‹Safari6/23/2003 Edge1/15/20206050
css.properties.background-position.left πŸ“‹Safari6/23/2003 Edge1/15/20206050
css.properties.background-position.right πŸ“‹Safari6/23/2003 Edge1/15/20206050
css.properties.background-position.top πŸ“‹Safari6/23/2003 Edge1/15/20206050
css.properties.block-size πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.block-size.auto πŸ“‹Safari7/20/2011 Edge1/15/20203101
css.properties.block-size.max-content Firefox3/19/2019 Edge1/15/2020302
css.properties.block-size.min-content Firefox3/19/2019 Edge1/15/2020302
css.properties.border-block-end πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.currentColor πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.dashed πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.dotted πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.double πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.groove πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.hidden πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.inset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.medium πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.outset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.ridge πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.solid πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.thick πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.thin πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.transparent πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-color πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-color.currentColor πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-color.transparent πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.dashed πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.dotted πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.double πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.groove πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.hidden πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.inset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.outset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.ridge πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.solid πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-width πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-width.medium πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-width.thick πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-width.thin πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.currentColor πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.dashed πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.dotted πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.double πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.groove πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.hidden πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.inset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.medium πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.outset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.ridge πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.solid πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.thick πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.thin πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.transparent πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-color πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-color.currentColor πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-color.transparent πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.dashed πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.dotted πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.double πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.groove πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.hidden πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.inset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.outset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.ridge πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.solid πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-width πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-width.medium πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-width.thick πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-width.thin πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-collapse.collapse Safari10/24/2003 Edge1/15/20205927
css.properties.border-collapse.separate Safari10/24/2003 Edge1/15/20205927
css.properties.border-inline-end πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.currentColor πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.dashed πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.dotted πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.double πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.groove πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.hidden πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.inset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.medium πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.outset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.ridge πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.solid πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.thick πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.thin πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.transparent πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-color πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-color.currentColor πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-color.transparent πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.dashed πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.dotted πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.double πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.groove πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.hidden πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.inset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.outset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.ridge πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.solid πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-width πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-width.medium πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-width.thick πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-width.thin πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.currentColor πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.dashed πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.dotted πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.double πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.groove πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.hidden πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.inset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.medium πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.outset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.ridge πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.solid πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.thick πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.thin πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.transparent πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-color πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-color.currentColor πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-color.transparent πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.dashed πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.dotted πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.double πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.groove πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.hidden πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.inset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.outset πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.ridge πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.solid πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-width πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-width.medium πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-width.thick πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-width.thin πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.break-after.auto Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.left Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.page Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.right Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.auto Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.left Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.page Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.right Safari9/20/2016 Edge1/15/20201212
css.properties.break-inside.auto Safari9/20/2016 Edge1/15/20201212
css.properties.break-inside.avoid Safari9/20/2016 Edge1/15/20201212
css.properties.caption-side.bottom Safari6/23/2003 Edge1/15/20206050
css.properties.caption-side.top Safari6/23/2003 Edge1/15/20206050
css.properties.caret-color πŸ“‹Firefox4/19/2017 Edge1/15/20201001
css.properties.caret-color.auto πŸ“‹Firefox4/19/2017 Edge1/15/20201001
css.properties.caret-color.currentColor πŸ“‹Firefox4/19/2017 Edge1/15/20201001
css.properties.caret-color.transparent πŸ“‹Firefox4/19/2017 Edge1/15/20201001
css.properties.clip.auto Safari6/23/2003 Edge1/15/20206050
css.properties.clip-path πŸ“‹Firefox6/30/2009 Edge1/15/20203851
Edge: Only supports clip paths defined by url().Internet Explorer: Only supports clip paths defined by url().
css.properties.clip-path.basic_shape πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.clip-path.html_elements Firefox6/30/2009 Edge1/15/20203851
css.properties.clip-path.is_animatable Firefox9/20/2016 Edge1/15/20201212
css.properties.clip-rule πŸ“‹Firefox6/30/2009 Edge1/15/20203851
css.properties.clip-rule.evenodd πŸ“‹Firefox6/30/2009 Edge1/15/20203851
css.properties.clip-rule.nonzero πŸ“‹Firefox6/30/2009 Edge1/15/20203851
css.properties.color-interpolation πŸ“‹Firefox6/17/2008 Edge1/15/20204229
css.properties.color-interpolation.auto πŸ“‹Firefox6/17/2008 Edge1/15/20204229
css.properties.color-interpolation.linearRGB πŸ“‹Firefox6/17/2008 Edge1/15/20204229
css.properties.color-interpolation.sRGB πŸ“‹Firefox6/17/2008 Edge1/15/20204229
css.properties.color-interpolation-filters πŸ“‹Safari10/26/2007 Edge1/15/20204464
css.properties.color-interpolation-filters.auto πŸ“‹Safari10/26/2007 Edge1/15/20204464
css.properties.color-interpolation-filters.linearRGB πŸ“‹Firefox6/25/2013 Edge1/15/20202395
css.properties.color-interpolation-filters.sRGB πŸ“‹Firefox6/25/2013 Edge1/15/20202395
css.properties.content.element_replacement Safari9/30/2015 Edge1/15/20201568
css.properties.cursor.grabbing πŸ“‹Firefox2/4/2014 Edge1/15/20202171
Chrome: Chrome 22 added Windows support.Chrome Android: Chrome Android 25 added Windows support.Edge: Edge 79 added Windows support.Quest Browser: Quest Browser 5.0 added Windows support.Opera: Opera 15 added Windows support.Opera Android: Opera Android 14 added Windows support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.Samsung Internet: Samsung Internet 1.5 added Windows support.WebView Android: WebView Android 4.4 added Windows support.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.url_positioning_syntax Firefox11/29/2005 Edge1/15/20205160
Firefox: Firefox 4 added macOS support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cx πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.properties.cy πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.properties.display.contents πŸ“‹Firefox3/31/2015 Edge1/15/20201751
css.properties.display.flow-root Firefox4/19/2017 Edge1/15/20201001
css.properties.dominant-baseline πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.alphabetic πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.auto πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.central πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.hanging πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.ideographic πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.mathematical πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.middle πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.font.font-width_keyword_values Firefox12/15/2015 Edge1/15/20201492
css.properties.font-kerning πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.font-kerning.auto πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.font-kerning.none πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.font-kerning.normal πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.font-smooth Safari6/8/2009 Edge1/15/20203873
Firefox: Only works on macOS.
css.properties.font-style.oblique-angle πŸ“‹Safari4/12/2018 Edge1/15/2020643
Chrome: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Chrome Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Edge: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Quest Browser: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Samsung Internet: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.
css.properties.font-variant.css_fonts_shorthand Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant.none πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.all-petite-caps πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.all-small-caps πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.normal πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.petite-caps πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.small-caps πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.titling-caps πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.unicase πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.full-width πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.jis04 πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.jis78 πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.jis83 πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.jis90 πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.normal πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.proportional-width πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.ruby πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.simplified πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.traditional πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-ligatures πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-ligatures.common-ligatures πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.contextual πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.discretionary-ligatures πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.historical-ligatures πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.no-common-ligatures πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.no-contextual πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.no-discretionary-ligatures πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.no-historical-ligatures πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.none πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.normal πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-numeric πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.diagonal-fractions πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.lining-nums πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.normal πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.oldstyle-nums πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.ordinal πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.proportional-nums πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.slashed-zero πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.stacked-fractions πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.tabular-nums πŸ“‹Firefox12/1/2014 Edge1/15/20201871
css.properties.grid-auto-flow.column πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-auto-flow.dense πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-auto-flow.row πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template.none πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-areas.none πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns.auto πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns.max-content πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns.min-content πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns.none πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-rows.auto πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-rows.max-content πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-rows.min-content πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-rows.none πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.properties.height.max-content πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.height.min-content πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.image-rendering πŸ“‹Firefox1/21/2010 Edge1/15/20203646
css.properties.image-rendering.auto πŸ“‹Firefox1/21/2010 Edge1/15/20203646
css.properties.image-rendering.crisp-edges πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.inline-size πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.inline-size.auto πŸ“‹Safari7/20/2011 Edge1/15/20203101
css.properties.inline-size.max-content Firefox3/19/2019 Edge1/15/2020302
css.properties.inline-size.min-content Firefox3/19/2019 Edge1/15/2020302
css.properties.isolation πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.isolation.auto πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.isolation.isolate πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.justify-content.flex_context.space-evenly Firefox3/7/2017 Edge1/15/20201044
css.properties.justify-content.flex_context.stretch Safari9/30/2015 Edge1/15/20201568
css.properties.justify-content.left Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-content.normal Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-content.right Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-items.center Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-items.left Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-items.legacy πŸ“‹Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-items.right Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-self.auto Firefox3/8/2016 Edge1/15/20201408
css.properties.justify-self.left Firefox3/8/2016 Edge1/15/20201408
css.properties.justify-self.normal Firefox3/8/2016 Edge1/15/20201408
css.properties.justify-self.right Firefox3/8/2016 Edge1/15/20201408
css.properties.justify-self.stretch Firefox3/8/2016 Edge1/15/20201408
css.properties.line-break.auto πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.line-break.loose πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.line-break.normal πŸ“‹Safari4/29/2005 Edge1/15/20205374
css.properties.line-break.strict πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.list-style-type.arabic-indic πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.bengali πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.cambodian πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.cjk-earthly-branch πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.cjk-heavenly-stem πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.cjk-ideographic πŸ“‹Firefox11/9/2004 Edge1/15/20205545
Opera: Until version 15, only decimal numbers display.Opera Android: Until version 15, only decimal numbers display.
css.properties.list-style-type.devanagari πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.ethiopic-halehame-ti-er Firefox11/9/2004 Edge1/15/20205545
css.properties.list-style-type.ethiopic-halehame-ti-et Firefox11/9/2004 Edge1/15/20205545
css.properties.list-style-type.gujarati πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.gurmukhi πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.hangul Firefox11/9/2004 Edge1/15/20205545
css.properties.list-style-type.hangul-consonant Firefox11/9/2004 Edge1/15/20205545
css.properties.list-style-type.kannada πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.khmer πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.lao πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.lower-armenian πŸ“‹Safari7/20/2011 Edge1/15/20203101
css.properties.list-style-type.malayalam πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.mongolian πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.myanmar πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.oriya πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.persian πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.telugu πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.thai πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.tibetan πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.upper-armenian πŸ“‹Safari7/20/2011 Edge1/15/20203101
css.properties.list-style-type.urdu Safari6/7/2010 Edge1/15/20203509
css.properties.margin-block-end πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-block-end.auto πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-block-start πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-block-start.auto πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-inline-end πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-inline-end.auto πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-inline-start πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-inline-start.auto πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.mask-type πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.mask-type.alpha πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.mask-type.luminance πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.max-block-size πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.max-block-size.max-content Firefox3/19/2019 Edge1/15/2020302
css.properties.max-block-size.min-content Firefox3/19/2019 Edge1/15/2020302
css.properties.max-block-size.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.max-height.max-content πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.max-height.min-content πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.max-inline-size πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.max-inline-size.max-content Firefox3/19/2019 Edge1/15/2020302
css.properties.max-inline-size.min-content Firefox3/19/2019 Edge1/15/2020302
css.properties.max-inline-size.none πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.max-width.max-content πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.max-width.min-content πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.min-block-size πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.min-block-size.auto πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.min-block-size.max-content Firefox3/19/2019 Edge1/15/2020302
css.properties.min-block-size.min-content Firefox3/19/2019 Edge1/15/2020302
css.properties.min-height.max-content Safari9/19/2017 Edge1/15/2020848
css.properties.min-height.min-content Safari9/19/2017 Edge1/15/2020848
css.properties.min-inline-size πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.min-inline-size.auto πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.min-inline-size.max-content Firefox3/19/2019 Edge1/15/2020302
css.properties.min-inline-size.min-content Firefox3/19/2019 Edge1/15/2020302
css.properties.min-width.max-content Safari9/19/2017 Edge1/15/2020848
css.properties.min-width.min-content Safari9/19/2017 Edge1/15/2020848
css.properties.mix-blend-mode πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.color πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.color-burn πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.color-dodge πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.darken πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.difference πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.exclusion πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.hard-light πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.hue πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.lighten πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.luminosity πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.multiply πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.normal πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.overlay πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.saturation πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.screen πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.soft-light πŸ“‹Firefox9/2/2014 Edge1/15/20201961
css.properties.object-fit πŸ“‹Firefox2/24/2015 Edge1/15/20201786
Edge: Only supported for <img> elements.
css.properties.object-fit.contain πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.object-fit.cover πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.object-fit.fill πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.object-fit.none πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.object-fit.scale-down πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.object-position πŸ“‹Firefox2/24/2015 Edge1/15/20201786
Edge: Only supported for <img> elements.
css.properties.outline.auto πŸ“‹Safari2/2/2004 Edge1/15/20205826
css.properties.padding-block-end πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.padding-block-start πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.padding-inline-end πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.padding-inline-start πŸ“‹Firefox9/22/2015 Edge1/15/20201576
css.properties.paint-order.fill πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.paint-order.markers πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.paint-order.normal πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.paint-order.stroke πŸ“‹Safari10/16/2014 Edge1/15/20201917
css.properties.place-content πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.properties.place-content.flex_context Safari9/30/2015 Edge1/15/20201568
Firefox: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.Firefox for Android: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.
css.properties.place-content.grid_context Firefox4/19/2017 Edge1/15/20201001
Firefox: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.Firefox for Android: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.
css.properties.place-items πŸ“‹Firefox3/8/2016 Edge1/15/20201408
css.properties.place-items.flex_context Firefox3/8/2016 Edge1/15/20201408
css.properties.place-items.grid_context Firefox3/8/2016 Edge1/15/20201408
css.properties.place-self πŸ“‹Firefox3/8/2016 Edge1/15/20201408
css.properties.place-self.flex_context Firefox3/8/2016 Edge1/15/20201408
css.properties.place-self.grid_context Firefox3/8/2016 Edge1/15/20201408
css.properties.r πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.properties.resize πŸ“‹Safari10/26/2007 Edge1/15/20204464
Firefox for Android: The property is recognized, but has no effect. See bug 1776834.Safari on iOS: The property is recognized, but has no effect. See bug 211994.WebView on iOS: The property is recognized, but has no effect. See bug 211994.
css.properties.resize.block_level_support Safari6/8/2009 Edge1/15/20203873
Firefox: resize doesn't have any effect on <iframe>. See bug 680823)
css.properties.resize.both πŸ“‹Safari10/26/2007 Edge1/15/20204464
css.properties.resize.horizontal πŸ“‹Safari10/26/2007 Edge1/15/20204464
css.properties.resize.none πŸ“‹Safari10/26/2007 Edge1/15/20204464
css.properties.resize.vertical πŸ“‹Safari10/26/2007 Edge1/15/20204464
css.properties.scroll-padding.auto πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align.center πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align.end πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align.none πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align.start πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.block πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.both πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.inline πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.none πŸ“‹Firefox7/2/2015 Edge1/15/20201658
css.properties.scroll-snap-type.x πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.y πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.shape-image-threshold πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-margin πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.border-box πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.circle Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.content-box πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.gradient πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.image πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.inset Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.margin-box πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.none πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.padding-box πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.polygon Safari3/27/2017 Edge1/15/20201024
css.properties.shape-rendering πŸ“‹Firefox6/17/2008 Edge1/15/20204229
css.properties.shape-rendering.auto πŸ“‹Firefox6/17/2008 Edge1/15/20204229
css.properties.shape-rendering.crispEdges πŸ“‹Safari6/8/2009 Edge1/15/20203873
css.properties.shape-rendering.geometricPrecision πŸ“‹Safari6/8/2009 Edge1/15/20203873
css.properties.shape-rendering.optimizeSpeed πŸ“‹Safari6/8/2009 Edge1/15/20203873
css.properties.text-align.center πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.text-align.end πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.text-align.left πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.text-align.right πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.text-align.start πŸ“‹Firefox11/9/2004 Edge1/15/20205545
css.properties.text-decoration-color πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.text-decoration-color.currentColor πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-color.transparent πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-line πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.text-decoration-line.blink πŸ“‹Firefox12/10/2013 Edge1/15/20202227
Chrome: The blink value does not have any effect.Chrome Android: The blink value does not have any effect.Edge: The blink value does not have any effect.Firefox: The blink value does not have any effect.Firefox for Android: The blink value does not have any effect.Quest Browser: The blink value does not have any effect.Samsung Internet: The blink value does not have any effect.WebView Android: The blink value does not have any effect.
css.properties.text-decoration-line.line-through πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-line.none πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-line.overline πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-line.underline πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.text-decoration-style.dashed πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style.dotted πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style.double πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style.solid πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style.wavy πŸ“‹Firefox8/16/2011 Edge1/15/20203074
css.properties.text-emphasis.circle πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.currentColor πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.dot πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.double-circle πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.filled πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.none πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.open πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.sesame πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.transparent πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.triangle πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis-color.currentColor πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis-color.transparent πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis-position.left Safari10/16/2014 Edge1/15/20201917
css.properties.text-emphasis-position.right Safari10/16/2014 Edge1/15/20201917
css.properties.text-orientation.sideways πŸ“‹Safari10/22/2013 Edge1/15/20202276
css.properties.text-rendering πŸ“‹Firefox11/9/2004 Edge1/15/20205545
Chrome: This property is only supported on Windows and Linux.Chrome: Initial versions had bugs on Windows and Linux that broke font substitution, small-caps, letter-spacing or caused text to overlap. See bug 40156511, bug 40430936, bug 40444347, bug 40286561.Chrome Android: This property is only supported on Windows and Linux.Chrome Android: Initial versions had bugs on Windows and Linux that broke font substitution, small-caps, letter-spacing or caused text to overlap. See bug 40156511, bug 40430936, bug 40444347, bug 40286561.Edge: This property is only supported on Windows and Linux.Edge: Initial versions had bugs on Windows and Linux that broke font substitution, small-caps, letter-spacing or caused text to overlap. See bug 40156511, bug 40430936, bug 40444347, bug 40286561.Firefox: This property is only supported on Windows and Linux.Firefox: The optimizeSpeed option has no effect on Firefox 4 because the standard code for text rendering is already fast and there is not a faster code path at this time. See bug 595688 for details.Quest Browser: This property is only supported on Windows and Linux.Quest Browser: Initial versions had bugs on Windows and Linux that broke font substitution, small-caps, letter-spacing or caused text to overlap. See bug 40156511, bug 40430936, bug 40444347, bug 40286561.Samsung Internet: This property is only supported on Windows and Linux. Samsung Internet is not on Windows or Linux.WebView Android: From version 3 to 4.3, there is a serious bug where text-rendering: optimizeLegibility causes custom web fonts to not render. This was fixed in version 4.4.
css.properties.text-rendering.auto Firefox11/9/2004 Edge1/15/20205545
Chrome: Chrome treats auto as optimizeSpeed.Chrome Android: Chrome Android treats auto as optimizeSpeed.Edge: Edge treats auto as optimizeSpeed.Firefox: If the font size is 20 pixels or higher, Firefox treats auto as optimizeLegibility. For smaller text, Firefox treats auto as optimizeSpeed. The 20-pixel threshold can be changed with the browser.display.auto_quality_min_font_size preference.Firefox for Android: If the font size is 20 pixels or higher, Firefox treats auto as optimizeLegibility. For smaller text, Firefox treats auto as optimizeSpeed. The 20-pixel threshold can be changed with the browser.display.auto_quality_min_font_size preference.Quest Browser: Quest Browser treats auto as optimizeSpeed.Opera: Opera treats auto as optimizeSpeed.Opera Android: Opera Android treats auto as optimizeSpeed.Safari: Safari treats auto as optimizeSpeed. See bug 41363.Safari on iOS: Safari on iOS treats auto as optimizeSpeed. See bug 41363.Samsung Internet: Samsung Internet treats auto as optimizeSpeed.WebView Android: WebView Android treats auto as optimizeSpeed.WebView on iOS: WebView on iOS treats auto as optimizeSpeed. See bug 41363.
css.properties.text-rendering.geometricPrecision Firefox11/9/2004 Edge1/15/20205545
Chrome: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Chrome Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Edge: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Firefox: Firefox treats geometricPrecision the same as optimizeLegibility.Firefox for Android: Firefox treats geometricPrecision the same as optimizeLegibility.Quest Browser: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Opera: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Opera Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Samsung Internet: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.WebView Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.
css.properties.text-rendering.optimizeLegibility πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.text-rendering.optimizeSpeed πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.properties.transform-box πŸ“‹Firefox8/8/2017 Edge1/15/2020890
css.properties.transform-box.fill-box πŸ“‹Firefox8/8/2017 Edge1/15/2020890
css.properties.transform-box.view-box πŸ“‹Firefox8/8/2017 Edge1/15/2020890
css.properties.unicode-bidi.isolate πŸ“‹Firefox11/15/2016 Edge1/15/20201156
Chrome: Before Chrome 47, -webkit-isolate could lock up the browser.Chrome: Since Chrome 19, the syntax from a previous version of the specification, where the isolate keyword could be used together with bidi-override, is allowed.Firefox: From Firefox 10 to Firefox 16 (inclusive), the isolate keyword could be used together with bidi-override, which was the syntax from a previous version of the specification. From Firefox 17, only one value is allowed. Use isolate-override instead the previous isolate bidi-override.Firefox for Android: From Firefox for Android 10 to Firefox for Android 16 (inclusive), the isolate keyword could be used together with bidi-override, which was the syntax from a previous version of the specification. From Firefox for Android 17, only one value is allowed. Use isolate-override instead the previous isolate bidi-override.Opera: Before Opera 34, -webkit-isolate could lock up the browser.Opera: Since Opera 15, the syntax from a previous version of the specification, where the isolate keyword could be used together with bidi-override, is allowed.Safari: Before Safari 9, -webkit-isolate could lock up the browser.Safari on iOS: Before Safari on iOS 9, -webkit-isolate could lock up the browser.WebView on iOS: Before WebView on iOS 9, -webkit-isolate could lock up the browser.
css.properties.unicode-bidi.isolate-override πŸ“‹Firefox11/15/2016 Edge1/15/20201156
css.properties.unicode-bidi.plaintext πŸ“‹Firefox11/15/2016 Edge1/15/20201156
Firefox: Before Firefox 50, the plaintext value was ignored for vertical writing modes (bug 1302734).Firefox: Before Firefox 15, plaintext didn't do anything to an inline element. The specification changed and the implementation was changed in Firefox 15.Firefox for Android: Before Firefox for Android 50, the plaintext value was ignored for vertical writing modes (bug 1302734).Firefox for Android: Before Firefox for Android 15, plaintext didn't do anything to an inline element. The specification changed and the implementation was changed in Firefox for Android 15.
css.properties.user-select πŸ“‹Safari10/26/2007 Edge1/15/20204464
css.properties.vector-effect πŸ“‹Safari7/20/2011 Edge1/15/20203101
css.properties.vector-effect.non-scaling-stroke πŸ“‹Safari7/20/2011 Edge1/15/20203101
css.properties.vector-effect.none πŸ“‹Safari7/20/2011 Edge1/15/20203101
css.properties.width.max-content πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.width.min-content πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.properties.will-change πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.will-change.auto πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.will-change.contents πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.will-change.scroll-position πŸ“‹Firefox2/24/2015 Edge1/15/20201786
css.properties.x πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.properties.y πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.selectors.any-link πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.selectors.attribute.case_insensitive_modifier Safari9/30/2015 Edge1/15/20201568
css.selectors.cue πŸ“‹Safari10/22/2013 Edge1/15/20202276
Firefox: From Firefox 69, only allowed properties apply to the ::cue pseudo-element with no argument. See Permitted properties for a list of the allowed properties.
css.selectors.default πŸ“‹Safari6/7/2010 Edge1/15/20203509
css.selectors.defined πŸ“‹Safari9/20/2016 Edge1/15/20201212
css.selectors.focus-within πŸ“‹Firefox3/7/2017 Edge1/15/20201044
css.selectors.host πŸ“‹Safari9/20/2016 Edge1/15/20201212
css.selectors.hostfunction πŸ“‹Safari9/20/2016 Edge1/15/20201212
Safari: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy.Safari on iOS: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy.WebView on iOS: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy.
css.selectors.indeterminate.radio Safari9/20/2016 Edge1/15/20201212
css.selectors.invalid.form Firefox6/5/2012 Edge1/15/20202780
css.selectors.placeholder πŸ“‹Firefox1/24/2017 Edge1/15/20201086
css.selectors.placeholder-shown πŸ“‹Safari9/30/2015 Edge1/15/20201568
css.selectors.placeholder-shown.non_text_types Safari9/30/2015 Edge1/15/20201568
css.selectors.scope πŸ“‹Safari10/22/2013 Edge1/15/20202276
Firefox: Firefox 55 removes support for <style scoped> but not for the :scope pseudo-class, which is still supported. <style scoped> made it possible to explicitly set up element scopes, but ongoing discussions about the design of this feature as well as lack of other implementations resulted in the decision to remove it.Firefox for Android: Firefox for Android 55 removes support for <style scoped> but not for the :scope pseudo-class, which is still supported. <style scoped> made it possible to explicitly set up element scopes, but ongoing discussions about the design of this feature as well as lack of other implementations resulted in the decision to remove it.
css.selectors.scope.dom_api Safari10/22/2013 Edge1/15/20202276
css.selectors.slotted πŸ“‹Safari9/20/2016 Edge1/15/20201212
css.selectors.valid.form Firefox6/5/2012 Edge1/15/20202780
css.types.basic-shape πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.animation Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.circle πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.ellipse πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.inset πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.polygon πŸ“‹Safari3/27/2017 Edge1/15/20201024
css.types.blend-mode πŸ“‹Firefox6/10/2014 Edge1/15/20202045
css.types.color.hsl.alpha_parameter Firefox3/7/2017 Edge1/15/20201044
css.types.color.hsl.space_separated_parameters Firefox3/7/2017 Edge1/15/20201044
css.types.color.rgb.alpha_parameter Firefox3/7/2017 Edge1/15/20201044
css.types.color.rgb.float_values Firefox3/7/2017 Edge1/15/20201044
css.types.color.rgb.space_separated_parameters Firefox3/7/2017 Edge1/15/20201044
css.types.color.rgb_hexadecimal_notation.alpha_hexadecimal_notation Firefox9/20/2016 Edge1/15/20201212
css.types.env πŸ“‹Safari4/12/2018 Edge1/15/2020643
css.types.env.safe-area-inset-bottom πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.types.env.safe-area-inset-left πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.types.env.safe-area-inset-right πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.types.env.safe-area-inset-top πŸ“‹Safari9/19/2017 Edge1/15/2020848
css.types.gradient.linear-gradient.doubleposition Firefox12/11/2018 Edge1/15/2020400
css.types.gradient.linear-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.radial-gradient.doubleposition Firefox12/11/2018 Edge1/15/2020400
css.types.gradient.radial-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.repeating-linear-gradient.doubleposition Firefox12/11/2018 Edge1/15/2020400
css.types.gradient.repeating-linear-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.repeating-radial-gradient.doubleposition Firefox12/11/2018 Edge1/15/2020400
css.types.gradient.repeating-radial-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
html.elements.a.rel.noopener πŸ“‹Firefox3/7/2017 Edge1/15/20201044
Firefox: Before Firefox 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox 63, these windows have the same features enabled by default as any other window.Firefox for Android: Before Firefox for Android 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox for Android 63, these windows have the same features enabled by default as any other window.
html.elements.area.rel.noopener πŸ“‹Firefox3/7/2017 Edge1/15/20201044
Firefox: Before Firefox 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox 63, these windows have the same features enabled by default as any other window.Firefox for Android: Before Firefox for Android 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox for Android 63, these windows have the same features enabled by default as any other window.
html.elements.bdi πŸ“‹Firefox1/31/2012 Edge1/15/20202906
html.elements.body.bottommargin Safari6/8/2009 Edge1/15/20203873
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.leftmargin Safari6/8/2009 Edge1/15/20203873
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.rightmargin Safari6/8/2009 Edge1/15/20203873
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.topmargin Safari6/8/2009 Edge1/15/20203873
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.details πŸ“‹Safari7/25/2012 Edge1/15/20202730
Firefox: Before Firefox 57, there was a bug meaning that <details> elements can't be made open by default using the open attribute if they have a CSS animation active on them.Firefox for Android: There is a bug meaning that <details> elements can't be made open by default using the open attribute if they have a CSS animation active on them.
html.elements.details.open Safari7/25/2012 Edge1/15/20202730
html.elements.embed.align πŸ“‹Firefox11/9/2004 Edge1/15/20205545
html.elements.embed.type πŸ“‹Firefox11/9/2004 Edge1/15/20205545
html.elements.fieldset.disabled πŸ“‹Firefox3/22/2011 Edge1/15/20203221
Edge: Does not work with nested fieldsets. For example: <fieldset disabled><fieldset><!--Still enabled--></fieldset></fieldset>Internet Explorer: Not all form control descendants of a disabled fieldset are properly disabled in IE11; see IE bug 817488: input[type='file'] not disabled inside disabled fieldset and IE bug 962368: Can still edit input[type='text'] within fieldset[disabled].
html.elements.iframe.sandbox.allow-forms πŸ“‹Safari6/7/2010 Edge1/15/20203509
html.elements.iframe.sandbox.allow-modals πŸ“‹Firefox9/20/2016 Edge1/15/20201212
html.elements.iframe.sandbox.allow-pointer-lock πŸ“‹Firefox9/20/2016 Edge1/15/20201212
html.elements.iframe.sandbox.allow-popups-to-escape-sandbox πŸ“‹Firefox9/20/2016 Edge1/15/20201212
html.elements.iframe.sandbox.allow-same-origin πŸ“‹Safari6/7/2010 Edge1/15/20203509
Chrome: Chrome 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Chrome Android: Chrome Android 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Edge: Edge 79 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Quest Browser: Quest Browser 6.0 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Opera: Opera 57 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Opera Android: Opera Android 49 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Safari: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Safari on iOS: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Samsung Internet: Samsung Internet 10.0 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.WebView Android: WebView Android 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.WebView on iOS: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.
html.elements.iframe.sandbox.allow-scripts πŸ“‹Safari6/7/2010 Edge1/15/20203509
html.elements.iframe.sandbox.allow-top-navigation πŸ“‹Safari6/7/2010 Edge1/15/20203509
html.elements.iframe.srcdoc πŸ“‹Safari7/25/2012 Edge1/15/20202730
html.elements.img.decoding πŸ“‹Safari4/12/2018 Edge1/15/2020643
html.elements.img.usemap.case_sensitive Firefox1/24/2017 Edge1/15/20201086
html.elements.link.rel.preconnect πŸ“‹Firefox7/2/2015 Edge1/15/20201658
Firefox: Before Firefox 41, it doesn't obey the crossorigin attribute.Firefox for Android: Before Firefox for Android 41, it doesn't obey the crossorigin attribute.
html.elements.link.sizes πŸ“‹Safari7/25/2012 Edge1/15/20202730
html.elements.meta.name.referrer πŸ“‹Firefox2/24/2015 Edge1/15/20201786
Chrome: Until Chrome 46, content values weren't constrained to the values listed in the spec.Chrome Android: Until Chrome Android 46, content values weren't constrained to the values listed in the spec.Firefox: The referrer value wasn't taken into account when navigation was happening via the context menu or middle click until Firefox 39.Firefox for Android: The referrer value wasn't taken into account when navigation was happening via the context menu or middle click until Firefox for Android 39.Internet Explorer: Browsers initially supported an early draft of the specification which can only use a meta tag and is only compatible with the origin value from the new spec.Quest Browser: Until Quest Browser 5.0, content values weren't constrained to the values listed in the spec.Opera: Until Opera 33, content values weren't constrained to the values listed in the spec.Opera Android: Until Opera Android 33, content values weren't constrained to the values listed in the spec.Samsung Internet: Until Samsung Internet 5.0, content values weren't constrained to the values listed in the spec.WebView Android: Until WebView Android 46, content values weren't constrained to the values listed in the spec.
html.elements.ol.reversed πŸ“‹Safari7/25/2012 Edge1/15/20202730
html.elements.rb πŸ“‹Safari6/7/2010 Edge1/15/20203509
Chrome: Blink has support for parsing the rb element, but not for rendering rb content as expected.Chrome Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.Edge: Blink has support for parsing the rb element, but not for rendering rb content as expected.Quest Browser: Blink has support for parsing the rb element, but not for rendering rb content as expected.Opera: Blink has support for parsing the rb element, but not for rendering rb content as expected.Opera Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.Safari: Safari has support for parsing the rb element, but not for rendering rb content as expected.Safari on iOS: Safari on iOS has support for parsing the rb element, but not for rendering rb content as expected.Samsung Internet: Blink has support for parsing the rb element, but not for rendering rb content as expected.WebView Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.WebView on iOS: WebView on iOS has support for parsing the rb element, but not for rendering rb content as expected.
html.elements.rtc πŸ“‹Firefox10/14/2014 Edge1/15/20201919
html.elements.script.type.module Safari3/27/2017 Edge1/15/20201024
Chrome: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Chrome Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Edge: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Quest Browser: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Opera: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Opera Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Safari: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).Safari on iOS: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).Samsung Internet: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.WebView Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.WebView on iOS: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).
html.elements.select.autocomplete πŸ“‹Safari3/21/2016 Edge1/15/20201395
html.elements.slot πŸ“‹Safari9/20/2016 Edge1/15/20201212
html.elements.slot.name Safari9/20/2016 Edge1/15/20201212
html.elements.summary πŸ“‹Safari7/25/2012 Edge1/15/20202730
html.elements.textarea.autocomplete πŸ“‹Safari3/21/2016 Edge1/15/20201395
html.global_attributes.slot πŸ“‹Safari9/20/2016 Edge1/15/20201212
css.properties.letter-spacing.svg_elements Safari7/20/2011 Firefox1/7/20203093
css.properties.word-spacing.svg_elements Safari7/20/2011 Firefox1/7/20203093

2019/12

API First Browser Date Last Browser Date Days Notes
css.properties.column-span πŸ“‹Edge7/29/2015 Firefox12/10/20191595
css.properties.column-span.all πŸ“‹Safari7/20/2011 Firefox12/10/20193065
css.properties.column-span.none πŸ“‹Safari7/20/2011 Firefox12/10/20193065

2019/10

API First Browser Date Last Browser Date Days Notes
css.properties.grid-auto-columns πŸ“‹Safari3/27/2017 Firefox10/22/2019939
Firefox: Does not accept multiple track-size values. See bug 1339672.Firefox for Android: Does not accept multiple track-size values. See bug 1339672.
css.properties.grid-auto-rows πŸ“‹Safari3/27/2017 Firefox10/22/2019939
Firefox: Does not accept multiple track-size values. See bug 1339672.Firefox for Android: Does not accept multiple track-size values. See bug 1339672.

2019/9

API First Browser Date Last Browser Date Days Notes
css.properties.position.sticky πŸ“‹Firefox9/2/2014 Safari9/19/20191843
css.properties.touch-action πŸ“‹Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.manipulation Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.none Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-x Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-y Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.line-break πŸ“‹Edge8/2/2016 Firefox9/3/20191127

2019/7

API First Browser Date Last Browser Date Days Notes
css.properties.line-clamp πŸ“‹Safari6/7/2010 Firefox7/9/20193319
Safari: Accidental exposure.Safari on iOS: Accidental exposure.WebView on iOS: Accidental exposure.

2019/5

API First Browser Date Last Browser Date Days Notes
css.properties.word-break.break-word πŸ“‹Safari10/26/2007 Firefox5/21/20194225

2019/3

API First Browser Date Last Browser Date Days Notes
css.properties.column-gap.multicol_context.calc_values Edge10/17/2017 Safari3/25/2019524
css.properties.gap.grid_context.calc_values Firefox3/7/2017 Safari3/25/2019748
html.elements.datalist πŸ“‹Firefox3/22/2011 Safari3/25/20192925
Firefox for Android: The dropdown menu containing available options does not appear. See bug 1535985.
html.elements.datalist.input_type_email πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_number πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_search πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_tel πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_text πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_url πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_color πŸ“‹Firefox4/29/2014 Safari3/25/20191791
Firefox for Android: Firefox for Android doesn't allow the user to choose a custom color, only one of the predefined ones.
html.elements.input.type_email.list πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_number.list πŸ“‹Firefox4/29/2014 Safari3/25/20191791
html.elements.input.type_search.list πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_tel.list πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_text.list πŸ“‹Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_url.list πŸ“‹Firefox3/22/2011 Safari3/25/20192925

2019/1

API First Browser Date Last Browser Date Days Notes
css.properties.break-after πŸ“‹Edge7/29/2015 Firefox1/29/20191280
css.properties.break-after.paged_context πŸ“‹Edge7/29/2015 Firefox1/29/20191280
css.properties.break-after.paged_context.page Edge7/29/2015 Firefox1/29/20191280
css.properties.break-before πŸ“‹Edge7/29/2015 Firefox1/29/20191280
css.properties.break-before.paged_context πŸ“‹Edge7/29/2015 Firefox1/29/20191280
css.properties.break-before.paged_context.page Edge7/29/2015 Firefox1/29/20191280
css.properties.break-inside πŸ“‹Edge7/29/2015 Firefox1/29/20191280
css.properties.break-inside.multicol_context πŸ“‹Edge7/29/2015 Firefox1/29/20191280
css.properties.break-inside.paged_context πŸ“‹Edge7/29/2015 Firefox1/29/20191280
html.elements.marquee πŸ“‹Safari2/2/2004 Firefox1/29/20195475
Firefox: Implements the HTMLDivElement interface.Firefox for Android: Implements the HTMLDivElement interface.

2018/12

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.any-hover πŸ“‹Safari9/30/2015 Firefox12/11/20181168
css.at-rules.media.any-pointer πŸ“‹Edge7/29/2015 Firefox12/11/20181231
css.at-rules.media.hover πŸ“‹Edge7/29/2015 Firefox12/11/20181231
Chrome: Before Chrome 41, the implementation was buggy and reported (hover: none) on non-touch-based computers with a mouse/trackpad. See bug 40397980.Chrome Android: On some Android devices, such as certain Samsung models, the (hover: hover) media query may incorrectly match. See bug 41445959.Quest Browser: On some Android devices, such as certain Samsung models, the (hover: hover) media query may incorrectly match. See bug 41445959.Opera: Before Opera 28, the implementation was buggy and reported (hover: none) on non-touch-based computers with a mouse/trackpad. See bug 40397980.Opera Android: On some Android devices, such as certain Samsung models, the (hover: hover) media query may incorrectly match. See bug 41445959.Samsung Internet: On some Android devices, such as certain Samsung models, the (hover: hover) media query may incorrectly match. See bug 41445959.WebView Android: On some Android devices, such as certain Samsung models, the (hover: hover) media query may incorrectly match. See bug 41445959.
css.at-rules.media.pointer πŸ“‹Edge7/29/2015 Firefox12/11/20181231

2018/10

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.-webkit-device-pixel-ratio πŸ“‹Safari10/26/2007 Firefox10/23/20184015
Firefox: Implemented as an alias for -moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for -moz-device-pixel-ratio.
css.at-rules.media.-webkit-max-device-pixel-ratio πŸ“‹Safari10/26/2007 Firefox10/23/20184015
Firefox: Implemented as an alias for max--moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for max--moz-device-pixel-ratio.
css.at-rules.media.-webkit-min-device-pixel-ratio πŸ“‹Safari10/26/2007 Firefox10/23/20184015
Firefox: Implemented as an alias for min--moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for min--moz-device-pixel-ratio.
css.properties.-webkit-mask-position-x Safari3/18/2008 Edge10/2/20183850
css.properties.-webkit-mask-position-y Safari3/18/2008 Edge10/2/20183850
css.properties.font-stretch.percentage Safari4/12/2018 Edge10/2/2018173
css.properties.mask-image.multiple_mask_images Safari6/8/2009 Edge10/2/20183403
css.properties.mask-image.svg_masks Safari6/8/2009 Edge10/2/20183403
css.properties.overflow-wrap πŸ“‹Safari10/22/2013 Edge10/2/20181806
css.properties.text-transform.uppercase_eszett Safari6/23/2003 Edge10/2/20185580
html.elements.a.download πŸ“‹Firefox4/2/2013 Edge10/2/20182009
Chrome: Starting in Chrome 65, cross-origin downloads are not supported on the <a> element.Chrome Android: Starting in Chrome Android 65, cross-origin downloads are not supported on the <a> element.Edge: Starting in Edge 79, cross-origin downloads are not supported on the <a> element.Edge: Until Edge 14 (build 14357), attempting to download data URIs caused Edge to crash (bug 7160092).Edge: Edge 17 or older didn't follow the attributes' value to determine filename (bug 7260192).Firefox for Android: The attribute's filename value only affects the suggested file name for the blob: and data: URI schemes. Other schemes ignore the suggested filename. See bug 1845642.Quest Browser: Starting in Quest Browser 5.0, cross-origin downloads are not supported on the <a> element.Opera: Starting in Opera 52, cross-origin downloads are not supported on the <a> element.Opera Android: Starting in Opera Android 47, cross-origin downloads are not supported on the <a> element.Samsung Internet: Starting in Samsung Internet 9.0, cross-origin downloads are not supported on the <a> element.WebView Android: Starting in WebView Android 65, cross-origin downloads are not supported on the <a> element.
html.elements.audio.muted πŸ“‹Firefox3/13/2012 Edge10/2/20182394
html.elements.output πŸ“‹Firefox3/22/2011 Edge10/2/20182751
html.elements.output.for πŸ“‹Firefox3/22/2011 Edge10/2/20182751
html.elements.output.form πŸ“‹Firefox3/22/2011 Edge10/2/20182751
html.elements.output.name πŸ“‹Firefox3/22/2011 Edge10/2/20182751

2018/9

API First Browser Date Last Browser Date Days Notes
css.properties.column-gap.grid_context πŸ“‹Edge10/17/2017 Safari9/17/2018335
css.properties.column-gap.multicol_context.percentage_values Edge10/17/2017 Safari9/17/2018335
css.properties.gap.grid_context πŸ“‹Edge10/17/2017 Safari9/17/2018335
css.properties.row-gap.grid_context πŸ“‹Edge10/17/2017 Safari9/17/2018335
css.at-rules.font-face.font-stretch πŸ“‹Safari3/27/2017 Firefox9/5/2018527
css.at-rules.font-face.src.format_variations Safari9/19/2017 Firefox9/5/2018351
css.properties.font-variation-settings πŸ“‹Safari9/19/2017 Firefox9/5/2018351
Safari: Requires macOS 10.13 High Sierra or later.Safari on iOS: Requires iOS 11 or later.WebView on iOS: Requires iOS 11 or later.
css.properties.font-variation-settings.normal πŸ“‹Safari9/19/2017 Firefox9/5/2018351
css.selectors.selection πŸ“‹Safari10/24/2003 Firefox9/5/20185430

2018/6

API First Browser Date Last Browser Date Days Notes
css.properties.font-weight.number Safari9/19/2017 Firefox6/26/2018280

2018/5

API First Browser Date Last Browser Date Days Notes
html.elements.script.nomodule πŸ“‹Safari9/19/2017 Firefox5/9/2018232

2018/4

API First Browser Date Last Browser Date Days Notes
css.properties.transform-origin.svg_elements Safari7/25/2012 Edge4/30/20182105
Firefox: Keywords and percentages refer to the canvas instead of the object itself. See bug 1209061.Firefox for Android: Keywords and percentages refer to the canvas instead of the object itself. See bug 1209061.Safari: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).Safari on iOS: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).WebView on iOS: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).
html.elements.a.ping πŸ“‹Firefox11/9/2004 Edge4/30/20184920
Firefox: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.Firefox for Android: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.
html.elements.area.ping πŸ“‹Firefox11/9/2004 Edge4/30/20184920
Firefox: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.Firefox for Android: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.
html.elements.input.minlength πŸ“‹Firefox1/24/2017 Edge4/30/2018461
html.elements.link.as πŸ“‹Safari9/20/2016 Edge4/30/2018587
html.elements.link.crossorigin πŸ“‹Firefox1/8/2013 Edge4/30/20181938
Firefox: Before Firefox 83, crossorigin is not supported for rel="icon".Firefox for Android: Before Firefox for Android 83, crossorigin is not supported for rel="icon".
html.elements.link.integrity πŸ“‹Firefox12/15/2015 Edge4/30/2018867
html.elements.script.integrity πŸ“‹Firefox12/15/2015 Edge4/30/2018867
html.elements.textarea.minlength πŸ“‹Firefox1/24/2017 Edge4/30/2018461
html.elements.input.webkitdirectory Edge11/12/2015 Safari4/12/2018882
Chrome Android: In Chrome for Android 131, choosing a directory crashes the browser (see bug 376834374).Chrome Android: Before version 131, users cannot choose a directory, only individual files (see bug 40248532.Safari on iOS: Before version 18.4, the attribute can be set but users cannot choose a directory, only individual files (see bug 271705).WebView Android: In Chrome for Android 131, choosing a directory crashes the browser (see bug 376834374).WebView Android: Before version 131, users cannot choose a directory, only individual files (see bug 40248532.WebView on iOS: Before version 18.4, the attribute can be set but users cannot choose a directory, only individual files (see bug 271705).

2018/3

API First Browser Date Last Browser Date Days Notes
css.properties.position.position_sticky_table_elements Safari10/16/2014 Firefox3/13/20181244
Firefox: Borders do not display on table headers if border-collapse is set to collapse (bug 1727594).Firefox for Android: Borders do not display on table headers if border-collapse is set to collapse (bug 1727594).

2018/1

API First Browser Date Last Browser Date Days Notes
html.global_attributes.title.multi-line_titles Edge7/29/2015 Firefox1/23/2018909

2017/10

API First Browser Date Last Browser Date Days Notes
css.properties.align-content.grid_context πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.align-items.grid_context πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.align-self.grid_context πŸ“‹Firefox3/7/2017 Edge10/17/2017224
Internet Explorer: Internet Explorer 10 and 11 have the property -ms-grid-row-align, which acts in a similar way to align-self.
css.properties.display.grid Firefox3/7/2017 Edge10/17/2017224
Internet Explorer: Internet Explorer implements an older version of the specification.Samsung Internet: Samsung Internet added this earlier than the corresponding Chrome version would indicate.
css.properties.display.inline-grid Firefox3/7/2017 Edge10/17/2017224
Internet Explorer: Internet Explorer implements an older version of the specification.Samsung Internet: Samsung Internet added this earlier than the corresponding Chrome version would indicate.
css.properties.gap πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.gap.grid_context.percentage_values Firefox3/7/2017 Edge10/17/2017224
css.properties.gap.normal πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid πŸ“‹Firefox3/7/2017 Edge10/17/2017224
Samsung Internet: This was added early so is out of sync with the equivalent Chromium version.
css.properties.grid.none πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-area πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-area.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-columns.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-columns.max-content πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-columns.min-content πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-flow πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-rows.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-rows.max-content πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-rows.min-content πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column-end πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column-end.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column-start πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column-start.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row-end πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row-end.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row-start πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row-start.auto πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-areas πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-columns πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-columns.fit-content πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-columns.minmax πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-rows πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-rows.fit-content πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-rows.minmax πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.justify-content.grid_context πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.justify-items.grid_context πŸ“‹Firefox3/8/2016 Edge10/17/2017588
css.properties.justify-self πŸ“‹Firefox3/8/2016 Edge10/17/2017588
css.properties.justify-self.grid_context πŸ“‹Firefox3/8/2016 Edge10/17/2017588
Internet Explorer: Internet Explorer 10 and 11 have the property -ms-grid-column-align, which acts in a similar way to justify-self.
css.properties.object-position.bottom πŸ“‹Firefox2/24/2015 Edge10/17/2017966
css.properties.object-position.center πŸ“‹Firefox2/24/2015 Edge10/17/2017966
css.properties.object-position.left πŸ“‹Firefox2/24/2015 Edge10/17/2017966
css.properties.object-position.right πŸ“‹Firefox2/24/2015 Edge10/17/2017966
css.properties.object-position.top πŸ“‹Firefox2/24/2015 Edge10/17/2017966
css.properties.row-gap πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.properties.row-gap.normal πŸ“‹Firefox3/7/2017 Edge10/17/2017224
css.types.calc.nested Firefox8/2/2016 Edge10/17/2017441
css.types.length.vmax Firefox2/19/2013 Edge10/17/20171701
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
html.elements.button.form Firefox3/22/2011 Edge10/17/20172401

2017/9

API First Browser Date Last Browser Date Days Notes
css.properties.cursor.grab Firefox2/4/2014 Safari9/19/20171323
Chrome: Chrome also continues to support the prefixed versions.Chrome: Chrome 22 added Windows support.Chrome Android: Chrome Android also continues to support the prefixed versions.Chrome Android: Chrome Android 25 added Windows support.Quest Browser: Quest Browser also continues to support the prefixed versions.Quest Browser: Quest Browser 5.0 added Windows support.Opera: Opera also continues to support the prefixed versions.Opera: Opera 22 added Windows support.Opera Android: Opera also continues to support the prefixed versions.Opera Android: Opera 22 added Windows support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView Android: WebView Android also continues to support the prefixed versions.WebView Android: WebView Android 4.4 added Windows support.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.font-stretch πŸ“‹Firefox12/20/2011 Safari9/19/20172100
Chrome: A font-stretch declaration must be added to the @font-face before this property will function.Chrome Android: A font-stretch declaration must be added to the @font-face before this property will function.Quest Browser: A font-stretch declaration must be added to the @font-face before this property will function.Opera: A font-stretch declaration must be added to the @font-face before this property will function.Opera Android: A font-stretch declaration must be added to the @font-face before this property will function.Samsung Internet: A font-stretch declaration must be added to the @font-face before this property will function.WebView Android: A font-stretch declaration must be added to the @font-face before this property will function.
css.properties.font-stretch.condensed πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.expanded πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.extra-condensed πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.extra-expanded πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.normal πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.semi-condensed πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.semi-expanded πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.ultra-condensed πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.ultra-expanded πŸ“‹Firefox12/20/2011 Safari9/19/20172100
css.properties.position.absolutely_positioned_flex_children Edge7/29/2015 Safari9/19/2017783

2017/8

API First Browser Date Last Browser Date Days Notes
css.types.gradient.linear-gradient.unitless_0_angle Safari10/22/2013 Firefox8/8/20171386
Firefox: Accepted only in -webkit-linear-gradient() and -moz-linear-gradient(), not linear-gradient().Firefox for Android: Accepted only in -webkit-linear-gradient() and -moz-linear-gradient(), not linear-gradient().
css.types.gradient.repeating-linear-gradient.unitless_0_angle Safari10/22/2013 Firefox8/8/20171386
Firefox: Accepted only in -webkit-repeating-linear-gradient() and -moz-repeating-linear-gradient(), not repeating-linear-gradient().Firefox for Android: Accepted only in -webkit-repeating-linear-gradient() and -moz-repeating-linear-gradient(), not repeating-linear-gradient().

2017/6

API First Browser Date Last Browser Date Days Notes
css.properties.appearance.none πŸ“‹Safari10/26/2007 Firefox6/13/20173518
Firefox: Doesn't work with <input type="checkbox"> and <input type="radio">.Firefox for Android: Doesn't work with <input type="checkbox"> and <input type="radio">.

2017/4

API First Browser Date Last Browser Date Days Notes
css.properties.-webkit-text-stroke πŸ“‹Safari10/26/2007 Edge4/5/20173449
css.properties.-webkit-text-stroke-color πŸ“‹Safari10/26/2007 Edge4/5/20173449
css.properties.-webkit-text-stroke-width πŸ“‹Safari10/26/2007 Edge4/5/20173449
css.properties.background.border-box πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.bottom πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.center πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.content-box πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.fixed πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.left πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.padding-box πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.right πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background.top πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.background-color.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-bottom.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-bottom-color.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-color.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-left.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-left-color.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-right.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-right-color.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-top.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.border-top-color.currentColor πŸ“‹Safari3/21/2016 Edge4/5/2017380
css.properties.custom-property πŸ“‹Firefox7/22/2014 Edge4/5/2017988
css.properties.display.table-caption Firefox11/9/2004 Edge4/5/20174530
css.properties.fill πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.fill.none πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.fill-opacity πŸ“‹Firefox11/9/2004 Edge4/5/20174530
css.properties.fill-rule πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.fill-rule.evenodd πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.fill-rule.nonzero πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.font-feature-settings πŸ“‹Firefox12/1/2014 Edge4/5/2017856
Firefox: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox: From Firefox 129 the -webkit-font-feature-settings alias has been added to support sites that are still supporting the vendor prefix.Firefox: From Firefox 4 to Firefox 14 (inclusive), Firefox supported an older, slightly different syntax. See OpenType Font Feature support in Firefox 4.Firefox for Android: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox for Android 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox for Android 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox for Android: From Firefox for Android 129 the -webkit-font-feature-settings alias has been added to support sites that are still supporting the vendor prefix.Firefox for Android: From Firefox for Android 4 to Firefox for Android 14 (inclusive), Firefox for Android supported an older, slightly different syntax. See OpenType Font Feature support in Firefox for Android 4.
css.properties.font-feature-settings.normal πŸ“‹Firefox8/28/2012 Edge4/5/20171681
css.properties.marker πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.marker.none πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-end πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-end.none πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-mid πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-mid.none πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-start πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-start.none πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.outline-offset πŸ“‹Safari2/2/2004 Edge4/5/20174811
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.stop-color πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.stop-opacity πŸ“‹Firefox6/17/2008 Edge4/5/20173214
css.properties.stroke πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke.none πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-dasharray πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-dasharray.none πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-dashoffset πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linecap πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linecap.butt πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linecap.round πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linecap.square πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linejoin πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linejoin.bevel πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linejoin.miter πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linejoin.round πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-miterlimit πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-opacity πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-width πŸ“‹Firefox11/29/2005 Edge4/5/20174145
css.types.var πŸ“‹Firefox7/22/2014 Edge4/5/2017988
html.global_attributes.dir πŸ“‹Firefox11/9/2004 Edge4/5/20174530

2017/3

API First Browser Date Last Browser Date Days Notes
css.properties.writing-mode πŸ“‹Edge7/29/2015 Safari3/27/2017607
Firefox: Firefox 42 added support for bidirectional and RTL scripts in vertical modes.Firefox for Android: Firefox for Android 42 added support for bidirectional and RTL scripts in vertical modes.Internet Explorer: Internet Explorer's implementation differs from the specification.Internet Explorer: Internet Explorer's implementation differs from the specification.
css.properties.writing-mode.lr Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.lr-tb Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.rl Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.rl-tb Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.tb Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.tb-rl Edge7/29/2015 Safari3/27/2017607
css.types.flex πŸ“‹Edge7/29/2015 Safari3/27/2017607
css.types.number.scientific_notation Firefox4/29/2014 Safari3/27/20171063
html.elements.area.download πŸ“‹Firefox4/2/2013 Safari3/27/20171455
html.elements.form.novalidate πŸ“‹Firefox3/22/2011 Safari3/27/20172197
html.elements.hr.color Firefox11/9/2004 Safari3/27/20174521
html.elements.iframe.allowfullscreen πŸ“‹Firefox1/8/2013 Safari3/27/20171539
Safari on iOS: Only available on iPad, not on iPhone.Safari on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.WebView on iOS: Only available on iPad, not on iPhone.WebView on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.
html.elements.meta.http-equiv.content-language πŸ“‹Firefox11/9/2004 Safari3/27/20174521
html.elements.meta.http-equiv.content-security-policy πŸ“‹Firefox11/9/2004 Safari3/27/20174521
html.elements.meta.http-equiv.content-type πŸ“‹Firefox11/9/2004 Safari3/27/20174521
css.properties.clip-path.svg_elements Safari10/22/2013 Firefox3/7/20171232
css.properties.column-count πŸ“‹Edge7/29/2015 Firefox3/7/2017587
Firefox: Before version 37, multiple columns didn't work with display: table-caption elements.Firefox for Android: Before version 37, multiple columns didn't work with display: table-caption elements.
css.properties.column-fill πŸ“‹Edge7/29/2015 Firefox3/7/2017587
css.properties.column-gap.multicol_context πŸ“‹Edge7/29/2015 Firefox3/7/2017587
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.column-rule πŸ“‹Edge7/29/2015 Firefox3/7/2017587
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.column-rule-color πŸ“‹Edge7/29/2015 Firefox3/7/2017587
css.properties.column-rule-style πŸ“‹Edge7/29/2015 Firefox3/7/2017587
css.properties.column-rule-width πŸ“‹Edge7/29/2015 Firefox3/7/2017587
css.properties.columns πŸ“‹Edge7/29/2015 Firefox3/7/2017587
Firefox: Before version 37, multiple columns didn't work with display: table-caption elements.Firefox for Android: Before version 37, multiple columns didn't work with display: table-caption elements.

2016/11

API First Browser Date Last Browser Date Days Notes
css.properties.border-image-repeat.space πŸ“‹Edge7/29/2015 Firefox11/15/2016475
css.properties.column-width πŸ“‹Edge7/29/2015 Firefox11/15/2016475
Firefox: Before version 37, multiple columns didn't work with display: table-caption elements.Firefox for Android: Before version 37, multiple columns didn't work with display: table-caption elements.
css.properties.pointer-events.visibleFill πŸ“‹Safari6/8/2009 Firefox11/15/20162717
css.properties.pointer-events.visiblePainted πŸ“‹Safari6/8/2009 Firefox11/15/20162717
css.properties.pointer-events.visibleStroke πŸ“‹Safari6/8/2009 Firefox11/15/20162717
html.elements.track.src πŸ“‹Safari7/25/2012 Firefox11/15/20161574
Firefox: Before Firefox 50, setting the src didn't work, though it didn't raise an error.Firefox for Android: Before Firefox for Android 50, setting the src didn't work, though it didn't raise an error.

2016/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.WOFF_2 πŸ“‹Firefox7/2/2015 Safari9/20/2016446
Safari: Supported only on macOS 10.12 (Sierra) and later.
css.at-rules.media.-webkit-transform-3d πŸ“‹Safari6/8/2009 Firefox9/20/20162661
css.properties.-webkit-text-fill-color πŸ“‹Safari10/26/2007 Firefox9/20/20163252
css.properties.background-position-x πŸ“‹Safari6/23/2003 Firefox9/20/20164838
css.properties.background-position-y πŸ“‹Safari6/23/2003 Firefox9/20/20164838
css.properties.background-repeat.round πŸ“‹Safari10/16/2014 Firefox9/20/2016705
css.properties.background-repeat.space πŸ“‹Safari10/16/2014 Firefox9/20/2016705
css.properties.box-align Safari10/26/2007 Firefox9/20/20163252
css.properties.box-direction Safari10/26/2007 Firefox9/20/20163252
css.properties.box-flex Safari10/26/2007 Firefox9/20/20163252
css.properties.box-ordinal-group Safari10/26/2007 Firefox9/20/20163252
css.properties.box-orient Safari10/26/2007 Firefox9/20/20163252
css.properties.box-pack Safari10/26/2007 Firefox9/20/20163252
css.properties.transition.allow-discrete πŸ“‹Firefox3/22/2011 Safari9/20/20162009
css.properties.transition.normal πŸ“‹Firefox3/22/2011 Safari9/20/20162009
html.elements.data πŸ“‹Firefox6/25/2013 Safari9/20/20161183
html.elements.data.value πŸ“‹Firefox6/25/2013 Safari9/20/20161183

2016/8

API First Browser Date Last Browser Date Days Notes
css.properties.text-anchor πŸ“‹Firefox6/17/2008 Edge8/2/20162968
css.properties.text-anchor.end πŸ“‹Firefox6/17/2008 Edge8/2/20162968
css.properties.text-anchor.middle πŸ“‹Firefox6/17/2008 Edge8/2/20162968
css.properties.text-anchor.start πŸ“‹Firefox6/17/2008 Edge8/2/20162968
css.types.calc.number_values Safari7/25/2012 Firefox8/2/20161469
html.elements.script.crossorigin πŸ“‹Firefox7/17/2012 Edge8/2/20161477
Safari: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.Safari on iOS: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.WebView on iOS: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.
html.elements.time πŸ“‹Firefox6/25/2013 Edge8/2/20161134
html.elements.time.datetime Firefox6/25/2013 Edge8/2/20161134

2016/3

API First Browser Date Last Browser Date Days Notes
css.properties.border-image-repeat.round πŸ“‹Firefox8/28/2012 Safari3/21/20161301
css.properties.filter πŸ“‹Firefox1/13/2015 Safari3/21/2016433
Internet Explorer: Internet Explorer 4 to 9 implemented a non-standard filter property. The syntax was completely different from this one and is not documented here.
css.types.global_keywords.unset πŸ“‹Firefox2/4/2014 Safari3/21/2016776
html.elements.img.sizes πŸ“‹Firefox5/12/2015 Safari3/21/2016314
html.elements.picture πŸ“‹Firefox5/12/2015 Safari3/21/2016314
html.elements.source.sizes πŸ“‹Firefox5/12/2015 Safari3/21/2016314
Chrome: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Chrome Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Samsung Internet: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).WebView Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).
html.elements.source.srcset πŸ“‹Firefox5/12/2015 Safari3/21/2016314
Chrome: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Chrome Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Samsung Internet: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).WebView Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).

2015/12

API First Browser Date Last Browser Date Days Notes
css.properties.writing-mode.horizontal-tb Edge7/29/2015 Firefox12/15/2015139
css.properties.writing-mode.vertical-lr Edge7/29/2015 Firefox12/15/2015139
css.properties.writing-mode.vertical-rl Edge7/29/2015 Firefox12/15/2015139

2015/11

API First Browser Date Last Browser Date Days Notes
css.selectors.in-range πŸ“‹Safari7/20/2011 Edge11/12/20151576
Chrome: Before Chrome 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome 52, it was changed to only match enabled read-write inputs.Chrome Android: Before Chrome Android 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome Android 52, it was changed to only match enabled read-write inputs.Firefox: Before Firefox 50, :in-range matched disabled and read-only inputs (see bug 1264157). In Firefox 50, it was changed to only match enabled read-write inputs.Quest Browser: Before Quest Browser 5.0, :in-range matched disabled and read-only inputs (see bug 41248615). In Quest Browser 5.0, it was changed to only match enabled read-write inputs.Opera: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Opera Android: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Safari: In Safari, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Safari on iOS: In Safari on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Samsung Internet: Before version 6.0, :in-range matched disabled and read-only inputs (see bug 41248615). In version 6.0, it was changed to only match enabled read-write inputs.WebView Android: Before version 52, :in-range matched disabled and read-only inputs (see bug 41248615). In version 52, it was changed to only match enabled read-write inputs.WebView on iOS: In WebView on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.
css.selectors.out-of-range πŸ“‹Safari7/20/2011 Edge11/12/20151576
css.types.global_keywords.initial πŸ“‹Safari2/2/2004 Edge11/12/20154301
html.elements.a.rel.noreferrer πŸ“‹Safari6/7/2010 Edge11/12/20151984
Internet Explorer: Only supported in IE11 in later versions of Windows 10 (creators update). (Per caniuse.com.)
html.elements.area.rel.noreferrer πŸ“‹Safari6/7/2010 Edge11/12/20151984
Internet Explorer: Only supported in IE11 in later versions of Windows 10 (creators update). (Per caniuse.com.)
html.elements.meter πŸ“‹Safari7/25/2012 Edge11/12/20151205
html.elements.meter.high πŸ“‹Safari7/25/2012 Edge11/12/20151205
html.elements.meter.low πŸ“‹Safari7/25/2012 Edge11/12/20151205
html.elements.meter.max πŸ“‹Safari7/25/2012 Edge11/12/20151205
html.elements.meter.min πŸ“‹Safari7/25/2012 Edge11/12/20151205
html.elements.meter.optimum πŸ“‹Safari7/25/2012 Edge11/12/20151205
html.elements.meter.value πŸ“‹Safari7/25/2012 Edge11/12/20151205
html.elements.template πŸ“‹Firefox6/25/2013 Edge11/12/2015870

2015/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.keyframes πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.at-rules.supports πŸ“‹Firefox6/25/2013 Safari9/30/2015827
css.properties.align-content πŸ“‹Firefox3/18/2014 Safari9/30/2015561
css.properties.align-content.flex_context πŸ“‹Firefox3/18/2014 Safari9/30/2015561
css.properties.align-content.normal πŸ“‹Firefox3/18/2014 Safari9/30/2015561
css.properties.align-items πŸ“‹Firefox4/2/2013 Safari9/30/2015911
css.properties.align-self πŸ“‹Firefox4/2/2013 Safari9/30/2015911
css.properties.animation πŸ“‹Firefox10/9/2012 Safari9/30/20151086
WebView Android: The animation-fill-mode property is not supported in Android browsers below 2.3.
css.properties.animation-delay πŸ“‹Firefox10/9/2012 Safari9/30/20151086
Firefox: Before Firefox 57, Firefox does not repaint elements outside the viewport that are animated into the viewport with a delay. This bug affects only some platforms, such as Windows.
css.properties.animation-direction πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-duration πŸ“‹Firefox10/9/2012 Safari9/30/20151086
Internet Explorer: Once the element has loaded, changing the value of this property has no effect.
css.properties.animation-fill-mode πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-iteration-count πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-name πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-play-state πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-timing-function πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.counter-increment.list-item πŸ“‹Firefox11/9/2004 Safari9/30/20153977
css.properties.counter-reset.list-item πŸ“‹Firefox11/9/2004 Safari9/30/20153977
Chrome: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Chrome Android: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Quest Browser: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Opera: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Opera Android: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Safari: Overriding the initial value of the implicit list-item counter results in incorrect values for the counter() function used to generate content, as it is not fully implemented; see bug 260436.Safari on iOS: Overriding the initial value of the implicit list-item counter results in incorrect values for the counter() function used to generate content, as it is not fully implemented; see bug 260436.Samsung Internet: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.WebView Android: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.WebView on iOS: Overriding the initial value of the implicit list-item counter results in incorrect values for the counter() function used to generate content, as it is not fully implemented; see bug 260436.
css.properties.cursor.zoom-in πŸ“‹Firefox9/17/2013 Safari9/30/2015743
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.zoom-out πŸ“‹Firefox9/17/2013 Safari9/30/2015743
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.display.flex Firefox4/2/2013 Safari9/30/2015911
Firefox: Firefox 28 added multi-line flexbox support.Firefox for Android: Firefox for Android 28 added multi-line flexbox support.Internet Explorer: IE incorrectly positions inline block content inside flex containers. See the discussion on Microsoft Answers.Internet Explorer: IE incorrectly positions inline block content inside flex containers. See the discussion on Microsoft Answers.
css.properties.display.inline-flex Firefox4/2/2013 Safari9/30/2015911
Firefox: Firefox 28 added multi-line flexbox support.Firefox for Android: Firefox for Android 28 added multi-line flexbox support.
css.properties.flex πŸ“‹Firefox6/25/2013 Safari9/30/2015827
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox: Before Firefox 32, Firefox wasn't able to animate values starting or stopping at 0.Firefox: Until Firefox 61, flex items that are sized according to their content are sized using fit-content, not max-content.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Firefox for Android: Before Firefox for Android 32, Firefox for Android wasn't able to animate values starting or stopping at 0.Firefox for Android: Until Firefox for Android 61, flex items that are sized according to their content are sized using fit-content, not max-content.Internet Explorer: Internet Explorer 11 ignores uses of calc() in the flex-basis part of the flex syntax. This can be worked around by using the longhand properties instead of the shorthand. See Flexbug #8 for more info.Internet Explorer: Internet Explorer 11 considers a unitless value in the flex-basis part to be syntactically invalid (and will thus be ignored). A workaround is to always include a unit in the flex-basis part of the flex shorthand value. See Flexbug #4 for more info.Internet Explorer: Internet Explorer 10 and 11 ignore uses of calc() in the flex-basis part of the flex syntax. This can be worked around by using the longhand properties instead of the shorthand. See Flexbug #8 for more info.Internet Explorer: Internet Explorer 10 and 11 consider a unitless value in the flex-basis part to be syntactically invalid (and will thus be ignored). A workaround is to always include a unit in the flex-basis part of the flex shorthand value. See Flexbug #4 for more info.
css.properties.flex-basis πŸ“‹Firefox6/25/2013 Safari9/30/2015827
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Internet Explorer: When a non-auto flex-basis is specified, Internet Explorer 10 and 11 always uses a content-box box model to calculate the size of a flex item, even if box-sizing: border-box is applied to the element. See Flexbug #7 for more info.
css.properties.flex-basis.auto Firefox6/25/2013 Safari9/30/2015827
css.properties.flex-direction πŸ“‹Firefox6/25/2013 Safari9/30/2015827
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.
css.properties.flex-flow πŸ“‹Firefox3/18/2014 Safari9/30/2015561
css.properties.flex-grow πŸ“‹Firefox4/2/2013 Safari9/30/2015911
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.
css.properties.flex-shrink πŸ“‹Firefox4/2/2013 Safari9/30/2015911
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox: Before Firefox 32, Firefox wasn't able to animate values starting or stopping at 0.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Firefox for Android: Before Firefox for Android 32, Firefox for Android wasn't able to animate values starting or stopping at 0.Internet Explorer: Internet Explorer 10 uses 0 instead of 1 as the initial value for the flex-shrink property. A workaround is to always set an explicit value for flex-shrink. See Flexbug #6 for more info.
css.properties.flex-wrap πŸ“‹Firefox3/18/2014 Safari9/30/2015561
Internet Explorer: Partial support due to large number of bugs present. See Flexbugs.
css.properties.justify-content πŸ“‹Firefox4/2/2013 Safari9/30/2015911
css.properties.justify-items πŸ“‹Firefox4/2/2013 Safari9/30/2015911
css.properties.justify-items.flex_context πŸ“‹Firefox4/2/2013 Safari9/30/2015911
css.properties.order πŸ“‹Firefox4/2/2013 Safari9/30/2015911
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.
css.properties.perspective πŸ“‹Firefox10/9/2012 Safari9/30/20151086
Firefox: From version 147, Firefox supports -webkit-perspective with unitless values for increased compatibility.Firefox for Android: From version 147, Firefox for Android supports -webkit-perspective with unitless values for increased compatibility.Safari on iOS: In iOS 13, the perspective property did not function properly. The issues were fixed in iOS 14.WebView on iOS: In iOS 13, the perspective property did not function properly. The issues were fixed in iOS 14.
css.properties.perspective-origin πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.quotes πŸ“‹Firefox11/29/2005 Safari9/30/20153592
css.properties.quotes.none πŸ“‹Firefox11/29/2005 Safari9/30/20153592
css.properties.transform πŸ“‹Firefox10/9/2012 Safari9/30/20151086
Internet Explorer: Internet Explorer does not support the global values initial and unset.Internet Explorer: Internet Explorer 5.5 or later supports a proprietary Matrix Filter which can be used to achieve a similar effect.WebView Android: Android 2.3 has a bug where input forms will "jump" when typing, if any container element has a -webkit-transform.
css.properties.transform-origin πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.transform-style πŸ“‹Firefox10/9/2012 Safari9/30/20151086
Safari: Before Safari 17, ::before and ::after pseudo elements were not included in the 3D rendering context (see bug 256430).
css.properties.transition πŸ“‹Firefox10/9/2012 Safari9/30/20151086
Firefox: Before Firefox 57, transitions do not work when transitioning from a text-shadow with a color specified to a text-shadow without a color specified (see bug 726550).Firefox: Before Firefox 57, cancelling a filling animation (for example, with animation-fill-mode: forwards set) can trigger a transition set on the same element, although only once (see bug 1192592 and these test cases for more information).Firefox: Before Firefox 57, the background-position property can't be transitioned between two values containing different numbers of <position> values, for example background-position: 10px 10px; and background-position: 20px 20px, 30px 30px; (see bug 1390446).Firefox for Android: Before Firefox for Android 57, transitions do not work when transitioning from a text-shadow with a color specified to a text-shadow without a color specified (see bug 726550).Firefox for Android: Before Firefox for Android 57, cancelling a filling animation (for example, with animation-fill-mode: forwards set) can trigger a transition set on the same element, although only once (see bug 1192592 and these test cases for more information).Firefox for Android: Before Firefox for Android 57, the background-position property can't be transitioned between two values containing different numbers of <position> values, for example background-position: 10px 10px; and background-position: 20px 20px, 30px 30px; (see bug 1390446).
css.properties.transition-delay πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.transition-duration πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.transition-property πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.transition-timing-function πŸ“‹Firefox10/9/2012 Safari9/30/20151086
css.properties.word-break.keep-all πŸ“‹Firefox8/28/2012 Safari9/30/20151128
css.types.color.named-color.rebeccapurple Firefox10/14/2014 Safari9/30/2015351

2015/7

API First Browser Date Last Browser Date Days Notes
css.at-rules.charset πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Firefox: Firefox 1 supported an invalid syntax where the character encoding is not between single or double quotes.Internet Explorer: From Internet Explorer 5.5 to IE 7 (inclusive), Internet Explorer supported an invalid syntax where the character encoding is not between single or double quotes.
css.at-rules.font-face πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.WOFF πŸ“‹Firefox6/30/2009 Edge7/29/20152220
css.at-rules.font-face.font-family πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.font-style πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.font-variant Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.font-weight πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.src πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.unicode-range πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.at-rules.import πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.at-rules.media πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.at-rules.media.aspect-ratio πŸ“‹Firefox6/30/2009 Edge7/29/20152220
css.at-rules.media.color πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.device-aspect-ratio πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.device-height πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.device-width πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.grid πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.height πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.media_features Firefox11/9/2004 Edge7/29/20153914
css.at-rules.media.nested-queries Firefox3/13/2012 Edge7/29/20151233
css.at-rules.media.orientation πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.width πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.at-rules.namespace πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.align-items.flex_context πŸ“‹Firefox4/2/2013 Edge7/29/2015848
Chrome: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome implements the new behavior beginning with Chrome 52.Chrome Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome Android implements the new behavior beginning with Chrome Android 52.Firefox: Multi-line flexbox has been supported since Firefox 28.Firefox for Android: Multi-line flexbox has been supported since Firefox for Android 28.Internet Explorer: In Internet Explorer 10 and 11, if column flex items have align-items: center; set on them and their content is too large, then they will overflow the bounds of their container. See Flexbug #2.Opera: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Opera implements the new behavior beginning with Opera 39.Opera Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Opera Android implements the new behavior beginning with Opera Android 41.Samsung Internet: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Samsung Internet implements the new behavior beginning with Samsung Internet 6.0.WebView Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. WebView Android implements the new behavior beginning with WebView Android 52.
css.properties.align-self.flex_context πŸ“‹Firefox4/2/2013 Edge7/29/2015848
Chrome: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome implements the new behavior beginning with Chrome 52.Chrome Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome Android implements the new behavior beginning with Chrome Android 52.Firefox: Before Firefox 27, only single-line flexbox is supported.Firefox for Android: Before Firefox for Android 27, only single-line flexbox is supported.Samsung Internet: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Samsung Internet implements the new behavior beginning with Samsung Internet 6.0.WebView Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. WebView Android implements the new behavior beginning with WebView Android 52.
css.properties.animation.alternate πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.alternate-reverse πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.auto πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.backwards πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.both πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.ease πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.ease-in πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.ease-in-out πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.ease-out πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.forwards πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.infinite πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.linear πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.none πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.normal πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.reverse πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.step-end πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation.step-start πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-direction.alternate πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-direction.alternate-reverse πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.animation-direction.normal πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-direction.reverse πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.animation-fill-mode.backwards πŸ“‹Safari6/7/2010 Edge7/29/20151878
css.properties.animation-fill-mode.both πŸ“‹Safari6/7/2010 Edge7/29/20151878
css.properties.animation-fill-mode.forwards πŸ“‹Safari6/7/2010 Edge7/29/20151878
css.properties.animation-fill-mode.none πŸ“‹Safari6/7/2010 Edge7/29/20151878
css.properties.animation-iteration-count.infinite πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-name.none πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-play-state.paused πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-play-state.running πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.ease πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.ease-in πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.ease-in-out πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.ease-out πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.linear πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.step-end πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.step-start πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.appearance.button πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.checkbox πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.listbox πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.menulist πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.meter πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.progress-bar πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.radio πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.searchfield πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.textarea πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.textfield πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.backface-visibility.hidden πŸ“‹Safari7/20/2011 Edge7/29/20151470
css.properties.backface-visibility.visible πŸ“‹Safari7/20/2011 Edge7/29/20151470
css.properties.background πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.SVG_image_as_background Safari3/18/2008 Edge7/29/20152689
css.properties.background.background-clip Safari7/20/2011 Edge7/29/20151470
css.properties.background.background-origin Safari7/20/2011 Edge7/29/20151470
css.properties.background.background-size Safari7/20/2011 Edge7/29/20151470
css.properties.background.local πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.multiple_backgrounds Safari4/15/2005 Edge7/29/20153757
css.properties.background.no-repeat πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.repeat πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.repeat-x πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.repeat-y πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.round πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.scroll πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.space πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-attachment πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-attachment.multiple_backgrounds Safari4/15/2005 Edge7/29/20153757
css.properties.background-attachment.scroll πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-clip πŸ“‹Safari6/7/2010 Edge7/29/20151878
Chrome: Chrome accepts alternate synonyms to its values: padding, border, and content.Chrome Android: Chrome Android accepts alternate synonyms to its values: padding, border, and content.Edge: Since Edge 79, accepts alternate synonyms to its values: padding, border, and content.Firefox: Used the -moz-background-clip: padding | border syntax.Internet Explorer: In IE 7 and IE 8 of Internet Explorer, this property always behaved like background-clip: padding-box when overflow was hidden, auto, or scroll.Quest Browser: Quest Browser accepts alternate synonyms to its values: padding, border, and content.Opera: Opera accepts alternate synonyms to its values: padding, border, and content.Opera Android: Opera accepts alternate synonyms to its values: padding, border, and content.Safari: Safari accepts alternate synonyms to its values: padding, border, and content.Safari on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.Samsung Internet: Samsung Internet accepts alternate synonyms to its values: padding, border, and content.WebView Android: WebView Android accepts alternate synonyms to its values: padding, border, and content.WebView on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.
css.properties.background-clip.border-box πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.background-clip.content-box πŸ“‹Safari10/26/2007 Edge7/29/20152833
Internet Explorer: In IE 7 and IE 9 of Internet Explorer, it always behaved like background-clip: padding-box if overflow: hidden | auto | scroll
css.properties.background-clip.padding-box πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.background-color πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: In Internet Explorer 8 and 9, there is a bug where a computed background-color of transparent causes click events to not get fired on overlaid elements.
css.properties.background-color.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-image πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: If the browser.display.use_document_colors user preference in about:config is set to false, background images will not be displayed.Firefox for Android: If the browser.display.use_document_colors user preference in about:config is set to false, background images will not be displayed.
css.properties.background-image.gradients πŸ“‹Safari6/8/2009 Edge7/29/20152242
Chrome: Some versions support only experimental gradients prefixed with -webkit.Chrome Android: Some versions support only experimental gradients prefixed with -webkit.Firefox: Some versions support only experimental gradients prefixed with -moz.Firefox for Android: Some versions support only experimental gradients prefixed with -moz.Quest Browser: Some versions support only experimental gradients prefixed with -webkit.Opera: Some versions support only experimental gradients prefixed with -o.Opera Android: Some versions support only experimental gradients prefixed with -webkit.Safari: Some versions support only experimental gradients prefixed with -webkit.Safari on iOS: Some versions support only experimental gradients prefixed with -webkit.Samsung Internet: Some versions support only experimental gradients prefixed with -webkit.WebView Android: Some versions support only experimental gradients prefixed with -webkit.WebView on iOS: Some versions support only experimental gradients prefixed with -webkit.
css.properties.background-image.multiple_backgrounds Safari4/15/2005 Edge7/29/20153757
css.properties.background-image.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-image.svg_images Safari6/7/2010 Edge7/29/20151878
Safari: Support of SVG in CSS background is incomplete.Safari on iOS: Support of SVG in CSS background is incomplete.WebView on iOS: Support of SVG in CSS background is incomplete.
css.properties.background-origin πŸ“‹Safari10/26/2007 Edge7/29/20152833
Chrome: Chrome accepts alternate synonyms to its values: padding, border, and content.Chrome Android: Chrome Android accepts alternate synonyms to its values: padding, border, and content.Edge: Since Edge 79, accepts alternate synonyms to its values: padding, border, and content.Firefox: Used the -moz-background-clip: padding | border syntax.Internet Explorer: In IE 7 and before, Internet explorer was behaving as if background-origin: border-box was set. In Internet Explorer 8, as if background-origin: padding-box, the regular default value, was set.Quest Browser: Quest Browser accepts alternate synonyms to its values: padding, border, and content.Opera: Opera accepts alternate synonyms to its values: padding, border, and content.Opera Android: Opera accepts alternate synonyms to its values: padding, border, and content.Safari: Webkit accepts alternate synonyms to its values: padding, border, and content.Safari on iOS: Webkit accepts alternate synonyms to its values: padding, border, and content.Samsung Internet: Samsung Internet accepts alternate synonyms to its values: padding, border, and content.WebView Android: WebView accepts alternate synonyms to its values: padding, border, and content.WebView on iOS: Webkit accepts alternate synonyms to its values: padding, border, and content.
css.properties.background-origin.border-box πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.background-origin.content-box πŸ“‹Safari10/26/2007 Edge7/29/20152833
Internet Explorer: In IE 7 and IE 9 of Internet Explorer, it always behaved like background-clip: padding if overflow: hidden | auto | scroll.
css.properties.background-origin.padding-box πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.background-position πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-position.multiple_backgrounds Safari4/15/2005 Edge7/29/20153757
css.properties.background-position.side-relative_values Firefox6/5/2012 Edge7/29/20151149
css.properties.background-repeat πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.2-value Safari6/7/2010 Edge7/29/20151878
css.properties.background-repeat.multiple_backgrounds Safari4/15/2005 Edge7/29/20153757
css.properties.background-repeat.no-repeat πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.repeat πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.repeat-x πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.repeat-y πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.background-size πŸ“‹Safari6/7/2010 Edge7/29/20151878
Chrome: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Chrome Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Quest Browser: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Opera Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera Android: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Safari: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Safari on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Samsung Internet: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.
css.properties.background-size.auto πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.background-size.contain πŸ“‹Firefox1/21/2010 Edge7/29/20152015
css.properties.background-size.cover πŸ“‹Firefox1/21/2010 Edge7/29/20152015
css.properties.border πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-color πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-color.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-left-radius πŸ“‹Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-left-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-bottom-left-radius.percentages Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-right-radius πŸ“‹Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-right-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-bottom-right-radius.percentages Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-style πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-style.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-width πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-width.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-width.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-width.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-collapse πŸ“‹Safari10/24/2003 Edge7/29/20154296
css.properties.border-color πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-color.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-image πŸ“‹Safari7/25/2012 Edge7/29/20151099
Chrome: Before Chrome 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Chrome Android: Before Chrome Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Edge: Before Edge 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Firefox: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox: Until Firefox 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox: From Firefox 48 until Firefox 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox: Until Firefox 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox: Before Firefox 15, an earlier version of the specification was implemented, prefixed.Firefox for Android: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox for Android: Until Firefox for Android 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox for Android: From Firefox for Android 48 until Firefox for Android 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox for Android: Until Firefox for Android 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox for Android: Before Firefox for Android 15, an earlier version of the specification was implemented, prefixed.Quest Browser: Before Quest Browser false, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera: Before Opera 98, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera Android: A border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Samsung Internet: Before Samsung Internet 23.0, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).WebView Android: Before WebView 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).
css.properties.border-image.fill Safari7/25/2012 Edge7/29/20151099
css.properties.border-image.gradient Safari6/8/2009 Edge7/29/20152242
css.properties.border-image.none πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.border-image.optional_border_image_slice Safari7/25/2012 Edge7/29/20151099
css.properties.border-image.repeat πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.border-image.round πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.border-image.space πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.border-image.stretch πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.border-image-outset πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-repeat πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-repeat.repeat πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-repeat.stretch πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-slice πŸ“‹Safari7/25/2012 Edge7/29/20151099
Firefox: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox: Until Firefox 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox: From Firefox 48 until Firefox 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox: Until Firefox 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox for Android: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox for Android: Until Firefox for Android 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox for Android: From Firefox for Android 48 until Firefox for Android 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox for Android: Until Firefox for Android 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).
css.properties.border-image-source πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-source.none πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-width πŸ“‹Firefox6/5/2012 Edge7/29/20151149
Chrome: Before Chrome 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Chrome Android: Before Chrome Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Edge: Before Edge 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Quest Browser: Before Quest Browser false, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera: Before Opera 98, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera Android: Before Opera Android 75, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Samsung Internet: Before Samsung Internet 23.0, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).WebView Android: Before WebView Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).
css.properties.border-image-width.auto πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.border-left πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-color πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-color.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.
css.properties.border-left-style.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-width πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-width.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-width.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-width.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-radius πŸ“‹Safari6/7/2010 Edge7/29/20151878
Chrome: Chrome ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox: To conform to the CSS3 standard, Firefox 4 changes the handling of <percentage> values to match the specification. You can specify an ellipse as a border on an arbitrary sized element with border-radius: 50%;. Firefox 4 also makes rounded corners clip content and images if overflow: visible is not set.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-style was solid. This has been fixed in Firefox 50.Opera: Before Opera 11.60, replaced elements with border-radius do not have rounded corners.Safari: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.Safari on iOS: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.WebView on iOS: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.
css.properties.border-radius.4_values_for_4_corners Safari6/7/2010 Edge7/29/20151878
css.properties.border-radius.elliptical_borders Safari10/26/2007 Edge7/29/20152833
Chrome: Before Chrome 4, the slash / notation is unsupported. If two values are specified, then an elliptical border is drawn on all four corners. -webkit-border-radius: 40px 10px; is equivalent to border-radius: 40px / 10px;.Safari: Before Safari 5, the slash / notation is unsupported. If two values are specified, then an elliptical border is drawn on all four corners. -webkit-border-radius: 40px 10px; is equivalent to border-radius: 40px / 10px;.
css.properties.border-radius.percentages Firefox3/22/2011 Edge7/29/20151590
Firefox: Before Firefox 4, <percentage> values are implemented in a non-standard way. Both horizontal and vertical radii were relative to the width of the border box.Opera: Before Opera 11.5, the implementation of <percentage> values was buggy.
css.properties.border-right πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-color πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-color.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.
css.properties.border-right-style.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-width πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-width.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-width.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-width.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-spacing πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-style.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-color πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-color.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-left-radius πŸ“‹Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-left-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-top-left-radius.percentages Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-right-radius πŸ“‹Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-right-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-top-right-radius.percentages Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-style πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-top-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners (with border-radius) were always rendered as if border-top-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-style.dashed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.dotted πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.double πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.groove πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.inset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.outset πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.ridge πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.solid πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-width πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-width.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-width.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-width.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-width πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-width.medium πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-width.thick πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.border-width.thin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.bottom πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: In Internet Explorer versions before 7, when both top and bottom are specified, the element position is overconstrained and the top property has precedence; the computed value of bottom is set to -top, while its specified value is ignored.
css.properties.bottom.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.box-shadow πŸ“‹Firefox3/22/2011 Edge7/29/20151590
Chrome: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Chrome Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Firefox: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Firefox for Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Internet Explorer: To use box-shadow in Internet Explorer 9 or later, you must set border-collapse to separate.Internet Explorer: Since version 5.5, Internet Explorer supports Microsoft's DropShadow and Shadow Filter. You can use this proprietary extension to cast a drop shadow (though the syntax and the effect are different from CSS3)Quest Browser: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Opera: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Opera Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Safari: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Safari on iOS: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Samsung Internet: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.WebView Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.WebView on iOS: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.
css.properties.box-shadow.inset Firefox6/30/2009 Edge7/29/20152220
Internet Explorer: inset must be the last keyword in the declaration.
css.properties.box-shadow.multiple_shadows Safari10/26/2007 Edge7/29/20152833
css.properties.box-shadow.none πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.box-shadow.spread_radius Firefox6/30/2009 Edge7/29/20152220
css.properties.box-sizing πŸ“‹Safari7/20/2011 Edge7/29/20151470
Chrome: box-sizing is not respected when the height is calculated from window.getComputedStyle().Chrome Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox: Before Firefox 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox for Android: Before Firefox for Android 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Internet Explorer: box-sizing is not respected when the height is calculated from window.getComputedStyle().Quest Browser: box-sizing is not respected when the height is calculated from window.getComputedStyle().Opera Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Samsung Internet: box-sizing is not respected when the height is calculated from window.getComputedStyle().WebView Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().
css.properties.box-sizing.border-box πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.box-sizing.content-box πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.caption-side πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.clear πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.clear.both πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.clear.left πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.clear.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.clear.right πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.clip πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Before Internet Explorer 7, Internet Explorer incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).Safari: Safari incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).Safari on iOS: Safari on iOS incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).WebView on iOS: WebView on iOS incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).
css.properties.color πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.color.transparent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.column-count.auto πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.column-fill.auto πŸ“‹Firefox11/20/2012 Edge7/29/2015981
css.properties.column-fill.balance πŸ“‹Firefox11/20/2012 Edge7/29/2015981
css.properties.column-gap πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.column-gap.normal πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.column-rule.dashed πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.dotted πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.double πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.groove πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.hidden πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.inset πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.medium πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.none πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.outset πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.ridge πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.solid πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.thick πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.thin πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.transparent πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-color.transparent πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.dashed πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.dotted πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.double πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.groove πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.hidden πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.inset πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.none πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.outset πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.ridge πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.solid πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-width.medium πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-width.thick πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-width.thin πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.column-width.auto Firefox11/29/2005 Edge7/29/20153529
css.properties.columns.auto πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.content πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.content.close-quote πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.content.no-close-quote πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.content.no-open-quote πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.content.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.content.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.content.open-quote πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.content.url πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.counter-increment πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.counter-increment.none πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.counter-reset πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.counter-reset.none πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.cursor πŸ“‹Safari2/2/2004 Edge7/29/20154195
Firefox: Starting in Firefox 67, the maximum size allowed for custom cursors is 32x32 pixels due to cursors being misused by certain malicious sites.Internet Explorer: In Internet Explorer 11, when cursor is applied to an element and this element is underneath an open <select> menu and the user hovers over a <select> menu item that's on top of said element, the cursor for said element will be displayed rather than the <select>'s normal cursor. See bug 817822.Safari on iOS: This property is only supported on iPads with an external pointing device.Safari on iOS: Unsupported values use the default pointer as a fallback.WebView on iOS: This property is only supported on iPads with an external pointing device.WebView on iOS: Unsupported values use the default pointer as a fallback.
css.properties.cursor.alias πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.all-scroll πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.auto πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.cursor.cell πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.cursor.col-resize πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.context-menu πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Chrome: This cursor is only supported on macOS and Linux.Chrome Android: This cursor is only supported on macOS and Linux.Firefox: This cursor is only supported on macOS and Linux.Quest Browser: This cursor is only supported on macOS and Linux.Opera Android: This cursor is only supported on macOS and Linux.Safari on iOS: If this value is used, the iPad will display the default pointer instead.Samsung Internet: This cursor is only supported on macOS and Linux.WebView Android: This cursor is only supported on macOS and Linux.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.copy πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.crosshair πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.default πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.e-resize πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ew-resize πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.help πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.move πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.n-resize πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ne-resize πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nesw-resize πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.no-drop πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.none πŸ“‹Firefox6/17/2008 Edge7/29/20152598
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.not-allowed πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ns-resize πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nw-resize πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nwse-resize πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.pointer πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.progress πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.row-resize πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.s-resize πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.se-resize πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.sw-resize πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.text πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.cursor.url Firefox11/29/2005 Edge7/29/20153529
Firefox: Firefox 4 added macOS support.
css.properties.cursor.vertical-text πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.w-resize πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.wait πŸ“‹Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.direction πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.direction.ltr πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.direction.rtl πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.display πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.display.block πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.display.inline πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.display.inline-block Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Until Internet Explorer 8, inline-block is only for natural inline elements.
css.properties.display.inline-table Safari6/23/2003 Edge7/29/20154419
css.properties.display.list-item πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.display.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
Chrome: Chrome 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.Chrome Android: Chrome Android 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.Quest Browser: Quest Browser 5.0 stopped creating layout objects for elements inside an <iframe> with display:none applied.Opera: Opera 52 stopped creating layout objects for elements inside an <iframe> with display:none applied.Opera Android: Opera Android 47 stopped creating layout objects for elements inside an <iframe> with display:none applied.Samsung Internet: Chrome 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.WebView Android: WebView Android 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.
css.properties.display.table Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-cell Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-column Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-column-group Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-footer-group Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-header-group Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-row Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-row-group Safari6/23/2003 Edge7/29/20154419
css.properties.empty-cells πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.empty-cells.hide πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.empty-cells.show πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.filter.blur πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.brightness πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.contrast πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.drop-shadow πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.grayscale πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.hue-rotate πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.invert πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.none πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.opacity πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.filter.saturate πŸ“‹Safari7/25/2012 Edge7/29/20151099
Chrome: In Chrome 18 to 19, the saturate() function only takes integers instead of decimal or percentage values. From Chrome 20, this bug is fixed.
css.properties.filter.sepia πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.properties.flex.auto πŸ“‹Firefox6/25/2013 Edge7/29/2015764
css.properties.flex.none πŸ“‹Firefox6/25/2013 Edge7/29/2015764
css.properties.flex-direction.column πŸ“‹Firefox6/25/2013 Edge7/29/2015764
css.properties.flex-direction.row πŸ“‹Firefox6/25/2013 Edge7/29/2015764
css.properties.flex-flow.column πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.column-reverse πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.nowrap πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.row πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.row-reverse πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.wrap πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.wrap-reverse πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-wrap.nowrap πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-wrap.wrap πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.flex-wrap.wrap-reverse πŸ“‹Safari10/22/2013 Edge7/29/2015645
css.properties.float πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.float.left πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.float.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.float.right πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.flood-color πŸ“‹Firefox6/17/2008 Edge7/29/20152598
css.properties.flood-color.currentColor πŸ“‹Firefox6/17/2008 Edge7/29/20152598
css.properties.flood-color.transparent πŸ“‹Firefox6/17/2008 Edge7/29/20152598
css.properties.flood-opacity πŸ“‹Firefox6/17/2008 Edge7/29/20152598
css.properties.font πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font.caption Safari6/23/2003 Edge7/29/20154419
css.properties.font.icon Safari6/23/2003 Edge7/29/20154419
css.properties.font.menu Safari6/23/2003 Edge7/29/20154419
css.properties.font.message-box Safari6/23/2003 Edge7/29/20154419
css.properties.font.small-caption Safari6/23/2003 Edge7/29/20154419
css.properties.font.status-bar Safari6/23/2003 Edge7/29/20154419
css.properties.font-family πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Not supported on option elements. See bug 1536148.Safari: Setting font-family: initial behaves like font-family: inherit. See bug 200709.Safari on iOS: Setting font-family: initial behaves like font-family: inherit. See bug 200709.WebView on iOS: Setting font-family: initial behaves like font-family: inherit. See bug 200709.
css.properties.font-family.cursive πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.fangsong πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.fantasy πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.kai πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.khmer-mul πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.monospace πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.nastaliq πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.sans-serif πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.serif πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-size πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-size.rem_values Safari10/22/2013 Edge7/29/2015645
Firefox: Before Firefox 57, animations using em units are not affected by changes to the font-size of the animated element's parent (bug 1254424).Firefox: Before Firefox 57, some language settings' inherited font-size is smaller than expected (bug 1391341).
css.properties.font-style πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 44, oblique was not distinguished from italic.Firefox for Android: Before Firefox for Android 44, oblique was not distinguished from italic.
css.properties.font-style.italic πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-style.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-style.oblique πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-variant πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Only supports the small-caps and normal keywords.
css.properties.font-variant.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-variant.turkic_is Firefox7/17/2012 Edge7/29/20151107
css.properties.font-weight πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.bold πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.bolder πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.lighter πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.height πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.height.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.hyphens.language_english Safari7/20/2011 Edge7/29/20151470
Firefox: For English, Firefox uses an en-US dictionaryFirefox for Android: For English, Firefox for Android uses an en-US dictionarySafari: For English, Safari uses different en-GB and en-US dictionaries.Safari on iOS: For English, Safari on iOS uses different en-GB and en-US dictionaries.WebView on iOS: For English, WebView on iOS uses different en-GB and en-US dictionaries.
css.properties.justify-content.flex_context πŸ“‹Firefox4/2/2013 Edge7/29/2015848
Chrome: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome implements the new behavior beginning with Chrome 52.Chrome Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome Android implements the new behavior beginning with Chrome Android 52.Firefox: Before Firefox 27, Firefox supported only single-line flexbox.Firefox for Android: Before Firefox for Android 27, Firefox for Android supported only single-line flexbox.Samsung Internet: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Samsung Internet implements the new behavior beginning with Samsung Internet 6.0.WebView Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. WebView Android implements the new behavior beginning with WebView Android 52.
css.properties.left πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.left.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.letter-spacing πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.letter-spacing.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.lighting-color πŸ“‹Firefox6/17/2008 Edge7/29/20152598
css.properties.lighting-color.currentColor πŸ“‹Firefox6/17/2008 Edge7/29/20152598
css.properties.lighting-color.transparent πŸ“‹Firefox6/17/2008 Edge7/29/20152598
css.properties.line-height πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.line-height.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style.inside πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style.outside πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-image πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 86, this property did not accept an <image> type, and required the URL of an image.Firefox for Android: Before Firefox for Android 86, this property did not accept an <image> type, and required the URL of an image.
css.properties.list-style-image.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-position πŸ“‹Safari6/23/2003 Edge7/29/20154419
Safari: In Safari, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.Safari on iOS: In Safari on iOS, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.WebView on iOS: In WebView on iOS, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.
css.properties.list-style-position.inside πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-position.outside πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.armenian πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.circle πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.decimal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.decimal-leading-zero πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.disc πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.georgian πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.hebrew πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.hiragana πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.hiragana-iroha πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.katakana πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.katakana-iroha πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.lower-alpha πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.lower-greek πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.lower-latin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.lower-roman πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.square πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.upper-alpha πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.upper-latin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.upper-roman πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.margin πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.margin.auto Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-bottom πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.margin-bottom.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-left πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.margin-left.auto Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-right πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.margin-right.auto Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-top πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.margin-top.auto Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.max-height πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: CSS 2.1 leaves the behavior of max-height with table undefined. Firefox supports applying max-height to table elements.Opera: CSS 2.1 leaves the behavior of max-height with table undefined. Opera supports applying max-height to table elements.
css.properties.max-height.none πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.max-width πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: CSS 2.1 leaves the behavior of max-width with table undefined. Firefox supports applying max-width to table elements.Firefox for Android: CSS 2.1 leaves the behavior of max-width with table undefined. Firefox for Android supports applying max-width to table elements.Opera: CSS 2.1 leaves the behavior of max-width with table undefined. Opera supports applying max-width to table elements.
css.properties.max-width.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.min-height πŸ“‹Safari4/15/2005 Edge7/29/20153757
Firefox: CSS 2.1 leaves the behavior of min-height with table undefined. Firefox supports applying min-height to table elements.Firefox for Android: CSS 2.1 leaves the behavior of min-height with table undefined. Firefox for Android supports applying min-height to table elements.Internet Explorer: In Internet Explorer 10 and 11, a min-height declaration on a column-direction flex container doesn't apply to the container's flex items. See Flexbug #3 for more info.Opera: CSS 2.1 leaves the behavior of min-height with table undefined. Opera supports applying min-height to table elements.
css.properties.min-height.auto Safari10/22/2013 Edge7/29/2015645
Firefox: Firefox 18 and later used auto as the initial value for min-height.Firefox for Android: Firefox for Android 18 and later used auto as the initial value for min-height.
css.properties.min-width πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: CSS 2.1 leaves the behavior of min-width with table undefined. Firefox supports applying min-width to table elements.Firefox for Android: CSS 2.1 leaves the behavior of min-width with table undefined. Firefox for Android supports applying min-width to table elements.Opera: CSS 2.1 leaves the behavior of min-width with table undefined. Opera supports applying min-width to table elements.
css.properties.min-width.auto Safari10/22/2013 Edge7/29/2015645
Chrome: Chrome uses auto as the initial value for min-width.Chrome Android: Chrome Android uses auto as the initial value for min-width.Edge: Edge uses auto as the initial value for min-width.Firefox: Firefox 18 and later (until the value was removed), used auto as the initial value for min-width.Firefox for Android: Firefox for Android 18 and later (until the value was removed), used auto as the initial value for min-width.Quest Browser: Quest Browser uses auto as the initial value for min-width.Opera: Opera uses auto as the initial value for min-width.Opera Android: Opera Android uses auto as the initial value for min-width.Samsung Internet: Samsung Internet uses auto as the initial value for min-width.WebView Android: WebView Android uses auto as the initial value for min-width.
css.properties.opacity πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.outline.currentColor πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.dashed πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.dotted πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.double πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.groove πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.inset πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.medium πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.none πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.outset πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.ridge πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.solid πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.thick πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.thin πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline.transparent πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-color πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-color.transparent πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style πŸ“‹Safari2/2/2004 Edge7/29/20154195
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.outline-style.auto πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.dashed πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.dotted πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.double πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.groove πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.inset πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.none πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.outset πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.ridge πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.solid πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-width πŸ“‹Safari2/2/2004 Edge7/29/20154195
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.outline-width.medium πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-width.thick πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.outline-width.thin πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.overflow πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: After Firefox 3.6, the overflow property is correctly applied to table group elements (<thead>, <tbody>, <tfoot>).Internet Explorer: From version 4 to 6, Internet Explorer enlarges an element with overflow: visible (default value) to fit the content inside it. height and width behave like min-height and min-width, respectively.
css.properties.overflow.auto πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.overflow.hidden πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.overflow.scroll πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.overflow.visible πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.overflow-wrap.break-word πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.overflow-wrap.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.overflow-x πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-x.auto πŸ“‹Safari10/26/2007 Edge7/29/20152833
Safari: Before Safari 12.1, overlay only had an effect on legacy scrollbars on macOS. Since Safari 12.1, it is parsed as auto.Safari on iOS: Before Safari on iOS 12.1, overlay only had an effect on legacy scrollbars on macOS. Since Safari on iOS 12.1, it is parsed as auto.WebView on iOS: Before WebView on iOS 12.1, overlay only had an effect on legacy scrollbars on macOS. Since WebView on iOS 12.1, it is parsed as auto.
css.properties.overflow-x.hidden πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-x.scroll πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-x.visible πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-y πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-y.auto πŸ“‹Safari10/26/2007 Edge7/29/20152833
Safari: Before Safari 12.1, overlay only had an effect on legacy scrollbars on macOS. Since Safari 12.1, it is parsed as auto.Safari on iOS: Before Safari on iOS 12.1, overlay only had an effect on legacy scrollbars on macOS. Since Safari on iOS 12.1, it is parsed as auto.WebView on iOS: Before WebView on iOS 12.1, overlay only had an effect on legacy scrollbars on macOS. Since WebView on iOS 12.1, it is parsed as auto.
css.properties.overflow-y.hidden πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-y.scroll πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-y.visible πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.padding πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.padding-bottom πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.padding-left πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.padding-right πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.padding-top πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.page-break-after πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-after.always πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-after.auto πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-after.left πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-after.right πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before.always πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before.auto πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before.left πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before.right πŸ“‹Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-inside πŸ“‹Safari4/15/2005 Edge7/29/20153757
css.properties.page-break-inside.auto πŸ“‹Safari4/15/2005 Edge7/29/20153757
css.properties.page-break-inside.avoid πŸ“‹Safari4/15/2005 Edge7/29/20153757
Firefox: Until Firefox 25, page-break-inside: avoid did not work with the height of a block.Firefox for Android: Until Firefox for Android 25, page-break-inside: avoid did not work with the height of a block.
css.properties.perspective.none πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.bottom πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.center πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.left πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.right πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.top πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.all πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.auto πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.fill πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.html_elements Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.none πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.painted πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.stroke πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.visible πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.properties.position πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.position.absolute πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 57, absolute positioning did not work correctly when applied to elements inside tables that have border-collapse applied to them (bug 1379306).Firefox: Before Firefox 30, absolute positioning of table rows and row groups was not supported (bug 63895).Firefox for Android: Before Firefox for Android 57, absolute positioning did not work correctly when applied to elements inside tables that have border-collapse applied to them (bug 1379306).Firefox for Android: Before Firefox for Android 30, absolute positioning of table rows and row groups was not supported (bug 63895).
css.properties.position.fixed πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 44, position: fixed didn't create a stacking context in most cases. Firefox and the specification have been modified to mimic Chrome and Safari's long-time behavior.Firefox for Android: Before Firefox for Android 44, position: fixed didn't create a stacking context in most cases. Firefox for Android and the specification have been modified to mimic Chrome and Safari's long-time behavior.Internet Explorer: In Internet Explorer, fixed positioning doesn't work if the document is in quirks mode.
css.properties.position.relative πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.position.static πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.right πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.right.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.table-layout πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.table-layout.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.table-layout.fixed πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-align πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-align.justify πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.blink πŸ“‹Safari6/23/2003 Edge7/29/20154419
Chrome: The blink value does not have any effect.Chrome Android: The blink value does not have any effect.Firefox: The blink value does not have any effect.Firefox for Android: The blink value does not have any effect.Quest Browser: The blink value does not have any effect.Opera: The blink value does not have any effect.Opera Android: The blink value does not have any effect.Safari: The blink value does not have any effect.Safari on iOS: The blink value does not have any effect.Samsung Internet: The blink value does not have any effect.WebView Android: The blink value does not have any effect.WebView on iOS: The blink value does not have any effect.
css.properties.text-decoration.line-through πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.overline πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.underline πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-indent πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-overflow πŸ“‹Safari4/15/2005 Edge7/29/20153757
Firefox: Until Firefox 10, handling of text-overflow on blocks with inline overflow on both horizontal sides was incorrect. Before Firefox 10, if only one value was specified (such as text-overflow: ellipsis;), text was ellipsed on both sides of the block, instead of only the end edge based on the block's text direction.Firefox for Android: Until Firefox for Android 10, handling of text-overflow on blocks with inline overflow on both horizontal sides was incorrect. Before Firefox for Android 10, if only one value was specified (such as text-overflow: ellipsis;), text was ellipsed on both sides of the block, instead of only the end edge based on the block's text direction.
css.properties.text-overflow.clip πŸ“‹Safari4/15/2005 Edge7/29/20153757
css.properties.text-overflow.ellipsis πŸ“‹Safari4/15/2005 Edge7/29/20153757
css.properties.text-shadow πŸ“‹Safari10/24/2003 Edge7/29/20154296
Firefox: Firefox versions before 57 have a bug whereby transitions will not work when transitioning from a text-shadow with a color specified to a text-shadow without a color specified (bug 726550).Firefox: From Firefox 4, the blur radius is capped at 300 for performance reasons.Firefox: Firefox theoretically supports infinite text-shadows (don't try it).Firefox: If the <color> value is unspecified, then Firefox uses the value of the element's color property.Firefox for Android: Firefox for Android versions before 57 have a bug whereby transitions will not work when transitioning from a text-shadow with a color specified to a text-shadow without a color specified (bug 726550).Firefox for Android: From Firefox for Android 4, the blur radius is capped at 300 for performance reasons.Firefox for Android: Firefox for Android theoretically supports infinite text-shadows (don't try it).Firefox for Android: If the <color> value is unspecified, then Firefox for Android uses the value of the element's color property.Opera: Opera supports a maximum of 6-9 text-shadows for performance reasons. The blur radius is limited to 100px.Opera: Opera 9.5 to 10.1 adheres to the old, reverse painting order (in CSS2, the first specified shadow is on the bottom).Safari: In Safari, any shadows that do not explicitly specify a color are transparent.Safari: Safari 1.1 to 3.2 only supports one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari 4.0 (WebKit 528) and later support multiple text-shadows.Safari on iOS: In Safari, any shadows that do not explicitly specify a color are transparent.Safari on iOS: Safari iOS 1 and 2 only support one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari iOS 3 (WebKit 528) and later support multiple text-shadows.WebView on iOS: In Safari, any shadows that do not explicitly specify a color are transparent.WebView on iOS: Safari iOS 1 and 2 only support one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari iOS 3 (WebKit 528) and later support multiple text-shadows.
css.properties.text-shadow.none πŸ“‹Safari10/24/2003 Edge7/29/20154296
css.properties.text-transform πŸ“‹Safari6/23/2003 Edge7/29/20154419
Chrome: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Chrome Android: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Quest Browser: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Opera: Since Opera 15, the text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Safari: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.Samsung Internet: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.WebView Android: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.WebView on iOS: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.
css.properties.text-transform.capitalize πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 14, some punctuation characters could interfere with correct capitalization. See bug 731536.Firefox for Android: Before Firefox for Android 14, some punctuation characters could interfere with correct capitalization. See bug 731536.
css.properties.text-transform.lowercase πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-transform.lowercase_sigma Firefox7/17/2012 Edge7/29/20151107
css.properties.text-transform.none πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.text-transform.turkic_is Firefox7/17/2012 Edge7/29/20151107
css.properties.text-transform.uppercase πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.top πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: In Internet Explorer versions before 7, when both top and bottom are specified, the element position is overconstrained and the top property has precedence; the computed value of bottom is set to -top, while its specified value is ignored.
css.properties.top.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.transform.3d Safari6/8/2009 Edge7/29/20152242
css.properties.transform.none πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transform-origin.bottom πŸ“‹Safari4/29/2005 Edge7/29/20153743
css.properties.transform-origin.center πŸ“‹Safari4/29/2005 Edge7/29/20153743
css.properties.transform-origin.left πŸ“‹Safari4/29/2005 Edge7/29/20153743
css.properties.transform-origin.right πŸ“‹Safari4/29/2005 Edge7/29/20153743
css.properties.transform-origin.three_value_syntax Safari6/7/2010 Edge7/29/20151878
css.properties.transform-origin.top πŸ“‹Safari4/29/2005 Edge7/29/20153743
css.properties.transform-style.flat πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.transform-style.preserve-3d πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.properties.transition.all πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition.ease πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition.ease-in πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition.ease-in-out πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition.ease-out πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition.linear πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition.none πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition.step-end πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition.step-start πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-property.IDENT_value Safari6/8/2009 Edge7/29/20152242
css.properties.transition-property.all πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-property.none πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.ease πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.ease-in πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.ease-in-out πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.ease-out πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.linear πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.step-end πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.step-start πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.properties.unicode-bidi πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.unicode-bidi.bidi-override πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.unicode-bidi.embed πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.unicode-bidi.normal πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.properties.user-select.auto Firefox11/9/2004 Edge7/29/20153914
css.properties.user-select.none Safari4/29/2005 Edge7/29/20153743
css.properties.user-select.text Firefox11/9/2004 Edge7/29/20153914
css.properties.vertical-align πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.baseline πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.bottom πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.middle πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.sub πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.super πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.text-bottom πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.text-top πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.top πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.visibility πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Internet Explorer doesn't support visibility: initial.Internet Explorer: Internet Explorer doesn't support visibility: unset.Internet Explorer: Up to Internet Explorer 7, descendants of hidden elements will still be invisible even if they have visibility set to visible.
css.properties.visibility.collapse πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Chrome: Before Chrome 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome: Before Chrome 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome: Since Chrome 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Chrome Android: Before Chrome Android 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome Android: Before Chrome Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome Android: Since Chrome Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Edge: For Edge 79 through Edge 91, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Edge: Since Edge 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Firefox: Firefox doesn't hide borders when hiding <col> and <colgroup> elements if border-collapse: collapse is set.Firefox: Before Firefox 88, collapse is not supported on ruby annotations.Firefox for Android: Firefox for Android doesn't hide borders when hiding <col> and <colgroup> elements if border-collapse: collapse is set.Firefox for Android: Before Firefox for Android 88, collapse is not supported on ruby annotations.Quest Browser: Before Quest Browser 5.0, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Quest Browser: Before Quest Browser 17.0, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Quest Browser: Since Quest Browser 17.0, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Opera: Before Opera 49, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera: Before Opera 78, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera: Since Opera 78, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Opera Android: Before Opera Android 46, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera Android: Before Opera Android 65, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera Android: Since Opera Android 65, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Safari: Safari treats visibility: collapse like hidden, leaving a white gap.Safari: Safari supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.Safari on iOS: Safari on iOS treats visibility: collapse like hidden, leaving a white gap.Safari on iOS: Safari on iOS supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.Samsung Internet: Before Samsung Internet 8.0, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Samsung Internet: Before Samsung Internet 16.0, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Samsung Internet: Since Samsung Internet 16.0, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.WebView Android: Before WebView Android 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.WebView Android: Before WebView Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.WebView Android: Since WebView Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.WebView on iOS: WebView on iOS treats visibility: collapse like hidden, leaving a white gap.WebView on iOS: WebView on iOS supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.
css.properties.visibility.hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.visibility.visible πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.white-space πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.nowrap πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.pre πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.pre-line πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.white-space.pre-wrap πŸ“‹Safari10/26/2007 Edge7/29/20152833
Internet Explorer: From Internet Explorer 5.5 to 7, word-wrap: break-word; can be used for line breaks in pre elements.
css.properties.white-space.textarea_support Safari6/23/2003 Edge7/29/20154419
css.properties.width πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.width.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.width.is_animatable Firefox10/9/2012 Edge7/29/20151023
css.properties.word-break πŸ“‹Safari10/26/2007 Edge7/29/20152833
Internet Explorer: No version of Internet Explorer supports the initial value.Internet Explorer: Don't use -ms-word-break, which is a synonym for word-break.
css.properties.word-break.break-all πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.word-break.normal πŸ“‹Safari10/26/2007 Edge7/29/20152833
css.properties.word-spacing πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.word-spacing.normal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.z-index πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.z-index.auto πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.properties.z-index.negative_values Safari6/23/2003 Edge7/29/20154419
css.selectors.active πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.active.non_a_elements Safari6/23/2003 Edge7/29/20154419
Safari on iOS: By default, Safari on iOS does not use the :active state unless there is a touchstart event handler on the relevant element or on the <body> element.WebView on iOS: By default, WebView on iOS does not use the :active state unless there is a touchstart event handler on the relevant element or on the <body> element.
css.selectors.after πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Firefox: Before Firefox 57, Firefox had a bug where ::after pseudo-elements were still generated, even if the content property value were set to normal or none.Firefox: Before Firefox 3.5, only the CSS level 2 behavior of :after was supported, which disallowed position, float, list-style-* and some display properties.Firefox for Android: Before Firefox for Android 57, Firefox for Android had a bug where ::after pseudo-elements were still generated, even if the content property value were set to normal or none.Firefox for Android: Before Firefox for Android 4.5, only the CSS level 2 behavior of :after was supported, which disallowed position, float, list-style-* and some display properties.
css.selectors.after.animation_and_transition_support Firefox3/22/2011 Edge7/29/20151590
css.selectors.attribute πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.selectors.before πŸ“‹Firefox11/29/2005 Edge7/29/20153529
Firefox: Before Firefox 57, Firefox had a bug where ::before pseudo-elements were still generated, even if the content property value were set to normal or none.Firefox: Before Firefox 3.5, only the CSS level 2 behavior of :before was supported, which disallowed position, float, list-style-* and some display properties.Firefox for Android: Before Firefox 57, Firefox had a bug where ::before pseudo-elements were still generated, even if the content property value were set to normal or none.
css.selectors.before.animation_and_transition_support Firefox3/22/2011 Edge7/29/20151590
css.selectors.checked πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Chrome: On macOS, styling <option> elements has no effect.Edge: On macOS, styling <option> elements has no effect.Firefox: From Firefox 56, <option> elements cannot be styled.Firefox: On macOS, styling <option> elements has no effect.Firefox for Android: From Firefox 56, <option> elements cannot be styled.Opera: On macOS, styling <option> elements has no effect.Safari: Styling <option> elements has no effect.Safari on iOS: Styling <option> elements has no effect.WebView on iOS: Styling <option> elements has no effect.
css.selectors.child πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.class πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.descendant πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.disabled πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Edge: Before Edge 79, Edge did not recognize :disabled on the <fieldset> element.Internet Explorer: Internet Explorer does not recognize :disabled on the <fieldset> element.
css.selectors.empty πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.selectors.enabled πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.selectors.first-child πŸ“‹Safari3/18/2008 Edge7/29/20152689
Internet Explorer: Internet Explorer 7 doesn't update :first-child styles when elements are added dynamically.Internet Explorer: In Internet Explorer 8, if an element is inserted dynamically by clicking on a link, then the :first-child style isn't applied until the link loses focus.
css.selectors.first-letter πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.first-line πŸ“‹Safari6/23/2003 Edge7/29/20154419
Chrome: Before Chrome 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome: Before Chrome 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome Android: Before Chrome Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome Android: Before Chrome Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Quest Browser: Before Quest Browser 5.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Quest Browser: Before Quest Browser 5.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Opera: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera Android: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera Android: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Safari: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Samsung Internet: Before Samsung Internet 8.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Samsung Internet: Before Samsung Internet 8.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView Android: Before WebView Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView Android: Before WebView Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.WebView on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.
css.selectors.first-of-type πŸ“‹Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.focus πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.hover πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Safari on iOS: As of Safari for iOS 7.1.2, tapping a clickable element causes the element to enter the :hover state. The element will remain in the :hover state until a different element has entered the :hover state.WebView on iOS: As of Safari for iOS 7.1.2, tapping a clickable element causes the element to enter the :hover state. The element will remain in the :hover state until a different element has entered the :hover state.
css.selectors.hover.a_elements Firefox11/9/2004 Edge7/29/20153914
css.selectors.hover.all_elements Firefox11/9/2004 Edge7/29/20153914
Edge: In Edge, hovering over an element and then scrolling up or down without moving the pointer will leave the element in the :hover state until the pointer is moved.Internet Explorer: In Internet Explorer 8 to Internet Explorer 11, hovering over an element and then scrolling up or down without moving the pointer will leave the element in the :hover state until the pointer is moved. See bug 926665.Internet Explorer: In Internet Explorer 9 (and possibly earlier), if a <table> has a parent with a non-auto width, overflow-x: auto;, the <table> has enough content to horizontally overflow its parent, and there are :hover styles set on elements within the table, then hovering over said elements will cause the <table>'s height to increase. See a live demo that triggers the bug. One workaround for the bug is to set min-height: 0%; (the % unit must be specified, since unitless and px don't work) on the <table>'s parent element.
css.selectors.id πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.indeterminate πŸ“‹Firefox10/24/2006 Edge7/29/20153200
css.selectors.indeterminate.checkbox Safari10/26/2007 Edge7/29/20152833
css.selectors.indeterminate.progress Safari7/20/2011 Edge7/29/20151470
css.selectors.invalid πŸ“‹Safari6/7/2010 Edge7/29/20151878
css.selectors.lang πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.selectors.last-child πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.selectors.last-of-type πŸ“‹Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.link πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.list πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.namespace πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.selectors.next-sibling πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.Internet Explorer: Internet Explorer 7 doesn't update the style correctly when an element is dynamically placed before an element that matched the selector.Internet Explorer: In Internet Explorer 8, if an element is inserted dynamically by clicking on a link the first-child style isn't applied until the link loses focus.
css.selectors.not πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.selectors.nth-child πŸ“‹Safari3/18/2008 Edge7/29/20152689
Opera: Before Opera 15, Opera does not handle dynamically inserted elements for :nth-child().Opera Android: Before Opera 15, Opera does not handle dynamically inserted elements for :nth-child().
css.selectors.nth-last-child πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.selectors.nth-last-of-type πŸ“‹Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.nth-of-type πŸ“‹Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.only-child πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.selectors.only-of-type πŸ“‹Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.optional πŸ“‹Safari6/7/2010 Edge7/29/20151878
css.selectors.required πŸ“‹Safari6/7/2010 Edge7/29/20151878
css.selectors.root πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.subsequent-sibling πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.target πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.selectors.type πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.type.namespaces Firefox11/9/2004 Edge7/29/20153914
css.selectors.universal πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.universal.namespaces Firefox11/9/2004 Edge7/29/20153914
css.selectors.valid πŸ“‹Safari6/7/2010 Edge7/29/20151878
css.selectors.visited πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.selectors.visited.privacy_measures Safari6/7/2010 Edge7/29/20151878
css.types.angle πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.angle.deg Safari6/8/2009 Edge7/29/20152242
css.types.angle.grad Safari6/8/2009 Edge7/29/20152242
css.types.angle.rad Safari6/8/2009 Edge7/29/20152242
css.types.angle.turn Safari6/8/2009 Edge7/29/20152242
css.types.angle-percentage πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.attr πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.types.calc πŸ“‹Firefox10/9/2012 Edge7/29/20151023
Firefox: Before Firefox 59 calc() is not supported in rgb() and other color functions.Firefox: Before Firefox 57 calc(1*2*3) is not parsed successfully.Firefox: Firefox 57 increased the number of places calc() could substitute another value. See bug 1350857.Firefox for Android: Before Firefox for Android 59 calc() is not supported in rgb() and other color functions.Firefox for Android: Before Firefox for Android 57 calc(1*2*3) is not parsed successfully.Firefox for Android: Firefox for Android 57 increased the number of places calc() could substitute another value. See bug 1350857.
css.types.calc.gradient_color_stops Safari7/25/2012 Edge7/29/20151099
css.types.color πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.color.currentcolor πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.types.color.hsl πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.types.color.named-color πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Internet Explorer 8 and later support gray color keywords spelled with an e (grey, darkgrey, darkslategrey, dimgrey, lightgrey, and lightslategrey). Internet Explorer 3 to Internet Explorer 7 only support the keywords spelled with a (gray, darkgray, darkslategray, dimgray, lightgray, and lightslategray).
css.types.color.named-color.transparent πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.color.rgb πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.color.rgb_hexadecimal_notation πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.color.system-color πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.color.transparent Safari6/23/2003 Edge7/29/20154419
css.types.counter πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.types.counters πŸ“‹Firefox11/29/2005 Edge7/29/20153529
css.types.dimension πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.easing-function πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.easing-function.cubic-bezier πŸ“‹Firefox3/22/2011 Edge7/29/20151590
css.types.easing-function.steps πŸ“‹Firefox3/22/2011 Edge7/29/20151590
css.types.filter-function πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.blur πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.brightness πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.contrast πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.drop-shadow πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.grayscale πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.hue-rotate πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.invert πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.opacity πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.saturate πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.sepia πŸ“‹Safari7/25/2012 Edge7/29/20151099
css.types.global_keywords Safari6/23/2003 Edge7/29/20154419
css.types.global_keywords.inherit πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.gradient πŸ“‹Firefox1/21/2010 Edge7/29/20152015
Firefox: Gradients are limited to background-image, border-image, and mask-image.Firefox for Android: Gradients are limited to background-image, border-image, and mask-image.
css.types.gradient.linear-gradient πŸ“‹Firefox10/9/2012 Edge7/29/20151023
Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Internet Explorer: Internet Explorer 5.5 through 9.0 supported gradients via a proprietary filter: -ms-filter: progid:DXImageTransform.Microsoft.Gradient().Opera: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Safari: Safari 4 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in linear-gradient(). This old outdated syntax is still supported for compatibility purposes.Safari: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Safari on iOS: Safari on iOS 3.2 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in linear-gradient(). This old outdated syntax is still supported for compatibility purposes.Safari on iOS: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.WebView on iOS: WebView on iOS 3.2 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in linear-gradient(). This old outdated syntax is still supported for compatibility purposes.WebView on iOS: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.
css.types.gradient.linear-gradient.to Firefox1/31/2012 Edge7/29/20151275
css.types.gradient.radial-gradient πŸ“‹Firefox10/9/2012 Edge7/29/20151023
Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Internet Explorer: Internet Explorer 5.5 through 9.0 supported gradients via a proprietary filter: -ms-filter: progid:DXImageTransform.Microsoft.Gradient().Safari: Safari 4 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.Safari on iOS: Safari on iOS 3.2 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.WebView on iOS: WebView on iOS 3.2 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.
css.types.gradient.radial-gradient.at Firefox1/31/2012 Edge7/29/20151275
css.types.gradient.repeating-linear-gradient πŸ“‹Firefox10/9/2012 Edge7/29/20151023
Firefox: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Firefox for Android: Before Firefox for Android 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Internet Explorer: Internet Explorer 5.5 through 9.0 supported gradients via a proprietary filter: -ms-filter: progid:DXImageTransform.Microsoft.Gradient().Opera: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Safari: Safari 4 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in repeating-linear-gradient(). This old outdated syntax is still supported for compatibility purposes.Safari: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Safari on iOS: Safari on iOS 3.2 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in repeating-linear-gradient(). This old outdated syntax is still supported for compatibility purposes.Safari on iOS: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.WebView on iOS: WebView on iOS 3.2 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in repeating-linear-gradient(). This old outdated syntax is still supported for compatibility purposes.WebView on iOS: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.
css.types.gradient.repeating-linear-gradient.to Firefox1/31/2012 Edge7/29/20151275
css.types.gradient.repeating-radial-gradient πŸ“‹Firefox10/9/2012 Edge7/29/20151023
Firefox: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox for Android: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Safari: Safari 4 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.Safari on iOS: Safari on iOS 3.2 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.WebView on iOS: WebView on iOS 3.2 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.
css.types.gradient.repeating-radial-gradient.at Firefox10/9/2012 Edge7/29/20151023
Firefox: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Before Firefox for Android 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.
css.types.image πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.integer πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.length πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.length.ch Firefox11/9/2004 Edge7/29/20153914
Firefox: From Firefox 1 to Firefox 3, ch was the width of the M character.Firefox: From Firefox 1 to Firefox 3, ch did not work with border-width and outline-width CSS properties.
css.types.length.em Safari6/23/2003 Edge7/29/20154419
css.types.length.ex Safari6/23/2003 Edge7/29/20154419
css.types.length.rem Firefox1/21/2010 Edge7/29/20152015
css.types.length.vh Safari7/25/2012 Edge7/29/20151099
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length.vmin Firefox2/19/2013 Edge7/29/2015890
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length.vw Safari7/25/2012 Edge7/29/20151099
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length-percentage πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.line-style πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.number πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.overflow πŸ“‹Safari6/23/2003 Edge7/29/20154419
Internet Explorer: From version 4 to 6, Internet Explorer enlarges an element with visible (default value) to fit the content inside it.
css.types.percentage πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.position πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.position.four_value_syntax Firefox6/5/2012 Edge7/29/20151149
css.types.position.keyword_value_syntax Safari6/23/2003 Edge7/29/20154419
css.types.ratio πŸ“‹Firefox6/30/2009 Edge7/29/20152220
css.types.shape πŸ“‹Firefox11/9/2004 Edge7/29/20153914
css.types.shape.rect Firefox11/9/2004 Edge7/29/20153914
Internet Explorer: For Internet Explorer versions 5.5 through 7, the rect() function uses spaces (instead of commas) to separate parameters. For Internet Explorer 8 and later versions, only the standard comma-separated syntax is supported.
css.types.string πŸ“‹Safari6/23/2003 Edge7/29/20154419
css.types.string.unicode_escaped_characters Safari6/23/2003 Edge7/29/20154419
css.types.time πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function πŸ“‹Safari3/18/2008 Edge7/29/20152689
Internet Explorer: Internet Explorer 9 supports 2D but not 3D transforms. In version 9, mixing 2D and 3D transform functions invalidates the entire property.
css.types.transform-function.matrix πŸ“‹Safari3/18/2008 Edge7/29/20152689
Firefox: Before Firefox 16, the translation values of matrix() could be <length>s, in addition to the standard <number>.
css.types.transform-function.matrix3d πŸ“‹Safari6/8/2009 Edge7/29/20152242
Firefox: Before Firefox 16, the translation values of matrix3d() could be <length>s, in addition to the standard <number>.
css.types.transform-function.perspective πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.rotate πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.rotate3d πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.rotateX πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.rotateY πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.rotateZ πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.scale πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.scale3d πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.scaleX πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.scaleY πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.scaleZ πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.skew πŸ“‹Safari3/18/2008 Edge7/29/20152689
Firefox: Firefox 14 removed experimental support for skew(), but it was reintroduced in Firefox 15.
css.types.transform-function.skewX πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.skewY πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.translate πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.translate3d πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.translateX πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.translateY πŸ“‹Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.translateZ πŸ“‹Safari6/8/2009 Edge7/29/20152242
css.types.url πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.a πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Starting with Firefox 41, <a> without href attribute is no longer classified as interactive content: clicking it inside <label> will activate labelled content (bug 1167816).Firefox for Android: Starting with Firefox for Android 41, <a> without href attribute is no longer classified as interactive content: clicking it inside <label> will activate labelled content (bug 1167816).
html.elements.a.charset πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.a.href πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.a.href.href_top Safari6/8/2009 Edge7/29/20152242
html.elements.a.hreflang πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.a.name πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.a.rel πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.a.rev πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.a.target πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.a.type πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.abbr πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.acronym πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.address πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.area πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.area.alt πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.area.coords πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.area.href πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.area.nohref πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.area.rel πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.area.shape πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.area.target πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.article πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.aside πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.audio πŸ“‹Safari3/18/2008 Edge7/29/20152689
Firefox: For Firefox to play audio, the server must serve the file using the correct MIME type.Firefox for Android: For Firefox for Android to play audio, the server must serve the file using the correct MIME type.
html.elements.audio.controls πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.audio.loop πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.audio.preload πŸ“‹Safari3/18/2008 Edge7/29/20152689
Chrome: Defaults to metadata in Chrome 64.Chrome Android: Defaults to metadata in Chrome Android 64.Quest Browser: Defaults to metadata in Quest Browser 5.0.Opera: Defaults to metadata in Opera 51.Opera Android: Defaults to metadata in Opera 51.Samsung Internet: Defaults to metadata in Samsung Internet 9.0.WebView Android: Defaults to metadata in Chrome 64.
html.elements.audio.src πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.b πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.base πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Internet Explorer: Before Internet Explorer 7, <base> can be positioned anywhere in the document and the nearest value of <base> is used.
html.elements.base.href πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.base.href.relative_url Safari10/26/2007 Edge7/29/20152833
html.elements.base.target πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.bdo πŸ“‹Safari6/8/2009 Edge7/29/20152242
html.elements.big πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.blockquote πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.blockquote.cite Firefox11/9/2004 Edge7/29/20153914
html.elements.body πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.body.alink Firefox11/9/2004 Edge7/29/20153914
html.elements.body.background Firefox11/9/2004 Edge7/29/20153914
html.elements.body.bgcolor Firefox11/9/2004 Edge7/29/20153914
html.elements.body.link Firefox11/9/2004 Edge7/29/20153914
html.elements.body.text Firefox11/9/2004 Edge7/29/20153914
html.elements.body.vlink Firefox11/9/2004 Edge7/29/20153914
html.elements.br πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.br.clear Firefox11/9/2004 Edge7/29/20153914
html.elements.button πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.button.disabled πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.button.formaction Firefox3/22/2011 Edge7/29/20151590
html.elements.button.formenctype Firefox3/22/2011 Edge7/29/20151590
html.elements.button.formmethod Firefox3/22/2011 Edge7/29/20151590
html.elements.button.formnovalidate Firefox3/22/2011 Edge7/29/20151590
html.elements.button.formtarget Firefox3/22/2011 Edge7/29/20151590
html.elements.button.name Firefox11/9/2004 Edge7/29/20153914
html.elements.button.type Firefox11/9/2004 Edge7/29/20153914
html.elements.button.value Firefox11/9/2004 Edge7/29/20153914
html.elements.canvas πŸ“‹Safari4/29/2005 Edge7/29/20153743
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.canvas.height πŸ“‹Safari4/29/2005 Edge7/29/20153743
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.canvas.width πŸ“‹Safari4/29/2005 Edge7/29/20153743
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.caption πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.caption.align Firefox11/9/2004 Edge7/29/20153914
html.elements.center πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.cite πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.code πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.col πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.col.align πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.col.span πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.col.valign πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.col.width πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup.align πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup.span πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup.valign πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup.width πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.dd πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element was implemented using the HTMLSpanElement interface instead of HTMLElement.
html.elements.del πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.del.cite Firefox11/9/2004 Edge7/29/20153914
html.elements.del.datetime Firefox11/9/2004 Edge7/29/20153914
html.elements.dfn πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.dir πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.dir.compact Firefox11/9/2004 Edge7/29/20153914
html.elements.div πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.div.align Firefox11/9/2004 Edge7/29/20153914
html.elements.dl πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.dt πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.em πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.embed πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.embed.height πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.embed.name πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.embed.src πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.embed.width πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.fieldset πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Chrome: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.Chrome Android: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.Edge: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 4511145.Quest Browser: Before version 12.0, this element did not support flexbox and grid layouts within this element. See bug 41027853.Samsung Internet: Before version 14.0, this element did not support flexbox and grid layouts within this element. See bug 41027853.WebView Android: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.
html.elements.fieldset.form πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.fieldset.name πŸ“‹Firefox3/22/2011 Edge7/29/20151590
html.elements.figcaption πŸ“‹Firefox3/22/2011 Edge7/29/20151590
html.elements.figure πŸ“‹Firefox3/22/2011 Edge7/29/20151590
html.elements.font πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.font.color Firefox11/9/2004 Edge7/29/20153914
html.elements.font.face Firefox11/9/2004 Edge7/29/20153914
html.elements.font.size Firefox11/9/2004 Edge7/29/20153914
html.elements.footer πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.form πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.form.accept-charset πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.form.action πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.form.autocomplete πŸ“‹Firefox3/22/2011 Edge7/29/20151590
Chrome: The Google Chrome UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Chrome might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Chrome Android: The Chrome Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Chrome Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Quest Browser: The Quest Browser UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Quest Browser might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Opera: The Opera UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Opera might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Opera Android: The Opera Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Opera Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Samsung Internet: The Samsung Internet UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Samsung Internet might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.WebView Android: The WebView Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, WebView Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.
html.elements.form.enctype πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.form.method πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.form.name πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.form.target πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.frame πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.frameborder Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.marginheight Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.marginwidth Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.name Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.noresize Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.scrolling Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.src Firefox11/9/2004 Edge7/29/20153914
html.elements.frameset πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.frameset.cols Firefox11/9/2004 Edge7/29/20153914
html.elements.frameset.rows Firefox11/9/2004 Edge7/29/20153914
html.elements.h1 πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.h2 πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.h3 πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.h4 πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.h5 πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.h6 πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.head πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.header πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.hgroup πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.hr πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.hr.align Firefox11/9/2004 Edge7/29/20153914
html.elements.hr.noshade Firefox11/9/2004 Edge7/29/20153914
html.elements.hr.size Firefox11/9/2004 Edge7/29/20153914
html.elements.hr.width Firefox11/9/2004 Edge7/29/20153914
html.elements.html πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.html.version πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.html.xmlns Safari6/23/2003 Edge7/29/20154419
html.elements.i πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.iframe πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: The resize CSS property doesn't have any effect on this element due to bug 680823.Firefox for Android: The resize CSS property doesn't have any effect on this element due to bug 680823.Safari: Safari has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.Safari on iOS: Safari on iOS has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.WebView on iOS: WebView on iOS has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.
html.elements.iframe.align πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.frameborder πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.height πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.longdesc πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.marginheight πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.marginwidth πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.name πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.sandbox πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.iframe.sandbox.allow-popups πŸ“‹Safari7/25/2012 Edge7/29/20151099
html.elements.iframe.scrolling πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.src πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.width πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.img.align πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.alt πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.border πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.crossorigin πŸ“‹Firefox11/8/2011 Edge7/29/20151359
html.elements.img.height πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.hspace πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.ismap πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.longdesc πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.name πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.src πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.img.srcset πŸ“‹Safari10/16/2014 Edge7/29/2015286
html.elements.img.usemap πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.vspace πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.img.width πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.input πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 89, manipulating the content of <input> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Firefox for Android: Before Firefox for Android 89, manipulating the content of <input> elements using Document.execCommand() commands requires workarounds (see bug 1220696).
html.elements.input.accept πŸ“‹Safari6/23/2003 Edge7/29/20154419
Safari on iOS: Does not support audio/* MIME type. See bug 242110.WebView on iOS: Does not support audio/* MIME type. See bug 242110.
html.elements.input.align πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.alt πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.autocomplete πŸ“‹Firefox3/22/2011 Edge7/29/20151590
html.elements.input.checked πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.disabled πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.form πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.formaction πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.formenctype πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.formmethod πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.formnovalidate πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.formtarget πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.max πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.maxlength πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.min πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.multiple πŸ“‹Safari6/8/2009 Edge7/29/20152242
html.elements.input.name πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.pattern πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.placeholder πŸ“‹Safari6/8/2009 Edge7/29/20152242
html.elements.input.readonly πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.required πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.size πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.src πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.step πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.type_button πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_checkbox πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_email πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Safari on iOS: Doesn't do validation, but instead offers a custom 'email' keyboard, which is designed to make entering email addresses easier.Safari on iOS: The custom 'email' keyboard does not provide a comma key, so users cannot enter multiple email addresses.Safari on iOS: Automatically applies a default style of opacity: 0.4 to disable textual <input> elements, including those of type 'email'. Other major browsers don't currently share this particular default style.WebView on iOS: Doesn't do validation, but instead offers a custom 'email' keyboard, which is designed to make entering email addresses easier.WebView on iOS: The custom 'email' keyboard does not provide a comma key, so users cannot enter multiple email addresses.WebView on iOS: Automatically applies a default style of opacity: 0.4 to disable textual <input> elements, including those of type 'email'. Other major browsers don't currently share this particular default style.
html.elements.input.type_file πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: You can set as well as get the value of HTMLInputElement.files in all modern browsers; this was most recently added to Firefox, in version 57 (see bug 1384030).
html.elements.input.type_hidden πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_image πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_number πŸ“‹Safari7/20/2011 Edge7/29/20151470
Chrome: Prevents users from typing non-numeric content.Chrome Android: Prevents users from typing non-numeric content.Firefox: Allows users to type non-numeric content, with the value reflecting an empty string.Firefox for Android: Allows users to type non-numeric content, with the value reflecting an empty string.Quest Browser: Prevents users from typing non-numeric content.Opera: Prevents users from typing non-numeric content.Opera Android: Prevents users from typing non-numeric content.Safari: Allows users to type non-numeric content, with the value reflecting an empty string.Safari on iOS: Allows users to type non-numeric content, with the value reflecting an empty string.Samsung Internet: Prevents users from typing non-numeric content.WebView Android: Prevents users from typing non-numeric content.WebView on iOS: Allows users to type non-numeric content, with the value reflecting an empty string.
html.elements.input.type_password πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_radio πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_range πŸ“‹Safari3/18/2008 Edge7/29/20152689
WebView Android: Pre-Chromium Android WebView recognizes the range type, but doesn't implement a range-specific control.
html.elements.input.type_reset πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Unlike other browsers, Firefox by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.Firefox for Android: Unlike other browsers, Firefox for Android by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.
html.elements.input.type_search πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.input.type_submit πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Unlike other browsers, Firefox by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.Firefox for Android: Unlike other browsers, Firefox for Android by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.
html.elements.input.type_tel πŸ“‹Safari6/8/2009 Edge7/29/20152242
Chrome: The field type doesn't demonstrate any special behavior.Safari: The field type doesn't demonstrate any special behavior.
html.elements.input.type_text πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_url πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.input.usemap πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.ins πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.ins.cite Firefox11/9/2004 Edge7/29/20153914
html.elements.ins.datetime Firefox11/9/2004 Edge7/29/20153914
html.elements.kbd πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, creating a <kbd> element incorrectly resulted in an HTMLSpanElement object, instead of the expected HTMLElement.
html.elements.label πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.label.for πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.legend πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.legend.align Firefox11/9/2004 Edge7/29/20153914
html.elements.li πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.li.type πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.li.value πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.link πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.link.charset πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.link.disabled πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Chrome: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Chrome Android: In Chrome Android and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Edge: Since Edge 79, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Quest Browser: In Quest Browser and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Opera: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Opera Android: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Samsung Internet: In Samsung Internet and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.WebView Android: In WebView Android and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.
html.elements.link.href πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.link.hreflang πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.link.media πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.link.rel πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.link.rel.icon Firefox10/24/2006 Edge7/29/20153200
Chrome: If both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.).Edge: In version 79 and later (Blink-based Edge), if both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.)Firefox: Before Firefox 83, the crossorigin attribute is not supported for rel="icon".Firefox: The media attribute is not supported for rel="icon", see bug 1603885.Opera: In version 15 and later (Blink-based Opera), if both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.)Safari: If both ICO and PNG are available, will ALWAYS use ICO file, regardless of sizes set. (Per caniuse.com.)Safari on iOS: Does not use favicons at all (but may have alternative for bookmarks, etc.). (Per caniuse.com.)WebView on iOS: Does not use favicons at all (but may have alternative for bookmarks, etc.). (Per caniuse.com.)
html.elements.link.rev πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.link.target πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.link.type πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.main πŸ“‹Firefox5/14/2013 Edge7/29/2015806
html.elements.map πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 5, in Quirks Mode, empty maps were no longer skipped over in favor of non-empty ones when matching.Firefox: Before Firefox 17, the default styling of the <map> HTML element was display: block;. This is now display: inline; and matches the behavior of the other browsers. It was already the case in Quirks Mode.
html.elements.map.name Safari6/23/2003 Edge7/29/20154419
html.elements.mark πŸ“‹Firefox3/22/2011 Edge7/29/20151590
html.elements.marquee.behavior Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.bgcolor Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.direction Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.height Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.hspace Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.loop Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.scrollamount Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.scrolldelay Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.truespeed Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.vspace Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.width Safari2/2/2004 Edge7/29/20154195
html.elements.menu πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.meta πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.meta.charset πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.meta.content πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.meta.http-equiv πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.meta.http-equiv.refresh πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.meta.name πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.meta.scheme πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.nav πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.nobr πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.noembed πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.noframes πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.noscript πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.archive πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.border πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.classid πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.codetype πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.data πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.declare πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.form πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.height πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.name πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.standby πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.type πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.usemap πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.object.width πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.ol πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.ol.compact Firefox11/9/2004 Edge7/29/20153914
html.elements.ol.start πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.ol.type πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.optgroup πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.optgroup.disabled πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Safari: Before Safari 7, the attribute can be set, but has no effect.Safari on iOS: The attribute can be set, but has no effect.WebView on iOS: The attribute can be set, but has no effect.
html.elements.optgroup.label πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.option πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.option.disabled πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.option.label πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before 77, Firefox didn't display the value of the label attribute as option text if element's content was empty. See bug 40545.Firefox: Historically, Firefox has allowed keyboard and mouse events to bubble up from the <option> element to the parent <select> element, although this behavior is inconsistent across many browsers. For better Web compatibility (and for technical reasons), they will not bubble up when Firefox is in multi-process mode and the <select> element is displayed as a drop-down list. The behavior is unchanged if the <select> is presented inline and it has either the multiple attribute defined or a size attribute set to more than 1. Rather than watching <option> elements for events, you should watch for change events on <select>. See bug 1090602 for details.Firefox: When Mozilla introduced dedicated content threads to Firefox (through the Electrolysis, or e10s, project), support for styling <option> elements was removed temporarily. Starting in Firefox 54, you can apply foreground and background colors to <option> elements again, using the color and background-color CSS properties. See bug 910022 for more information. Note that this is still disabled in Linux due to lack of contrast (see bug 1338283 for progress on this).Firefox for Android: Before 77, Firefox didn't display the value of the label attribute as option text if element's content was empty. See bug 40545.
html.elements.option.selected πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.option.value πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.p πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.param πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.param.name Firefox11/9/2004 Edge7/29/20153914
html.elements.param.type Firefox11/9/2004 Edge7/29/20153914
html.elements.param.value Firefox11/9/2004 Edge7/29/20153914
html.elements.param.valuetype Firefox11/9/2004 Edge7/29/20153914
html.elements.plaintext πŸ“‹Safari6/8/2009 Edge7/29/20152242
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.pre πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.pre.width Firefox11/9/2004 Edge7/29/20153914
Chrome: Specifying the width attribute has no layout effect.Chrome Android: Specifying the width attribute has no layout effect.Edge: Specifying the width attribute has no layout effect.Firefox: Since Firefox 29, specifying the width attribute has no layout effect.Firefox for Android: Since Firefox for Android 29, specifying the width attribute has no layout effect.Internet Explorer: Specifying the width attribute has no layout effect.Quest Browser: Specifying the width attribute has no layout effect.Opera: Specifying the width attribute has no layout effect.Opera Android: Specifying the width attribute has no layout effect.Safari: Specifying the width attribute has no layout effect.Safari on iOS: Specifying the width attribute has no layout effect.Samsung Internet: Specifying the width attribute has no layout effect.WebView Android: Specifying the width attribute has no layout effect.WebView on iOS: Specifying the width attribute has no layout effect.
html.elements.progress πŸ“‹Firefox8/16/2011 Edge7/29/20151443
Firefox: Before Firefox 14, the <progress> element was incorrectly classified as a form element, and therefore had a form attribute. This has been fixed.Firefox: Firefox provides the ::-moz-progress-bar pseudo-element, which lets you style the part of the interior of the progress bar representing the amount of work completed so far.Firefox for Android: Before Firefox for Android 14, the <progress> element was incorrectly classified as a form element, and therefore had a form attribute. This has been fixed.Firefox for Android: Firefox for Android provides the ::-moz-progress-bar pseudo-element, which lets you style the part of the interior of the progress bar representing the amount of work completed so far.Safari on iOS: Safari on iOS does not support indeterminate progress bars (they are rendered like 0%-completed progress bars).WebView on iOS: WebView on iOS does not support indeterminate progress bars (they are rendered like 0%-completed progress bars).
html.elements.progress.max πŸ“‹Firefox8/16/2011 Edge7/29/20151443
html.elements.progress.value πŸ“‹Firefox8/16/2011 Edge7/29/20151443
html.elements.q πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.q.cite πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.rp πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.rt πŸ“‹Safari6/7/2010 Edge7/29/20151878
Chrome: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Chrome Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Quest Browser: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Opera: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Opera Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Safari: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.Safari on iOS: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.Samsung Internet: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.WebView Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.WebView on iOS: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.
html.elements.ruby πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.s πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.samp πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.script πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Starting in Firefox 4, inserting <script> elements that have been created by calling document.createElement("script") no longer enforces execution in insertion order. This change lets Firefox properly abide by the specification. To make script-inserted external scripts execute in their insertion order, set .async=false on them.
html.elements.script.async πŸ“‹Safari6/8/2009 Edge7/29/20152242
html.elements.script.defer πŸ“‹Safari10/26/2007 Edge7/29/20152833
Chrome: Chrome does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Chrome Android: Chrome Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Firefox: Since Firefox 3.6, the defer attribute is ignored on scripts that don't have the src attribute. However, in Firefox 3.5 even inline scripts are deferred if the defer attribute is set.Internet Explorer: Before version 10, Internet Explorer implemented defer by a proprietary specification. Since version 10 it conforms to the W3C specification.Quest Browser: Quest Browser does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Opera: Opera does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Opera Android: Opera Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Samsung Internet: Samsung Internet does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348WebView Android: WebView Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348
html.elements.script.src πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.script.type πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.section πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.select πŸ“‹Safari6/23/2003 Edge7/29/20154419
Chrome: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Chrome Android: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Firefox: Historically, Firefox has allowed keyboard and mouse events to bubble up from the <option> element to the parent <select> element, although this behavior is inconsistent across many browsers. For better Web compatibility (and for technical reasons), when Firefox is in multi-process mode the <select> element is displayed as a drop-down list. The behavior is unchanged if the <select> is presented inline and it has either the multiple attribute defined or a size attribute set to more than 1. Rather than watching <option> elements for events, you should watch for change events on <select>. See bug 1090602 for details.Firefox for Android: Firefox for Android, by default, sets a background-image gradient on all <select multiple> elements. This can be disabled using background-image: none.Quest Browser: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Safari: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Safari on iOS: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Samsung Internet: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.WebView Android: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.WebView on iOS: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.
html.elements.select.disabled πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.select.form πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.select.multiple πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.select.name πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.select.required πŸ“‹Firefox3/22/2011 Edge7/29/20151590
html.elements.select.size πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.small πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.source πŸ“‹Safari3/18/2008 Edge7/29/20152689
Firefox: Until Firefox 15, Firefox picked the first source element that has a type matching the MIME-type of a supported media format; see bug 449363 for details.Firefox for Android: Until Firefox for Android 15, Firefox for Android picked the first source element that has a type matching the MIME-type of a supported media format; see bug 449363 for details.
html.elements.source.media πŸ“‹Safari3/18/2008 Edge7/29/20152689
Firefox: media is supported in <source> within <picture>, <audio>, and <video>. In Firefox 53-119, media is supported only in <source> within <picture>.Firefox for Android: media is supported in <source> within <picture>, <audio>, and <video>. In Firefox for Android 53-119, media is supported only in <source> within <picture>.
html.elements.source.src πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.source.type πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.span πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.strike πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.strong πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, creating a <strong> element incorrectly resulted in an HTMLSpanElement object, instead of the expected HTMLElement.
html.elements.style πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.style.media πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.style.type πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before 75, Firefox accepted any CSS media (MIME) type, with optional parameters. Starting in 75, this has been restricted to the string 'text/css', per the spec.
html.elements.sub πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.sup πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.table πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.table.align Safari6/23/2003 Edge7/29/20154419
html.elements.table.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.table.border Safari6/23/2003 Edge7/29/20154419
html.elements.table.cellpadding Safari6/23/2003 Edge7/29/20154419
html.elements.table.cellspacing Safari6/23/2003 Edge7/29/20154419
html.elements.table.frame Safari6/23/2003 Edge7/29/20154419
html.elements.table.rules Safari6/23/2003 Edge7/29/20154419
html.elements.table.summary Safari6/23/2003 Edge7/29/20154419
html.elements.table.width Safari6/23/2003 Edge7/29/20154419
html.elements.tbody πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.tbody.align Firefox11/9/2004 Edge7/29/20153914
html.elements.tbody.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.tbody.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.td πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.td.abbr Safari6/23/2003 Edge7/29/20154419
html.elements.td.align Firefox11/9/2004 Edge7/29/20153914
html.elements.td.axis Safari6/23/2003 Edge7/29/20154419
html.elements.td.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.td.colspan Safari6/23/2003 Edge7/29/20154419
html.elements.td.headers Safari6/23/2003 Edge7/29/20154419
html.elements.td.rowspan Safari6/23/2003 Edge7/29/20154419
html.elements.td.scope Safari6/23/2003 Edge7/29/20154419
html.elements.td.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.td.width Safari6/23/2003 Edge7/29/20154419
html.elements.textarea πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 6, when a <textarea> was focused, the insertion point was placed at the end of the text by default. Other major browsers place the insertion point at the beginning of the text.Firefox: A default background-image gradient is applied to all <textarea> elements, which can be disabled using background-image: none.Firefox: Before Firefox 89, manipulating the content of <textarea> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Firefox for Android: Before Firefox for Android 6, when a <textarea> was focused, the insertion point was placed at the end of the text by default. Other major browsers place the insertion point at the beginning of the text.Firefox for Android: A default background-image gradient is applied to all <textarea> elements, which can be disabled using background-image: none.Firefox for Android: Before Firefox for Android 89, manipulating the content of <textarea> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Safari on iOS: Unlike other major browsers, a default style of opacity: 0.4 is applied to disabled <textarea> elements.WebView on iOS: Unlike other major browsers, a default style of opacity: 0.4 is applied to disabled <textarea> elements.
html.elements.textarea.cols πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.disabled πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.form πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.maxlength πŸ“‹Safari6/7/2010 Edge7/29/20151878
Safari: Before Safari 17, newline characters counted as two characters instead of one. See bug 249916.Safari on iOS: Before Safari on iOS 17, newline characters counted as two characters instead of one. See bug 249916.WebView on iOS: Before WebView on iOS 17, newline characters counted as two characters instead of one. See bug 249916.
html.elements.textarea.name πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.placeholder πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.textarea.readonly πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.required πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.textarea.rows πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.wrap πŸ“‹Firefox3/22/2011 Edge7/29/20151590
html.elements.tfoot πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.tfoot.align Firefox11/9/2004 Edge7/29/20153914
html.elements.tfoot.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.tfoot.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.th πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.th.abbr Safari6/23/2003 Edge7/29/20154419
html.elements.th.align Firefox11/9/2004 Edge7/29/20153914
html.elements.th.axis Safari6/23/2003 Edge7/29/20154419
html.elements.th.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.th.colspan Safari6/23/2003 Edge7/29/20154419
html.elements.th.headers Safari6/23/2003 Edge7/29/20154419
html.elements.th.rowspan Safari6/23/2003 Edge7/29/20154419
html.elements.th.scope Safari6/23/2003 Edge7/29/20154419
html.elements.th.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.th.width Safari6/23/2003 Edge7/29/20154419
html.elements.thead πŸ“‹Safari6/23/2003 Edge7/29/20154419
Safari: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.Safari on iOS: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.WebView on iOS: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.
html.elements.thead.align Firefox11/9/2004 Edge7/29/20153914
html.elements.thead.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.thead.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.title πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.tr πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.elements.tr.align Firefox11/9/2004 Edge7/29/20153914
html.elements.tr.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.tr.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.track πŸ“‹Safari7/25/2012 Edge7/29/20151099
Chrome Android: Doesn't work for fullscreen video.Quest Browser: Doesn't work for fullscreen video.Samsung Internet: Doesn't work for fullscreen video.WebView Android: Doesn't work for fullscreen video.
html.elements.track.default πŸ“‹Safari7/25/2012 Edge7/29/20151099
html.elements.track.kind πŸ“‹Safari7/25/2012 Edge7/29/20151099
html.elements.track.label πŸ“‹Safari7/25/2012 Edge7/29/20151099
html.elements.track.srclang πŸ“‹Safari7/25/2012 Edge7/29/20151099
html.elements.tt πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.u πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.ul πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.ul.compact πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.ul.type πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.var πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.video πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.video.autoplay πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.video.controls πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.video.height πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.video.loop πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.video.muted πŸ“‹Safari6/7/2010 Edge7/29/20151878
html.elements.video.poster πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.video.preload πŸ“‹Safari3/18/2008 Edge7/29/20152689
Chrome: Defaults to metadata in Chrome 64.Chrome Android: Defaults to metadata in Chrome Android 64.Quest Browser: Defaults to metadata in Quest Browser 5.0.Opera: Defaults to metadata in Opera 51.Opera Android: Defaults to metadata in Opera Android 47.Samsung Internet: Defaults to metadata in Samsung Internet 9.0.WebView Android: Defaults to metadata in WebView Android 64.
html.elements.video.src πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.video.width πŸ“‹Safari3/18/2008 Edge7/29/20152689
html.elements.wbr πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.elements.xmp πŸ“‹Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.global_attributes.accesskey πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.global_attributes.class πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.global_attributes.contenteditable πŸ“‹Firefox6/17/2008 Edge7/29/20152598
html.global_attributes.data_attributes πŸ“‹Safari7/20/2011 Edge7/29/20151470
html.global_attributes.draggable πŸ“‹Firefox10/24/2006 Edge7/29/20153200
html.global_attributes.hidden πŸ“‹Firefox3/22/2011 Edge7/29/20151590
Safari: This attribute has no effect on <option> elements.Safari on iOS: This attribute has no effect on <option> elements.WebView on iOS: This attribute has no effect on <option> elements.
html.global_attributes.id πŸ“‹Safari6/23/2003 Edge7/29/20154419
Firefox: id is a true global attribute only since Firefox 32.Firefox for Android: id is a true global attribute only since Firefox for Android 32.
html.global_attributes.lang πŸ“‹Firefox11/9/2004 Edge7/29/20153914
html.global_attributes.spellcheck πŸ“‹Firefox10/24/2006 Edge7/29/20153200
Chrome Android: Only supported on <textarea>.Firefox for Android: Only supported on <textarea>.Opera Android: Only supported on <textarea>.Safari on iOS: Only supported on <textarea>.Samsung Internet: Only supported on <textarea>.WebView Android: Only supported on <textarea>.WebView on iOS: Only supported on <textarea>.
html.global_attributes.style πŸ“‹Safari6/23/2003 Edge7/29/20154419
html.global_attributes.tabindex πŸ“‹Firefox11/29/2005 Edge7/29/20153529
html.global_attributes.title πŸ“‹Firefox11/9/2004 Edge7/29/20153914