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 Chrome and Safari, 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
css.properties.text-indent.each-line πŸ“‹Safari9/20/2021 Chrome3/10/20261632
css.properties.text-indent.hanging πŸ“‹Safari9/20/2021 Chrome3/10/20261632

2026/2

API First Browser Date Last Browser Date Days Notes
css.properties.word-spacing.percentages Safari10/22/2013 Chrome2/10/20264494

2026/1

API First Browser Date Last Browser Date Days Notes
css.properties.background-position-x.side-relative_values Safari3/14/2022 Chrome1/13/20261401
css.properties.background-position-y.side-relative_values Safari3/14/2022 Chrome1/13/20261401
css.properties.position-area.block-end πŸ“‹Safari9/15/2025 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/202632
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 Chrome1/13/202632
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 Chrome1/13/202632
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 Chrome1/13/202632
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.span-all πŸ“‹Safari9/15/2025 Chrome1/13/2026120
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-area.top πŸ“‹Safari9/15/2025 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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 Chrome1/13/2026120
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.flip-x πŸ“‹Safari12/12/2025 Chrome1/13/202632
css.properties.position-try.flip-y πŸ“‹Safari12/12/2025 Chrome1/13/202632
css.properties.position-try.self-x-end πŸ“‹Safari12/12/2025 Chrome1/13/202632
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 Chrome1/13/202632
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 Chrome1/13/202632
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 Chrome1/13/202632
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.flip-x πŸ“‹Safari12/12/2025 Chrome1/13/202632
css.properties.position-try-fallbacks.flip-y πŸ“‹Safari12/12/2025 Chrome1/13/202632
css.properties.position-try-fallbacks.self-x-end πŸ“‹Safari12/12/2025 Chrome1/13/202632
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 Chrome1/13/202632
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 Chrome1/13/202632
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 Chrome1/13/202632
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.types.color.color.colorSpace_parameter_accepts_display-p3-linear_value πŸ“‹Safari12/12/2025 Chrome1/13/202632

2025/12

API First Browser Date Last Browser Date Days Notes
css.properties.field-sizing πŸ“‹Chrome3/19/2024 Safari12/12/2025633
css.properties.field-sizing.content πŸ“‹Chrome3/19/2024 Safari12/12/2025633
css.properties.field-sizing.fixed πŸ“‹Chrome3/19/2024 Safari12/12/2025633
css.properties.font-family.math Chrome1/10/2023 Safari12/12/20251067
css.properties.math-shift πŸ“‹Chrome1/10/2023 Safari12/12/20251067
css.properties.math-shift.compact πŸ“‹Chrome1/10/2023 Safari12/12/20251067
css.properties.math-shift.normal πŸ“‹Chrome1/10/2023 Safari12/12/20251067
css.properties.position-area.span-self-x-end πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-area.span-self-x-start πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-area.span-self-y-end πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-area.span-self-y-start πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-try.span-self-x-end πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-try.span-self-x-start πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-try.span-self-y-end πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-try.span-self-y-start πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-try-fallbacks.span-self-x-end πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-try-fallbacks.span-self-x-start πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-try-fallbacks.span-self-y-end πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-try-fallbacks.span-self-y-start πŸ“‹Chrome12/2/2025 Safari12/12/202510
css.properties.position-visibility πŸ“‹Chrome5/14/2024 Safari12/12/2025577
css.properties.position-visibility.always πŸ“‹Chrome5/14/2024 Safari12/12/2025577
css.properties.position-visibility.anchors-visible πŸ“‹Chrome5/14/2024 Safari12/12/2025577
css.properties.position-visibility.no-overflow πŸ“‹Chrome5/14/2024 Safari12/12/2025577
css.properties.scrollbar-color πŸ“‹Chrome1/23/2024 Safari12/12/2025689
css.properties.scrollbar-color.auto πŸ“‹Chrome1/23/2024 Safari12/12/2025689
css.properties.text-decoration.auto πŸ“‹Chrome11/17/2020 Safari12/12/20251851
css.properties.text-decoration.currentColor πŸ“‹Chrome3/9/2017 Safari12/12/20253200
css.properties.text-decoration.dashed πŸ“‹Chrome3/9/2017 Safari12/12/20253200
css.properties.text-decoration.dotted πŸ“‹Chrome3/9/2017 Safari12/12/20253200
css.properties.text-decoration.double πŸ“‹Chrome3/9/2017 Safari12/12/20253200
css.properties.text-decoration.from-font πŸ“‹Chrome11/17/2020 Safari12/12/20251851
css.properties.text-decoration.grammar-error πŸ“‹Chrome1/23/2024 Safari12/12/2025689
css.properties.text-decoration.includes_color-and-style Chrome3/9/2017 Safari12/12/20253200
css.properties.text-decoration.includes_thickness Chrome11/17/2020 Safari12/12/20251851
css.properties.text-decoration.solid πŸ“‹Chrome3/9/2017 Safari12/12/20253200
css.properties.text-decoration.spelling-error πŸ“‹Chrome1/23/2024 Safari12/12/2025689
css.properties.text-decoration.transparent πŸ“‹Chrome3/9/2017 Safari12/12/20253200
css.properties.text-decoration.wavy πŸ“‹Chrome3/9/2017 Safari12/12/20253200
css.properties.text-decoration-line.grammar-error πŸ“‹Chrome1/23/2024 Safari12/12/2025689
css.properties.text-decoration-line.spelling-error πŸ“‹Chrome1/23/2024 Safari12/12/2025689
css.selectors.nesting.at-scope Chrome12/2/2025 Safari12/12/202510
css.types.sibling-count πŸ“‹Chrome6/24/2025 Safari12/12/2025171
css.types.sibling-index πŸ“‹Chrome6/24/2025 Safari12/12/2025171

2025/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.keyframes.named_range_keyframes πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.at-rules.position-try πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.align-items.anchor-center πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.align-self.anchor-center πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.anchor-name πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.anchor-name.none πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.anchor-scope πŸ“‹Chrome11/12/2024 Safari9/15/2025307
css.properties.anchor-scope.all πŸ“‹Chrome11/12/2024 Safari9/15/2025307
css.properties.anchor-scope.none πŸ“‹Chrome11/12/2024 Safari9/15/2025307
css.properties.animation-range πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-range.normal πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-range-end πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-range-end.normal πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-range-start πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-range-start.normal πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-timeline πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-timeline.auto πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-timeline.none πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.animation-timeline.scroll πŸ“‹Chrome7/18/2023 Safari9/15/2025790
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 πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.block-size.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.bottom.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.bottom.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.content-visibility.auto πŸ“‹Chrome8/25/2020 Safari9/15/20251847
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.dynamic-range-limit πŸ“‹Chrome4/29/2025 Safari9/15/2025139
css.properties.dynamic-range-limit.no-limit πŸ“‹Chrome4/29/2025 Safari9/15/2025139
css.properties.dynamic-range-limit.standard πŸ“‹Chrome4/29/2025 Safari9/15/2025139
css.properties.height.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inline-size.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inset.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inset.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.inset-block.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inset-block.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.inset-block-end.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inset-block-end.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.inset-block-start.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inset-block-start.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.inset-inline.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inset-inline.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.inset-inline-end.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inset-inline-end.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.inset-inline-start.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.inset-inline-start.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.justify-items.anchor-center πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.justify-self.anchor-center πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.left.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.left.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-block.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-block-end.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-block-start.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-bottom.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-inline.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-inline-end.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-inline-start.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-left.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-right.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.margin-top.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.max-block-size.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.max-height.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.max-inline-size.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.max-width.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.min-block-size.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.min-height.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.min-inline-size.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.min-width.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.overflow-block πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-block.auto πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-block.clip πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-block.hidden πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-block.scroll πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-block.visible πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-inline πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-inline.auto πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-inline.clip πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-inline.hidden πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-inline.scroll πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.overflow-inline.visible πŸ“‹Chrome4/1/2025 Safari9/15/2025167
css.properties.place-items.anchor-center πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.place-self.anchor-center πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-anchor.auto πŸ“‹Chrome5/14/2024 Safari9/15/2025489
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 πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.center πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.none πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-bottom πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-left πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-right πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-self-block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-self-block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-self-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-self-inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-self-inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-self-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-top πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-x-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-x-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-y-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.span-y-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-area.start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try.block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.bottom πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.center πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.flip-block πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try.flip-inline πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try.flip-start πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try.inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.left πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.none πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try.right πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.self-block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.self-block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.self-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.self-inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.self-inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.self-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-all πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-bottom πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-left πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-right πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-self-block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-self-block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-self-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-self-inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-self-inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-self-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-top πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-x-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-x-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-y-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.span-y-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.top πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.x-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.x-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.y-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try.y-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks πŸ“‹Chrome8/20/2024 Safari9/15/2025391
css.properties.position-try-fallbacks.block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.bottom πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.center πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.flip-block πŸ“‹Chrome8/20/2024 Safari9/15/2025391
css.properties.position-try-fallbacks.flip-inline πŸ“‹Chrome8/20/2024 Safari9/15/2025391
css.properties.position-try-fallbacks.flip-start πŸ“‹Chrome8/20/2024 Safari9/15/2025391
css.properties.position-try-fallbacks.inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.left πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.none πŸ“‹Chrome8/20/2024 Safari9/15/2025391
css.properties.position-try-fallbacks.position-area πŸ“‹Chrome8/20/2024 Safari9/15/2025391
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 πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.self-block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.self-block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.self-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.self-inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.self-inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.self-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-all πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-bottom πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-left πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-right πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-self-block-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-self-block-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-self-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-self-inline-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-self-inline-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-self-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-top πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-x-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-x-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-y-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.span-y-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.top πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.x-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.x-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.y-end πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-fallbacks.y-start πŸ“‹Chrome9/17/2024 Safari9/15/2025363
css.properties.position-try-order πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try-order.most-block-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try-order.most-height πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try-order.most-inline-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try-order.most-width πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.position-try-order.normal πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.right.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.right.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.scroll-timeline πŸ“‹Chrome7/18/2023 Safari9/15/2025790
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.none πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.scroll-timeline-axis πŸ“‹Chrome7/18/2023 Safari9/15/2025790
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-axis.block πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.scroll-timeline-axis.inline πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.scroll-timeline-axis.x πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.scroll-timeline-axis.y πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.scroll-timeline-name πŸ“‹Chrome7/18/2023 Safari9/15/2025790
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.scroll-timeline-name.none πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.text-wrap.pretty πŸ“‹Chrome9/12/2023 Safari9/15/2025734
css.properties.text-wrap-style.pretty πŸ“‹Chrome10/15/2024 Safari9/15/2025335
css.properties.timeline-scope πŸ“‹Chrome8/15/2023 Safari9/15/2025762
css.properties.timeline-scope.none πŸ“‹Chrome8/15/2023 Safari9/15/2025762
css.properties.top.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.properties.top.anchor-size πŸ“‹Chrome1/14/2025 Safari9/15/2025244
css.properties.view-timeline πŸ“‹Chrome7/18/2023 Safari9/15/2025790
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline.none πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.view-timeline-axis πŸ“‹Chrome7/18/2023 Safari9/15/2025790
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline-axis.block πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.view-timeline-axis.inline πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.view-timeline-axis.x πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.view-timeline-axis.y πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.view-timeline-inset πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.view-timeline-inset.auto πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.view-timeline-name πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.view-timeline-name.none πŸ“‹Chrome7/18/2023 Safari9/15/2025790
css.properties.width.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.types.anchor πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.types.anchor-size πŸ“‹Chrome5/14/2024 Safari9/15/2025489
css.types.anchor-size.inset_margin Chrome1/14/2025 Safari9/15/2025244
css.types.calc.typed_division_produces_unitless_number πŸ“‹Chrome9/2/2025 Safari9/15/202513
css.types.progress πŸ“‹Chrome6/24/2025 Safari9/15/202583
css.types.sign.typed_division_produces_unitless_number πŸ“‹Chrome9/2/2025 Safari9/15/202513
css.at-rules.font-face.font-feature-settings πŸ“‹Safari9/20/2016 Chrome9/2/20253269
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.
css.properties.text-autospace πŸ“‹Safari3/31/2025 Chrome9/2/2025155
css.properties.text-autospace.no-autospace πŸ“‹Safari3/31/2025 Chrome9/2/2025155
css.properties.text-autospace.normal πŸ“‹Safari3/31/2025 Chrome9/2/2025155

2025/6

API First Browser Date Last Browser Date Days Notes
css.properties.height.stretch πŸ“‹Safari9/30/2015 Chrome6/24/20253555
css.properties.max-height.stretch πŸ“‹Safari9/30/2015 Chrome6/24/20253555
css.properties.max-width.stretch πŸ“‹Safari10/22/2013 Chrome6/24/20254263
css.properties.min-height.stretch Safari9/30/2015 Chrome6/24/20253555
css.properties.min-width.stretch Safari10/22/2013 Chrome6/24/20254263
css.properties.width.stretch πŸ“‹Safari10/22/2013 Chrome6/24/20254263
css.types.abs πŸ“‹Safari3/14/2022 Chrome6/24/20251198
css.types.sign πŸ“‹Safari3/14/2022 Chrome6/24/20251198

2025/5

API First Browser Date Last Browser Date Days Notes
css.properties.view-transition-name.match-element πŸ“‹Safari3/31/2025 Chrome5/27/202557

2025/4

API First Browser Date Last Browser Date Days Notes
css.properties.print-color-adjust πŸ“‹Safari3/14/2022 Chrome4/29/20251142
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 Chrome4/29/20254661
css.properties.print-color-adjust.exact πŸ“‹Safari7/25/2012 Chrome4/29/20254661
css.types.basic-shape.shape πŸ“‹Safari3/31/2025 Chrome4/1/20251
css.types.gradient.conic-gradient.single_color_stop πŸ“‹Safari3/31/2025 Chrome4/1/20251
css.types.gradient.linear-gradient.single_color_stop πŸ“‹Safari3/31/2025 Chrome4/1/20251
css.types.gradient.radial-gradient.single_color_stop πŸ“‹Safari3/31/2025 Chrome4/1/20251
css.types.gradient.repeating-conic-gradient.single_color_stop πŸ“‹Safari3/31/2025 Chrome4/1/20251
css.types.gradient.repeating-linear-gradient.single_color_stop πŸ“‹Safari3/31/2025 Chrome4/1/20251
css.types.gradient.repeating-radial-gradient.single_color_stop πŸ“‹Safari3/31/2025 Chrome4/1/20251

2025/3

API First Browser Date Last Browser Date Days Notes
css.properties.animation-duration.auto πŸ“‹Chrome7/18/2023 Safari3/31/2025622
Firefox: Firefox does not currently support the auto value and only accepts values in seconds or milliseconds. It's recommended that 1ms is used until auto is supported.Firefox for Android: Firefox for Android does not currently support the auto value and only accepts values in seconds or milliseconds. It's recommended that 1ms is used until auto is supported.
css.properties.container-type.weak_containment πŸ“‹Chrome9/17/2024 Safari3/31/2025195
css.properties.writing-mode.sideways-lr Chrome1/14/2025 Safari3/31/202576
css.properties.writing-mode.sideways-rl Chrome1/14/2025 Safari3/31/202576
css.selectors.details-content πŸ“‹Chrome11/12/2024 Safari3/31/2025139
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.types.attr.declaration-value πŸ“‹Chrome2/4/2025 Safari3/31/202555

2025/2

API First Browser Date Last Browser Date Days Notes
css.properties.text-box πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box.auto πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box.none πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box.normal πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box.text πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box.trim-both πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box.trim-end πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box.trim-start πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box-edge πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box-edge.auto πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box-edge.text πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box-trim πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box-trim.none πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box-trim.trim-both πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box-trim.trim-end πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.properties.text-box-trim.trim-start πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.types.text-edge πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.types.text-edge.alphabetic πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.types.text-edge.cap πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.types.text-edge.ex πŸ“‹Safari12/11/2024 Chrome2/4/202555
css.types.text-edge.text πŸ“‹Safari12/11/2024 Chrome2/4/202555

2024/12

API First Browser Date Last Browser Date Days Notes
css.at-rules.page πŸ“‹Chrome5/21/2009 Safari12/11/20245683
css.at-rules.page.size πŸ“‹Chrome10/25/2011 Safari12/11/20244796
css.at-rules.page.size.jis-b4 πŸ“‹Chrome5/19/2020 Safari12/11/20241667
css.at-rules.page.size.jis-b5 πŸ“‹Chrome5/19/2020 Safari12/11/20241667
css.at-rules.view-transition πŸ“‹Chrome6/11/2024 Safari12/11/2024183
css.properties.ruby-align πŸ“‹Chrome8/20/2024 Safari12/11/2024113
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 πŸ“‹Chrome8/20/2024 Safari12/11/2024113
css.properties.ruby-align.space-around πŸ“‹Chrome8/20/2024 Safari12/11/2024113
css.properties.ruby-align.space-between πŸ“‹Chrome8/20/2024 Safari12/11/2024113
css.properties.ruby-align.start πŸ“‹Chrome8/20/2024 Safari12/11/2024113
css.properties.ruby-position πŸ“‹Chrome7/27/2020 Safari12/11/20241598
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.inter-character Chrome7/27/2020 Safari12/11/20241598
Chrome: This value is only supported with the prefixed version of the property.Chrome Android: This value is only supported with the prefixed version of the property.Edge: This value is only supported with the prefixed version of the property.Quest Browser: This value is only supported with the prefixed version of the property.Opera: This value is only supported with the prefixed version of the property.Opera Android: This value is only supported with the prefixed version of the property.Samsung Internet: This value is only supported with the prefixed version of the property.WebView Android: This value is only supported with the prefixed version of the property.
css.properties.ruby-position.over Chrome7/27/2020 Safari12/11/20241598
css.properties.ruby-position.under Chrome7/27/2020 Safari12/11/20241598
css.properties.scrollbar-gutter πŸ“‹Chrome9/21/2021 Safari12/11/20241177
css.properties.scrollbar-gutter.auto πŸ“‹Chrome9/21/2021 Safari12/11/20241177
css.properties.scrollbar-gutter.stable πŸ“‹Chrome9/21/2021 Safari12/11/20241177
css.properties.scrollbar-width πŸ“‹Chrome1/23/2024 Safari12/11/2024323
css.properties.scrollbar-width.auto πŸ“‹Chrome1/23/2024 Safari12/11/2024323
css.properties.scrollbar-width.none πŸ“‹Chrome1/23/2024 Safari12/11/2024323
css.properties.scrollbar-width.thin πŸ“‹Chrome1/23/2024 Safari12/11/2024323
css.properties.text-underline-offset.percentage πŸ“‹Chrome11/17/2020 Safari12/11/20241485
css.properties.text-underline-position.left πŸ“‹Chrome12/4/2018 Safari12/11/20242199
css.properties.text-underline-position.right πŸ“‹Chrome12/4/2018 Safari12/11/20242199
css.properties.view-transition-class πŸ“‹Chrome5/14/2024 Safari12/11/2024211
css.properties.view-transition-class.none πŸ“‹Chrome5/14/2024 Safari12/11/2024211
css.selectors.active-view-transition-type πŸ“‹Chrome5/14/2024 Safari12/11/2024211
css.selectors.target-text πŸ“‹Chrome3/2/2021 Safari12/11/20241380

2024/11

API First Browser Date Last Browser Date Days Notes
css.properties.font-variant-emoji πŸ“‹Safari5/13/2024 Chrome11/12/2024183

2024/10

API First Browser Date Last Browser Date Days Notes
css.properties.box-decoration-break πŸ“‹Safari10/22/2013 Chrome10/15/20244011
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 Chrome10/15/20244011
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 Chrome10/15/20244011
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 πŸ“‹Safari3/5/2024 Chrome10/15/2024224
css.properties.text-wrap.stable πŸ“‹Safari5/13/2024 Chrome10/15/2024155
css.properties.text-wrap-mode πŸ“‹Safari3/5/2024 Chrome10/15/2024224
css.properties.text-wrap-mode.nowrap Safari3/5/2024 Chrome10/15/2024224
css.properties.text-wrap-mode.wrap Safari3/5/2024 Chrome10/15/2024224
css.properties.text-wrap-style πŸ“‹Safari5/13/2024 Chrome10/15/2024155
css.properties.text-wrap-style.auto πŸ“‹Safari5/13/2024 Chrome10/15/2024155
css.properties.text-wrap-style.balance πŸ“‹Safari5/13/2024 Chrome10/15/2024155
css.properties.text-wrap-style.stable πŸ“‹Safari5/13/2024 Chrome10/15/2024155

2024/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.container.style_queries_for_custom_properties πŸ“‹Chrome3/7/2023 Safari9/16/2024559
Safari: The document element cannot be a container. See bug 271040.Safari on iOS: The document element cannot be a container. See bug 271040.WebView on iOS: The document element cannot be a container. See bug 271040.
css.properties.backdrop-filter πŸ“‹Chrome7/30/2019 Safari9/16/20241875
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 πŸ“‹Chrome8/25/2020 Safari9/16/20241483
css.properties.content-visibility.hidden πŸ“‹Chrome8/25/2020 Safari9/16/20241483
css.properties.content-visibility.is_transitionable πŸ“‹Chrome9/12/2023 Safari9/16/2024370
css.properties.content-visibility.keyframe_animatable πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.content-visibility.visible πŸ“‹Chrome8/25/2020 Safari9/16/20241483
css.properties.display.is_transitionable πŸ“‹Chrome9/12/2023 Safari9/16/2024370
css.properties.display.keyframe_animatable πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.basic_shape πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.border-box πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.content-box πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.fill-box πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.none πŸ“‹Chrome2/4/2020 Safari9/16/20241686
css.properties.offset-path.padding-box πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.stroke-box πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.view-box πŸ“‹Chrome8/15/2023 Safari9/16/2024398
css.properties.transition-behavior.transitionable_content-visibility πŸ“‹Chrome9/12/2023 Safari9/16/2024370
css.properties.transition-behavior.transitionable_display πŸ“‹Chrome9/12/2023 Safari9/16/2024370
css.properties.view-transition-name πŸ“‹Chrome3/7/2023 Safari9/16/2024559
css.properties.view-transition-name.none πŸ“‹Chrome3/7/2023 Safari9/16/2024559
css.properties.white-space.collapse πŸ“‹Chrome5/30/2023 Safari9/16/2024475
css.properties.white-space.preserve πŸ“‹Chrome5/30/2023 Safari9/16/2024475
css.properties.white-space.preserve-breaks πŸ“‹Chrome5/30/2023 Safari9/16/2024475
css.properties.white-space.wrap πŸ“‹Chrome5/30/2023 Safari9/16/2024475
css.selectors.-webkit-slider-runnable-track Chrome3/26/2013 Safari9/16/20244192
css.selectors.-webkit-slider-thumb Chrome1/14/2014 Safari9/16/20243898
css.selectors.active-view-transition πŸ“‹Chrome5/14/2024 Safari9/16/2024125
css.selectors.view-transition πŸ“‹Chrome1/10/2023 Safari9/16/2024615
css.selectors.view-transition-group πŸ“‹Chrome1/10/2023 Safari9/16/2024615
css.selectors.view-transition-image-pair πŸ“‹Chrome1/10/2023 Safari9/16/2024615
css.selectors.view-transition-new πŸ“‹Chrome1/10/2023 Safari9/16/2024615
css.selectors.view-transition-old πŸ“‹Chrome1/10/2023 Safari9/16/2024615
css.types.color.color.relative_syntax πŸ“‹Chrome10/31/2023 Safari9/16/2024321
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 Chrome1/23/2024 Safari9/16/2024237
css.types.color.hsl.relative_syntax πŸ“‹Chrome5/14/2024 Safari9/16/2024125
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 Chrome1/23/2024 Safari9/16/2024237
css.types.color.hwb.relative_syntax πŸ“‹Chrome5/14/2024 Safari9/16/2024125
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 πŸ“‹Chrome10/31/2023 Safari9/16/2024321
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 πŸ“‹Chrome2/20/2024 Safari9/16/2024209
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 Chrome2/20/2024 Safari9/16/2024209
css.types.color.rgb.relative_syntax πŸ“‹Chrome2/20/2024 Safari9/16/2024209
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.

2024/7

API First Browser Date Last Browser Date Days Notes
css.properties.align-content.flex_context.safe_unsafe Chrome7/18/2023 Safari7/29/2024377
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 Chrome7/18/2023 Safari7/29/2024377
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 Chrome7/18/2023 Safari7/29/2024377
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 Chrome7/18/2023 Safari7/29/2024377
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 πŸ“‹Safari3/27/2023 Chrome7/23/2024484
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 Chrome7/23/2024309
css.properties.font-size-adjust.none πŸ“‹Safari3/27/2023 Chrome7/23/2024484
css.properties.font-size-adjust.two-values Safari9/18/2023 Chrome7/23/2024309

2024/5

API First Browser Date Last Browser Date Days Notes
css.selectors.state πŸ“‹Safari3/5/2024 Chrome5/14/202470
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 Chrome5/14/2024792
css.types.mod.mixed_type_parameters πŸ“‹Safari12/11/2023 Chrome5/14/2024155
css.types.rem πŸ“‹Safari3/14/2022 Chrome5/14/2024792
css.types.rem.mixed_type_parameters πŸ“‹Safari12/11/2023 Chrome5/14/2024155
css.types.round πŸ“‹Safari3/14/2022 Chrome5/14/2024792
css.types.round.mixed_type_parameters πŸ“‹Safari12/11/2023 Chrome5/14/2024155
css.at-rules.import.supports πŸ“‹Chrome2/20/2024 Safari5/13/202483
css.at-rules.starting-style πŸ“‹Chrome9/12/2023 Safari5/13/2024244
css.properties.text-wrap.balance πŸ“‹Chrome5/30/2023 Safari5/13/2024349
css.types.color.light-dark πŸ“‹Chrome3/19/2024 Safari5/13/202455

2024/4

API First Browser Date Last Browser Date Days Notes
css.properties.direction.vertical_slider_direction Safari5/18/2023 Chrome4/16/2024334
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 Safari3/5/2024 Chrome4/16/202442
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

2024/3

API First Browser Date Last Browser Date Days Notes
css.properties.align-content.block_context πŸ“‹Safari3/5/2024 Chrome3/19/202414
css.properties.align-content.multicol_context πŸ“‹Safari3/5/2024 Chrome3/19/202414
css.properties.paint-order πŸ“‹Safari9/19/2017 Chrome3/19/20242373
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
css.at-rules.scope πŸ“‹Chrome10/10/2023 Safari3/5/2024147
css.properties.content.alt_text Chrome9/10/2019 Safari3/5/20241638
css.properties.rx πŸ“‹Chrome5/19/2015 Safari3/5/20243213
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 πŸ“‹Chrome8/31/2016 Safari3/5/20242743
css.properties.ry πŸ“‹Chrome5/19/2015 Safari3/5/20243213
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 πŸ“‹Chrome8/31/2016 Safari3/5/20242743
css.properties.text-decoration-thickness.percentage Chrome11/17/2020 Safari3/5/20241204
css.properties.text-wrap πŸ“‹Chrome5/30/2023 Safari3/5/2024280
css.properties.text-wrap.nowrap πŸ“‹Chrome5/30/2023 Safari3/5/2024280
css.properties.text-wrap.wrap πŸ“‹Chrome5/30/2023 Safari3/5/2024280
css.properties.transition.transition-behavior Chrome9/12/2023 Safari3/5/2024175
css.properties.transition-behavior πŸ“‹Chrome9/12/2023 Safari3/5/2024175
css.properties.transition-behavior.allow-discrete πŸ“‹Chrome9/12/2023 Safari3/5/2024175
css.properties.transition-behavior.normal πŸ“‹Chrome9/12/2023 Safari3/5/2024175
css.properties.white-space-collapse πŸ“‹Chrome5/30/2023 Safari3/5/2024280
css.properties.white-space-collapse.break-spaces πŸ“‹Chrome5/30/2023 Safari3/5/2024280
css.properties.white-space-collapse.collapse πŸ“‹Chrome5/30/2023 Safari3/5/2024280
css.properties.white-space-collapse.preserve πŸ“‹Chrome5/30/2023 Safari3/5/2024280
css.properties.white-space-collapse.preserve-breaks πŸ“‹Chrome5/30/2023 Safari3/5/2024280
css.selectors.backdrop.inherit_from_originating_element Chrome2/20/2024 Safari3/5/202414
css.selectors.grammar-error πŸ“‹Chrome1/23/2024 Safari3/5/202442
css.selectors.spelling-error πŸ“‹Chrome1/23/2024 Safari3/5/202442

2024/2

API First Browser Date Last Browser Date Days Notes
css.types.color.oklab.relative_syntax πŸ“‹Safari3/27/2023 Chrome2/20/2024330
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.

2023/12

API First Browser Date Last Browser Date Days Notes
css.properties.counter-set πŸ“‹Chrome8/25/2020 Safari12/11/20231203
css.properties.counter-set.list-item πŸ“‹Chrome8/25/2020 Safari12/11/20231203
css.properties.counter-set.none πŸ“‹Chrome8/25/2020 Safari12/11/20231203
css.properties.mask-border πŸ“‹Chrome12/11/2008 Safari12/11/20235478
css.properties.mask-border-outset πŸ“‹Chrome12/11/2008 Safari12/11/20235478
css.properties.mask-border-repeat πŸ“‹Chrome12/11/2008 Safari12/11/20235478
css.properties.mask-border-slice πŸ“‹Chrome12/11/2008 Safari12/11/20235478
css.properties.mask-border-source πŸ“‹Chrome12/11/2008 Safari12/11/20235478
css.properties.mask-border-width πŸ“‹Chrome12/11/2008 Safari12/11/20235478
css.properties.offset-position.normal πŸ“‹Chrome8/15/2023 Safari12/11/2023118
css.selectors.highlight πŸ“‹Chrome9/2/2022 Safari12/11/2023465
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.
css.selectors.nesting πŸ“‹Chrome12/5/2023 Safari12/11/20236
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.basic-shape.rect πŸ“‹Chrome10/31/2023 Safari12/11/202341
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 πŸ“‹Chrome10/31/2023 Safari12/11/202341
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.easing-function.linear-function πŸ“‹Chrome5/2/2023 Safari12/11/2023223
css.types.length.cap Chrome10/10/2023 Safari12/11/202362
css.types.length.rcap πŸ“‹Chrome10/10/2023 Safari12/11/202362
css.types.length.rch πŸ“‹Chrome3/7/2023 Safari12/11/2023279
css.types.length.rex πŸ“‹Chrome3/7/2023 Safari12/11/2023279
css.types.length.ric πŸ“‹Chrome3/7/2023 Safari12/11/2023279
css.types.ray.position Chrome8/15/2023 Safari12/11/2023118
css.at-rules.media.scripting πŸ“‹Safari9/18/2023 Chrome12/5/202378
css.properties.background-clip.text πŸ“‹Safari9/16/2020 Chrome12/5/20231175
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 πŸ“‹Safari3/14/2022 Chrome12/5/2023631
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 πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-composite πŸ“‹Safari3/14/2022 Chrome12/5/2023631
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 πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-composite.exclude πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-composite.intersect πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-composite.subtract πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-image πŸ“‹Safari3/14/2022 Chrome12/5/2023631
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 πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-mode.alpha πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-mode.luminance πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-mode.match-source πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-origin πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-position πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-repeat πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.properties.mask-size πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.selectors.dir πŸ“‹Safari3/27/2023 Chrome12/5/2023253
css.types.exp πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.types.hypot πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.types.log πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.types.pow πŸ“‹Safari3/14/2022 Chrome12/5/2023631
css.types.sqrt πŸ“‹Safari3/14/2022 Chrome12/5/2023631

2023/10

API First Browser Date Last Browser Date Days Notes
css.properties.clip-path.border-box πŸ“‹Safari9/19/2019 Chrome10/31/20231503
css.properties.clip-path.content-box πŸ“‹Safari9/19/2019 Chrome10/31/20231503
css.properties.clip-path.fill-box πŸ“‹Safari3/24/2020 Chrome10/31/20231316
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 πŸ“‹Safari9/19/2019 Chrome10/31/20231503
css.properties.clip-path.padding-box πŸ“‹Safari9/19/2019 Chrome10/31/20231503
css.properties.clip-path.stroke-box πŸ“‹Safari3/24/2020 Chrome10/31/20231316
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 πŸ“‹Safari3/24/2020 Chrome10/31/20231316
css.selectors.user-invalid πŸ“‹Safari5/18/2023 Chrome10/31/2023166
css.selectors.user-valid πŸ“‹Safari5/18/2023 Chrome10/31/2023166
css.types.calc.color_component Safari3/27/2023 Chrome10/31/2023218
css.types.color.lab.relative_syntax πŸ“‹Safari3/27/2023 Chrome10/31/2023218
css.properties.clear.inline-end πŸ“‹Safari9/20/2021 Chrome10/10/2023750
css.properties.clear.inline-start πŸ“‹Safari9/20/2021 Chrome10/10/2023750
css.properties.float.inline-end πŸ“‹Safari9/20/2021 Chrome10/10/2023750
css.properties.float.inline-start πŸ“‹Safari9/20/2021 Chrome10/10/2023750
css.properties.resize.block Safari9/12/2022 Chrome10/10/2023393
css.properties.resize.inline Safari9/12/2022 Chrome10/10/2023393
css.properties.transform-box.border-box πŸ“‹Safari9/19/2017 Chrome10/10/20232212
css.properties.transform-box.content-box πŸ“‹Safari3/24/2020 Chrome10/10/20231295
css.properties.transform-box.stroke-box πŸ“‹Safari3/24/2020 Chrome10/10/20231295

2023/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.counter-style πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.counter-style.additive-symbols πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.counter-style.fallback πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.counter-style.negative πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.counter-style.pad πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.counter-style.prefix πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.counter-style.range πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.counter-style.suffix πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.counter-style.symbols πŸ“‹Chrome5/25/2021 Safari9/18/2023846
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 πŸ“‹Chrome5/25/2021 Safari9/18/2023846
css.at-rules.font-face.size-adjust πŸ“‹Chrome7/20/2021 Safari9/18/2023790
css.at-rules.font-face.src.tech_keyword Chrome11/29/2022 Safari9/18/2023293
css.at-rules.media.overflow-block πŸ“‹Chrome5/2/2023 Safari9/18/2023139
css.at-rules.media.overflow-inline πŸ“‹Chrome5/2/2023 Safari9/18/2023139
css.at-rules.media.update πŸ“‹Chrome5/2/2023 Safari9/18/2023139
css.at-rules.supports.font-format Chrome11/29/2022 Safari9/18/2023293
css.at-rules.supports.font-tech Chrome11/29/2022 Safari9/18/2023293
css.properties.background-image.image-set πŸ“‹Chrome5/2/2023 Safari9/18/2023139
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 πŸ“‹Chrome10/19/2021 Safari9/18/2023699
css.properties.contain-intrinsic-block-size.none πŸ“‹Chrome2/1/2022 Safari9/18/2023594
css.properties.contain-intrinsic-height πŸ“‹Chrome10/19/2021 Safari9/18/2023699
css.properties.contain-intrinsic-height.none πŸ“‹Chrome2/1/2022 Safari9/18/2023594
css.properties.contain-intrinsic-inline-size πŸ“‹Chrome10/19/2021 Safari9/18/2023699
css.properties.contain-intrinsic-inline-size.none πŸ“‹Chrome2/1/2022 Safari9/18/2023594
css.properties.contain-intrinsic-size πŸ“‹Chrome5/19/2020 Safari9/18/20231217
css.properties.contain-intrinsic-size.auto_none Chrome9/12/2023 Safari9/18/20236
css.properties.contain-intrinsic-size.none πŸ“‹Chrome2/1/2022 Safari9/18/2023594
css.properties.contain-intrinsic-width πŸ“‹Chrome10/19/2021 Safari9/18/2023699
css.properties.contain-intrinsic-width.none πŸ“‹Chrome2/1/2022 Safari9/18/2023594
css.properties.content.image-set πŸ“‹Chrome5/2/2023 Safari9/18/2023139
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 πŸ“‹Chrome9/27/2022 Safari9/18/2023356
css.properties.hyphens πŸ“‹Chrome12/1/2016 Safari9/18/20232482
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 Chrome9/1/2015 Safari9/18/20232939
css.properties.list-style-type.ethiopic-halehame-am Chrome9/1/2015 Safari9/18/20232939
css.properties.offset.normal πŸ“‹Chrome8/15/2023 Safari9/18/202334
css.properties.offset-path.url πŸ“‹Chrome8/15/2023 Safari9/18/202334
css.selectors.backdrop.popover Chrome5/30/2023 Safari9/18/2023111
css.selectors.only-child.no_parent_required Chrome3/9/2017 Safari9/18/20232384
css.selectors.popover-open πŸ“‹Chrome5/30/2023 Safari9/18/2023111
css.types.image.image-set πŸ“‹Chrome5/2/2023 Safari9/18/2023139
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.types.ray.size Chrome8/15/2023 Safari9/18/202334
css.properties.font-variant-position πŸ“‹Safari3/21/2016 Chrome9/12/20232731
css.properties.font-variant-position.normal πŸ“‹Safari3/21/2016 Chrome9/12/20232731
css.properties.font-variant-position.sub πŸ“‹Safari3/21/2016 Chrome9/12/20232731
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 πŸ“‹Safari3/21/2016 Chrome9/12/20232731
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 πŸ“‹Safari9/12/2022 Chrome9/12/2023365
css.properties.grid-template-rows.subgrid πŸ“‹Safari9/12/2022 Chrome9/12/2023365

2023/8

API First Browser Date Last Browser Date Days Notes
css.properties.offset.auto πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.border-box πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.bottom πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.center πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.content-box πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.fill-box πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.left πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.padding-box πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.right πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.stroke-box πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.top πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset.view-box πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-anchor πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-anchor.auto πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-anchor.bottom πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-anchor.center πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-anchor.left πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-anchor.right πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-anchor.top πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-path.ray πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-position πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-position.auto πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-position.bottom πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-position.center πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-position.left πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-position.right πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.properties.offset-position.top πŸ“‹Safari9/12/2022 Chrome8/15/2023337
css.types.color.lab.mixed_type_parameters Safari12/13/2022 Chrome8/15/2023245
css.types.color.lch.mixed_type_parameters Safari12/13/2022 Chrome8/15/2023245
css.types.color.oklab.mixed_type_parameters Safari12/13/2022 Chrome8/15/2023245
css.types.color.oklch.mixed_type_parameters Safari12/13/2022 Chrome8/15/2023245
css.types.ray πŸ“‹Safari9/12/2022 Chrome8/15/2023337

2023/7

API First Browser Date Last Browser Date Days Notes
css.properties.display.multi-keyword_values Safari9/20/2021 Chrome7/18/2023666
css.types.color.system-color.accentcolor_accentcolortext πŸ“‹Safari5/18/2023 Chrome7/18/202361
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

2023/5

API First Browser Date Last Browser Date Days Notes
css.types.overflow.overlay Safari9/17/2018 Chrome5/30/20231716
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/4

API First Browser Date Last Browser Date Days Notes
css.properties.animation-composition πŸ“‹Safari9/12/2022 Chrome4/4/2023204
css.properties.animation-composition.accumulate πŸ“‹Safari9/12/2022 Chrome4/4/2023204
css.properties.animation-composition.add πŸ“‹Safari9/12/2022 Chrome4/4/2023204
css.properties.animation-composition.replace πŸ“‹Safari9/12/2022 Chrome4/4/2023204
css.properties.hyphens.language_czech Safari3/21/2016 Chrome4/4/20232570
css.properties.hyphens.language_dutch Safari7/20/2011 Chrome4/4/20234276
css.properties.hyphens.language_italian Safari7/20/2011 Chrome4/4/20234276
css.properties.hyphens.language_russian Safari7/20/2011 Chrome4/4/20234276
css.properties.hyphens.language_swedish Safari7/20/2011 Chrome4/4/20234276
css.properties.hyphens.language_ukrainian Safari3/21/2016 Chrome4/4/20232570

2023/3

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.or_syntax Chrome8/2/2022 Safari3/27/2023237
css.at-rules.media.range_syntax Chrome8/2/2022 Safari3/27/2023237
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 πŸ“‹Chrome8/2/2022 Safari3/27/2023237
css.at-rules.property πŸ“‹Chrome8/25/2020 Safari3/27/2023944
css.at-rules.property.inherits πŸ“‹Chrome8/25/2020 Safari3/27/2023944
css.at-rules.property.initial-value πŸ“‹Chrome8/25/2020 Safari3/27/2023944
css.at-rules.property.syntax πŸ“‹Chrome8/25/2020 Safari3/27/2023944
css.properties.font-size.xxx-large Chrome12/10/2019 Safari3/27/20231203
css.properties.font-synthesis-small-caps πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-small-caps.auto πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-small-caps.none πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-style πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-style.auto πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-style.none πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-weight πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-weight.auto πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-weight.none πŸ“‹Chrome1/4/2022 Safari3/27/2023447
css.properties.outline πŸ“‹Chrome9/21/2021 Safari3/27/2023552
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 Chrome9/4/2018 Safari3/27/20231665
css.selectors.fullscreen πŸ“‹Chrome12/4/2018 Safari3/27/20231574
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.
css.types.length.lh πŸ“‹Chrome1/10/2023 Safari3/27/202376
css.types.length.rlh πŸ“‹Chrome3/7/2023 Safari3/27/202320
css.at-rules.font-feature-values πŸ“‹Safari3/21/2016 Chrome3/7/20232542
css.at-rules.font-feature-values.annotation Safari3/21/2016 Chrome3/7/20232542
css.at-rules.font-feature-values.character-variant Safari3/21/2016 Chrome3/7/20232542
css.at-rules.font-feature-values.historical-forms Safari3/21/2016 Chrome3/7/20232542
css.at-rules.font-feature-values.ornaments Safari3/21/2016 Chrome3/7/20232542
css.at-rules.font-feature-values.styleset Safari3/21/2016 Chrome3/7/20232542
css.at-rules.font-feature-values.stylistic Safari3/21/2016 Chrome3/7/20232542
css.at-rules.font-feature-values.swash Safari3/21/2016 Chrome3/7/20232542
css.properties.font-variant.historical-forms πŸ“‹Safari3/21/2016 Chrome3/7/20232542
css.properties.font-variant-alternates πŸ“‹Safari3/21/2016 Chrome3/7/20232542
css.properties.font-variant-alternates.annotation πŸ“‹Safari12/13/2022 Chrome3/7/202384
css.properties.font-variant-alternates.character_variant πŸ“‹Safari12/13/2022 Chrome3/7/202384
css.properties.font-variant-alternates.historical-forms πŸ“‹Safari3/21/2016 Chrome3/7/20232542
css.properties.font-variant-alternates.normal πŸ“‹Safari3/21/2016 Chrome3/7/20232542
css.properties.font-variant-alternates.ornaments πŸ“‹Safari12/13/2022 Chrome3/7/202384
css.properties.font-variant-alternates.styleset πŸ“‹Safari12/13/2022 Chrome3/7/202384
css.properties.font-variant-alternates.stylistic πŸ“‹Safari12/13/2022 Chrome3/7/202384
css.properties.font-variant-alternates.swash πŸ“‹Safari12/13/2022 Chrome3/7/202384
css.selectors.nth-child.of_syntax Safari9/30/2015 Chrome3/7/20232715
css.selectors.nth-last-child.of_syntax Safari9/30/2015 Chrome3/7/20232715
css.types.acos πŸ“‹Safari3/14/2022 Chrome3/7/2023358
css.types.asin πŸ“‹Safari3/14/2022 Chrome3/7/2023358
css.types.atan πŸ“‹Safari3/14/2022 Chrome3/7/2023358
css.types.atan2 πŸ“‹Safari3/14/2022 Chrome3/7/2023358
css.types.color.color πŸ“‹Safari9/20/2021 Chrome3/7/2023533
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 Chrome3/7/2023533
css.types.color.color-mix πŸ“‹Safari12/13/2022 Chrome3/7/202384
css.types.color.lab πŸ“‹Safari9/20/2021 Chrome3/7/2023533
css.types.color.lch πŸ“‹Safari9/20/2021 Chrome3/7/2023533
css.types.color.oklab πŸ“‹Safari3/14/2022 Chrome3/7/2023358
css.types.color.oklch πŸ“‹Safari3/14/2022 Chrome3/7/2023358
css.types.cos πŸ“‹Safari3/14/2022 Chrome3/7/2023358
css.types.gradient.conic-gradient.hue_interpolation_method Safari12/13/2022 Chrome3/7/202384
css.types.gradient.conic-gradient.interpolation_color_space Safari12/13/2022 Chrome3/7/202384
css.types.gradient.linear-gradient.hue_interpolation_method Safari12/13/2022 Chrome3/7/202384
css.types.gradient.linear-gradient.interpolation_color_space Safari12/13/2022 Chrome3/7/202384
css.types.gradient.radial-gradient.hue_interpolation_method Safari12/13/2022 Chrome3/7/202384
css.types.gradient.radial-gradient.interpolation_color_space Safari12/13/2022 Chrome3/7/202384
css.types.gradient.repeating-conic-gradient.hue_interpolation_method Safari12/13/2022 Chrome3/7/202384
css.types.gradient.repeating-conic-gradient.interpolation_color_space Safari12/13/2022 Chrome3/7/202384
css.types.gradient.repeating-linear-gradient.hue_interpolation_method Safari12/13/2022 Chrome3/7/202384
css.types.gradient.repeating-linear-gradient.interpolation_color_space Safari12/13/2022 Chrome3/7/202384
css.types.gradient.repeating-radial-gradient.hue_interpolation_method Safari12/13/2022 Chrome3/7/202384
css.types.gradient.repeating-radial-gradient.interpolation_color_space Safari12/13/2022 Chrome3/7/202384
css.types.sin πŸ“‹Safari3/14/2022 Chrome3/7/2023358
css.types.tan πŸ“‹Safari3/14/2022 Chrome3/7/2023358

2023/2

API First Browser Date Last Browser Date Days Notes
css.properties.font-variant.sub πŸ“‹Safari3/21/2016 Chrome2/7/20232514
css.properties.font-variant.super πŸ“‹Safari3/21/2016 Chrome2/7/20232514
css.properties.initial-letter πŸ“‹Safari9/30/2015 Chrome2/7/20232687
Safari: See bug 229090 for the unprefixed property.Safari on iOS: See bug 229090 for the unprefixed property.Safari on iOS: Does not support decimal values. See bug 296785.WebView on iOS: See bug 229090 for the unprefixed property.WebView on iOS: Does not support decimal values. See bug 296785.
css.properties.initial-letter.normal πŸ“‹Safari9/30/2015 Chrome2/7/20232687
css.selectors.autofill πŸ“‹Safari9/20/2021 Chrome2/7/2023505
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.selectors.picture-in-picture πŸ“‹Safari3/24/2020 Chrome2/7/20231050
css.types.calc-keyword.e Safari3/14/2022 Chrome2/7/2023330

2023/1

API First Browser Date Last Browser Date Days Notes
css.properties.container.normal πŸ“‹Safari9/12/2022 Chrome1/10/2023120
css.properties.math-style πŸ“‹Safari4/26/2021 Chrome1/10/2023624
css.properties.math-style.compact πŸ“‹Safari4/26/2021 Chrome1/10/2023624
css.properties.math-style.normal πŸ“‹Safari4/26/2021 Chrome1/10/2023624
css.types.calc-keyword.pi Safari3/14/2022 Chrome1/10/2023302

2022/12

API First Browser Date Last Browser Date Days Notes
css.properties.align-items.flex_context.last_baseline Chrome11/29/2022 Safari12/13/202214
css.properties.align-self.flex_context.last_baseline Chrome11/29/2022 Safari12/13/202214

2022/11

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.src.format_keyword Safari6/8/2009 Chrome11/29/20224922
css.types.length.vb Safari3/14/2022 Chrome11/29/2022260
css.types.length.vi Safari3/14/2022 Chrome11/29/2022260
css.types.length.viewport_percentage_units_dynamic Safari3/14/2022 Chrome11/29/2022260
css.types.length.viewport_percentage_units_large Safari3/14/2022 Chrome11/29/2022260
css.types.length.viewport_percentage_units_small Safari3/14/2022 Chrome11/29/2022260

2022/10

API First Browser Date Last Browser Date Days Notes
css.properties.grid-template-columns.animation Safari9/12/2022 Chrome10/25/202243
css.properties.grid-template-rows.animation Safari9/12/2022 Chrome10/25/202243

2022/9

API First Browser Date Last Browser Date Days Notes
css.types.length.ic Safari3/14/2022 Chrome9/27/2022197
css.at-rules.container πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.at-rules.media.forced-colors πŸ“‹Chrome3/2/2021 Safari9/12/2022559
css.at-rules.media.resolution πŸ“‹Chrome8/20/2013 Safari9/12/20223310
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.properties.contain.inline-size πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container.inline-size πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container.none πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container.scroll-state πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container.size πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container-name πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container-name.none πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container-type πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container-type.inline-size πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container-type.normal πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.container-type.size πŸ“‹Chrome9/2/2022 Safari9/12/202210
css.properties.flex.fit-content πŸ“‹Chrome9/21/2021 Safari9/12/2022356
css.properties.flex.max-content πŸ“‹Chrome9/21/2021 Safari9/12/2022356
css.properties.flex.min-content πŸ“‹Chrome9/21/2021 Safari9/12/2022356
css.properties.flex-basis.fit-content Chrome9/21/2021 Safari9/12/2022356
css.properties.flex-basis.max-content Chrome9/21/2021 Safari9/12/2022356
css.properties.flex-basis.min-content Chrome9/21/2021 Safari9/12/2022356
css.properties.offset πŸ“‹Chrome12/1/2016 Safari9/12/20222111
css.properties.offset.none πŸ“‹Chrome9/5/2017 Safari9/12/20221833
css.properties.offset-distance πŸ“‹Chrome12/1/2016 Safari9/12/20222111
css.properties.offset-path.path Chrome1/23/2018 Safari9/12/20221693
css.properties.offset-rotate πŸ“‹Chrome1/25/2017 Safari9/12/20222056
css.properties.offset-rotate.auto πŸ“‹Chrome10/13/2015 Safari9/12/20222526
css.properties.offset-rotate.reverse πŸ“‹Chrome10/13/2015 Safari9/12/20222526
css.properties.overflow.clip πŸ“‹Chrome4/13/2021 Safari9/12/2022517
css.properties.overflow-x.clip πŸ“‹Chrome4/13/2021 Safari9/12/2022517
css.properties.overflow-y.clip πŸ“‹Chrome4/13/2021 Safari9/12/2022517
css.properties.overscroll-behavior πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior.auto πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior.contain πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior.none πŸ“‹Chrome12/6/2017 Safari9/12/20221741
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-block πŸ“‹Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-block.auto πŸ“‹Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-block.contain πŸ“‹Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-block.none πŸ“‹Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-inline πŸ“‹Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-inline.auto πŸ“‹Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-inline.contain πŸ“‹Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-inline.none πŸ“‹Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-x πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-x.auto πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-x.contain πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-x.none πŸ“‹Chrome12/6/2017 Safari9/12/20221741
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-y πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-y.auto πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-y.contain πŸ“‹Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-y.none πŸ“‹Chrome12/6/2017 Safari9/12/20221741
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.text-align-last πŸ“‹Chrome12/1/2015 Safari9/12/20222477
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 πŸ“‹Chrome12/1/2015 Safari9/12/20222477
css.properties.text-align-last.center πŸ“‹Chrome12/1/2015 Safari9/12/20222477
css.properties.text-align-last.end πŸ“‹Chrome12/1/2015 Safari9/12/20222477
css.properties.text-align-last.justify πŸ“‹Chrome12/1/2015 Safari9/12/20222477
css.properties.text-align-last.left πŸ“‹Chrome12/1/2015 Safari9/12/20222477
css.properties.text-align-last.right πŸ“‹Chrome12/1/2015 Safari9/12/20222477
css.properties.text-align-last.start πŸ“‹Chrome12/1/2015 Safari9/12/20222477
css.properties.user-select.all Chrome8/31/2016 Safari9/12/20222203
css.types.basic-shape.path.offset-path πŸ“‹Chrome1/25/2017 Safari9/12/20222056
css.types.calc-keyword.NaN Chrome3/1/2022 Safari9/12/2022195
css.types.calc-keyword.infinity Chrome3/1/2022 Safari9/12/2022195
css.types.length.container_query_length_units Chrome9/2/2022 Safari9/12/202210
css.types.overflow.clip Chrome4/13/2021 Safari9/12/2022517
css.types.resolution πŸ“‹Chrome8/20/2013 Safari9/12/20223310
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.types.resolution.dpcm Chrome8/20/2013 Safari9/12/20223310
css.types.resolution.dpi Chrome8/20/2013 Safari9/12/20223310
css.types.resolution.dppx Chrome8/20/2013 Safari9/12/20223310
css.types.resolution.x Chrome7/24/2018 Safari9/12/20221511
css.selectors.has πŸ“‹Safari3/14/2022 Chrome9/2/2022172
css.selectors.modal πŸ“‹Safari7/20/2022 Chrome9/2/202244

2022/8

API First Browser Date Last Browser Date Days Notes
css.properties.rotate πŸ“‹Safari4/26/2021 Chrome8/2/2022463
css.properties.rotate.none πŸ“‹Safari4/26/2021 Chrome8/2/2022463
css.properties.rotate.x_y_z_angle Safari4/26/2021 Chrome8/2/2022463
css.properties.scale πŸ“‹Safari4/26/2021 Chrome8/2/2022463
css.properties.scale.none πŸ“‹Safari4/26/2021 Chrome8/2/2022463
css.properties.translate πŸ“‹Safari4/26/2021 Chrome8/2/2022463
css.properties.translate.none πŸ“‹Safari4/26/2021 Chrome8/2/2022463

2022/7

API First Browser Date Last Browser Date Days Notes
css.properties.align-content.flex_context.start_end Chrome8/31/2021 Safari7/20/2022323
Opera: Before version 79, this value is recognized, but has no effect.Opera Android: This value is recognized, but has no effect.

2022/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-palette-values πŸ“‹Safari3/14/2022 Chrome4/26/202243
css.at-rules.font-palette-values.base-palette πŸ“‹Safari3/14/2022 Chrome4/26/202243
css.at-rules.font-palette-values.font-family πŸ“‹Safari3/14/2022 Chrome4/26/202243
css.at-rules.font-palette-values.override-colors πŸ“‹Safari3/14/2022 Chrome4/26/202243
css.properties.font-palette πŸ“‹Safari3/14/2022 Chrome4/26/202243
css.properties.font-palette.dark πŸ“‹Safari3/14/2022 Chrome4/26/202243
css.properties.font-palette.light πŸ“‹Safari3/14/2022 Chrome4/26/202243
css.properties.font-palette.normal πŸ“‹Safari3/14/2022 Chrome4/26/202243
css.types.color.hwb πŸ“‹Safari9/20/2021 Chrome4/26/2022218

2022/3

API First Browser Date Last Browser Date Days Notes
css.properties.mix-blend-mode.plus-lighter πŸ“‹Safari3/21/2016 Chrome3/29/20222199
css.at-rules.import.layer πŸ“‹Chrome3/1/2022 Safari3/14/202213
css.at-rules.layer πŸ“‹Chrome3/1/2022 Safari3/14/202213
css.properties.accent-color πŸ“‹Chrome8/31/2021 Safari3/14/2022195
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 Chrome8/31/2021 Safari3/14/2022195
css.properties.align-items.flex_context.start_end Chrome8/31/2021 Safari3/14/2022195
css.properties.align-self.flex_context.start_end Chrome8/31/2021 Safari3/14/2022195
Opera: Before version 79, this value is recognized, but has no effect.
css.properties.appearance πŸ“‹Chrome7/27/2020 Safari3/14/2022595
css.properties.appearance.auto πŸ“‹Chrome5/19/2020 Safari3/14/2022664
css.properties.backface-visibility πŸ“‹Chrome7/16/2014 Safari3/14/20222798
css.properties.background-attachment.fixed πŸ“‹Chrome12/11/2008 Safari3/14/20224841
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 πŸ“‹Chrome12/11/2008 Safari3/14/20224841
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 πŸ“‹Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.content πŸ“‹Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.layout πŸ“‹Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.none πŸ“‹Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.paint πŸ“‹Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.size πŸ“‹Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.strict πŸ“‹Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.style πŸ“‹Chrome7/20/2016 Safari3/14/20222063
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.flex-basis.content Chrome9/21/2021 Safari3/14/2022174
css.properties.justify-content.flex_context.start_end Chrome8/31/2021 Safari3/14/2022195
css.properties.mask-origin.border Chrome12/11/2008 Safari3/14/20224841
css.properties.mask-origin.content Chrome12/11/2008 Safari3/14/20224841
css.properties.mask-origin.padding Chrome12/11/2008 Safari3/14/20224841
css.properties.offset-path πŸ“‹Chrome12/1/2016 Safari3/14/20221929
Samsung Internet: path() is the only value type supported.
css.properties.overflow-wrap.anywhere πŸ“‹Chrome2/4/2020 Safari3/14/2022769
css.properties.scroll-behavior πŸ“‹Chrome9/5/2017 Safari3/14/20221651
css.properties.scroll-behavior.auto πŸ“‹Chrome9/5/2017 Safari3/14/20221651
css.properties.scroll-behavior.smooth πŸ“‹Chrome9/5/2017 Safari3/14/20221651
css.properties.text-align.match-parent πŸ“‹Chrome12/13/2011 Safari3/14/20223744
css.properties.text-combine-upright πŸ“‹Chrome1/20/2016 Safari3/14/20222245
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 πŸ“‹Chrome1/20/2016 Safari3/14/20222245
css.properties.text-combine-upright.none πŸ“‹Chrome1/20/2016 Safari3/14/20222245
css.properties.text-decoration-skip-ink πŸ“‹Chrome1/23/2018 Safari3/14/20221511
css.properties.text-decoration-skip-ink.auto πŸ“‹Chrome1/23/2018 Safari3/14/20221511
css.properties.text-decoration-skip-ink.none πŸ“‹Chrome1/23/2018 Safari3/14/20221511
css.selectors.backdrop πŸ“‹Chrome8/26/2014 Safari3/14/20222757
css.selectors.backdrop.dialog Chrome1/14/2014 Safari3/14/20222981
css.selectors.focus-visible πŸ“‹Chrome10/20/2020 Safari3/14/2022510
css.types.calc-keyword πŸ“‹Chrome3/1/2022 Safari3/14/202213
css.types.global_keywords.revert-layer πŸ“‹Chrome3/1/2022 Safari3/14/202213
css.types.transform-function.perspective.none πŸ“‹Chrome1/4/2022 Safari3/14/202269
css.properties.text-emphasis πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-color πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-position πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-position.over Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-position.under Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style.circle πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style.dot πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style.double-circle πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style.filled πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style.none πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style.open πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style.sesame πŸ“‹Safari10/22/2013 Chrome3/1/20223052
css.properties.text-emphasis-style.triangle πŸ“‹Safari10/22/2013 Chrome3/1/20223052

2022/2

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.dynamic-range πŸ“‹Safari3/24/2020 Chrome2/1/2022679
css.properties.color-scheme.only Safari9/19/2019 Chrome2/1/2022866

2022/1

API First Browser Date Last Browser Date Days Notes
css.properties.font-synthesis πŸ“‹Safari9/30/2015 Chrome1/4/20222288
css.properties.font-synthesis.none πŸ“‹Safari9/30/2015 Chrome1/4/20222288
css.properties.font-synthesis.small-caps Safari3/27/2017 Chrome1/4/20221744
css.properties.font-synthesis.style Safari3/27/2017 Chrome1/4/20221744
css.properties.font-synthesis.weight Safari3/27/2017 Chrome1/4/20221744

2021/11

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.prefers-contrast πŸ“‹Safari4/26/2021 Chrome11/15/2021203

2021/9

API First Browser Date Last Browser Date Days Notes
css.properties.flex.content πŸ“‹Safari9/20/2021 Chrome9/21/20211
css.properties.aspect-ratio πŸ“‹Chrome1/19/2021 Safari9/20/2021244
css.properties.aspect-ratio.auto πŸ“‹Chrome1/19/2021 Safari9/20/2021244
css.properties.border-end-end-radius πŸ“‹Chrome3/2/2021 Safari9/20/2021202
css.properties.border-end-start-radius πŸ“‹Chrome3/2/2021 Safari9/20/2021202
css.properties.border-start-end-radius πŸ“‹Chrome3/2/2021 Safari9/20/2021202
css.properties.border-start-start-radius πŸ“‹Chrome3/2/2021 Safari9/20/2021202
css.properties.list-style-type.cjk-decimal πŸ“‹Chrome5/25/2021 Safari9/20/2021118
css.properties.list-style-type.disclosure-closed πŸ“‹Chrome3/2/2021 Safari9/20/2021202
css.properties.list-style-type.disclosure-open πŸ“‹Chrome3/2/2021 Safari9/20/2021202
css.properties.list-style-type.ethiopic-numeric πŸ“‹Chrome5/25/2021 Safari9/20/2021118
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 πŸ“‹Chrome5/25/2021 Safari9/20/2021118
css.properties.list-style-type.japanese-informal πŸ“‹Chrome5/25/2021 Safari9/20/2021118
css.properties.list-style-type.korean-hangul-formal πŸ“‹Chrome9/1/2015 Safari9/20/20212211
css.properties.list-style-type.korean-hanja-formal πŸ“‹Chrome9/1/2015 Safari9/20/20212211
css.properties.list-style-type.korean-hanja-informal πŸ“‹Chrome9/1/2015 Safari9/20/20212211
css.properties.list-style-type.simp-chinese-formal πŸ“‹Chrome9/1/2015 Safari9/20/20212211
css.properties.list-style-type.simp-chinese-informal πŸ“‹Chrome9/1/2015 Safari9/20/20212211
css.properties.list-style-type.tamil πŸ“‹Chrome5/25/2021 Safari9/20/2021118
css.properties.list-style-type.trad-chinese-formal πŸ“‹Chrome9/1/2015 Safari9/20/20212211
css.properties.list-style-type.trad-chinese-informal πŸ“‹Chrome9/1/2015 Safari9/20/20212211
css.properties.scroll-margin-block πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-block-end πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-block-start πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-inline πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-inline-end πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-inline-start πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block.auto πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block-end πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block-end.auto πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block-start πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block-start.auto πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-bottom.auto πŸ“‹Chrome10/22/2019 Safari9/20/2021699
css.properties.scroll-padding-inline πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline.auto πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline-end πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline-end.auto πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline-start πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline-start.auto πŸ“‹Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-left.auto πŸ“‹Chrome10/22/2019 Safari9/20/2021699
css.properties.scroll-padding-right.auto πŸ“‹Chrome10/22/2019 Safari9/20/2021699
css.properties.scroll-padding-top.auto πŸ“‹Chrome10/22/2019 Safari9/20/2021699
css.properties.scroll-snap-stop πŸ“‹Chrome6/4/2019 Safari9/20/2021839
css.properties.scroll-snap-stop.always πŸ“‹Chrome6/4/2019 Safari9/20/2021839
css.properties.scroll-snap-stop.normal πŸ“‹Chrome6/4/2019 Safari9/20/2021839
css.selectors.any-link.not_match_link Chrome3/6/2018 Safari9/20/20211294
css.selectors.link.not_match_link Chrome12/11/2008 Safari9/20/20214666
css.selectors.visited.not_match_link Chrome12/11/2008 Safari9/20/20214666
css.types.gradient.linear-gradient.premultiplied_gradients Chrome8/20/2013 Safari9/20/20212953
css.types.gradient.radial-gradient.premultiplied_gradients Chrome8/20/2013 Safari9/20/20212953

2021/8

API First Browser Date Last Browser Date Days Notes
css.properties.justify-content.flex_context.left_right Safari9/30/2015 Chrome8/31/20212162
Internet Explorer: This value is recognized, but has no effect.Opera Android: This value is recognized, but has no effect.

2021/5

API First Browser Date Last Browser Date Days Notes
css.properties.list-style-type.afar Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.amharic Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.amharic-abegede Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.asterisks Safari7/20/2011 Chrome5/25/20213597
css.properties.list-style-type.binary Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-abegede Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-abegede-am-et Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-abegede-gez Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-abegede-ti-er Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-abegede-ti-et Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-halehame-aa-er Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-halehame-aa-et Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-halehame-am-et Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-halehame-gez Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-halehame-om-et Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-halehame-sid-et Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-halehame-so-et Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.ethiopic-halehame-tig Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.footnotes Safari7/20/2011 Chrome5/25/20213597
css.properties.list-style-type.lower-hexadecimal Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.lower-norwegian Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.octal Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.oromo Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.sidama Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.somali Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.tigre Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.tigrinya-er Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.tigrinya-er-abegede Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.tigrinya-et Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.tigrinya-et-abegede Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.upper-greek Safari6/23/2003 Chrome5/25/20216546
css.properties.list-style-type.upper-hexadecimal Safari6/7/2010 Chrome5/25/20214005
css.properties.list-style-type.upper-norwegian Safari6/7/2010 Chrome5/25/20214005

2021/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.supports.selector Chrome5/19/2020 Safari4/26/2021342
css.properties.border-block πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.currentColor πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.dashed πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.dotted πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.double πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.groove πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.hidden πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.inset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.medium πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.none πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.outset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.ridge πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.solid πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.thick πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.thin πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block.transparent πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-color πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-color.currentColor πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-color.transparent πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.dashed πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.dotted πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.double πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.groove πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.hidden πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.inset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.none πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.outset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.ridge πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-style.solid πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-width πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-width.medium πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-width.thick πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-block-width.thin πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.currentColor πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.dashed πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.dotted πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.double πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.groove πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.hidden πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.inset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.medium πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.none πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.outset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.ridge πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.solid πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.thick πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.thin πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline.transparent πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-color πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-color.currentColor πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-color.transparent πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.dashed πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.dotted πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.double πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.groove πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.hidden πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.inset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.none πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.outset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.ridge πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-style.solid πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-width πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-width.medium πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-width.thick πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.border-inline-width.thin πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.column-gap.flex_context πŸ“‹Chrome7/27/2020 Safari4/26/2021273
css.properties.gap.flex_context πŸ“‹Chrome7/27/2020 Safari4/26/2021273
css.properties.gap.multicol_context πŸ“‹Chrome4/17/2018 Safari4/26/20211105
css.properties.inset πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-block πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-block.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-block-end πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-block-end.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-block-start πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-block-start.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-inline πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-inline.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-inline-end πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-inline-end.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-inline-start πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.inset-inline-start.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.list-style-type.string Chrome12/10/2019 Safari4/26/2021503
css.properties.margin-block πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.margin-block.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.margin-inline πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.margin-inline.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.padding-block πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.padding-inline πŸ“‹Chrome11/17/2020 Safari4/26/2021160
css.properties.quotes.auto πŸ“‹Chrome11/17/2020 Safari4/26/2021160
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 πŸ“‹Chrome7/27/2020 Safari4/26/2021273
css.properties.scroll-margin πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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.
css.properties.scroll-margin-bottom πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome9/4/2018 Safari4/26/2021965
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 πŸ“‹Chrome3/2/2021 Safari4/26/202155
css.selectors.marker.animation_and_transition_support Chrome10/20/2020 Safari4/26/2021188

2021/3

API First Browser Date Last Browser Date Days Notes
css.properties.text-decoration-thickness πŸ“‹Safari3/25/2019 Chrome3/2/2021708
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.clip-path.path Safari3/24/2020 Chrome1/19/2021301
css.properties.hyphens.auto Safari7/20/2011 Chrome1/19/20213471
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.manual Safari7/20/2011 Chrome1/19/20213471
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.none Safari7/20/2011 Chrome1/19/20213471
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.selectors.is πŸ“‹Safari9/16/2020 Chrome1/19/2021125
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 Chrome1/19/2021125
css.selectors.not.selector_list Safari9/30/2015 Chrome1/19/20211938
css.selectors.where πŸ“‹Safari9/16/2020 Chrome1/19/2021125
css.selectors.where.forgiving_selector_list Safari9/16/2020 Chrome1/19/2021125
css.types.basic-shape.path.clip-path πŸ“‹Safari3/24/2020 Chrome1/19/2021301

2020/11

API First Browser Date Last Browser Date Days Notes
css.properties.hyphens.language_croatian Safari3/21/2016 Chrome11/17/20201702
css.properties.hyphens.language_danish Safari7/20/2011 Chrome11/17/20203408
css.properties.hyphens.language_french Safari7/20/2011 Chrome11/17/20203408
css.properties.hyphens.language_german_reformed_orthography Safari7/20/2011 Chrome11/17/20203408
css.properties.hyphens.language_hungarian Safari3/21/2016 Chrome11/17/20201702
css.properties.hyphens.language_norwegian_no Safari7/20/2011 Chrome11/17/20203408
css.properties.hyphens.language_portuguese Safari3/21/2016 Chrome11/17/20201702
css.properties.hyphens.language_spanish Safari7/20/2011 Chrome11/17/20203408
css.properties.text-decoration-thickness.auto πŸ“‹Safari3/25/2019 Chrome11/17/2020603
css.properties.text-decoration-thickness.from-font πŸ“‹Safari3/25/2019 Chrome11/17/2020603
css.properties.text-underline-offset πŸ“‹Safari3/25/2019 Chrome11/17/2020603
css.properties.text-underline-offset.auto πŸ“‹Safari3/25/2019 Chrome11/17/2020603
css.properties.text-underline-position.from-font πŸ“‹Safari3/25/2019 Chrome11/17/2020603

2020/10

API First Browser Date Last Browser Date Days Notes
css.selectors.marker πŸ“‹Safari4/12/2018 Chrome10/20/2020922
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.animation-timing-function.jump Chrome9/10/2019 Safari9/16/2020372
css.properties.text-orientation πŸ“‹Chrome1/20/2016 Safari9/16/20201701
css.properties.transition-timing-function.jump Chrome9/10/2019 Safari9/16/2020372
css.types.easing-function.steps.jump Chrome9/10/2019 Safari9/16/2020372

2020/8

API First Browser Date Last Browser Date Days Notes
css.properties.page πŸ“‹Safari6/23/2003 Chrome8/25/20206273
css.properties.page.auto πŸ“‹Safari6/23/2003 Chrome8/25/20206273

2020/7

API First Browser Date Last Browser Date Days Notes
css.types.global_keywords.revert πŸ“‹Safari3/21/2016 Chrome7/27/20201589

2020/5

API First Browser Date Last Browser Date Days Notes
css.properties.line-break.anywhere πŸ“‹Safari9/19/2019 Chrome5/19/2020243

2020/4

API First Browser Date Last Browser Date Days Notes
css.properties.color-scheme πŸ“‹Safari9/19/2019 Chrome4/7/2020201
css.properties.color-scheme.dark Safari9/19/2019 Chrome4/7/2020201
css.properties.color-scheme.light Safari9/19/2019 Chrome4/7/2020201
css.properties.color-scheme.normal Safari9/19/2019 Chrome4/7/2020201
css.properties.image-orientation πŸ“‹Safari3/24/2020 Chrome4/7/202014
css.properties.image-orientation.from-image πŸ“‹Safari3/24/2020 Chrome4/7/202014
css.properties.image-orientation.none πŸ“‹Safari3/24/2020 Chrome4/7/202014

2020/3

API First Browser Date Last Browser Date Days Notes
css.properties.font-optical-sizing πŸ“‹Chrome12/10/2019 Safari3/24/2020105
css.properties.font-optical-sizing.auto πŸ“‹Chrome12/10/2019 Safari3/24/2020105
css.properties.font-optical-sizing.none πŸ“‹Chrome12/10/2019 Safari3/24/2020105
css.properties.opacity.percentages Chrome10/22/2019 Safari3/24/2020154
css.properties.overflow.multiple_keywords Chrome7/24/2018 Safari3/24/2020609
css.properties.tab-size.length πŸ“‹Chrome4/14/2015 Safari3/24/20201806
css.properties.text-orientation.mixed πŸ“‹Chrome1/20/2016 Safari3/24/20201525
css.properties.text-orientation.upright πŸ“‹Chrome6/7/2011 Safari3/24/20203213
css.properties.white-space.break-spaces πŸ“‹Chrome7/30/2019 Safari3/24/2020238
css.selectors.part πŸ“‹Chrome3/12/2019 Safari3/24/2020378
css.types.basic-shape.path πŸ“‹Chrome7/20/2016 Safari3/24/20201343
css.types.clamp πŸ“‹Chrome12/10/2019 Safari3/24/2020105
css.types.length.Q Chrome12/6/2017 Safari3/24/2020839

2019/12

API First Browser Date Last Browser Date Days Notes
css.types.max πŸ“‹Safari4/12/2018 Chrome12/10/2019607
css.types.min πŸ“‹Safari4/12/2018 Chrome12/10/2019607

2019/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.display-mode πŸ“‹Chrome4/14/2015 Safari9/19/20191619
css.at-rules.media.display-mode.browser πŸ“‹Chrome4/14/2015 Safari9/19/20191619
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 πŸ“‹Chrome12/1/2015 Safari9/19/20191388
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 πŸ“‹Chrome4/14/2015 Safari9/19/20191619
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 πŸ“‹Chrome4/14/2015 Safari9/19/20191619
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.properties.display.flow-root Chrome4/19/2017 Safari9/19/2019883
css.properties.pointer-events.bounding-box πŸ“‹Chrome2/20/2014 Safari9/19/20192037
css.properties.position.sticky πŸ“‹Chrome1/25/2017 Safari9/19/2019967
css.properties.touch-action πŸ“‹Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.manipulation Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.none Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-x Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-y Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pinch-zoom Chrome1/25/2017 Safari9/19/2019967
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.

2019/7

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.prefers-color-scheme πŸ“‹Safari3/25/2019 Chrome7/30/2019127
css.properties.backdrop-filter.none πŸ“‹Safari9/30/2015 Chrome7/30/20191399

2019/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.prefers-reduced-motion πŸ“‹Safari3/27/2017 Chrome4/23/2019757

2019/3

API First Browser Date Last Browser Date Days Notes
css.properties.block-size πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.block-size.fit-content πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.block-size.max-content Chrome3/9/2017 Safari3/25/2019746
css.properties.block-size.min-content Chrome3/9/2017 Safari3/25/2019746
css.properties.border-block-end πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.currentColor πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.dashed πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.dotted πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.double πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.groove πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.hidden πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.inset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.medium πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.none πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.outset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.ridge πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.solid πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.thick πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.thin πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end.transparent πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-color πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-color.currentColor πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-color.transparent πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.dashed πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.dotted πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.double πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.groove πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.hidden πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.inset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.none πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.outset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.ridge πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-style.solid πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-width πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-width.medium πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-width.thick πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-end-width.thin πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.currentColor πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.dashed πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.dotted πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.double πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.groove πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.hidden πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.inset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.medium πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.none πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.outset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.ridge πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.solid πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.thick πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.thin πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start.transparent πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-color πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-color.currentColor πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-color.transparent πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.dashed πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.dotted πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.double πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.groove πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.hidden πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.inset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.none πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.outset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.ridge πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-style.solid πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-width πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-width.medium πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-width.thick πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-block-start-width.thin πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.currentColor πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.dashed πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.dotted πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.double πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.groove πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.hidden πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.inset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.medium πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.none πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.outset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.ridge πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.solid πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.thick πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.thin πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end.transparent πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-color πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-color.currentColor πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-color.transparent πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.dashed πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.dotted πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.double πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.groove πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.hidden πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.inset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.none πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.outset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.ridge πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-style.solid πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-width πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-width.medium πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-width.thick πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-end-width.thin πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.currentColor πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.dashed πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.dotted πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.double πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.groove πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.hidden πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.inset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.medium πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.none πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.outset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.ridge πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.solid πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.thick πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.thin πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start.transparent πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-color πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-color.currentColor πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-color.transparent πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.dashed πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.dotted πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.double πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.groove πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.hidden πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.inset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.none πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.outset πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.ridge πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-style.solid πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-width πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-width.medium πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-width.thick πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.border-inline-start-width.thin πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.clip-path.is_animatable Chrome12/1/2016 Safari3/25/2019844
css.properties.column-gap.multicol_context.calc_values Chrome4/17/2018 Safari3/25/2019342
css.properties.gap.grid_context.calc_values Chrome4/17/2018 Safari3/25/2019342
css.properties.inline-size πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.inline-size.fit-content πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.inline-size.max-content Chrome3/9/2017 Safari3/25/2019746
css.properties.inline-size.min-content Chrome3/9/2017 Safari3/25/2019746
css.properties.margin-block-end πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.margin-block-end.auto πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.margin-block-start πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.margin-block-start.auto πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.margin-inline-end πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.margin-inline-end.auto πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.margin-inline-start πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.margin-inline-start.auto πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.max-block-size πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.max-block-size.fit-content Chrome3/9/2017 Safari3/25/2019746
css.properties.max-block-size.max-content Chrome3/9/2017 Safari3/25/2019746
css.properties.max-block-size.min-content Chrome3/9/2017 Safari3/25/2019746
css.properties.max-block-size.none πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.max-inline-size πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.max-inline-size.fit-content Chrome3/9/2017 Safari3/25/2019746
css.properties.max-inline-size.max-content Chrome3/9/2017 Safari3/25/2019746
css.properties.max-inline-size.min-content Chrome3/9/2017 Safari3/25/2019746
css.properties.max-inline-size.none πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.min-block-size πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.min-block-size.auto πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.min-block-size.fit-content Chrome3/9/2017 Safari3/25/2019746
css.properties.min-block-size.max-content Chrome3/9/2017 Safari3/25/2019746
css.properties.min-block-size.min-content Chrome3/9/2017 Safari3/25/2019746
css.properties.min-inline-size πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.min-inline-size.auto πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.min-inline-size.fit-content Chrome3/9/2017 Safari3/25/2019746
css.properties.min-inline-size.max-content Chrome3/9/2017 Safari3/25/2019746
css.properties.min-inline-size.min-content Chrome3/9/2017 Safari3/25/2019746
css.properties.padding-block-end πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.padding-block-start πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.padding-inline-end πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.padding-inline-start πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.properties.text-decoration-color πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.text-decoration-line πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.text-decoration-style πŸ“‹Chrome3/9/2017 Safari3/25/2019746
css.properties.text-underline-position πŸ“‹Chrome2/20/2014 Safari3/25/20191859
css.properties.text-underline-position.auto πŸ“‹Chrome2/20/2014 Safari3/25/20191859
css.properties.text-underline-position.under πŸ“‹Chrome2/20/2014 Safari3/25/20191859
css.types.color.hsl.alpha_parameter Chrome3/6/2018 Safari3/25/2019384
css.types.color.hsl.space_separated_parameters Chrome3/6/2018 Safari3/25/2019384
css.types.color.rgb.alpha_parameter Chrome3/6/2018 Safari3/25/2019384
css.types.color.rgb.float_values Chrome4/17/2018 Safari3/25/2019342
css.types.color.rgb.space_separated_parameters Chrome3/6/2018 Safari3/25/2019384
css.types.gradient.conic-gradient πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.types.gradient.conic-gradient.doubleposition Chrome1/29/2019 Safari3/25/201955
css.types.gradient.linear-gradient.doubleposition Chrome12/4/2018 Safari3/25/2019111
css.types.gradient.radial-gradient.doubleposition Chrome12/4/2018 Safari3/25/2019111
css.types.gradient.repeating-conic-gradient πŸ“‹Chrome9/4/2018 Safari3/25/2019202
css.types.gradient.repeating-linear-gradient.doubleposition Chrome12/4/2018 Safari3/25/2019111
css.types.gradient.repeating-radial-gradient.doubleposition Chrome12/4/2018 Safari3/25/2019111

2018/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.calc πŸ“‹Chrome4/17/2018 Safari9/17/2018153
css.properties.column-gap.grid_context πŸ“‹Chrome4/17/2018 Safari9/17/2018153
css.properties.column-gap.multicol_context.percentage_values Chrome4/17/2018 Safari9/17/2018153
css.properties.gap.grid_context πŸ“‹Chrome4/17/2018 Safari9/17/2018153
css.properties.row-gap.grid_context πŸ“‹Chrome4/17/2018 Safari9/17/2018153
css.properties.scroll-padding.auto πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-align πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-align.center πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-align.end πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-align.none πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-align.start πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-type πŸ“‹Safari9/19/2017 Chrome9/4/2018350
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.
css.properties.scroll-snap-type.block πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-type.both πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-type.inline πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-type.none πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-type.x πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.properties.scroll-snap-type.y πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.types.env πŸ“‹Safari4/12/2018 Chrome9/4/2018145
css.types.env.safe-area-inset-bottom πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.types.env.safe-area-inset-left πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.types.env.safe-area-inset-right πŸ“‹Safari9/19/2017 Chrome9/4/2018350
css.types.env.safe-area-inset-top πŸ“‹Safari9/19/2017 Chrome9/4/2018350

2018/7

API First Browser Date Last Browser Date Days Notes
css.properties.cursor.grab Safari9/19/2017 Chrome7/24/2018308
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.cursor.grabbing πŸ“‹Safari9/19/2017 Chrome7/24/2018308
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.

2018/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.OpenType_SBIX Safari3/21/2016 Chrome4/17/2018757
css.at-rules.font-face.src.format_variations Safari9/19/2017 Chrome4/17/2018210
css.properties.gap.grid_context.percentage_values Safari9/19/2017 Chrome4/17/2018210
css.at-rules.font-face.OpenType_COLRv0 Chrome8/31/2016 Safari4/12/2018589
css.at-rules.font-face.font-display πŸ“‹Chrome7/25/2017 Safari4/12/2018261
css.properties.caret-color πŸ“‹Chrome3/9/2017 Safari4/12/2018399
css.properties.caret-color.auto πŸ“‹Chrome3/9/2017 Safari4/12/2018399
css.properties.caret-color.currentColor πŸ“‹Chrome3/9/2017 Safari4/12/2018399
css.properties.caret-color.transparent πŸ“‹Chrome3/9/2017 Safari4/12/2018399
css.properties.display.contents πŸ“‹Chrome3/6/2018 Safari4/12/201837
css.properties.font-stretch.percentage Chrome10/17/2017 Safari4/12/2018177
css.properties.font-style.oblique-angle πŸ“‹Chrome10/17/2017 Safari4/12/2018177
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.

2018/3

API First Browser Date Last Browser Date Days Notes
css.selectors.any-link πŸ“‹Safari9/30/2015 Chrome3/6/2018888

2018/1

API First Browser Date Last Browser Date Days Notes
css.properties.transform-box πŸ“‹Safari9/19/2017 Chrome1/23/2018126
css.properties.transform-box.fill-box πŸ“‹Safari9/19/2017 Chrome1/23/2018126
css.properties.transform-box.view-box πŸ“‹Safari9/19/2017 Chrome1/23/2018126

2017/12

API First Browser Date Last Browser Date Days Notes
css.properties.font-variant-east-asian πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.full-width πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.jis04 πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.jis78 πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.jis83 πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.jis90 πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.normal πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.proportional-width πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.ruby πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.simplified πŸ“‹Safari3/21/2016 Chrome12/6/2017625
css.properties.font-variant-east-asian.traditional πŸ“‹Safari3/21/2016 Chrome12/6/2017625

2017/10

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.font-stretch πŸ“‹Safari3/27/2017 Chrome10/17/2017204
css.properties.font-variation-settings πŸ“‹Safari9/19/2017 Chrome10/17/201728
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 Chrome10/17/201728
css.properties.font-weight.number Safari9/19/2017 Chrome10/17/201728
css.properties.text-emphasis-position.left Safari10/16/2014 Chrome10/17/20171097
css.properties.text-emphasis-position.right Safari10/16/2014 Chrome10/17/20171097
css.types.color.rgb_hexadecimal_notation.alpha_hexadecimal_notation Safari9/20/2016 Chrome10/17/2017392

2017/9

API First Browser Date Last Browser Date Days Notes
css.properties.align-content.flex_context.first_baseline Chrome6/5/2017 Safari9/19/2017106
css.properties.align-content.flex_context.space-evenly Chrome7/25/2017 Safari9/19/201756
css.properties.align-items.flex_context.first_baseline Chrome6/5/2017 Safari9/19/2017106
css.properties.align-items.grid_context.start_end Chrome3/9/2017 Safari9/19/2017194
css.properties.align-self.flex_context.first_baseline Chrome6/5/2017 Safari9/19/2017106
css.properties.font.font-width_keyword_values Chrome7/25/2017 Safari9/19/201756
css.properties.font-family.system-ui Chrome1/25/2017 Safari9/19/2017237
Firefox: Supported on macOS only.
css.properties.font-stretch πŸ“‹Chrome7/25/2017 Safari9/19/201756
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 πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.font-stretch.expanded πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.font-stretch.extra-condensed πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.font-stretch.extra-expanded πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.font-stretch.normal πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.font-stretch.semi-condensed πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.font-stretch.semi-expanded πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.font-stretch.ultra-condensed πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.font-stretch.ultra-expanded πŸ“‹Chrome7/25/2017 Safari9/19/201756
css.properties.grid-auto-columns.max-content πŸ“‹Chrome3/9/2017 Safari9/19/2017194
css.properties.grid-auto-columns.min-content πŸ“‹Chrome3/9/2017 Safari9/19/2017194
css.properties.grid-auto-rows.max-content πŸ“‹Chrome3/9/2017 Safari9/19/2017194
css.properties.grid-auto-rows.min-content πŸ“‹Chrome3/9/2017 Safari9/19/2017194
css.properties.height.fit-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.height.max-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.height.min-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.justify-content.flex_context.space-evenly Chrome7/25/2017 Safari9/19/201756
css.properties.line-break πŸ“‹Chrome4/19/2017 Safari9/19/2017153
css.properties.max-height.fit-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
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-height.max-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.max-height.min-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.max-width.fit-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
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-width.max-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.max-width.min-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.min-height.fit-content Chrome10/13/2015 Safari9/19/2017707
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-height.max-content Chrome10/13/2015 Safari9/19/2017707
css.properties.min-height.min-content Chrome10/13/2015 Safari9/19/2017707
css.properties.min-width.fit-content Chrome10/13/2015 Safari9/19/2017707
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-width.max-content Chrome10/13/2015 Safari9/19/2017707
css.properties.min-width.min-content Chrome10/13/2015 Safari9/19/2017707
css.properties.place-content.grid_context Chrome6/5/2017 Safari9/19/2017106
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 πŸ“‹Chrome6/5/2017 Safari9/19/2017106
css.properties.place-items.flex_context Chrome6/5/2017 Safari9/19/2017106
css.properties.place-items.grid_context Chrome6/5/2017 Safari9/19/2017106
css.properties.place-self πŸ“‹Chrome6/5/2017 Safari9/19/2017106
css.properties.place-self.flex_context Chrome6/5/2017 Safari9/19/2017106
css.properties.place-self.grid_context Chrome6/5/2017 Safari9/19/2017106
css.properties.position.absolutely_positioned_flex_children Chrome7/20/2016 Safari9/19/2017426
css.properties.unicode-bidi.isolate πŸ“‹Chrome1/20/2016 Safari9/19/2017608
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 πŸ“‹Chrome1/20/2016 Safari9/19/2017608
css.properties.unicode-bidi.plaintext πŸ“‹Chrome1/20/2016 Safari9/19/2017608
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.width.fit-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.width.max-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.properties.width.min-content πŸ“‹Chrome10/13/2015 Safari9/19/2017707
css.types.calc.nested Chrome5/25/2016 Safari9/19/2017482

2017/7

API First Browser Date Last Browser Date Days Notes
css.selectors.focus-within πŸ“‹Safari3/27/2017 Chrome7/25/2017120

2017/6

API First Browser Date Last Browser Date Days Notes
css.properties.place-content πŸ“‹Safari9/30/2015 Chrome6/5/2017614
css.properties.place-content.flex_context Safari9/30/2015 Chrome6/5/2017614
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.

2017/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.color-gamut πŸ“‹Safari9/20/2016 Chrome4/19/2017211
css.at-rules.media.color-gamut.p3 πŸ“‹Safari9/20/2016 Chrome4/19/2017211
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 Chrome4/19/2017211
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 Chrome4/19/2017211
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.

2017/3

API First Browser Date Last Browser Date Days Notes
css.at-rules.keyframes.ignore_important_declarations Chrome9/1/2015 Safari3/27/2017573
css.properties.align-content.grid_context πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.align-items.grid_context πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.align-self.grid_context πŸ“‹Chrome3/9/2017 Safari3/27/201718
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 Chrome3/9/2017 Safari3/27/201718
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 Chrome3/9/2017 Safari3/27/201718
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 πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.gap.normal πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid πŸ“‹Chrome3/9/2017 Safari3/27/201718
Samsung Internet: This was added early so is out of sync with the equivalent Chromium version.
css.properties.grid.none πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-area πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-area.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-auto-columns πŸ“‹Chrome3/9/2017 Safari3/27/201718
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-columns.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-auto-flow πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-auto-flow.column πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-auto-flow.dense πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-auto-flow.row πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-auto-rows πŸ“‹Chrome3/9/2017 Safari3/27/201718
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.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-column πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-column.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-column-end πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-column-end.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-column-start πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-column-start.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-row πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-row.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-row-end πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-row-end.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-row-start πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-row-start.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template.none πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-areas πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-areas.none πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-columns πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-columns.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-columns.fit-content πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-columns.max-content πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-columns.min-content πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-columns.minmax πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-columns.none πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-columns.repeat πŸ“‹Chrome3/9/2017 Safari3/27/201718
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 πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-rows.auto πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-rows.fit-content πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-rows.max-content πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-rows.min-content πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-rows.minmax πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-rows.none πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.grid-template-rows.repeat πŸ“‹Chrome3/9/2017 Safari3/27/201718
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.justify-content.grid_context πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.justify-items.grid_context πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.justify-self πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.properties.justify-self.auto Chrome3/9/2017 Safari3/27/201718
css.properties.justify-self.grid_context πŸ“‹Chrome3/9/2017 Safari3/27/201718
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.justify-self.left Chrome3/9/2017 Safari3/27/201718
css.properties.justify-self.normal Chrome3/9/2017 Safari3/27/201718
css.properties.justify-self.right Chrome3/9/2017 Safari3/27/201718
css.properties.justify-self.stretch Chrome3/9/2017 Safari3/27/201718
css.properties.row-gap πŸ“‹Chrome12/1/2015 Safari3/27/2017482
css.properties.row-gap.normal πŸ“‹Chrome12/1/2015 Safari3/27/2017482
css.properties.shape-image-threshold πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-margin πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.border-box πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.circle Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.content-box πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.gradient πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.image πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.inset Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.margin-box πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.none πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.padding-box πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.properties.shape-outside.polygon Chrome8/26/2014 Safari3/27/2017944
css.properties.writing-mode πŸ“‹Chrome1/20/2016 Safari3/27/2017432
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 Chrome1/20/2016 Safari3/27/2017432
css.properties.writing-mode.lr-tb Chrome1/20/2016 Safari3/27/2017432
css.properties.writing-mode.rl Chrome1/20/2016 Safari3/27/2017432
css.properties.writing-mode.rl-tb Chrome1/20/2016 Safari3/27/2017432
css.properties.writing-mode.tb Chrome1/20/2016 Safari3/27/2017432
css.properties.writing-mode.tb-rl Chrome1/20/2016 Safari3/27/2017432
css.selectors.placeholder πŸ“‹Chrome3/9/2017 Safari3/27/201718
css.types.basic-shape πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.types.basic-shape.animation Chrome8/26/2014 Safari3/27/2017944
css.types.basic-shape.circle πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.types.basic-shape.ellipse πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.types.basic-shape.inset πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.types.basic-shape.polygon πŸ“‹Chrome8/26/2014 Safari3/27/2017944
css.types.flex πŸ“‹Chrome8/20/2013 Safari3/27/20171315
css.types.number.scientific_notation Chrome5/19/2015 Safari3/27/2017678
css.properties.align-content.flex_context.baseline Safari9/30/2015 Chrome3/9/2017526
css.properties.align-content.flex_context.stretch Safari9/30/2015 Chrome3/9/2017526
css.properties.align-self.flex_context.stretch πŸ“‹Safari9/30/2015 Chrome3/9/2017526
css.properties.justify-content.flex_context.stretch Safari9/30/2015 Chrome3/9/2017526
css.properties.text-decoration-color.currentColor πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-color.transparent πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-line.blink πŸ“‹Safari10/16/2014 Chrome3/9/2017875
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 πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-line.none πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-line.overline πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-line.underline πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-style.dashed πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-style.dotted πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-style.double πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-style.solid πŸ“‹Safari10/16/2014 Chrome3/9/2017875
css.properties.text-decoration-style.wavy πŸ“‹Safari10/16/2014 Chrome3/9/2017875

2017/1

API First Browser Date Last Browser Date Days Notes
css.properties.border-image-repeat.space πŸ“‹Safari3/21/2016 Chrome1/25/2017310
css.properties.position.position_sticky_table_elements Safari10/16/2014 Chrome1/25/2017832
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).

2016/12

API First Browser Date Last Browser Date Days Notes
css.properties.clip-path πŸ“‹Safari3/21/2016 Chrome12/1/2016255
Edge: Only supports clip paths defined by url().Internet Explorer: Only supports clip paths defined by url().
css.properties.hyphens.language_english Safari7/20/2011 Chrome12/1/20161961
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.

2016/10

API First Browser Date Last Browser Date Days Notes
css.properties.user-select πŸ“‹Safari10/26/2007 Chrome10/12/20163274
css.selectors.defined πŸ“‹Safari9/20/2016 Chrome10/12/201622
css.selectors.host πŸ“‹Safari9/20/2016 Chrome10/12/201622
css.selectors.hostfunction πŸ“‹Safari9/20/2016 Chrome10/12/201622
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.

2016/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.WOFF_2 πŸ“‹Chrome7/16/2014 Safari9/20/2016797
Safari: Supported only on macOS 10.12 (Sierra) and later.
css.properties.break-after πŸ“‹Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.auto Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.avoid-column Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.avoid-page Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.column Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.left Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.page Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.paged_context πŸ“‹Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.paged_context.avoid-page Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.paged_context.page Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.recto Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.right Chrome4/13/2016 Safari9/20/2016160
css.properties.break-after.verso Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before πŸ“‹Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.auto Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.avoid-column Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.avoid-page Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.column Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.left Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.page Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.paged_context πŸ“‹Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.paged_context.page Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.recto Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.right Chrome4/13/2016 Safari9/20/2016160
css.properties.break-before.verso Chrome4/13/2016 Safari9/20/2016160
css.properties.break-inside πŸ“‹Chrome4/13/2016 Safari9/20/2016160
css.properties.break-inside.auto Chrome4/13/2016 Safari9/20/2016160
css.properties.break-inside.avoid Chrome4/13/2016 Safari9/20/2016160
css.properties.break-inside.avoid-column Chrome4/13/2016 Safari9/20/2016160
css.properties.break-inside.avoid-page Chrome4/13/2016 Safari9/20/2016160
css.properties.break-inside.multicol_context πŸ“‹Chrome4/13/2016 Safari9/20/2016160
css.properties.break-inside.multicol_context.avoid-column Chrome4/13/2016 Safari9/20/2016160
css.properties.break-inside.paged_context πŸ“‹Chrome4/13/2016 Safari9/20/2016160
css.properties.column-gap.multicol_context πŸ“‹Chrome4/13/2016 Safari9/20/2016160
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.image-rendering.pixelated πŸ“‹Chrome3/3/2015 Safari9/20/2016567
css.properties.mix-blend-mode.color πŸ“‹Chrome3/3/2015 Safari9/20/2016567
css.properties.mix-blend-mode.hue πŸ“‹Chrome3/3/2015 Safari9/20/2016567
css.properties.mix-blend-mode.luminosity πŸ“‹Chrome3/3/2015 Safari9/20/2016567
css.properties.mix-blend-mode.saturation πŸ“‹Chrome3/3/2015 Safari9/20/2016567
css.properties.object-fit πŸ“‹Chrome1/14/2014 Safari9/20/2016980
Edge: Only supported for <img> elements.
css.properties.object-fit.contain πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-fit.cover πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-fit.fill πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-fit.none πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-fit.scale-down πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-position πŸ“‹Chrome1/14/2014 Safari9/20/2016980
Edge: Only supported for <img> elements.
css.properties.object-position.bottom πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-position.center πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-position.left πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-position.right πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.object-position.top πŸ“‹Chrome1/14/2014 Safari9/20/2016980
css.properties.transition.allow-discrete πŸ“‹Chrome8/26/2014 Safari9/20/2016756
css.properties.transition.normal πŸ“‹Chrome8/26/2014 Safari9/20/2016756
css.selectors.indeterminate.radio Chrome11/18/2014 Safari9/20/2016672
css.selectors.slotted πŸ“‹Chrome4/13/2016 Safari9/20/2016160
css.types.image.cross-fade πŸ“‹Chrome2/8/2012 Safari9/20/20161686
Chrome: Supports the original dual-image with percentage implementation only.Chrome: See bug 40470742 for supporting the unprefixed cross-fade() function.Chrome Android: Supports the original dual-image with percentage implementation only.Chrome Android: See bug 40470742 for supporting the unprefixed cross-fade() function.Edge: Supports the original dual-image with percentage implementation only.Edge: See bug 40470742 for supporting the unprefixed cross-fade() function.Quest Browser: Supports the original dual-image with percentage implementation only.Quest Browser: See bug 40470742 for supporting the unprefixed cross-fade() function.Opera: Supports the original dual-image with percentage implementation only.Opera: See bug 40470742 for supporting the unprefixed cross-fade() function.Opera Android: Supports the original dual-image with percentage implementation only.Opera Android: See bug 40470742 for supporting the unprefixed cross-fade() function.Safari: Supports the original dual-image with percentage implementation only.Safari: Supports the original dual-image with percentage implementation only.Safari on iOS: Support for the original dual-image with percentage implementation only.Safari on iOS: Supports the original dual-image with percentage implementation only.Samsung Internet: Supports the original dual-image with percentage implementation only.Samsung Internet: See bug 40470742 for supporting the unprefixed cross-fade() function.WebView Android: Supports the original dual-image with percentage implementation only.WebView Android: See bug 40470742 for supporting the unprefixed cross-fade() function.WebView on iOS: Support for the original dual-image with percentage implementation only.WebView on iOS: Supports the original dual-image with percentage implementation only.

2016/8

API First Browser Date Last Browser Date Days Notes
css.properties.filter πŸ“‹Safari3/21/2016 Chrome8/31/2016163
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.

2016/7

API First Browser Date Last Browser Date Days Notes
css.properties.align-items.flex_context πŸ“‹Safari10/22/2013 Chrome7/20/20161002
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.font-variant.css_fonts_shorthand Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant.none πŸ“‹Safari9/30/2015 Chrome7/20/2016294
css.properties.font-variant-caps πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-caps.all-petite-caps πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-caps.all-small-caps πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-caps.normal πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-caps.petite-caps πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-caps.small-caps πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-caps.titling-caps πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-caps.unicase πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.diagonal-fractions πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.lining-nums πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.normal πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.oldstyle-nums πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.ordinal πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.proportional-nums πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.slashed-zero πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.stacked-fractions πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.font-variant-numeric.tabular-nums πŸ“‹Safari3/21/2016 Chrome7/20/2016121
css.properties.justify-content.flex_context πŸ“‹Safari10/22/2013 Chrome7/20/20161002
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.justify-items πŸ“‹Safari9/30/2015 Chrome7/20/2016294
css.properties.justify-items.center Safari9/30/2015 Chrome7/20/2016294
css.properties.justify-items.flex_context πŸ“‹Safari9/30/2015 Chrome7/20/2016294
css.properties.justify-items.left Safari9/30/2015 Chrome7/20/2016294
css.properties.justify-items.legacy πŸ“‹Safari9/30/2015 Chrome7/20/2016294
css.properties.justify-items.right Safari9/30/2015 Chrome7/20/2016294

2016/4

API First Browser Date Last Browser Date Days Notes
css.properties.column-count πŸ“‹Safari9/30/2015 Chrome4/13/2016196
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 πŸ“‹Safari9/30/2015 Chrome4/13/2016196
css.properties.column-fill.auto πŸ“‹Safari10/16/2014 Chrome4/13/2016545
css.properties.column-fill.balance πŸ“‹Safari10/16/2014 Chrome4/13/2016545
css.properties.column-rule πŸ“‹Safari9/30/2015 Chrome4/13/2016196
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.column-rule-color πŸ“‹Safari9/30/2015 Chrome4/13/2016196
css.properties.column-rule-style πŸ“‹Safari9/30/2015 Chrome4/13/2016196
css.properties.column-rule-width πŸ“‹Safari9/30/2015 Chrome4/13/2016196
css.properties.column-span πŸ“‹Safari9/30/2015 Chrome4/13/2016196
css.properties.column-width πŸ“‹Safari9/30/2015 Chrome4/13/2016196
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.columns πŸ“‹Safari9/30/2015 Chrome4/13/2016196
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.columns.auto πŸ“‹Safari10/26/2007 Chrome4/13/20163092

2016/3

API First Browser Date Last Browser Date Days Notes
css.properties.all πŸ“‹Chrome8/26/2014 Safari3/21/2016573
css.properties.background.border-box πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background.bottom πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background.center πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background.content-box πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background.fixed πŸ“‹Chrome10/25/2011 Safari3/21/20161609
css.properties.background.left πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background.padding-box πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background.right πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background.top πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.background-color.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-bottom.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-bottom-color.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-color.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-image-repeat.round πŸ“‹Chrome10/1/2013 Safari3/21/2016902
css.properties.border-left.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-left-color.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-right.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-right-color.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-top.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.border-top-color.currentColor πŸ“‹Chrome11/12/2013 Safari3/21/2016860
css.properties.custom-property πŸ“‹Chrome3/2/2016 Safari3/21/201619
css.properties.font-feature-settings πŸ“‹Chrome1/20/2016 Safari3/21/201661
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 πŸ“‹Chrome12/13/2011 Safari3/21/20161560
css.properties.font-variant-ligatures πŸ“‹Chrome4/8/2014 Safari3/21/2016713
css.properties.will-change πŸ“‹Chrome7/16/2014 Safari3/21/2016614
css.properties.will-change.auto πŸ“‹Chrome7/16/2014 Safari3/21/2016614
css.properties.will-change.contents πŸ“‹Chrome7/16/2014 Safari3/21/2016614
css.properties.will-change.scroll-position πŸ“‹Chrome7/16/2014 Safari3/21/2016614
css.types.global_keywords.unset πŸ“‹Chrome3/3/2015 Safari3/21/2016384
css.types.var πŸ“‹Chrome3/2/2016 Safari3/21/201619
css.selectors.attribute.case_insensitive_modifier Safari9/30/2015 Chrome3/2/2016154

2016/1

API First Browser Date Last Browser Date Days Notes
css.properties.writing-mode.horizontal-tb Safari9/30/2015 Chrome1/20/2016112
css.properties.writing-mode.vertical-lr Safari9/30/2015 Chrome1/20/2016112
css.properties.writing-mode.vertical-rl Safari9/30/2015 Chrome1/20/2016112

2015/12

API First Browser Date Last Browser Date Days Notes
css.selectors.placeholder-shown πŸ“‹Safari9/30/2015 Chrome12/1/201562
css.selectors.placeholder-shown.non_text_types Safari9/30/2015 Chrome12/1/201562

2015/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.keyframes πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.at-rules.media.any-hover πŸ“‹Chrome3/3/2015 Safari9/30/2015211
css.at-rules.media.any-pointer πŸ“‹Chrome3/3/2015 Safari9/30/2015211
css.at-rules.media.hover πŸ“‹Chrome10/7/2014 Safari9/30/2015358
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 πŸ“‹Chrome3/3/2015 Safari9/30/2015211
css.at-rules.supports πŸ“‹Chrome7/9/2013 Safari9/30/2015813
css.properties.align-content πŸ“‹Chrome8/20/2013 Safari9/30/2015771
css.properties.align-content.flex_context πŸ“‹Chrome7/31/2012 Safari9/30/20151156
css.properties.align-content.normal πŸ“‹Chrome8/20/2013 Safari9/30/2015771
css.properties.align-items πŸ“‹Chrome8/20/2013 Safari9/30/2015771
css.properties.align-self πŸ“‹Chrome8/20/2013 Safari9/30/2015771
css.properties.animation πŸ“‹Chrome5/19/2015 Safari9/30/2015134
WebView Android: The animation-fill-mode property is not supported in Android browsers below 2.3.
css.properties.animation-delay πŸ“‹Chrome5/19/2015 Safari9/30/2015134
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 πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.animation-duration πŸ“‹Chrome5/19/2015 Safari9/30/2015134
Internet Explorer: Once the element has loaded, changing the value of this property has no effect.
css.properties.animation-fill-mode πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.animation-iteration-count πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.animation-name πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.animation-play-state πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.animation-timing-function πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.color-interpolation-filters.linearRGB πŸ“‹Chrome7/9/2013 Safari9/30/2015813
css.properties.color-interpolation-filters.sRGB πŸ“‹Chrome7/9/2013 Safari9/30/2015813
css.properties.content.element_replacement Chrome7/9/2013 Safari9/30/2015813
css.properties.counter-increment.list-item πŸ“‹Chrome7/9/2013 Safari9/30/2015813
css.properties.counter-reset.list-item πŸ“‹Chrome7/9/2013 Safari9/30/2015813
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 πŸ“‹Chrome8/26/2014 Safari9/30/2015400
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 πŸ“‹Chrome8/26/2014 Safari9/30/2015400
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 πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.cy πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.display.flex Chrome8/20/2013 Safari9/30/2015771
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 Chrome8/20/2013 Safari9/30/2015771
Firefox: Firefox 28 added multi-line flexbox support.Firefox for Android: Firefox for Android 28 added multi-line flexbox support.
css.properties.flex πŸ“‹Chrome8/20/2013 Safari9/30/2015771
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 πŸ“‹Chrome8/20/2013 Safari9/30/2015771
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 Chrome9/25/2012 Safari9/30/20151100
css.properties.flex-direction πŸ“‹Chrome8/20/2013 Safari9/30/2015771
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 πŸ“‹Chrome8/20/2013 Safari9/30/2015771
css.properties.flex-grow πŸ“‹Chrome8/20/2013 Safari9/30/2015771
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 πŸ“‹Chrome8/20/2013 Safari9/30/2015771
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 πŸ“‹Chrome8/20/2013 Safari9/30/2015771
Internet Explorer: Partial support due to large number of bugs present. See Flexbugs.
css.properties.font-kerning πŸ“‹Chrome2/20/2014 Safari9/30/2015587
css.properties.font-kerning.auto πŸ“‹Chrome2/20/2014 Safari9/30/2015587
css.properties.font-kerning.none πŸ“‹Chrome2/20/2014 Safari9/30/2015587
css.properties.font-kerning.normal πŸ“‹Chrome2/20/2014 Safari9/30/2015587
css.properties.justify-content πŸ“‹Chrome8/20/2013 Safari9/30/2015771
css.properties.order πŸ“‹Chrome8/20/2013 Safari9/30/2015771
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 πŸ“‹Chrome7/16/2014 Safari9/30/2015441
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 πŸ“‹Chrome7/16/2014 Safari9/30/2015441
css.properties.quotes πŸ“‹Chrome4/27/2011 Safari9/30/20151617
css.properties.quotes.none πŸ“‹Chrome4/27/2011 Safari9/30/20151617
css.properties.r πŸ“‹Chrome5/19/2015 Safari9/30/2015134
css.properties.transform πŸ“‹Chrome7/16/2014 Safari9/30/2015441
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 πŸ“‹Chrome7/16/2014 Safari9/30/2015441
css.properties.transform-style πŸ“‹Chrome7/16/2014 Safari9/30/2015441
Safari: Before Safari 17, ::before and ::after pseudo elements were not included in the 3D rendering context (see bug 256430).
css.properties.transition πŸ“‹Chrome3/26/2013 Safari9/30/2015918
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 πŸ“‹Chrome3/26/2013 Safari9/30/2015918
css.properties.transition-duration πŸ“‹Chrome3/26/2013 Safari9/30/2015918
css.properties.transition-property πŸ“‹Chrome3/26/2013 Safari9/30/2015918
css.properties.transition-timing-function πŸ“‹Chrome3/26/2013 Safari9/30/2015918
css.properties.word-break.keep-all πŸ“‹Chrome7/21/2015 Safari9/30/201571
css.properties.x πŸ“‹Chrome4/14/2015 Safari9/30/2015169
css.properties.y πŸ“‹Chrome4/14/2015 Safari9/30/2015169
css.selectors.invalid.form Chrome1/21/2015 Safari9/30/2015252
css.selectors.valid.form Chrome1/21/2015 Safari9/30/2015252
css.types.color.named-color.rebeccapurple Chrome10/7/2014 Safari9/30/2015358

2015/3

API First Browser Date Last Browser Date Days Notes
css.properties.isolation πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.isolation.auto πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.isolation.isolate πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.color-burn πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.color-dodge πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.darken πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.difference πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.exclusion πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.hard-light πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.lighten πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.multiply πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.normal πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.overlay πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.screen πŸ“‹Safari10/16/2014 Chrome3/3/2015138
css.properties.mix-blend-mode.soft-light πŸ“‹Safari10/16/2014 Chrome3/3/2015138

2015/1

API First Browser Date Last Browser Date Days Notes
css.types.gradient.linear-gradient.interpolation_hints Safari10/22/2013 Chrome1/21/2015456
css.types.gradient.radial-gradient.interpolation_hints Safari10/22/2013 Chrome1/21/2015456
css.types.gradient.repeating-linear-gradient.interpolation_hints Safari10/22/2013 Chrome1/21/2015456
css.types.gradient.repeating-radial-gradient.interpolation_hints Safari10/22/2013 Chrome1/21/2015456

2014/10

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.color-index πŸ“‹Chrome8/20/2013 Safari10/16/2014422
css.properties.background-blend-mode πŸ“‹Chrome5/20/2014 Safari10/16/2014149
css.properties.background-repeat.round πŸ“‹Chrome10/1/2013 Safari10/16/2014380
css.properties.background-repeat.space πŸ“‹Chrome10/1/2013 Safari10/16/2014380
css.properties.font-variant.turkic_is Chrome11/12/2013 Safari10/16/2014338
css.properties.line-break.loose πŸ“‹Chrome2/21/2013 Safari10/16/2014602
css.properties.line-break.strict πŸ“‹Chrome2/21/2013 Safari10/16/2014602
css.properties.paint-order.fill πŸ“‹Chrome5/20/2014 Safari10/16/2014149
css.properties.paint-order.markers πŸ“‹Chrome5/20/2014 Safari10/16/2014149
css.properties.paint-order.normal πŸ“‹Chrome5/20/2014 Safari10/16/2014149
css.properties.paint-order.stroke πŸ“‹Chrome5/20/2014 Safari10/16/2014149
css.properties.text-transform.turkic_is Chrome11/12/2013 Safari10/16/2014338
css.types.blend-mode πŸ“‹Chrome5/20/2014 Safari10/16/2014149

2014/7

API First Browser Date Last Browser Date Days Notes
css.properties.align-self.flex_context πŸ“‹Safari10/22/2013 Chrome7/16/2014267
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.

2013/11

API First Browser Date Last Browser Date Days Notes
css.properties.color-interpolation.linearRGB πŸ“‹Safari6/8/2009 Chrome11/12/20131618
css.properties.font-size.rem_values Safari10/22/2013 Chrome11/12/201321
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-variant-ligatures.common-ligatures πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.contextual πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.discretionary-ligatures πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.historical-ligatures πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.no-common-ligatures πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.no-contextual πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.no-discretionary-ligatures πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.no-historical-ligatures πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.none πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.font-variant-ligatures.normal πŸ“‹Safari10/22/2013 Chrome11/12/201321
css.properties.outline.currentColor πŸ“‹Safari2/2/2004 Chrome11/12/20133571
css.properties.pointer-events.visibleFill πŸ“‹Safari6/8/2009 Chrome11/12/20131618
css.properties.pointer-events.visiblePainted πŸ“‹Safari6/8/2009 Chrome11/12/20131618
css.properties.pointer-events.visibleStroke πŸ“‹Safari6/8/2009 Chrome11/12/20131618
css.properties.shape-rendering.crispEdges πŸ“‹Safari6/8/2009 Chrome11/12/20131618
css.properties.shape-rendering.geometricPrecision πŸ“‹Safari6/8/2009 Chrome11/12/20131618
css.properties.shape-rendering.optimizeSpeed πŸ“‹Safari6/8/2009 Chrome11/12/20131618
css.properties.text-decoration.blink πŸ“‹Safari6/23/2003 Chrome11/12/20133795
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-rendering.optimizeLegibility πŸ“‹Safari6/7/2010 Chrome11/12/20131254
css.properties.text-rendering.optimizeSpeed πŸ“‹Safari6/7/2010 Chrome11/12/20131254
css.types.calc.number_values Safari7/25/2012 Chrome11/12/2013475

2013/10

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.nested-queries Chrome3/26/2013 Safari10/22/2013210
css.properties.align-items.flex_context.baseline Chrome7/31/2012 Safari10/22/2013448
css.properties.align-self.auto πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.align-self.flex_context.baseline πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.align-self.normal πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.align-self.stretch πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.background-position.side-relative_values Chrome2/21/2013 Safari10/22/2013243
css.properties.buffered-rendering Chrome7/9/2013 Safari10/22/2013105
css.properties.buffered-rendering.auto Chrome7/9/2013 Safari10/22/2013105
css.properties.buffered-rendering.dynamic Chrome7/9/2013 Safari10/22/2013105
css.properties.buffered-rendering.static Chrome7/9/2013 Safari10/22/2013105
css.properties.clip-path.basic_shape πŸ“‹Chrome11/6/2012 Safari10/22/2013350
css.properties.clip-path.html_elements Chrome11/6/2012 Safari10/22/2013350
css.properties.clip-path.svg_elements Chrome11/6/2012 Safari10/22/2013350
css.properties.content.gradient πŸ“‹Chrome3/26/2013 Safari10/22/2013210
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.properties.flex.auto πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex.none πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-direction.column πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-direction.column-reverse πŸ“‹Chrome7/31/2012 Safari10/22/2013448
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 πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-direction.row-reverse πŸ“‹Chrome7/31/2012 Safari10/22/2013448
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-flow.column πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-flow.column-reverse πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-flow.nowrap πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-flow.row πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-flow.row-reverse πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-flow.wrap πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-flow.wrap-reverse πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-wrap.nowrap πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-wrap.wrap πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.flex-wrap.wrap-reverse πŸ“‹Chrome7/31/2012 Safari10/22/2013448
css.properties.image-rendering.crisp-edges πŸ“‹Chrome8/2/2011 Safari10/22/2013812
css.properties.justify-content.left Chrome7/31/2012 Safari10/22/2013448
css.properties.justify-content.normal Chrome7/31/2012 Safari10/22/2013448
css.properties.justify-content.right Chrome7/31/2012 Safari10/22/2013448
css.properties.line-break.auto πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.mask-type πŸ“‹Chrome1/10/2013 Safari10/22/2013285
css.properties.mask-type.alpha πŸ“‹Chrome1/10/2013 Safari10/22/2013285
css.properties.mask-type.luminance πŸ“‹Chrome1/10/2013 Safari10/22/2013285
css.properties.min-height.auto Chrome7/31/2012 Safari10/22/2013448
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.auto Chrome7/31/2012 Safari10/22/2013448
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.overflow-wrap πŸ“‹Chrome11/6/2012 Safari10/22/2013350
css.properties.tab-size πŸ“‹Chrome7/31/2012 Safari10/22/2013448
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.
css.properties.text-emphasis.circle πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.currentColor πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.dot πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.double-circle πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.filled πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.none πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.open πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.sesame πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.transparent πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis.triangle πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis-color.currentColor πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-emphasis-color.transparent πŸ“‹Chrome2/21/2013 Safari10/22/2013243
css.properties.text-orientation.sideways πŸ“‹Chrome6/7/2011 Safari10/22/2013868
css.properties.width.is_animatable Chrome3/26/2013 Safari10/22/2013210
css.selectors.-webkit-meter-inner-element Chrome11/6/2012 Safari10/22/2013350
css.selectors.-webkit-progress-bar Chrome2/21/2013 Safari10/22/2013243
css.selectors.-webkit-progress-inner-element Chrome11/6/2012 Safari10/22/2013350
css.selectors.-webkit-progress-value Chrome2/21/2013 Safari10/22/2013243
css.selectors.after.animation_and_transition_support Chrome3/26/2013 Safari10/22/2013210
css.selectors.before.animation_and_transition_support Chrome3/26/2013 Safari10/22/2013210
css.selectors.cue πŸ“‹Chrome3/26/2013 Safari10/22/2013210
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.cue.selector_argument Chrome3/26/2013 Safari10/22/2013210
css.selectors.future πŸ“‹Chrome11/6/2012 Safari10/22/2013350
css.selectors.past πŸ“‹Chrome11/6/2012 Safari10/22/2013350
css.selectors.scope πŸ“‹Chrome5/21/2013 Safari10/22/2013154
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 Chrome5/21/2013 Safari10/22/2013154
css.types.calc πŸ“‹Chrome3/26/2013 Safari10/22/2013210
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.gradient πŸ“‹Chrome3/26/2013 Safari10/22/2013210
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 πŸ“‹Chrome3/26/2013 Safari10/22/2013210
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 Chrome3/26/2013 Safari10/22/2013210
css.types.gradient.linear-gradient.unitless_0_angle Chrome3/26/2013 Safari10/22/2013210
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.radial-gradient πŸ“‹Chrome3/26/2013 Safari10/22/2013210
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 Chrome3/26/2013 Safari10/22/2013210
css.types.gradient.repeating-linear-gradient πŸ“‹Chrome3/26/2013 Safari10/22/2013210
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 Chrome3/26/2013 Safari10/22/2013210
css.types.gradient.repeating-linear-gradient.unitless_0_angle Chrome3/26/2013 Safari10/22/2013210
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().
css.types.gradient.repeating-radial-gradient πŸ“‹Chrome3/26/2013 Safari10/22/2013210
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 Chrome3/26/2013 Safari10/22/2013210
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.length.ch Chrome5/21/2013 Safari10/22/2013154
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.vmax Chrome3/26/2013 Safari10/22/2013210
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 Chrome3/26/2013 Safari10/22/2013210
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.position.four_value_syntax Chrome2/21/2013 Safari10/22/2013243
css.properties.text-transform.lowercase_sigma Safari7/25/2012 Chrome10/1/2013433

2013/2

API First Browser Date Last Browser Date Days Notes
css.properties.orphans πŸ“‹Safari4/15/2005 Chrome2/21/20132869
css.properties.widows πŸ“‹Safari4/15/2005 Chrome2/21/20132869

2012/7

API First Browser Date Last Browser Date Days Notes
css.properties.background.background-clip Safari7/20/2011 Chrome7/31/2012377
css.properties.background.background-origin Safari7/20/2011 Chrome7/31/2012377
css.properties.background.background-size Safari7/20/2011 Chrome7/31/2012377
css.properties.animation-direction.alternate-reverse πŸ“‹Chrome5/15/2012 Safari7/25/201271
css.properties.animation-direction.reverse πŸ“‹Chrome5/15/2012 Safari7/25/201271
css.properties.border-image πŸ“‹Chrome12/13/2011 Safari7/25/2012225
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 Chrome12/13/2011 Safari7/25/2012225
css.properties.border-image.optional_border_image_slice Chrome12/13/2011 Safari7/25/2012225
css.properties.border-image-outset πŸ“‹Chrome10/25/2011 Safari7/25/2012274
css.properties.border-image-repeat πŸ“‹Chrome10/25/2011 Safari7/25/2012274
css.properties.border-image-repeat.repeat πŸ“‹Chrome10/25/2011 Safari7/25/2012274
css.properties.border-image-repeat.stretch πŸ“‹Chrome10/25/2011 Safari7/25/2012274
css.properties.border-image-slice πŸ“‹Chrome10/25/2011 Safari7/25/2012274
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 πŸ“‹Chrome10/25/2011 Safari7/25/2012274
css.properties.border-image-source.none πŸ“‹Chrome10/25/2011 Safari7/25/2012274
css.properties.border-image-width πŸ“‹Chrome12/13/2011 Safari7/25/2012225
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 πŸ“‹Chrome12/13/2011 Safari7/25/2012225
css.properties.filter.blur πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.brightness πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.contrast πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.drop-shadow πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.grayscale πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.hue-rotate πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.invert πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.none πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.opacity πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.filter.saturate πŸ“‹Chrome3/28/2012 Safari7/25/2012119
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 πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.properties.flood-color πŸ“‹Chrome5/25/2010 Safari7/25/2012792
css.properties.flood-color.currentColor πŸ“‹Chrome5/25/2010 Safari7/25/2012792
css.properties.flood-color.transparent πŸ“‹Chrome5/25/2010 Safari7/25/2012792
css.properties.flood-opacity πŸ“‹Chrome5/25/2010 Safari7/25/2012792
css.properties.image-rendering πŸ“‹Chrome8/2/2011 Safari7/25/2012358
css.properties.image-rendering.auto πŸ“‹Chrome8/2/2011 Safari7/25/2012358
css.properties.lighting-color πŸ“‹Chrome5/25/2010 Safari7/25/2012792
css.properties.lighting-color.currentColor πŸ“‹Chrome5/25/2010 Safari7/25/2012792
css.properties.lighting-color.transparent πŸ“‹Chrome5/25/2010 Safari7/25/2012792
css.properties.text-rendering.geometricPrecision Chrome8/2/2011 Safari7/25/2012358
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.transform-origin.svg_elements Chrome5/15/2012 Safari7/25/201271
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)" />).
css.selectors.first πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.calc.gradient_color_stops Chrome5/15/2012 Safari7/25/201271
css.types.easing-function.cubic-bezier πŸ“‹Chrome12/13/2011 Safari7/25/2012225
css.types.filter-function πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.blur πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.brightness πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.contrast πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.drop-shadow πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.grayscale πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.hue-rotate πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.invert πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.opacity πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.saturate πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.filter-function.sepia πŸ“‹Chrome3/28/2012 Safari7/25/2012119
css.types.length.vh Chrome6/26/2012 Safari7/25/201229
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 Chrome6/26/2012 Safari7/25/201229
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.

2012/3

API First Browser Date Last Browser Date Days Notes
css.properties.max-height.none πŸ“‹Safari4/15/2005 Chrome3/28/20122539

2011/12

API First Browser Date Last Browser Date Days Notes
css.properties.border-image.none πŸ“‹Safari10/26/2007 Chrome12/13/20111509
css.properties.border-image.repeat πŸ“‹Safari10/26/2007 Chrome12/13/20111509
css.properties.border-image.round πŸ“‹Safari10/26/2007 Chrome12/13/20111509
css.properties.border-image.space πŸ“‹Safari10/26/2007 Chrome12/13/20111509
css.properties.border-image.stretch πŸ“‹Safari10/26/2007 Chrome12/13/20111509

2011/10

API First Browser Date Last Browser Date Days Notes
css.properties.clip-rule πŸ“‹Safari6/7/2010 Chrome10/25/2011505
css.properties.clip-rule.evenodd πŸ“‹Safari6/7/2010 Chrome10/25/2011505
css.properties.clip-rule.nonzero πŸ“‹Safari6/7/2010 Chrome10/25/2011505

2011/9

API First Browser Date Last Browser Date Days Notes
css.properties.table-layout πŸ“‹Safari6/23/2003 Chrome9/16/20113007
css.properties.table-layout.auto πŸ“‹Safari6/23/2003 Chrome9/16/20113007
css.properties.table-layout.fixed πŸ“‹Safari6/23/2003 Chrome9/16/20113007

2011/8

API First Browser Date Last Browser Date Days Notes
css.properties.list-style-type.lower-armenian πŸ“‹Safari7/20/2011 Chrome8/2/201113
css.properties.list-style-type.upper-armenian πŸ“‹Safari7/20/2011 Chrome8/2/201113

2011/7

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.WOFF πŸ“‹Chrome9/2/2010 Safari7/20/2011321
css.properties.-webkit-border-before Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-locale Chrome4/27/2011 Safari7/20/201184
css.properties.-webkit-logical-height Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-logical-width Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-margin-after Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-margin-before Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-max-logical-height Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-max-logical-width Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-min-logical-height Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-min-logical-width Chrome12/2/2010 Safari7/20/2011230
css.properties.-webkit-text-combine Chrome2/3/2011 Safari7/20/2011167
css.properties.alignment-baseline πŸ“‹Chrome12/11/2008 Safari7/20/2011951
css.properties.alignment-baseline.alphabetic Chrome12/11/2008 Safari7/20/2011951
css.properties.alignment-baseline.baseline Chrome12/11/2008 Safari7/20/2011951
css.properties.alignment-baseline.central Chrome12/11/2008 Safari7/20/2011951
css.properties.alignment-baseline.ideographic Chrome12/11/2008 Safari7/20/2011951
css.properties.alignment-baseline.mathematical Chrome12/11/2008 Safari7/20/2011951
css.properties.alignment-baseline.middle Chrome12/11/2008 Safari7/20/2011951
css.properties.alignment-baseline.text-after-edge Chrome12/11/2008 Safari7/20/2011951
css.properties.alignment-baseline.text-before-edge Chrome12/11/2008 Safari7/20/2011951
css.properties.backface-visibility.hidden πŸ“‹Chrome6/7/2011 Safari7/20/201143
css.properties.backface-visibility.visible πŸ“‹Chrome6/7/2011 Safari7/20/201143
css.properties.block-size.auto πŸ“‹Chrome12/2/2010 Safari7/20/2011230
css.properties.border-radius.percentages Chrome12/2/2010 Safari7/20/2011230
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.box-shadow πŸ“‹Chrome3/8/2011 Safari7/20/2011134
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-sizing πŸ“‹Chrome3/8/2011 Safari7/20/2011134
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.column-span.all πŸ“‹Chrome9/2/2010 Safari7/20/2011321
css.properties.column-span.none πŸ“‹Chrome9/2/2010 Safari7/20/2011321
css.properties.hyphenate-character.auto πŸ“‹Chrome9/2/2010 Safari7/20/2011321
css.properties.inline-size.auto πŸ“‹Chrome12/2/2010 Safari7/20/2011230
css.properties.letter-spacing.svg_elements Chrome12/11/2008 Safari7/20/2011951
css.properties.vector-effect πŸ“‹Chrome9/2/2010 Safari7/20/2011321
css.properties.vector-effect.non-scaling-stroke πŸ“‹Chrome9/2/2010 Safari7/20/2011321
css.properties.vector-effect.none πŸ“‹Chrome9/2/2010 Safari7/20/2011321
css.properties.word-spacing.svg_elements Chrome12/11/2008 Safari7/20/2011951
css.selectors.-webkit-meter-bar Chrome6/7/2011 Safari7/20/201143
css.selectors.-webkit-meter-even-less-good-value Chrome6/7/2011 Safari7/20/201143
css.selectors.-webkit-meter-optimum-value Chrome6/7/2011 Safari7/20/201143
css.selectors.-webkit-meter-suboptimum-value Chrome6/7/2011 Safari7/20/201143
css.selectors.in-range πŸ“‹Chrome3/8/2011 Safari7/20/2011134
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.indeterminate.progress Chrome9/2/2010 Safari7/20/2011321
css.selectors.out-of-range πŸ“‹Chrome3/8/2011 Safari7/20/2011134
css.types.easing-function.steps πŸ“‹Chrome12/2/2010 Safari7/20/2011230

2011/6

API First Browser Date Last Browser Date Days Notes
css.properties.perspective.none πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.properties.perspective-origin.bottom πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.properties.perspective-origin.center πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.properties.perspective-origin.left πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.properties.perspective-origin.right πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.properties.perspective-origin.top πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.properties.transform.3d Safari6/8/2009 Chrome6/7/2011729
css.properties.transform-origin.three_value_syntax Safari6/7/2010 Chrome6/7/2011365
css.properties.transform-style.flat πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.properties.transform-style.preserve-3d πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.types.transform-function.matrix3d πŸ“‹Safari6/8/2009 Chrome6/7/2011729
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 Chrome6/7/2011729
css.types.transform-function.rotate3d πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.types.transform-function.rotateX πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.types.transform-function.rotateY πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.types.transform-function.rotateZ πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.types.transform-function.scale3d πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.types.transform-function.scaleZ πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.types.transform-function.translate3d πŸ“‹Safari6/8/2009 Chrome6/7/2011729
css.types.transform-function.translateZ πŸ“‹Safari6/8/2009 Chrome6/7/2011729

2011/3

API First Browser Date Last Browser Date Days Notes
css.selectors.default πŸ“‹Safari6/7/2010 Chrome3/8/2011274
css.selectors.invalid πŸ“‹Safari6/7/2010 Chrome3/8/2011274
css.selectors.optional πŸ“‹Safari6/7/2010 Chrome3/8/2011274
css.selectors.required πŸ“‹Safari6/7/2010 Chrome3/8/2011274
css.selectors.valid πŸ“‹Safari6/7/2010 Chrome3/8/2011274

2010/12

API First Browser Date Last Browser Date Days Notes
css.properties.background-image.svg_images Safari6/7/2010 Chrome12/2/2010178
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.mask-image.svg_masks Safari6/8/2009 Chrome12/2/2010542

2010/10

API First Browser Date Last Browser Date Days Notes
css.properties.border-image.gradient Safari6/8/2009 Chrome10/19/2010498

2010/9

API First Browser Date Last Browser Date Days Notes
css.properties.line-clamp πŸ“‹Safari6/7/2010 Chrome9/2/201087
Safari: Accidental exposure.Safari on iOS: Accidental exposure.WebView on iOS: Accidental exposure.
css.properties.list-style-type.arabic-indic πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.bengali πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.cambodian πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.cjk-earthly-branch πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.cjk-heavenly-stem πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.devanagari πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.ethiopic-halehame-ti-er Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.ethiopic-halehame-ti-et Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.gujarati πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.gurmukhi πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.hangul Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.hangul-consonant Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.kannada πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.khmer πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.lao πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.malayalam πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.mongolian πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.myanmar πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.oriya πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.persian πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.telugu πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.thai πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.tibetan πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.properties.list-style-type.urdu Safari6/7/2010 Chrome9/2/201087
css.selectors.-webkit-inner-spin-button Safari6/7/2010 Chrome9/2/201087
css.selectors.left πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.selectors.right πŸ“‹Safari6/7/2010 Chrome9/2/201087
css.selectors.visited.privacy_measures Safari6/7/2010 Chrome9/2/201087

2010/6

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.aspect-ratio πŸ“‹Chrome9/15/2009 Safari6/7/2010265
css.at-rules.media.orientation πŸ“‹Chrome9/15/2009 Safari6/7/2010265
css.properties.animation-fill-mode.backwards πŸ“‹Chrome9/15/2009 Safari6/7/2010265
css.properties.animation-fill-mode.both πŸ“‹Chrome9/15/2009 Safari6/7/2010265
css.properties.animation-fill-mode.forwards πŸ“‹Chrome9/15/2009 Safari6/7/2010265
css.properties.animation-fill-mode.none πŸ“‹Chrome9/15/2009 Safari6/7/2010265
css.properties.background-clip πŸ“‹Chrome12/11/2008 Safari6/7/2010543
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-repeat.2-value Chrome9/15/2009 Safari6/7/2010265
css.properties.background-size πŸ“‹Chrome9/15/2009 Safari6/7/2010265
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.contain πŸ“‹Chrome9/15/2009 Safari6/7/2010265
css.properties.background-size.cover πŸ“‹Chrome9/15/2009 Safari6/7/2010265
css.properties.border-bottom-left-radius πŸ“‹Chrome1/25/2010 Safari6/7/2010133
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.percentages Chrome1/25/2010 Safari6/7/2010133
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 πŸ“‹Chrome1/25/2010 Safari6/7/2010133
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.percentages Chrome1/25/2010 Safari6/7/2010133
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-radius πŸ“‹Chrome1/25/2010 Safari6/7/2010133
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 Chrome1/25/2010 Safari6/7/2010133
css.properties.border-top-left-radius πŸ“‹Chrome1/25/2010 Safari6/7/2010133
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.percentages Chrome1/25/2010 Safari6/7/2010133
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 πŸ“‹Chrome1/25/2010 Safari6/7/2010133
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.percentages Chrome1/25/2010 Safari6/7/2010133
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.box-shadow.inset Chrome12/11/2008 Safari6/7/2010543
Internet Explorer: inset must be the last keyword in the declaration.
css.properties.box-shadow.spread_radius Chrome12/11/2008 Safari6/7/2010543
css.properties.cursor.none πŸ“‹Chrome5/25/2010 Safari6/7/201013
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.list-style-type.cjk-ideographic πŸ“‹Chrome12/11/2008 Safari6/7/2010543
Opera: Until version 15, only decimal numbers display.Opera Android: Until version 15, only decimal numbers display.
css.properties.text-rendering πŸ“‹Chrome1/25/2010 Safari6/7/2010133
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 Chrome1/25/2010 Safari6/7/2010133
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.types.length.rem Chrome1/25/2010 Safari6/7/2010133
css.types.ratio πŸ“‹Chrome9/15/2009 Safari6/7/2010265

2010/5

API First Browser Date Last Browser Date Days Notes
css.properties.font-smooth Safari6/8/2009 Chrome5/25/2010351
Firefox: Only works on macOS.

2010/1

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.font-family πŸ“‹Safari3/18/2008 Chrome1/25/2010678
css.at-rules.font-face.font-style πŸ“‹Safari3/18/2008 Chrome1/25/2010678
css.at-rules.font-face.font-variant Safari3/18/2008 Chrome1/25/2010678
css.at-rules.font-face.font-weight πŸ“‹Safari3/18/2008 Chrome1/25/2010678
css.at-rules.font-face.src πŸ“‹Safari3/18/2008 Chrome1/25/2010678
css.properties.-webkit-box-reflect Safari6/8/2009 Chrome1/25/2010231
css.properties.-webkit-text-stroke πŸ“‹Safari10/26/2007 Chrome1/25/2010822
css.properties.resize.block_level_support Safari6/8/2009 Chrome1/25/2010231
Firefox: resize doesn't have any effect on <iframe>. See bug 680823)
css.selectors.first-child πŸ“‹Safari3/18/2008 Chrome1/25/2010678
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.nth-last-child πŸ“‹Safari3/18/2008 Chrome1/25/2010678
css.selectors.nth-last-of-type πŸ“‹Safari3/18/2008 Chrome1/25/2010678
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.types.easing-function πŸ“‹Safari3/18/2008 Chrome1/25/2010678

2009/9

API First Browser Date Last Browser Date Days Notes
css.properties.animation.alternate πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.alternate-reverse πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.auto πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.backwards πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.both πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.ease πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.ease-in πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.ease-in-out πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.ease-out πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.forwards πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.infinite πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.linear πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.none πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.normal πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.paused πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.reverse πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.running πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.step-end πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation.step-start πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-direction.alternate πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-direction.normal πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-iteration-count.infinite πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-name.none πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-play-state.paused πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-play-state.running πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-timing-function.ease πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-timing-function.ease-in πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-timing-function.ease-in-out πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-timing-function.ease-out πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-timing-function.linear πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-timing-function.step-end πŸ“‹Safari6/8/2009 Chrome9/15/200999
css.properties.animation-timing-function.step-start πŸ“‹Safari6/8/2009 Chrome9/15/200999

2009/6

API First Browser Date Last Browser Date Days Notes
css.at-rules.charset πŸ“‹Chrome5/21/2009 Safari6/8/200918
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.media.-webkit-transform-3d πŸ“‹Chrome5/21/2009 Safari6/8/200918
css.properties.-webkit-border-horizontal-spacing Chrome12/11/2008 Safari6/8/2009179
css.properties.-webkit-border-vertical-spacing Chrome12/11/2008 Safari6/8/2009179
css.properties.-webkit-column-break-after Chrome12/11/2008 Safari6/8/2009179
css.properties.-webkit-column-break-before Chrome12/11/2008 Safari6/8/2009179
css.properties.-webkit-column-break-inside Chrome12/11/2008 Safari6/8/2009179
css.properties.-webkit-perspective-origin-x Chrome5/21/2009 Safari6/8/200918
css.properties.-webkit-perspective-origin-y Chrome5/21/2009 Safari6/8/200918
css.properties.-webkit-rtl-ordering Chrome12/11/2008 Safari6/8/2009179
css.properties.-webkit-transform-origin-x Chrome12/11/2008 Safari6/8/2009179
css.properties.-webkit-transform-origin-y Chrome12/11/2008 Safari6/8/2009179
css.properties.-webkit-transform-origin-z Chrome5/21/2009 Safari6/8/200918
css.properties.-webkit-user-drag Chrome12/11/2008 Safari6/8/2009179
css.properties.background-image.gradients πŸ“‹Chrome12/11/2008 Safari6/8/2009179
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.baseline-shift πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.baseline-shift.baseline πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.baseline-shift.sub πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.baseline-shift.super πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.color-interpolation πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.color-interpolation.auto πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.color-interpolation.sRGB πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.display.table-caption Chrome12/11/2008 Safari6/8/2009179
css.properties.dominant-baseline πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.dominant-baseline.alphabetic πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.dominant-baseline.auto πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.dominant-baseline.central πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.dominant-baseline.hanging πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.dominant-baseline.ideographic πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.dominant-baseline.mathematical πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.dominant-baseline.middle πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.fill πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.fill.none πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.fill-opacity πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.fill-rule πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.fill-rule.evenodd πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.fill-rule.nonzero πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.marker πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.marker.none πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.marker-end πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.marker-end.none πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.marker-mid πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.marker-mid.none πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.marker-start πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.marker-start.none πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.mask-clip.border Chrome12/11/2008 Safari6/8/2009179
Chrome: Only works when using -webkit-mask-clip.Chrome Android: Only works when using -webkit-mask-clip.Edge: Only works when using -webkit-mask-clip.Quest Browser: Only works when using -webkit-mask-clip.Opera: Only works when using -webkit-mask-clip.Opera Android: Only works when using -webkit-mask-clip.Samsung Internet: Only works when using -webkit-mask-clip.
css.properties.mask-clip.content Chrome12/11/2008 Safari6/8/2009179
Chrome: Only works when using -webkit-mask-clip.Chrome Android: Only works when using -webkit-mask-clip.Edge: Only works when using -webkit-mask-clip.Quest Browser: Only works when using -webkit-mask-clip.Opera: Only works when using -webkit-mask-clip.Opera Android: Only works when using -webkit-mask-clip.Samsung Internet: Only works when using -webkit-mask-clip.
css.properties.mask-clip.padding Chrome12/11/2008 Safari6/8/2009179
Chrome: Only works when using -webkit-mask-clip.Chrome Android: Only works when using -webkit-mask-clip.Edge: Only works when using -webkit-mask-clip.Quest Browser: Only works when using -webkit-mask-clip.Opera: Only works when using -webkit-mask-clip.Opera Android: Only works when using -webkit-mask-clip.Samsung Internet: Only works when using -webkit-mask-clip.
css.properties.mask-clip.text Chrome12/11/2008 Safari6/8/2009179
Chrome: Only works when using -webkit-mask-clip.Chrome Android: Only works when using -webkit-mask-clip.Edge: Only works when using -webkit-mask-clip.Quest Browser: Only works when using -webkit-mask-clip.Opera: Only works when using -webkit-mask-clip.Opera Android: Only works when using -webkit-mask-clip.Samsung Internet: Only works when using -webkit-mask-clip.
css.properties.mask-image.multiple_mask_images Chrome12/11/2008 Safari6/8/2009179
css.properties.pointer-events πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.pointer-events.all πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.pointer-events.auto πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.pointer-events.fill πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.pointer-events.html_elements Chrome5/21/2009 Safari6/8/200918
css.properties.pointer-events.none πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.pointer-events.painted πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.pointer-events.stroke πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.pointer-events.visible πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.shape-rendering πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.shape-rendering.auto πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stop-color πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stop-opacity πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke.none πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-dasharray πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-dasharray.none πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-dashoffset πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-linecap πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-linecap.butt πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-linecap.round πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-linecap.square πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-linejoin πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-linejoin.bevel πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-linejoin.miter πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-linejoin.round πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-miterlimit πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-opacity πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.stroke-width πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.text-align.center πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.text-align.left πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.text-align.right πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.text-anchor πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.text-anchor.end πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.text-anchor.middle πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.text-anchor.start πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.properties.transition-property.IDENT_value Chrome12/11/2008 Safari6/8/2009179
css.selectors.-webkit-resizer Chrome5/21/2009 Safari6/8/200918
css.selectors.-webkit-scrollbar Chrome5/21/2009 Safari6/8/200918
Safari on iOS: From Safari 13, only display: none works with this pseudo-element. Other styles have no effect.WebView on iOS: From Safari 13, only display: none works with this pseudo-element. Other styles have no effect.
css.selectors.-webkit-scrollbar-button Chrome5/21/2009 Safari6/8/200918
css.selectors.-webkit-scrollbar-corner Chrome5/21/2009 Safari6/8/200918
css.selectors.-webkit-scrollbar-thumb Chrome5/21/2009 Safari6/8/200918
css.selectors.-webkit-scrollbar-track Chrome5/21/2009 Safari6/8/200918
css.selectors.-webkit-scrollbar-track-piece Chrome5/21/2009 Safari6/8/200918
css.selectors.after πŸ“‹Chrome12/11/2008 Safari6/8/2009179
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.before πŸ“‹Chrome12/11/2008 Safari6/8/2009179
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.read-only πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.selectors.read-write πŸ“‹Chrome12/11/2008 Safari6/8/2009179
css.types.angle πŸ“‹Chrome5/21/2009 Safari6/8/200918
css.types.angle.deg Chrome5/21/2009 Safari6/8/200918
css.types.angle.grad Chrome5/21/2009 Safari6/8/200918
css.types.angle.rad Chrome5/21/2009 Safari6/8/200918
css.types.angle.turn Chrome5/21/2009 Safari6/8/200918
css.types.angle-percentage πŸ“‹Chrome5/21/2009 Safari6/8/200918
css.types.color.currentcolor πŸ“‹Chrome12/11/2008 Safari6/8/2009179

2009/5

API First Browser Date Last Browser Date Days Notes
css.properties.counter-increment πŸ“‹Safari10/26/2007 Chrome5/21/2009573
css.properties.counter-increment.none πŸ“‹Safari10/26/2007 Chrome5/21/2009573
css.properties.counter-reset πŸ“‹Safari10/26/2007 Chrome5/21/2009573
css.properties.counter-reset.none πŸ“‹Safari10/26/2007 Chrome5/21/2009573
css.properties.direction πŸ“‹Safari6/23/2003 Chrome5/21/20092159
css.properties.direction.ltr πŸ“‹Safari6/23/2003 Chrome5/21/20092159
css.properties.direction.rtl πŸ“‹Safari6/23/2003 Chrome5/21/20092159
css.properties.font-weight πŸ“‹Safari6/23/2003 Chrome5/21/20092159
css.properties.font-weight.bold πŸ“‹Safari6/23/2003 Chrome5/21/20092159
css.properties.font-weight.bolder πŸ“‹Safari6/23/2003 Chrome5/21/20092159
css.properties.font-weight.lighter πŸ“‹Safari6/23/2003 Chrome5/21/20092159
css.properties.font-weight.normal πŸ“‹Safari6/23/2003 Chrome5/21/20092159
css.properties.text-shadow πŸ“‹Safari10/24/2003 Chrome5/21/20092036
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 Chrome5/21/20092036
css.properties.unicode-bidi πŸ“‹Safari4/15/2005 Chrome5/21/20091497
css.properties.unicode-bidi.bidi-override πŸ“‹Safari4/15/2005 Chrome5/21/20091497
css.properties.unicode-bidi.embed πŸ“‹Safari4/15/2005 Chrome5/21/20091497
css.properties.unicode-bidi.normal πŸ“‹Safari4/15/2005 Chrome5/21/20091497
css.selectors.only-child πŸ“‹Safari3/18/2008 Chrome5/21/2009429
css.types.attr πŸ“‹Safari3/18/2008 Chrome5/21/2009429

2008/12

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.at-rules.font-face.unicode-range πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.at-rules.import πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.at-rules.media πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.-webkit-device-pixel-ratio πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/2008412
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 Chrome12/11/2008412
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.at-rules.media.color πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.device-aspect-ratio πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.device-height πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.device-width πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.grid πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.height πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.media_features Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.monochrome πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.media.width πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.at-rules.namespace πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.-webkit-mask-box-image Safari3/18/2008 Chrome12/11/2008268
css.properties.-webkit-mask-composite Safari3/18/2008 Chrome12/11/2008268
css.properties.-webkit-mask-position-x Safari3/18/2008 Chrome12/11/2008268
css.properties.-webkit-mask-position-y Safari3/18/2008 Chrome12/11/2008268
css.properties.-webkit-text-fill-color πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.-webkit-text-security Safari10/26/2007 Chrome12/11/2008412
css.properties.-webkit-text-stroke-color πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.-webkit-text-stroke-width πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.button πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.checkbox πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.listbox πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.menulist πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.menulist-button πŸ“‹Safari10/26/2007 Chrome12/11/2008412
Firefox: See bug 1481615.Firefox for Android: See bug 1481615.
css.properties.appearance.meter πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.none πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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">.
css.properties.appearance.progress-bar πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.radio πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.searchfield πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.textarea πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.appearance.textfield πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.background πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.SVG_image_as_background Safari3/18/2008 Chrome12/11/2008268
css.properties.background.local πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.multiple_backgrounds Safari4/15/2005 Chrome12/11/20081336
css.properties.background.no-repeat πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.repeat πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.repeat-x πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.repeat-y πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.round πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.scroll πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.space πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-attachment πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-attachment.multiple_backgrounds Safari4/15/2005 Chrome12/11/20081336
css.properties.background-attachment.scroll πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-clip.border-box πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.background-clip.content-box πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/2008412
css.properties.background-color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.background-image πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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.multiple_backgrounds Safari4/15/2005 Chrome12/11/20081336
css.properties.background-image.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-origin πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/2008412
css.properties.background-origin.content-box πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/2008412
css.properties.background-position πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-position.bottom πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-position.center πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-position.left πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-position.multiple_backgrounds Safari4/15/2005 Chrome12/11/20081336
css.properties.background-position.right πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-position.top πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-position-x πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-position-y πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-repeat πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-repeat.multiple_backgrounds Safari4/15/2005 Chrome12/11/20081336
css.properties.background-repeat.no-repeat πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-repeat.repeat πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-repeat.repeat-x πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-repeat.repeat-y πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.background-size.auto πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.border πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.dashed πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.dashed πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-color.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-left-radius.elliptical_corners Safari10/26/2007 Chrome12/11/2008412
css.properties.border-bottom-right-radius.elliptical_corners Safari10/26/2007 Chrome12/11/2008412
css.properties.border-bottom-style πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.border-bottom-style.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-style.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-style.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-style.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-style.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-style.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-style.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-style.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-style.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-width πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-width.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-width.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-bottom-width.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-collapse πŸ“‹Safari10/24/2003 Chrome12/11/20081875
css.properties.border-collapse.collapse Safari10/24/2003 Chrome12/11/20081875
css.properties.border-collapse.separate Safari10/24/2003 Chrome12/11/20081875
css.properties.border-color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-color.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.dashed πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-color.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.border-left-style.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-style.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-width πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-width.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-width.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-left-width.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-radius.elliptical_borders Safari10/26/2007 Chrome12/11/2008412
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-right πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.dashed πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-color.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.border-right-style.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-style.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-width πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-width.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-width.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-right-width.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-spacing πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.border-style.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-style.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.dashed πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-color.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-left-radius.elliptical_corners Safari10/26/2007 Chrome12/11/2008412
css.properties.border-top-right-radius.elliptical_corners Safari10/26/2007 Chrome12/11/2008412
css.properties.border-top-style πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.border-top-style.dotted πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-style.double πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-style.groove πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-style.hidden πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-style.inset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-style.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-style.outset πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-style.ridge πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-style.solid πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-width πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-width.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-width.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-top-width.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-width πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-width.medium πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-width.thick πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.border-width.thin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.bottom πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.box-align Safari10/26/2007 Chrome12/11/2008412
css.properties.box-direction Safari10/26/2007 Chrome12/11/2008412
css.properties.box-flex Safari10/26/2007 Chrome12/11/2008412
css.properties.box-ordinal-group Safari10/26/2007 Chrome12/11/2008412
css.properties.box-orient Safari10/26/2007 Chrome12/11/2008412
css.properties.box-pack Safari10/26/2007 Chrome12/11/2008412
css.properties.box-shadow.multiple_shadows Safari10/26/2007 Chrome12/11/2008412
css.properties.box-shadow.none πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.box-sizing.border-box πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.box-sizing.content-box πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.caption-side πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.caption-side.bottom Safari6/23/2003 Chrome12/11/20081998
css.properties.caption-side.top Safari6/23/2003 Chrome12/11/20081998
css.properties.clear πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.clear.both πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.clear.left πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.clear.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.clear.right πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.clip πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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.clip.auto Safari6/23/2003 Chrome12/11/20081998
css.properties.color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.color.transparent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.color-interpolation-filters πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.color-interpolation-filters.auto πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-count.auto πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-gap πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-gap.normal πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.dashed πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.dotted πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.double πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.groove πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.hidden πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.inset πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.medium πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.none πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.outset πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.ridge πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.solid πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.thick πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.thin πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule.transparent πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-color.transparent πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.dashed πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.dotted πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.double πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.groove πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.hidden πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.inset πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.none πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.outset πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.ridge πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-style.solid πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-width.medium πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-width.thick πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-rule-width.thin πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.column-width.auto Safari10/26/2007 Chrome12/11/2008412
css.properties.content πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.content.close-quote πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.content.no-close-quote πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.content.no-open-quote πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.content.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.content.normal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.content.open-quote πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.content.url πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.cursor πŸ“‹Safari2/2/2004 Chrome12/11/20081774
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/20081774
css.properties.cursor.cell πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.cursor.col-resize πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/20081774
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 Chrome12/11/20081774
css.properties.cursor.url Safari10/26/2007 Chrome12/11/2008412
Firefox: Firefox 4 added macOS support.
css.properties.cursor.url_positioning_syntax Safari10/26/2007 Chrome12/11/2008412
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.cursor.vertical-text πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/20081774
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 Chrome12/11/20081774
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 πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.display.block πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.display.inline πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.display.inline-block Safari6/23/2003 Chrome12/11/20081998
Internet Explorer: Until Internet Explorer 8, inline-block is only for natural inline elements.
css.properties.display.inline-table Safari6/23/2003 Chrome12/11/20081998
css.properties.display.list-item πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.display.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.display.table-cell Safari6/23/2003 Chrome12/11/20081998
css.properties.display.table-column Safari6/23/2003 Chrome12/11/20081998
css.properties.display.table-column-group Safari6/23/2003 Chrome12/11/20081998
css.properties.display.table-footer-group Safari6/23/2003 Chrome12/11/20081998
css.properties.display.table-header-group Safari6/23/2003 Chrome12/11/20081998
css.properties.display.table-row Safari6/23/2003 Chrome12/11/20081998
css.properties.display.table-row-group Safari6/23/2003 Chrome12/11/20081998
css.properties.empty-cells πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.empty-cells.hide πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.empty-cells.show πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.float πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.float.left πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.float.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.float.right πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font.caption Safari6/23/2003 Chrome12/11/20081998
css.properties.font.icon Safari6/23/2003 Chrome12/11/20081998
css.properties.font.menu Safari6/23/2003 Chrome12/11/20081998
css.properties.font.message-box Safari6/23/2003 Chrome12/11/20081998
css.properties.font.small-caption Safari6/23/2003 Chrome12/11/20081998
css.properties.font.status-bar Safari6/23/2003 Chrome12/11/20081998
css.properties.font-family πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.font-family.fangsong πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-family.fantasy πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-family.kai πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-family.khmer-mul πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-family.monospace πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-family.nastaliq πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-family.sans-serif πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-family.serif πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-size πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-style πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.font-style.normal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-style.oblique πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.font-variant πŸ“‹Safari6/23/2003 Chrome12/11/20081998
Internet Explorer: Only supports the small-caps and normal keywords.
css.properties.font-variant.normal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.height πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.height.auto πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.left πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.left.auto πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.letter-spacing πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.letter-spacing.normal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.line-break.normal πŸ“‹Safari4/29/2005 Chrome12/11/20081322
css.properties.line-height πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.line-height.normal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style.inside πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style.outside πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-image πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.list-style-position πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.list-style-position.outside πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.armenian πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.circle πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.decimal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.decimal-leading-zero πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.disc πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.georgian πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.hebrew πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.hiragana πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.hiragana-iroha πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.katakana πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.katakana-iroha πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.lower-alpha πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.lower-greek πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.lower-latin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.lower-roman πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.square πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.upper-alpha πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.upper-latin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.list-style-type.upper-roman πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.margin πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.margin.auto Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.margin-bottom.auto πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.margin-left.auto Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.margin-right.auto Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.margin-top.auto Safari6/23/2003 Chrome12/11/20081998
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 πŸ“‹Safari4/15/2005 Chrome12/11/20081336
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-width πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.min-height πŸ“‹Safari4/15/2005 Chrome12/11/20081336
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-width πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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.opacity πŸ“‹Safari4/29/2005 Chrome12/11/20081322
css.properties.outline.auto πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.dashed πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.dotted πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.double πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.groove πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.inset πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.medium πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.none πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.outset πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.ridge πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.solid πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.thick πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.thin πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline.transparent πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-color πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-color.transparent πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-offset πŸ“‹Safari2/2/2004 Chrome12/11/20081774
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 πŸ“‹Safari2/2/2004 Chrome12/11/20081774
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 Chrome12/11/20081774
css.properties.outline-style.dashed πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-style.dotted πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-style.double πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-style.groove πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-style.inset πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-style.none πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-style.outset πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-style.ridge πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-style.solid πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-width πŸ“‹Safari2/2/2004 Chrome12/11/20081774
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 Chrome12/11/20081774
css.properties.outline-width.thick πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.outline-width.thin πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.overflow πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow.hidden πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow.scroll πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow.visible πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow-wrap.break-word πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.overflow-wrap.normal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.overflow-x πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow-x.auto πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/2008412
css.properties.overflow-x.scroll πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow-x.visible πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow-y πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow-y.auto πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/2008412
css.properties.overflow-y.scroll πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.overflow-y.visible πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.padding πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.padding-bottom πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.padding-left πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.padding-right πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.padding-top πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.page-break-after πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-after.always πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-after.auto πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-after.left πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-after.right πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-before πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-before.always πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-before.auto πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-before.left πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-before.right πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.properties.page-break-inside πŸ“‹Safari4/15/2005 Chrome12/11/20081336
css.properties.page-break-inside.auto πŸ“‹Safari4/15/2005 Chrome12/11/20081336
css.properties.page-break-inside.avoid πŸ“‹Safari4/15/2005 Chrome12/11/20081336
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.position πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.position.absolute πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.position.static πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.resize πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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.both πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.resize.horizontal πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.resize.none πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.resize.vertical πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.right πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.right.auto πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-align πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-align.end πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.text-align.justify πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-align.start πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.text-decoration πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-decoration.line-through πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-decoration.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-decoration.overline πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-decoration.underline πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-indent πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-overflow πŸ“‹Safari4/15/2005 Chrome12/11/20081336
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 Chrome12/11/20081336
css.properties.text-overflow.ellipsis πŸ“‹Safari4/15/2005 Chrome12/11/20081336
css.properties.text-transform πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.text-transform.none πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-transform.uppercase πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.text-transform.uppercase_eszett Safari6/23/2003 Chrome12/11/20081998
css.properties.top πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.properties.transform.none πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transform-origin.bottom πŸ“‹Safari4/29/2005 Chrome12/11/20081322
css.properties.transform-origin.center πŸ“‹Safari4/29/2005 Chrome12/11/20081322
css.properties.transform-origin.left πŸ“‹Safari4/29/2005 Chrome12/11/20081322
css.properties.transform-origin.right πŸ“‹Safari4/29/2005 Chrome12/11/20081322
css.properties.transform-origin.top πŸ“‹Safari4/29/2005 Chrome12/11/20081322
css.properties.transition.all πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition.ease πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition.ease-in πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition.ease-in-out πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition.ease-out πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition.linear πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition.none πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition.step-end πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition.step-start πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-property.all πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-property.none πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-timing-function.ease πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-timing-function.ease-in πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-timing-function.ease-in-out πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-timing-function.ease-out πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-timing-function.linear πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-timing-function.step-end πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.transition-timing-function.step-start πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.properties.user-modify Safari10/26/2007 Chrome12/11/2008412
Firefox: While the CSS property is parsed and accepted, it does not have any effect.Firefox for Android: While the CSS property is parsed and accepted, it does not have any effect.
css.properties.user-modify.read-write-plaintext-only Safari10/26/2007 Chrome12/11/2008412
css.properties.user-select.auto Safari4/29/2005 Chrome12/11/20081322
css.properties.user-select.none Safari4/29/2005 Chrome12/11/20081322
css.properties.user-select.text Safari4/29/2005 Chrome12/11/20081322
css.properties.vertical-align πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.vertical-align.baseline πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.vertical-align.bottom πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.vertical-align.middle πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.vertical-align.sub πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.vertical-align.super πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.vertical-align.text-bottom πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.vertical-align.text-top πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.vertical-align.top πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.visibility πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 πŸ“‹Safari4/15/2005 Chrome12/11/20081336
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 Chrome12/11/20081998
css.properties.visibility.visible πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.white-space πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.white-space.normal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.white-space.nowrap πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.white-space.pre πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.white-space.pre-line πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.white-space.pre-wrap πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/20081998
css.properties.width πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.width.auto πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.word-break πŸ“‹Safari10/26/2007 Chrome12/11/2008412
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 Chrome12/11/2008412
css.properties.word-break.break-word πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.word-break.normal πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.properties.word-spacing πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.word-spacing.normal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.z-index πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.z-index.auto πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.properties.z-index.negative_values Safari6/23/2003 Chrome12/11/20081998
css.properties.zoom πŸ“‹Safari3/18/2008 Chrome12/11/2008268
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.
css.selectors.-webkit-search-cancel-button Safari10/26/2007 Chrome12/11/2008412
css.selectors.-webkit-search-results-button Safari10/26/2007 Chrome12/11/2008412
css.selectors.active πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.selectors.active.non_a_elements Safari6/23/2003 Chrome12/11/20081998
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.attribute πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.selectors.checked πŸ“‹Safari3/18/2008 Chrome12/11/2008268
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 Chrome12/11/20081998
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.class πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.selectors.descendant πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.selectors.disabled πŸ“‹Safari3/18/2008 Chrome12/11/2008268
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 πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.selectors.enabled πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.selectors.first-letter πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.selectors.first-line πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/2008268
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 Chrome12/11/20081998
css.selectors.hover πŸ“‹Safari4/29/2005 Chrome12/11/20081322
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 Safari4/29/2005 Chrome12/11/20081322
css.selectors.hover.all_elements Safari4/29/2005 Chrome12/11/20081322
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 Chrome12/11/20081998
css.selectors.indeterminate πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.selectors.indeterminate.checkbox Safari10/26/2007 Chrome12/11/2008412
css.selectors.lang πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.selectors.last-child πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.selectors.last-of-type πŸ“‹Safari3/18/2008 Chrome12/11/2008268
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 Chrome12/11/20081998
css.selectors.list πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.selectors.namespace πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.selectors.next-sibling πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.selectors.nth-child πŸ“‹Safari3/18/2008 Chrome12/11/2008268
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-of-type πŸ“‹Safari3/18/2008 Chrome12/11/2008268
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-of-type πŸ“‹Safari3/18/2008 Chrome12/11/2008268
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.root πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.selectors.selection πŸ“‹Safari10/24/2003 Chrome12/11/20081875
css.selectors.subsequent-sibling πŸ“‹Safari10/26/2007 Chrome12/11/2008412
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.target πŸ“‹Safari4/15/2005 Chrome12/11/20081336
css.selectors.type πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.selectors.type.namespaces Safari4/15/2005 Chrome12/11/20081336
css.selectors.universal πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.selectors.universal.namespaces Safari4/15/2005 Chrome12/11/20081336
css.selectors.visited πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.color.hsl πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.color.named-color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/2008268
css.types.color.rgb πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.color.rgb_hexadecimal_notation πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.color.system-color πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.color.transparent Safari6/23/2003 Chrome12/11/20081998
css.types.counter πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.types.counters πŸ“‹Safari10/26/2007 Chrome12/11/2008412
css.types.dimension πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.global_keywords Safari6/23/2003 Chrome12/11/20081998
css.types.global_keywords.inherit πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.global_keywords.initial πŸ“‹Safari2/2/2004 Chrome12/11/20081774
css.types.image πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.integer πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.length πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.length.em Safari6/23/2003 Chrome12/11/20081998
css.types.length.ex Safari6/23/2003 Chrome12/11/20081998
css.types.length-percentage πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.line-style πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.number πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.overflow πŸ“‹Safari6/23/2003 Chrome12/11/20081998
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 Chrome12/11/20081998
css.types.position πŸ“‹Safari6/23/2003 Chrome12/11/20081998
css.types.position.keyword_value_syntax Safari6/23/2003 Chrome12/11/20081998
css.types.shape πŸ“‹Safari4/15/2005 Chrome12/11/20081336
css.types.shape.rect Safari4/15/2005 Chrome12/11/20081336
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 Chrome12/11/20081998
css.types.string.unicode_escaped_characters Safari6/23/2003 Chrome12/11/20081998
css.types.time πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function πŸ“‹Safari3/18/2008 Chrome12/11/2008268
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 Chrome12/11/2008268
Firefox: Before Firefox 16, the translation values of matrix() could be <length>s, in addition to the standard <number>.
css.types.transform-function.rotate πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function.scale πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function.scaleX πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function.scaleY πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function.skew πŸ“‹Safari3/18/2008 Chrome12/11/2008268
Firefox: Firefox 14 removed experimental support for skew(), but it was reintroduced in Firefox 15.
css.types.transform-function.skewX πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function.skewY πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function.translate πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function.translateX πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.transform-function.translateY πŸ“‹Safari3/18/2008 Chrome12/11/2008268
css.types.url πŸ“‹Safari6/23/2003 Chrome12/11/20081998