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 Chrome Android, 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.animation-trigger πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.animation-trigger.none πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.text-indent.each-line πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.text-indent.hanging πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger.auto πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger.none πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger.normal πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger-name πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger-name.none πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger-source πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger-source.auto πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.timeline-trigger-source.none πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.trigger-scope πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.trigger-scope.all πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026
css.properties.trigger-scope.none πŸ“‹Chrome3/10/2026 Chrome Android3/10/2026

2026/2

API First Browser Date Last Browser Date Days Notes
css.properties.column-height πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.column-height.auto πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.column-wrap πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.column-wrap.auto πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.column-wrap.nowrap πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.column-wrap.wrap πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.columns.column-height πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.text-justify πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
Edge: Standard values inter-character and none are supported. The deprecated distribute value is also supported.Internet Explorer: Standard values inter-character and none are supported. The deprecated distribute value is also supported.
css.properties.text-justify.auto πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.text-justify.inter-character πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.text-justify.inter-word πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.text-justify.none πŸ“‹Chrome2/10/2026 Chrome Android2/10/2026
css.properties.word-spacing.percentages Chrome2/10/2026 Chrome Android2/10/2026

2026/1

API First Browser Date Last Browser Date Days Notes
css.at-rules.container.scroll-state_queries.scrolled πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.background-position-x.side-relative_values Chrome1/13/2026 Chrome Android1/13/2026
css.properties.background-position-y.side-relative_values Chrome1/13/2026 Chrome Android1/13/2026
css.properties.caret-shape πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.caret-shape.auto πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.caret-shape.bar πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.caret-shape.block πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.caret-shape.underscore πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.position-anchor.none Chrome1/13/2026 Chrome Android1/13/2026
css.properties.position-area.block-end πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.position-try.flip-y πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.position-try.self-x-end πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.position-try-fallbacks.flip-y πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.properties.position-try-fallbacks.self-x-end πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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 πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
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.selectors.search-text πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026
css.types.color.color.colorSpace_parameter_accepts_display-p3-linear_value πŸ“‹Chrome1/13/2026 Chrome Android1/13/2026

2025/12

API First Browser Date Last Browser Date Days Notes
css.at-rules.container.anchor_position_queries πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.at-rules.container.anchor_position_queries.fallback πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.at-rules.container.anchor_position_queries.fallback.any_value πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.container-type.anchored πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.font-language-override πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.font-language-override.normal πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-area.span-self-x-end πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-area.span-self-x-start πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-area.span-self-y-end πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-area.span-self-y-start πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-try.span-self-x-end πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-try.span-self-x-start πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-try.span-self-y-end πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-try.span-self-y-start πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-try-fallbacks.span-self-x-end πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-try-fallbacks.span-self-x-start πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-try-fallbacks.span-self-y-end πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.properties.position-try-fallbacks.span-self-y-start πŸ“‹Chrome12/2/2025 Chrome Android12/2/2025
css.selectors.nesting.at-scope Chrome12/2/2025 Chrome Android12/2/2025

2025/10

API First Browser Date Last Browser Date Days Notes
css.at-rules.container.style_queries_for_custom_properties.range_syntax πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.properties.interest-delay πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.properties.interest-delay.normal πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.properties.interest-delay-end πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.properties.interest-delay-end.normal πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.properties.interest-delay-start πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.properties.interest-delay-start.normal πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.selectors.interest-source πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.selectors.interest-target πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.selectors.target-after πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.selectors.target-before πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025
css.types.if.style.range_syntax πŸ“‹Chrome10/28/2025 Chrome Android10/28/2025

2025/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.font-feature-settings πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
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.at-rules.font-face.font-variation-settings πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.caret-animation πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.caret-animation.auto πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.caret-animation.manual πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.scroll-target-group πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.scroll-target-group.auto πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.scroll-target-group.none πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.text-autospace πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.text-autospace.no-autospace πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.text-autospace.normal πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.view-transition-group πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.properties.view-transition-group.contain Chrome9/2/2025 Chrome Android9/2/2025
css.properties.view-transition-group.nearest Chrome9/2/2025 Chrome Android9/2/2025
css.properties.view-transition-group.normal Chrome9/2/2025 Chrome Android9/2/2025
css.selectors.view-transition-group-children πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.types.calc.typed_division_produces_unitless_number πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025
css.types.sign.typed_division_produces_unitless_number πŸ“‹Chrome9/2/2025 Chrome Android9/2/2025

2025/8

API First Browser Date Last Browser Date Days Notes
css.at-rules.function πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.at-rules.function.result πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-end-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-end-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-end-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-end-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-end-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-end-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-end-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-start-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-start-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-start-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-start-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-start-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-start-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-block-start-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-left-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-left-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-left-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-left-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-left-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-left-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-left-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-right-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-right-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-right-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-right-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-right-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-right-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-right-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-bottom-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-end-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-end-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-end-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-end-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-end-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-end-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-end-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-start-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-start-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-start-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-start-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-start-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-start-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-end-start-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-end-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-end-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-end-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-end-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-end-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-end-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-end-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-start-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-start-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-start-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-start-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-start-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-start-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-inline-start-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-left-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-left-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-left-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-left-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-left-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-left-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-left-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-right-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-right-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-right-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-right-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-right-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-right-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-right-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-end-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-end-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-end-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-end-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-end-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-end-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-end-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-start-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-start-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-start-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-start-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-start-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-start-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-start-start-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-left-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-left-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-left-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-left-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-left-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-left-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-left-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-right-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-right-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-right-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-right-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-right-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-right-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-right-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-shape πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-shape.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-shape.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-shape.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-shape.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-shape.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.properties.corner-top-shape.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.corner-shape-value πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.corner-shape-value.bevel πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.corner-shape-value.notch πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.corner-shape-value.round πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.corner-shape-value.scoop πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.corner-shape-value.square πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.corner-shape-value.squircle πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.corner-shape-value.superellipse πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.dashed-function πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.superellipse πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025
css.types.type πŸ“‹Chrome8/5/2025 Chrome Android8/5/2025

2025/6

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.horizontal-viewport-segments πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.at-rules.media.vertical-viewport-segments πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.block-size.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.flex.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.flex-basis.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.height.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.inline-size.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.max-block-size.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.max-height.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.max-inline-size.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.max-width.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.min-block-size.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.min-height.stretch Chrome6/24/2025 Chrome Android6/24/2025
css.properties.min-inline-size.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.properties.min-width.stretch Chrome6/24/2025 Chrome Android6/24/2025
css.properties.width.stretch πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.abs πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.env.viewport-segment-bottom πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.env.viewport-segment-height πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.env.viewport-segment-left πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.env.viewport-segment-right πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.env.viewport-segment-top πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.env.viewport-segment-width πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.progress πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.sibling-count πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.sibling-index πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025
css.types.sign πŸ“‹Chrome6/24/2025 Chrome Android6/24/2025

2025/5

API First Browser Date Last Browser Date Days Notes
css.properties.reading-flow πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.reading-flow.flex-flow πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.reading-flow.flex-visual πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.reading-flow.grid-columns πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.reading-flow.grid-order πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.reading-flow.grid-rows πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.reading-flow.normal πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.reading-flow.source-order πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.reading-order πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.properties.view-transition-name.match-element πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.types.if πŸ“‹Chrome5/27/2025 Chrome Android5/27/2025
css.types.if.style Chrome5/27/2025 Chrome Android5/27/2025

2025/4

API First Browser Date Last Browser Date Days Notes
css.properties.dynamic-range-limit πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
css.properties.dynamic-range-limit.constrained πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
css.properties.dynamic-range-limit.dynamic-range-limit-mix_values πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
css.properties.dynamic-range-limit.no-limit πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
css.properties.dynamic-range-limit.standard πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
css.properties.print-color-adjust πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
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 πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
css.properties.print-color-adjust.exact πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
css.types.dynamic-range-limit-mix πŸ“‹Chrome4/29/2025 Chrome Android4/29/2025
css.properties.appearance.base-select πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.interactivity πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.interactivity.auto πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.interactivity.inert πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-block πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-block.auto πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-block.clip πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-block.hidden πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-block.overlay Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-block.scroll πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-block.visible πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-inline πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-inline.auto πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-inline.clip πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-inline.hidden πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-inline.overlay πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-inline.scroll πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.overflow-inline.visible πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.scroll-marker-group πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.scroll-marker-group.after πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.scroll-marker-group.before πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.properties.scroll-marker-group.none πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.after.nested_marker πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.before.nested_marker πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.column πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.column.nested_scroll-marker Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.picker πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.block-end πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.block-start πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.down πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.inline-end πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.inline-start πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.left πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.right πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.star πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-button.up πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-marker πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.scroll-marker-group πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.selectors.target-current πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.types.basic-shape.shape πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.types.gradient.conic-gradient.single_color_stop πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.types.gradient.linear-gradient.single_color_stop πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.types.gradient.radial-gradient.single_color_stop πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.types.gradient.repeating-conic-gradient.single_color_stop πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.types.gradient.repeating-linear-gradient.single_color_stop πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025
css.types.gradient.repeating-radial-gradient.single_color_stop πŸ“‹Chrome4/1/2025 Chrome Android4/1/2025

2025/2

API First Browser Date Last Browser Date Days Notes
css.at-rules.container.scroll-state_queries πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.at-rules.container.scroll-state_queries.scrollable πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.at-rules.container.scroll-state_queries.snapped πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.at-rules.container.scroll-state_queries.stuck πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.container-type.scroll-state πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.scroll-initial-target πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.scroll-initial-target.nearest πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.scroll-initial-target.none πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box.auto πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box.none πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box.normal πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box.text πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box.trim-both πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box.trim-end πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box.trim-start πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box-edge πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box-edge.auto πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box-edge.text πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box-trim πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box-trim.none πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box-trim.trim-both πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box-trim.trim-end πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.properties.text-box-trim.trim-start πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.selectors.checkmark πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.selectors.open πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
Chrome: The selector is recognized, but has no effect.Chrome Android: The selector is recognized, but has no effect.Edge: The selector is recognized, but has no effect.Opera: The selector is recognized, but has no effect.Opera Android: The selector is recognized, but has no effect.Samsung Internet: The selector is recognized, but has no effect.WebView Android: The selector is recognized, but has no effect.
css.selectors.picker-icon πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.declaration-value πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.angle πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.color πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.custom-ident πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.ident πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.image πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.integer πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.length πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.length-percentage πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.number πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.percentage πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.resolution πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.string πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.time πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.transform-function πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.attr.type_function.url πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.text-edge πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.text-edge.alphabetic πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.text-edge.cap πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.text-edge.ex πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025
css.types.text-edge.text πŸ“‹Chrome2/4/2025 Chrome Android2/4/2025

2025/1

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.device-posture πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.bottom.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.inset.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.inset-block.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.inset-block-end.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.inset-block-start.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.inset-inline.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.inset-inline-end.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.inset-inline-start.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.left.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-block.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-block-end.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-block-start.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-bottom.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-inline.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-inline-end.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-inline-start.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-left.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-right.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.margin-top.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.right.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.top.anchor-size πŸ“‹Chrome1/14/2025 Chrome Android1/14/2025
css.properties.writing-mode.sideways-lr Chrome1/14/2025 Chrome Android1/14/2025
css.properties.writing-mode.sideways-rl Chrome1/14/2025 Chrome Android1/14/2025
css.types.anchor-size.inset_margin Chrome1/14/2025 Chrome Android1/14/2025

2024/11

API First Browser Date Last Browser Date Days Notes
css.at-rules.page.bottom-center πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.bottom-left πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.bottom-left-corner πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.bottom-right πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.bottom-right-corner πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.left-bottom πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.left-middle πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.left-top πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.right-bottom πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.right-middle πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.right-top πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.top-center πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.top-left πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.top-left-corner πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.top-right πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.at-rules.page.top-right-corner πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.properties.anchor-scope πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.properties.anchor-scope.all πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.properties.anchor-scope.none πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.properties.font-variant-emoji πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.properties.font-variant-emoji.emoji πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.properties.font-variant-emoji.normal πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.properties.font-variant-emoji.text πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.properties.font-variant-emoji.unicode πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
css.selectors.details-content πŸ“‹Chrome11/12/2024 Chrome Android11/12/2024
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.

2024/10

API First Browser Date Last Browser Date Days Notes
css.properties.box-decoration-break πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
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 πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
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 πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
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.justify-items.block_context πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.justify-self.block_context πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap.auto πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap.stable πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap-mode πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap-mode.nowrap Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap-mode.wrap Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap-style πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap-style.auto πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap-style.balance πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap-style.pretty πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024
css.properties.text-wrap-style.stable πŸ“‹Chrome10/15/2024 Chrome Android10/15/2024

2024/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.prefers-color-scheme.respects-inherited-scheme Chrome9/17/2024 Chrome Android9/17/2024
Chrome: Only supports SVG images, not iframes.Chrome Android: Only supports SVG images, not iframes.Edge: Only supports SVG images, not iframes.Opera: Only supports SVG images, not iframes.Opera Android: Only supports SVG images, not iframes.Samsung Internet: Only supports SVG images, not iframes.WebView Android: Only supports SVG images, not iframes.
css.properties.container-type.weak_containment πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.interpolate-size πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.interpolate-size.allow-keywords πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.interpolate-size.numeric-only πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.center πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.none πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-bottom πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-left πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-right πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-self-block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-self-block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-self-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-self-inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-self-inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-self-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-top πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-x-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-x-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-y-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.span-y-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-area.start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.bottom πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.center πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.left πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.right πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.self-block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.self-block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.self-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.self-inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.self-inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.self-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-all πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-bottom πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-left πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-right πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-self-block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-self-block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-self-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-self-inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-self-inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-self-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-top πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-x-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-x-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-y-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.span-y-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.top πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.x-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.x-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.y-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try.y-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.bottom πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.center πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.left πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.right πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.self-block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.self-block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.self-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.self-inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.self-inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.self-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-all πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-bottom πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-left πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-right πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-self-block-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-self-block-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-self-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-self-inline-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-self-inline-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-self-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-top πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-x-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-x-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-y-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.span-y-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.top πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.x-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.x-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.y-end πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.properties.position-try-fallbacks.y-start πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024
css.types.calc-size πŸ“‹Chrome9/17/2024 Chrome Android9/17/2024

2024/8

API First Browser Date Last Browser Date Days Notes
css.properties.position-try-fallbacks πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
css.properties.position-try-fallbacks.flip-block πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
css.properties.position-try-fallbacks.flip-inline πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
css.properties.position-try-fallbacks.flip-start πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
css.properties.position-try-fallbacks.none πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
css.properties.position-try-fallbacks.position-area πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
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.ruby-align πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
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 Chrome Android8/20/2024
css.properties.ruby-align.space-around πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
css.properties.ruby-align.space-between πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024
css.properties.ruby-align.start πŸ“‹Chrome8/20/2024 Chrome Android8/20/2024

2024/7

API First Browser Date Last Browser Date Days Notes
css.properties.font-size-adjust πŸ“‹Chrome7/23/2024 Chrome Android7/23/2024
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 πŸ“‹Chrome7/23/2024 Chrome Android7/23/2024
css.properties.font-size-adjust.none πŸ“‹Chrome7/23/2024 Chrome Android7/23/2024
css.properties.font-size-adjust.two-values Chrome7/23/2024 Chrome Android7/23/2024

2024/6

API First Browser Date Last Browser Date Days Notes
css.at-rules.view-transition πŸ“‹Chrome6/11/2024 Chrome Android6/11/2024

2024/5

API First Browser Date Last Browser Date Days Notes
css.at-rules.position-try πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.align-items.anchor-center πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.align-self.anchor-center πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.anchor-name πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.anchor-name.none πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.block-size.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.bottom.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.height.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.inline-size.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.inset.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.inset-block.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.inset-block-end.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.inset-block-start.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.inset-inline.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.inset-inline-end.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.inset-inline-start.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.justify-items.anchor-center πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.justify-self.anchor-center πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.left.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.max-block-size.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.max-height.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.max-inline-size.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.max-width.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.min-block-size.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.min-height.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.min-inline-size.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.min-width.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.place-items.anchor-center πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.place-self.anchor-center πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-anchor.auto πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
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-try πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try.flip-block πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try.flip-inline πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try.flip-start πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try.none πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try-order πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try-order.most-block-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try-order.most-height πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try-order.most-inline-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try-order.most-width πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-try-order.normal πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-visibility πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-visibility.always πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-visibility.anchors-visible πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.position-visibility.no-overflow πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.right.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.top.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.view-transition-class πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.view-transition-class.none πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.properties.width.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.selectors.active-view-transition πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.selectors.active-view-transition-type πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.selectors.state πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
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.anchor πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.types.anchor-size πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.types.color.hsl.relative_syntax πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
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.relative_syntax πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
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.mod πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.types.mod.mixed_type_parameters πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.types.rem πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.types.rem.mixed_type_parameters πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.types.round πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024
css.types.round.mixed_type_parameters πŸ“‹Chrome5/14/2024 Chrome Android5/14/2024

2024/4

API First Browser Date Last Browser Date Days Notes
css.properties.direction.vertical_slider_direction Chrome4/16/2024 Chrome Android4/16/2024
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 Chrome4/16/2024 Chrome Android4/16/2024
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 πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.align-content.multicol_context πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.field-sizing πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.field-sizing.content πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.field-sizing.fixed πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.paint-order πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
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.properties.text-spacing-trim πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.text-spacing-trim.normal πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.text-spacing-trim.space-all πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.text-spacing-trim.space-first πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.properties.text-spacing-trim.trim-start πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024
css.types.color.light-dark πŸ“‹Chrome3/19/2024 Chrome Android3/19/2024

2024/2

API First Browser Date Last Browser Date Days Notes
css.at-rules.import.supports πŸ“‹Chrome2/20/2024 Chrome Android2/20/2024
css.properties.align-self.position_absolute_context πŸ“‹Chrome2/20/2024 Chrome Android2/20/2024
css.properties.justify-self.position_absolute_context πŸ“‹Chrome2/20/2024 Chrome Android2/20/2024
css.properties.place-self.position_absolute_context πŸ“‹Chrome2/20/2024 Chrome Android2/20/2024
css.selectors.backdrop.inherit_from_originating_element Chrome2/20/2024 Chrome Android2/20/2024
css.types.color.oklab.relative_syntax πŸ“‹Chrome2/20/2024 Chrome Android2/20/2024
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.
css.types.color.oklch.relative_syntax πŸ“‹Chrome2/20/2024 Chrome Android2/20/2024
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 Chrome Android2/20/2024
css.types.color.rgb.relative_syntax πŸ“‹Chrome2/20/2024 Chrome Android2/20/2024
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/1

API First Browser Date Last Browser Date Days Notes
css.properties.display.ruby Chrome1/23/2024 Chrome Android1/23/2024
css.properties.display.ruby-text Chrome1/23/2024 Chrome Android1/23/2024
css.properties.font-palette.animation_computed Chrome1/23/2024 Chrome Android1/23/2024
css.properties.font-palette.palette-mix_function πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.scrollbar-color πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.scrollbar-color.auto πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.scrollbar-width πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.scrollbar-width.auto πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.scrollbar-width.none πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.scrollbar-width.thin πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.text-decoration.grammar-error πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.text-decoration.spelling-error πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.text-decoration-line.grammar-error πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.properties.text-decoration-line.spelling-error πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.selectors.grammar-error πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.selectors.spelling-error πŸ“‹Chrome1/23/2024 Chrome Android1/23/2024
css.types.color.hsl.mixed_type_parameters Chrome1/23/2024 Chrome Android1/23/2024
css.types.color.hwb.mixed_type_parameters Chrome1/23/2024 Chrome Android1/23/2024

2023/12

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.scripting πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.background-clip.text πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
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 πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
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 πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-clip.border-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-clip.content-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-clip.fill-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-clip.no-clip Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-clip.padding-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-clip.stroke-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-clip.view-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-composite πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
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 πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-composite.exclude πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-composite.intersect πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-composite.subtract πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-image πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
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 πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-mode.alpha πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-mode.luminance πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-mode.match-source πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-origin πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-origin.border-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-origin.content-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-origin.fill-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-origin.padding-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-origin.stroke-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-origin.view-box Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-position πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-repeat πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.properties.mask-size πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.selectors.dir πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.selectors.nesting πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
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.exp πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.types.hypot πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.types.log πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.types.pow πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023
css.types.sqrt πŸ“‹Chrome12/5/2023 Chrome Android12/5/2023

2023/10

API First Browser Date Last Browser Date Days Notes
css.properties.clip-path.border-box πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
css.properties.clip-path.content-box πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
css.properties.clip-path.fill-box πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
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 πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
css.properties.clip-path.padding-box πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
css.properties.clip-path.stroke-box πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
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 πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
css.properties.word-break.auto-phrase πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
Chrome: This value is only applicable if lang="ja" is specified. This value has no effect on other locales.Chrome Android: This value is only applicable if lang="ja" is specified. This value has no effect on other locales.Edge: This value is only applicable if lang="ja" is specified. This value has no effect on other locales.Opera: This value is only applicable if lang="ja" is specified. This value has no effect on other locales.Opera Android: This value is only applicable if lang="ja" is specified. This value has no effect on other locales.Samsung Internet: This value is only applicable if lang="ja" is specified. This value has no effect on other locales.WebView Android: This value is only applicable if lang="ja" is specified. This value has no effect on other locales.
css.selectors.user-invalid πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
css.selectors.user-valid πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
css.types.basic-shape.rect πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
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 Chrome Android10/31/2023
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.calc.color_component Chrome10/31/2023 Chrome Android10/31/2023
css.types.color.color.relative_syntax πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
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.lab.relative_syntax πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
css.types.color.lch.relative_syntax πŸ“‹Chrome10/31/2023 Chrome Android10/31/2023
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.at-rules.media.prefers-reduced-transparency πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.at-rules.scope πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.properties.clear.inline-end πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.properties.clear.inline-start πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.properties.float.inline-end πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.properties.float.inline-start πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.properties.resize.block Chrome10/10/2023 Chrome Android10/10/2023
css.properties.resize.inline Chrome10/10/2023 Chrome Android10/10/2023
css.properties.transform-box.border-box πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.properties.transform-box.content-box πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.properties.transform-box.stroke-box πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023
css.types.length.cap Chrome10/10/2023 Chrome Android10/10/2023
css.types.length.rcap πŸ“‹Chrome10/10/2023 Chrome Android10/10/2023

2023/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.starting-style πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.contain-intrinsic-size.auto_none Chrome9/12/2023 Chrome Android9/12/2023
css.properties.content-visibility.is_transitionable πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.display.is_transitionable πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.font-variant-position πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.font-variant-position.normal πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.font-variant-position.sub πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
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 πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
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 πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.grid-template-rows.subgrid πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.overlay πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.overlay.auto πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.overlay.none πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.text-wrap.pretty πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.transition.transition-behavior Chrome9/12/2023 Chrome Android9/12/2023
css.properties.transition-behavior πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.transition-behavior.allow-discrete πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.transition-behavior.normal πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.transition-behavior.transitionable_content-visibility πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023
css.properties.transition-behavior.transitionable_display πŸ“‹Chrome9/12/2023 Chrome Android9/12/2023

2023/8

API First Browser Date Last Browser Date Days Notes
css.properties.content-visibility.keyframe_animatable πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.display.keyframe_animatable πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.auto πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.border-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.bottom πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.center πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.content-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.fill-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.left πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.normal πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.padding-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.right πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.stroke-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.top πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset.view-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-anchor πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-anchor.auto πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-anchor.bottom πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-anchor.center πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-anchor.left πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-anchor.right πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-anchor.top πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.basic_shape πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.border-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.content-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.fill-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.padding-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.ray πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.stroke-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.url πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-path.view-box πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-position πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-position.auto πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-position.bottom πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-position.center πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-position.left πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-position.normal πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-position.right πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.offset-position.top πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.timeline-scope πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.properties.timeline-scope.none πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.types.color.lab.mixed_type_parameters Chrome8/15/2023 Chrome Android8/15/2023
css.types.color.lch.mixed_type_parameters Chrome8/15/2023 Chrome Android8/15/2023
css.types.color.oklab.mixed_type_parameters Chrome8/15/2023 Chrome Android8/15/2023
css.types.color.oklch.mixed_type_parameters Chrome8/15/2023 Chrome Android8/15/2023
css.types.ray πŸ“‹Chrome8/15/2023 Chrome Android8/15/2023
css.types.ray.position Chrome8/15/2023 Chrome Android8/15/2023
css.types.ray.size Chrome8/15/2023 Chrome Android8/15/2023

2023/7

API First Browser Date Last Browser Date Days Notes
css.at-rules.keyframes.named_range_keyframes πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.align-content.flex_context.safe_unsafe Chrome7/18/2023 Chrome Android7/21/20233
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 Chrome Android7/21/20233
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 Chrome Android7/21/20233
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.animation.animation-timeline_included Chrome7/18/2023 Chrome Android7/21/20233
Chrome: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Chrome Android: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Edge: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Opera: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Opera Android: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Samsung Internet: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.WebView Android: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.
css.properties.animation-duration.auto πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
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.animation-range πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-range.normal πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-range-end πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-range-end.normal πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-range-start πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-range-start.normal πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-timeline πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-timeline.auto πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-timeline.none πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.animation-timeline.scroll πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
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 Chrome Android7/21/20233
css.properties.display.multi-keyword_values Chrome7/18/2023 Chrome Android7/21/20233
css.properties.justify-content.flex_context.safe_unsafe Chrome7/18/2023 Chrome Android7/21/20233
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.scroll-timeline πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
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 Chrome Android7/21/20233
css.properties.scroll-timeline-axis πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
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 Chrome Android7/21/20233
css.properties.scroll-timeline-axis.inline πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.scroll-timeline-axis.x πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.scroll-timeline-axis.y πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.scroll-timeline-name πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
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 Chrome Android7/21/20233
css.properties.view-timeline πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline.none πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.view-timeline-axis πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
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 Chrome Android7/21/20233
css.properties.view-timeline-axis.inline πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.view-timeline-axis.x πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.view-timeline-axis.y πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.view-timeline-inset πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.view-timeline-inset.auto πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.view-timeline-name πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.properties.view-timeline-name.none πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
css.types.color.system-color.accentcolor_accentcolortext πŸ“‹Chrome7/18/2023 Chrome Android7/21/20233
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.properties.text-wrap πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.text-wrap.balance πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.text-wrap.nowrap πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.text-wrap.wrap πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space.collapse πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space.preserve πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space.preserve-breaks πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space.shorthand_values Chrome5/30/2023 Chrome Android5/30/2023
Chrome: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.Chrome Android: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.Edge: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.Firefox: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.Firefox for Android: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.Opera: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.Opera Android: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.Samsung Internet: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.WebView Android: Only accepts values for white-space-collapse and text-wrap-mode, not white-space-trim.
css.properties.white-space.wrap πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space-collapse πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space-collapse.break-spaces πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space-collapse.collapse πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space-collapse.preserve πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.properties.white-space-collapse.preserve-breaks πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.selectors.backdrop.popover Chrome5/30/2023 Chrome Android5/30/2023
css.selectors.popover-open πŸ“‹Chrome5/30/2023 Chrome Android5/30/2023
css.types.overflow.overlay Chrome5/30/2023 Chrome Android5/30/2023
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.
css.at-rules.media.overflow-block πŸ“‹Chrome5/2/2023 Chrome Android5/2/2023
css.at-rules.media.overflow-inline πŸ“‹Chrome5/2/2023 Chrome Android5/2/2023
css.at-rules.media.update πŸ“‹Chrome5/2/2023 Chrome Android5/2/2023
css.properties.background-image.image-set πŸ“‹Chrome5/2/2023 Chrome Android5/2/2023
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.content.image-set πŸ“‹Chrome5/2/2023 Chrome Android5/2/2023
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.easing-function.linear-function πŸ“‹Chrome5/2/2023 Chrome Android5/2/2023
css.types.image.image-set πŸ“‹Chrome5/2/2023 Chrome Android5/2/2023
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.

2023/4

API First Browser Date Last Browser Date Days Notes
css.properties.animation-composition πŸ“‹Chrome4/4/2023 Chrome Android4/4/2023
css.properties.animation-composition.accumulate πŸ“‹Chrome4/4/2023 Chrome Android4/4/2023
css.properties.animation-composition.add πŸ“‹Chrome4/4/2023 Chrome Android4/4/2023
css.properties.animation-composition.replace πŸ“‹Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_afrikaans Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_albanian Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_amharic Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_czech Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_dutch Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_ethiopic_script_mul Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_galician Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_georgian Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_italian Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_latvian Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_lithuanian Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_modern_greek Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_russian Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_slovak Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_swedish Chrome4/4/2023 Chrome Android4/4/2023
css.properties.hyphens.language_ukrainian Chrome4/4/2023 Chrome Android4/4/2023

2023/3

API First Browser Date Last Browser Date Days Notes
css.at-rules.container.style_queries_for_custom_properties πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
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.at-rules.font-feature-values πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.at-rules.font-feature-values.annotation Chrome3/7/2023 Chrome Android3/7/2023
css.at-rules.font-feature-values.character-variant Chrome3/7/2023 Chrome Android3/7/2023
css.at-rules.font-feature-values.historical-forms Chrome3/7/2023 Chrome Android3/7/2023
css.at-rules.font-feature-values.ornaments Chrome3/7/2023 Chrome Android3/7/2023
css.at-rules.font-feature-values.styleset Chrome3/7/2023 Chrome Android3/7/2023
css.at-rules.font-feature-values.stylistic Chrome3/7/2023 Chrome Android3/7/2023
css.at-rules.font-feature-values.swash Chrome3/7/2023 Chrome Android3/7/2023
css.properties.baseline-source πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.baseline-source.auto πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.baseline-source.first πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.baseline-source.last πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant.historical-forms πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates.annotation πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates.character_variant πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates.historical-forms πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates.normal πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates.ornaments πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates.styleset πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates.stylistic πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.font-variant-alternates.swash πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.view-transition-name πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.properties.view-transition-name.none πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.selectors.nth-child.of_syntax Chrome3/7/2023 Chrome Android3/7/2023
css.selectors.nth-last-child.of_syntax Chrome3/7/2023 Chrome Android3/7/2023
css.types.acos πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.asin πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.atan πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.atan2 πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.color.color πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
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 Chrome3/7/2023 Chrome Android3/7/2023
css.types.color.color-mix πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.color.lab πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.color.lch πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.color.oklab πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.color.oklch πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.cos πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.conic-gradient.hue_interpolation_method Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.conic-gradient.interpolation_color_space Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.linear-gradient.hue_interpolation_method Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.linear-gradient.interpolation_color_space Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.radial-gradient.hue_interpolation_method Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.radial-gradient.interpolation_color_space Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.repeating-conic-gradient.hue_interpolation_method Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.repeating-conic-gradient.interpolation_color_space Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.repeating-linear-gradient.hue_interpolation_method Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.repeating-linear-gradient.interpolation_color_space Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.repeating-radial-gradient.hue_interpolation_method Chrome3/7/2023 Chrome Android3/7/2023
css.types.gradient.repeating-radial-gradient.interpolation_color_space Chrome3/7/2023 Chrome Android3/7/2023
css.types.length.rch πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.length.rex πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.length.ric πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.length.rlh πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.sin πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023
css.types.tan πŸ“‹Chrome3/7/2023 Chrome Android3/7/2023

2023/2

API First Browser Date Last Browser Date Days Notes
css.properties.font-variant.sub πŸ“‹Chrome2/7/2023 Chrome Android2/7/2023
css.properties.font-variant.super πŸ“‹Chrome2/7/2023 Chrome Android2/7/2023
css.properties.initial-letter πŸ“‹Chrome2/7/2023 Chrome Android2/7/2023
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 πŸ“‹Chrome2/7/2023 Chrome Android2/7/2023
css.selectors.autofill πŸ“‹Chrome2/7/2023 Chrome Android2/7/2023
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 πŸ“‹Chrome2/7/2023 Chrome Android2/7/2023
css.types.calc-keyword.e Chrome2/7/2023 Chrome Android2/7/2023

2023/1

API First Browser Date Last Browser Date Days Notes
css.properties.container.normal πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.display.math Chrome1/10/2023 Chrome Android1/10/2023
css.properties.font-family.math Chrome1/10/2023 Chrome Android1/10/2023
css.properties.font-size.math Chrome1/10/2023 Chrome Android1/10/2023
css.properties.hyphenate-limit-chars πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.hyphenate-limit-chars.auto πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.math-depth πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.math-depth.auto-add πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.math-shift πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.math-shift.compact πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.math-shift.normal πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.math-style πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.math-style.compact πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.math-style.normal πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.properties.text-transform.math-auto πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.selectors.view-transition πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.selectors.view-transition-group πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.selectors.view-transition-image-pair πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.selectors.view-transition-new πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.selectors.view-transition-old πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023
css.types.calc-keyword.pi Chrome1/10/2023 Chrome Android1/10/2023
css.types.length.lh πŸ“‹Chrome1/10/2023 Chrome Android1/10/2023

2022/11

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.src.drop_invalid_item Chrome11/29/2022 Chrome Android11/29/2022
Chrome: Chrome drops invalid item for tech() but not other invalid valuesChrome Android: Chrome Android drops invalid item for tech() but not other invalid valuesEdge: Edge drops invalid item for tech() but not other invalid valuesOpera: Opera drops invalid item for tech() but not other invalid valuesOpera Android: Opera Android drops invalid item for tech() but not other invalid valuesSamsung Internet: Samsung Internet drops invalid item for tech() but not other invalid valuesWebView Android: WebView Android drops invalid item for tech() but not other invalid values
css.at-rules.font-face.src.format_keyword Chrome11/29/2022 Chrome Android11/29/2022
css.at-rules.font-face.src.tech_keyword Chrome11/29/2022 Chrome Android11/29/2022
css.at-rules.supports.font-format Chrome11/29/2022 Chrome Android11/29/2022
css.at-rules.supports.font-tech Chrome11/29/2022 Chrome Android11/29/2022
css.properties.align-items.flex_context.last_baseline Chrome11/29/2022 Chrome Android11/29/2022
css.properties.align-self.flex_context.last_baseline Chrome11/29/2022 Chrome Android11/29/2022
css.properties.overflow.replaced_elements πŸ“‹Chrome11/29/2022 Chrome Android11/29/2022
css.properties.overflow-x.replaced_elements πŸ“‹Chrome11/29/2022 Chrome Android11/29/2022
css.properties.overflow-y.replaced_elements πŸ“‹Chrome11/29/2022 Chrome Android11/29/2022
css.types.length.vb Chrome11/29/2022 Chrome Android11/29/2022
css.types.length.vi Chrome11/29/2022 Chrome Android11/29/2022
css.types.length.viewport_percentage_units_dynamic Chrome11/29/2022 Chrome Android11/29/2022
css.types.length.viewport_percentage_units_large Chrome11/29/2022 Chrome Android11/29/2022
css.types.length.viewport_percentage_units_small Chrome11/29/2022 Chrome Android11/29/2022

2022/10

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

2022/9

API First Browser Date Last Browser Date Days Notes
css.properties.forced-color-adjust.preserve-parent-color πŸ“‹Chrome9/27/2022 Chrome Android9/27/2022
css.properties.hyphenate-character πŸ“‹Chrome9/27/2022 Chrome Android9/27/2022
css.types.length.ic Chrome9/27/2022 Chrome Android9/27/2022
css.at-rules.container πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.contain.inline-size πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container.inline-size πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container.none πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container.scroll-state πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container.size πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container-name πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container-name.none πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container-type πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container-type.inline-size πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container-type.normal πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.properties.container-type.size πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.selectors.has πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.selectors.highlight πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
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.modal πŸ“‹Chrome9/2/2022 Chrome Android9/2/2022
css.selectors.selection.text-decoration Chrome9/2/2022 Chrome Android9/2/2022
css.types.length.container_query_length_units Chrome9/2/2022 Chrome Android9/2/2022

2022/8

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.or_syntax Chrome8/2/2022 Chrome Android8/2/2022
css.at-rules.media.range_syntax Chrome8/2/2022 Chrome Android8/2/2022
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 Chrome Android8/2/2022
css.properties.object-view-box πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.object-view-box.none πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.overflow-clip-margin.border-box πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.overflow-clip-margin.content-box πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.overflow-clip-margin.padding-box πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.rotate πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.rotate.none πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.rotate.x_y_z_angle Chrome8/2/2022 Chrome Android8/2/2022
css.properties.scale πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.scale.none πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.translate πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022
css.properties.translate.none πŸ“‹Chrome8/2/2022 Chrome Android8/2/2022

2022/5

API First Browser Date Last Browser Date Days Notes
css.properties.break-after.multicol_context.avoid Chrome5/24/2022 Chrome Android5/24/2022
css.properties.break-after.multicol_context.avoid-column Chrome5/24/2022 Chrome Android5/24/2022
css.properties.break-before.multicol_context.avoid Chrome5/24/2022 Chrome Android5/24/2022
css.properties.break-before.multicol_context.avoid-column Chrome5/24/2022 Chrome Android5/24/2022
css.types.color.system-color.mark πŸ“‹Chrome5/24/2022 Chrome Android5/24/2022
css.types.color.system-color.marktext πŸ“‹Chrome5/24/2022 Chrome Android5/24/2022

2022/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-palette-values πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.at-rules.font-palette-values.base-palette πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.at-rules.font-palette-values.font-family πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.at-rules.font-palette-values.override-colors πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.properties.font-palette πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.properties.font-palette.dark πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.properties.font-palette.light πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.properties.font-palette.normal πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.types.color.hwb πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022
css.types.color.system-color.buttonborder πŸ“‹Chrome4/26/2022 Chrome Android4/26/2022

2022/3

API First Browser Date Last Browser Date Days Notes
css.properties.mix-blend-mode.plus-lighter πŸ“‹Chrome3/29/2022 Chrome Android3/29/2022
css.at-rules.import.layer πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.at-rules.layer πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-color πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-position πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-position.over Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-position.under Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style.circle πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style.dot πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style.double-circle πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style.filled πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style.none πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style.open πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style.sesame πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.properties.text-emphasis-style.triangle πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.types.calc-keyword πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022
css.types.calc-keyword.NaN Chrome3/1/2022 Chrome Android3/1/2022
css.types.calc-keyword.infinity Chrome3/1/2022 Chrome Android3/1/2022
css.types.global_keywords.revert-layer πŸ“‹Chrome3/1/2022 Chrome Android3/1/2022

2022/2

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.OpenType_COLRv1 Chrome2/1/2022 Chrome Android2/1/2022
css.at-rules.media.dynamic-range πŸ“‹Chrome2/1/2022 Chrome Android2/1/2022
css.at-rules.media.video-dynamic-range πŸ“‹Chrome2/1/2022 Chrome Android2/1/2022
css.properties.color-scheme.only Chrome2/1/2022 Chrome Android2/1/2022
css.properties.contain-intrinsic-block-size.none πŸ“‹Chrome2/1/2022 Chrome Android2/1/2022
css.properties.contain-intrinsic-height.none πŸ“‹Chrome2/1/2022 Chrome Android2/1/2022
css.properties.contain-intrinsic-inline-size.none πŸ“‹Chrome2/1/2022 Chrome Android2/1/2022
css.properties.contain-intrinsic-size.none πŸ“‹Chrome2/1/2022 Chrome Android2/1/2022
css.properties.contain-intrinsic-width.none πŸ“‹Chrome2/1/2022 Chrome Android2/1/2022

2022/1

API First Browser Date Last Browser Date Days Notes
css.properties.font-synthesis πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis.none πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis.small-caps Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis.style Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis.weight Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-small-caps πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-small-caps.auto πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-small-caps.none πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-style πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-style.auto πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-style.none πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-weight πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-weight.auto πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.properties.font-synthesis-weight.none πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022
css.types.transform-function.perspective.none πŸ“‹Chrome1/4/2022 Chrome Android1/4/2022

2021/11

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

2021/10

API First Browser Date Last Browser Date Days Notes
css.properties.contain-intrinsic-block-size πŸ“‹Chrome10/19/2021 Chrome Android10/19/2021
css.properties.contain-intrinsic-height πŸ“‹Chrome10/19/2021 Chrome Android10/19/2021
css.properties.contain-intrinsic-inline-size πŸ“‹Chrome10/19/2021 Chrome Android10/19/2021
css.properties.contain-intrinsic-width πŸ“‹Chrome10/19/2021 Chrome Android10/19/2021

2021/9

API First Browser Date Last Browser Date Days Notes
css.properties.flex.content πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.properties.flex.fit-content πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.properties.flex.max-content πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.properties.flex.min-content πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.properties.flex-basis.content Chrome9/21/2021 Chrome Android9/21/2021
css.properties.flex-basis.fit-content Chrome9/21/2021 Chrome Android9/21/2021
css.properties.flex-basis.max-content Chrome9/21/2021 Chrome Android9/21/2021
css.properties.flex-basis.min-content Chrome9/21/2021 Chrome Android9/21/2021
css.properties.outline πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
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.properties.scrollbar-gutter πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.properties.scrollbar-gutter.auto πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.properties.scrollbar-gutter.stable πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.types.env.keyboard-inset-bottom πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.types.env.keyboard-inset-height πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.types.env.keyboard-inset-left πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.types.env.keyboard-inset-right πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.types.env.keyboard-inset-top πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021
css.types.env.keyboard-inset-width πŸ“‹Chrome9/21/2021 Chrome Android9/21/2021

2021/8

API First Browser Date Last Browser Date Days Notes
css.properties.accent-color πŸ“‹Chrome8/31/2021 Chrome Android8/31/2021
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 Chrome Android8/31/2021
css.properties.align-content.flex_context.start_end Chrome8/31/2021 Chrome Android8/31/2021
Opera: Before version 79, this value is recognized, but has no effect.Opera Android: This value is recognized, but has no effect.
css.properties.align-items.flex_context.start_end Chrome8/31/2021 Chrome Android8/31/2021
css.properties.align-self.flex_context.start_end Chrome8/31/2021 Chrome Android8/31/2021
Opera: Before version 79, this value is recognized, but has no effect.
css.properties.justify-content.flex_context.left_right Chrome8/31/2021 Chrome Android8/31/2021
Internet Explorer: This value is recognized, but has no effect.Opera Android: This value is recognized, but has no effect.
css.properties.justify-content.flex_context.start_end Chrome8/31/2021 Chrome Android8/31/2021
css.types.env.titlebar-area-height πŸ“‹Chrome8/31/2021 Chrome Android8/31/2021
Chrome: Before version 93, Linux is unsupported.Chrome Android: Before version 93, Linux is unsupported.Edge: Before version 93, Linux is unsupported.
css.types.env.titlebar-area-width πŸ“‹Chrome8/31/2021 Chrome Android8/31/2021
Chrome: Before version 93, Linux is unsupported.Chrome Android: Before version 93, Linux is unsupported.Edge: Before version 93, Linux is unsupported.
css.types.env.titlebar-area-x πŸ“‹Chrome8/31/2021 Chrome Android8/31/2021
Chrome: Before version 93, Linux is unsupported.Chrome Android: Before version 93, Linux is unsupported.Edge: Before version 93, Linux is unsupported.
css.types.env.titlebar-area-y πŸ“‹Chrome8/31/2021 Chrome Android8/31/2021
Chrome: Before version 93, Linux is unsupported.Chrome Android: Before version 93, Linux is unsupported.Edge: Before version 93, Linux is unsupported.

2021/7

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.size-adjust πŸ“‹Chrome7/20/2021 Chrome Android7/20/2021

2021/5

API First Browser Date Last Browser Date Days Notes
css.at-rules.counter-style πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.additive-symbols πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.fallback πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.negative πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.pad πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.prefix πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.range πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.speak-as πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.suffix πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.at-rules.counter-style.symbols πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
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 Chrome Android5/25/2021
css.properties.list-style-type.afar Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.amharic Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.amharic-abegede Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.asterisks Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.binary Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.cjk-decimal πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-abegede Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-abegede-am-et Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-abegede-gez Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-abegede-ti-er Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-abegede-ti-et Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-halehame-aa-er Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-halehame-aa-et Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-halehame-am-et Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-halehame-gez Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-halehame-om-et Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-halehame-sid-et Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-halehame-so-et Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-halehame-tig Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.ethiopic-numeric πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
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.footnotes Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.japanese-formal πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.japanese-informal πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.lower-hexadecimal Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.lower-norwegian Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.octal Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.oromo Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.sidama Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.somali Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.tamil πŸ“‹Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.tigre Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.tigrinya-er Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.tigrinya-er-abegede Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.tigrinya-et Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.tigrinya-et-abegede Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.upper-greek Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.upper-hexadecimal Chrome5/25/2021 Chrome Android5/25/2021
css.properties.list-style-type.upper-norwegian Chrome5/25/2021 Chrome Android5/25/2021

2021/4

API First Browser Date Last Browser Date Days Notes
css.properties.overflow.clip πŸ“‹Chrome4/13/2021 Chrome Android4/13/2021
css.properties.overflow-clip-margin πŸ“‹Chrome4/13/2021 Chrome Android4/13/2021
Chrome: Only works when both axes are using overflow: clip. See bug 40235584.Chrome Android: Only works when both axes are using overflow: clip. See bug 40235584.Edge: Only works when both axes are using overflow: clip. See bug 40235584.Firefox: Only supports using a length, not a visual box. See bug 1661582.Firefox for Android: Only supports using a length, not a visual box. See bug 1661582.Quest Browser: Only works when both axes are using overflow: clip. See bug 40235584.Opera: Only works when both axes are using overflow: clip. See bug 40235584.Opera Android: Only works when both axes are using overflow: clip. See bug 40235584.Samsung Internet: Only works when both axes are using overflow: clip. See bug 40235584.WebView Android: Only works when both axes are using overflow: clip. See bug 40235584.
css.properties.overflow-x.clip πŸ“‹Chrome4/13/2021 Chrome Android4/13/2021
css.properties.overflow-y.clip πŸ“‹Chrome4/13/2021 Chrome Android4/13/2021
css.types.overflow.clip Chrome4/13/2021 Chrome Android4/13/2021

2021/3

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.forced-colors πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.border-end-end-radius πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.border-end-start-radius πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.border-start-end-radius πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.border-start-start-radius πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.filter.svg_elements Chrome3/2/2021 Chrome Android3/2/2021
css.properties.forced-color-adjust πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.forced-color-adjust.auto πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.forced-color-adjust.none πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.list-style-type.disclosure-closed πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.list-style-type.disclosure-open πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.properties.text-decoration-thickness πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
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.
css.selectors.file-selector-button πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021
css.selectors.target-text πŸ“‹Chrome3/2/2021 Chrome Android3/2/2021

2021/1

API First Browser Date Last Browser Date Days Notes
css.properties.aspect-ratio πŸ“‹Chrome1/19/2021 Chrome Android1/19/2021
css.properties.aspect-ratio.auto πŸ“‹Chrome1/19/2021 Chrome Android1/19/2021
css.properties.clip-path.path Chrome1/19/2021 Chrome Android1/19/2021
css.properties.hyphens.auto Chrome Android12/6/2016 Chrome1/19/20211505
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.manual Chrome Android12/6/2016 Chrome1/19/20211505
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.none Chrome Android12/6/2016 Chrome1/19/20211505
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.selectors.is πŸ“‹Chrome1/19/2021 Chrome Android1/19/2021
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 Chrome1/19/2021 Chrome Android1/19/2021
css.selectors.not.selector_list Chrome1/19/2021 Chrome Android1/19/2021
css.selectors.where πŸ“‹Chrome1/19/2021 Chrome Android1/19/2021
css.selectors.where.forgiving_selector_list Chrome1/19/2021 Chrome Android1/19/2021
css.types.basic-shape.path.clip-path πŸ“‹Chrome1/19/2021 Chrome Android1/19/2021

2020/11

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.ascent-override πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.at-rules.font-face.descent-override πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.at-rules.font-face.line-gap-override πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.currentColor πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.dashed πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.dotted πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.double πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.groove πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.hidden πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.inset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.medium πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.none πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.outset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.ridge πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.solid πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.thick πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.thin πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block.transparent πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-color πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-color.currentColor πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-color.transparent πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.dashed πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.dotted πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.double πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.groove πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.hidden πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.inset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.none πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.outset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.ridge πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-style.solid πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-width πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-width.medium πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-width.thick πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-block-width.thin πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.currentColor πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.dashed πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.dotted πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.double πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.groove πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.hidden πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.inset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.medium πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.none πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.outset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.ridge πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.solid πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.thick πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.thin πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline.transparent πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-color πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-color.currentColor πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-color.transparent πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.dashed πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.dotted πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.double πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.groove πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.hidden πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.inset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.none πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.outset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.ridge πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-style.solid πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-width πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-width.medium πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-width.thick πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.border-inline-width.thin πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_armenian Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_assamese Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_basque Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_belarusian Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_bengali Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_bulgarian Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_croatian Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_cyrillic_mongolian Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_danish Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_estonian Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_ethiopic_script_und Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_french Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_german_reformed_orthography Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_german_swiss_orthography Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_german_traditional_orthography Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_gujarati Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_hindi Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_hungarian Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_irish Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_kannada Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_latin Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_malayalam Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_marathi Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_norwegian_nn Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_norwegian_no Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_old_slavonic Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_oriya Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_portuguese Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_punjabi Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_slovenian Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_spanish Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_tamil Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_telugu Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_turkmen Chrome11/17/2020 Chrome Android11/17/2020
css.properties.hyphens.language_welsh Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-block πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-block.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-block-end πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-block-end.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-block-start πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-block-start.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-inline πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-inline.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-inline-end πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-inline-end.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-inline-start πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.inset-inline-start.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.margin-block πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.margin-block.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.margin-inline πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.margin-inline.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.padding-block πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.padding-inline πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.quotes.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
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.text-decoration.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-decoration.from-font πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-decoration.includes_thickness Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-decoration-thickness.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-decoration-thickness.from-font πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-decoration-thickness.percentage Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-underline-offset πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-underline-offset.auto πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-underline-offset.percentage πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020
css.properties.text-underline-position.from-font πŸ“‹Chrome11/17/2020 Chrome Android11/17/2020

2020/10

API First Browser Date Last Browser Date Days Notes
css.selectors.focus-visible πŸ“‹Chrome10/20/2020 Chrome Android10/20/2020
css.selectors.marker πŸ“‹Chrome10/20/2020 Chrome Android10/20/2020
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.
css.selectors.marker.animation_and_transition_support Chrome10/20/2020 Chrome Android10/20/2020

2020/8

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.prefers-reduced-data πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.at-rules.page.page-orientation πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.at-rules.property πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.at-rules.property.inherits πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.at-rules.property.initial-value πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.at-rules.property.syntax πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.properties.content-visibility πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.properties.content-visibility.auto πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
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.content-visibility.hidden πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.properties.content-visibility.visible πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.properties.counter-set πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.properties.counter-set.list-item πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.properties.counter-set.none πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.properties.page πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020
css.properties.page.auto πŸ“‹Chrome8/25/2020 Chrome Android8/25/2020

2020/7

API First Browser Date Last Browser Date Days Notes
css.properties.appearance πŸ“‹Chrome7/27/2020 Chrome Android7/27/2020
css.properties.column-gap.flex_context πŸ“‹Chrome7/27/2020 Chrome Android7/27/2020
css.properties.gap.flex_context πŸ“‹Chrome7/27/2020 Chrome Android7/27/2020
css.properties.row-gap.flex_context πŸ“‹Chrome7/27/2020 Chrome Android7/27/2020
css.properties.ruby-position πŸ“‹Chrome7/27/2020 Chrome Android7/27/2020
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 Chrome Android7/27/2020
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 Chrome Android7/27/2020
css.properties.ruby-position.under Chrome7/27/2020 Chrome Android7/27/2020
css.types.global_keywords.revert πŸ“‹Chrome7/27/2020 Chrome Android7/27/2020

2020/5

API First Browser Date Last Browser Date Days Notes
css.at-rules.page.size.jis-b4 πŸ“‹Chrome5/19/2020 Chrome Android5/19/2020
css.at-rules.page.size.jis-b5 πŸ“‹Chrome5/19/2020 Chrome Android5/19/2020
css.at-rules.supports.selector Chrome5/19/2020 Chrome Android5/19/2020
css.properties.appearance.auto πŸ“‹Chrome5/19/2020 Chrome Android5/19/2020
css.properties.contain-intrinsic-size πŸ“‹Chrome5/19/2020 Chrome Android5/19/2020
css.properties.line-break.anywhere πŸ“‹Chrome5/19/2020 Chrome Android5/19/2020
css.selectors.xr-overlay πŸ“‹Chrome5/19/2020 Chrome Android5/19/2020

2020/4

API First Browser Date Last Browser Date Days Notes
css.properties.color-scheme πŸ“‹Chrome4/7/2020 Chrome Android4/7/2020
css.properties.color-scheme.dark Chrome4/7/2020 Chrome Android4/7/2020
css.properties.color-scheme.light Chrome4/7/2020 Chrome Android4/7/2020
css.properties.color-scheme.normal Chrome4/7/2020 Chrome Android4/7/2020
css.properties.image-orientation πŸ“‹Chrome4/7/2020 Chrome Android4/7/2020
css.properties.image-orientation.from-image πŸ“‹Chrome4/7/2020 Chrome Android4/7/2020
css.properties.image-orientation.none πŸ“‹Chrome4/7/2020 Chrome Android4/7/2020

2020/2

API First Browser Date Last Browser Date Days Notes
css.properties.offset-path.none πŸ“‹Chrome2/4/2020 Chrome Android2/4/2020
css.properties.overflow-wrap.anywhere πŸ“‹Chrome2/4/2020 Chrome Android2/4/2020
css.properties.speak πŸ“‹Chrome2/4/2020 Chrome Android2/4/2020
Chrome: The implementation is not compliant with the specification, see bug 40813740.Chrome Android: The implementation is not compliant with the specification, see bug 40813740.Edge: The implementation is not compliant with the specification, see bug 40813740.Quest Browser: The implementation is not compliant with the specification, see bug 40813740.Opera: The implementation is not compliant with the specification, see bug 40813740.Opera Android: The implementation is not compliant with the specification, see bug 40813740.Samsung Internet: The implementation is not compliant with the specification, see bug 40813740.WebView Android: The implementation is not compliant with the specification, see bug 40813740.

2019/12

API First Browser Date Last Browser Date Days Notes
css.properties.font-optical-sizing πŸ“‹Chrome12/10/2019 Chrome Android12/17/20197
css.properties.font-optical-sizing.auto πŸ“‹Chrome12/10/2019 Chrome Android12/17/20197
css.properties.font-optical-sizing.none πŸ“‹Chrome12/10/2019 Chrome Android12/17/20197
css.properties.font-size.xxx-large Chrome12/10/2019 Chrome Android12/17/20197
css.properties.list-style-type.string Chrome12/10/2019 Chrome Android12/17/20197
css.types.clamp πŸ“‹Chrome12/10/2019 Chrome Android12/17/20197
css.types.max πŸ“‹Chrome12/10/2019 Chrome Android12/17/20197
css.types.min πŸ“‹Chrome12/10/2019 Chrome Android12/17/20197

2019/10

API First Browser Date Last Browser Date Days Notes
css.properties.opacity.percentages Chrome10/22/2019 Chrome Android10/22/2019
css.properties.scroll-padding-bottom.auto πŸ“‹Chrome10/22/2019 Chrome Android10/22/2019
css.properties.scroll-padding-left.auto πŸ“‹Chrome10/22/2019 Chrome Android10/22/2019
css.properties.scroll-padding-right.auto πŸ“‹Chrome10/22/2019 Chrome Android10/22/2019
css.properties.scroll-padding-top.auto πŸ“‹Chrome10/22/2019 Chrome Android10/22/2019
css.properties.shape-image-threshold.percentages Chrome10/22/2019 Chrome Android10/22/2019

2019/9

API First Browser Date Last Browser Date Days Notes
css.properties.animation-timing-function.jump Chrome9/10/2019 Chrome Android9/10/2019
css.properties.content.alt_text Chrome9/10/2019 Chrome Android9/10/2019
css.properties.overscroll-behavior-block πŸ“‹Chrome9/10/2019 Chrome Android9/10/2019
css.properties.overscroll-behavior-block.auto πŸ“‹Chrome9/10/2019 Chrome Android9/10/2019
css.properties.overscroll-behavior-block.contain πŸ“‹Chrome9/10/2019 Chrome Android9/10/2019
css.properties.overscroll-behavior-block.none πŸ“‹Chrome9/10/2019 Chrome Android9/10/2019
css.properties.overscroll-behavior-inline πŸ“‹Chrome9/10/2019 Chrome Android9/10/2019
css.properties.overscroll-behavior-inline.auto πŸ“‹Chrome9/10/2019 Chrome Android9/10/2019
css.properties.overscroll-behavior-inline.contain πŸ“‹Chrome9/10/2019 Chrome Android9/10/2019
css.properties.overscroll-behavior-inline.none πŸ“‹Chrome9/10/2019 Chrome Android9/10/2019
css.properties.transition-timing-function.jump Chrome9/10/2019 Chrome Android9/10/2019
css.types.easing-function.steps.jump Chrome9/10/2019 Chrome Android9/10/2019

2019/7

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.prefers-color-scheme πŸ“‹Chrome7/30/2019 Chrome Android7/30/2019
css.properties.backdrop-filter πŸ“‹Chrome7/30/2019 Chrome Android7/30/2019
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.backdrop-filter.none πŸ“‹Chrome7/30/2019 Chrome Android7/30/2019
css.properties.white-space.break-spaces πŸ“‹Chrome7/30/2019 Chrome Android7/30/2019

2019/6

API First Browser Date Last Browser Date Days Notes
css.properties.scroll-snap-stop πŸ“‹Chrome6/4/2019 Chrome Android6/4/2019
css.properties.scroll-snap-stop.always πŸ“‹Chrome6/4/2019 Chrome Android6/4/2019
css.properties.scroll-snap-stop.normal πŸ“‹Chrome6/4/2019 Chrome Android6/4/2019

2019/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.prefers-reduced-motion πŸ“‹Chrome4/23/2019 Chrome Android4/24/20191

2019/3

API First Browser Date Last Browser Date Days Notes
css.selectors.part πŸ“‹Chrome3/12/2019 Chrome Android3/12/2019

2019/1

API First Browser Date Last Browser Date Days Notes
css.types.gradient.conic-gradient.doubleposition Chrome1/29/2019 Chrome Android1/29/2019

2018/12

API First Browser Date Last Browser Date Days Notes
css.properties.display.list-item.legend-support Chrome12/4/2018 Chrome Android12/4/2018
css.properties.text-underline-position.left πŸ“‹Chrome12/4/2018 Chrome Android12/4/2018
css.properties.text-underline-position.right πŸ“‹Chrome12/4/2018 Chrome Android12/4/2018
css.selectors.fullscreen πŸ“‹Chrome12/4/2018 Chrome Android12/4/2018
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.gradient.linear-gradient.doubleposition Chrome12/4/2018 Chrome Android12/4/2018
css.types.gradient.radial-gradient.doubleposition Chrome12/4/2018 Chrome Android12/4/2018
css.types.gradient.repeating-linear-gradient.doubleposition Chrome12/4/2018 Chrome Android12/4/2018
css.types.gradient.repeating-radial-gradient.doubleposition Chrome12/4/2018 Chrome Android12/4/2018

2018/9

API First Browser Date Last Browser Date Days Notes
css.properties.border-block-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.currentColor πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.dashed πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.dotted πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.double πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.groove πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.hidden πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.inset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.medium πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.outset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.ridge πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.solid πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.thick πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.thin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end.transparent πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-color πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-color.currentColor πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-color.transparent πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.dashed πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.dotted πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.double πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.groove πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.hidden πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.inset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.outset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.ridge πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-style.solid πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-width πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-width.medium πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-width.thick πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-end-width.thin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.currentColor πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.dashed πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.dotted πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.double πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.groove πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.hidden πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.inset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.medium πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.outset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.ridge πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.solid πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.thick πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.thin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start.transparent πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-color πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-color.currentColor πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-color.transparent πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.dashed πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.dotted πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.double πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.groove πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.hidden πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.inset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.outset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.ridge πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-style.solid πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-width πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-width.medium πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-width.thick πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-block-start-width.thin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.currentColor πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.dashed πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.dotted πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.double πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.groove πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.hidden πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.inset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.medium πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.outset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.ridge πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.solid πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.thick πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.thin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end.transparent πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-color πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-color.currentColor πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-color.transparent πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.dashed πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.dotted πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.double πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.groove πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.hidden πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.inset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.outset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.ridge πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-style.solid πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-width πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-width.medium πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-width.thick πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-end-width.thin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.currentColor πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.dashed πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.dotted πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.double πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.groove πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.hidden πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.inset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.medium πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.outset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.ridge πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.solid πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.thick πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.thin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start.transparent πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-color πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-color.currentColor πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-color.transparent πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.dashed πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.dotted πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.double πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.groove πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.hidden πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.inset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.outset πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.ridge πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-style.solid πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-width πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-width.medium πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-width.thick πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.border-inline-start-width.thin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.margin-block-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.margin-block-end.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.margin-block-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.margin-block-start.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.margin-inline-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.margin-inline-end.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.margin-inline-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.margin-inline-start.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.padding-block-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.padding-block-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.padding-inline-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.padding-inline-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-margin πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
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-block πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-margin-block-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-margin-block-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-margin-bottom πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
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-inline πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-margin-inline-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-margin-inline-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-margin-left πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
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 Chrome Android9/4/2018
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 Chrome Android9/4/2018
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 Chrome Android9/4/2018
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.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-block πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-block.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-block-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-block-end.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-block-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-block-start.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-bottom πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
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-inline πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-inline.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-inline-end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-inline-end.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-inline-start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-inline-start.auto πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-padding-left πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
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 Chrome Android9/4/2018
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 Chrome Android9/4/2018
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-snap-align πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-align.center πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-align.end πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-align.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-align.start πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-type πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
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 πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-type.both πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-type.inline πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-type.none πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-type.x πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.properties.scroll-snap-type.y πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.selectors.backdrop.fullscreen Chrome9/4/2018 Chrome Android9/4/2018
css.types.env πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.types.env.safe-area-inset-bottom πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.types.env.safe-area-inset-left πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.types.env.safe-area-inset-right πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.types.env.safe-area-inset-top πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.types.gradient.conic-gradient πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018
css.types.gradient.repeating-conic-gradient πŸ“‹Chrome9/4/2018 Chrome Android9/4/2018

2018/7

API First Browser Date Last Browser Date Days Notes
css.properties.cursor.grab Chrome7/24/2018 Chrome Android7/24/2018
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 πŸ“‹Chrome7/24/2018 Chrome Android7/24/2018
Chrome: Chrome 22 added Windows support.Chrome Android: Chrome Android 25 added Windows support.Edge: Edge 79 added Windows support.Quest Browser: Quest Browser 5.0 added Windows support.Opera: Opera 15 added Windows support.Opera Android: Opera Android 14 added Windows support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.Samsung Internet: Samsung Internet 1.5 added Windows support.WebView Android: WebView Android 4.4 added Windows support.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.overflow.multiple_keywords Chrome7/24/2018 Chrome Android7/24/2018
css.types.resolution.x Chrome7/24/2018 Chrome Android7/24/2018

2018/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.OpenType_CBDT_CBLC Chrome4/17/2018 Chrome Android4/17/2018
css.at-rules.font-face.OpenType_SBIX Chrome4/17/2018 Chrome Android4/17/2018
css.at-rules.font-face.src.format_variations Chrome4/17/2018 Chrome Android4/17/2018
css.at-rules.media.calc πŸ“‹Chrome4/17/2018 Chrome Android4/17/2018
css.at-rules.media.media_query_values Chrome4/17/2018 Chrome Android4/17/2018
css.properties.column-gap.grid_context πŸ“‹Chrome4/17/2018 Chrome Android4/17/2018
css.properties.column-gap.multicol_context.calc_values Chrome4/17/2018 Chrome Android4/17/2018
css.properties.column-gap.multicol_context.percentage_values Chrome4/17/2018 Chrome Android4/17/2018
css.properties.gap.grid_context πŸ“‹Chrome4/17/2018 Chrome Android4/17/2018
css.properties.gap.grid_context.calc_values Chrome4/17/2018 Chrome Android4/17/2018
css.properties.gap.grid_context.percentage_values Chrome4/17/2018 Chrome Android4/17/2018
css.properties.gap.multicol_context πŸ“‹Chrome4/17/2018 Chrome Android4/17/2018
css.properties.row-gap.grid_context πŸ“‹Chrome4/17/2018 Chrome Android4/17/2018
css.types.color.rgb.float_values Chrome4/17/2018 Chrome Android4/17/2018

2018/3

API First Browser Date Last Browser Date Days Notes
css.properties.display.contents πŸ“‹Chrome3/6/2018 Chrome Android3/6/2018
css.properties.display.contents.contents_unusual πŸ“‹Chrome3/6/2018 Chrome Android3/6/2018
css.selectors.any-link πŸ“‹Chrome3/6/2018 Chrome Android3/6/2018
css.selectors.any-link.not_match_link Chrome3/6/2018 Chrome Android3/6/2018
css.types.color.hsl.alpha_parameter Chrome3/6/2018 Chrome Android3/6/2018
css.types.color.hsl.space_separated_parameters Chrome3/6/2018 Chrome Android3/6/2018
css.types.color.rgb.alpha_parameter Chrome3/6/2018 Chrome Android3/6/2018
css.types.color.rgb.space_separated_parameters Chrome3/6/2018 Chrome Android3/6/2018
css.types.image.paint πŸ“‹Chrome3/6/2018 Chrome Android3/6/2018

2018/1

API First Browser Date Last Browser Date Days Notes
css.properties.offset-path.path Chrome1/23/2018 Chrome Android1/23/2018
css.properties.text-decoration-skip-ink πŸ“‹Chrome1/23/2018 Chrome Android1/23/2018
css.properties.text-decoration-skip-ink.auto πŸ“‹Chrome1/23/2018 Chrome Android1/23/2018
css.properties.text-decoration-skip-ink.none πŸ“‹Chrome1/23/2018 Chrome Android1/23/2018
css.properties.transform-box πŸ“‹Chrome1/23/2018 Chrome Android1/23/2018
css.properties.transform-box.fill-box πŸ“‹Chrome1/23/2018 Chrome Android1/23/2018
css.properties.transform-box.view-box πŸ“‹Chrome1/23/2018 Chrome Android1/23/2018

2017/12

API First Browser Date Last Browser Date Days Notes
css.properties.font-variant-east-asian πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.full-width πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.jis04 πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.jis78 πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.jis83 πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.jis90 πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.normal πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.proportional-width πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.ruby πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.simplified πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.font-variant-east-asian.traditional πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior.auto πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior.contain πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior.none πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-x πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior-x.auto πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior-x.contain πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior-x.none πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-y πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior-y.auto πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior-y.contain πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
css.properties.overscroll-behavior-y.none πŸ“‹Chrome Android12/5/2017 Chrome12/6/20171
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.types.length.Q Chrome Android12/5/2017 Chrome12/6/20171

2017/10

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.font-stretch πŸ“‹Chrome10/17/2017 Chrome Android10/24/20177
css.properties.font-stretch.percentage Chrome10/17/2017 Chrome Android10/24/20177
css.properties.font-style.oblique-angle πŸ“‹Chrome10/17/2017 Chrome Android10/24/20177
Chrome: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Chrome Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Edge: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Quest Browser: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Samsung Internet: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.
css.properties.font-variation-settings πŸ“‹Chrome10/17/2017 Chrome Android10/24/20177
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 πŸ“‹Chrome10/17/2017 Chrome Android10/24/20177
css.properties.font-weight.number Chrome10/17/2017 Chrome Android10/24/20177
css.properties.text-emphasis-position.left Chrome10/17/2017 Chrome Android10/24/20177
css.properties.text-emphasis-position.right Chrome10/17/2017 Chrome Android10/24/20177
css.types.color.rgb_hexadecimal_notation.alpha_hexadecimal_notation Chrome10/17/2017 Chrome Android10/24/20177

2017/9

API First Browser Date Last Browser Date Days Notes
css.properties.offset.none πŸ“‹Chrome9/5/2017 Chrome Android9/5/2017
css.properties.scroll-behavior πŸ“‹Chrome9/5/2017 Chrome Android9/5/2017
css.properties.scroll-behavior.auto πŸ“‹Chrome9/5/2017 Chrome Android9/5/2017
css.properties.scroll-behavior.smooth πŸ“‹Chrome9/5/2017 Chrome Android9/5/2017

2017/8

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.font-display πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.align-content.flex_context.space-evenly Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font.font-width_keyword_values Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font-stretch πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
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 Chrome Android8/1/20177
css.properties.font-stretch.expanded πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font-stretch.extra-condensed πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font-stretch.extra-expanded πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font-stretch.normal πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font-stretch.semi-condensed πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font-stretch.semi-expanded πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font-stretch.ultra-condensed πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.font-stretch.ultra-expanded πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177
css.properties.justify-content.flex_context.space-evenly Chrome7/25/2017 Chrome Android8/1/20177
css.selectors.focus-within πŸ“‹Chrome7/25/2017 Chrome Android8/1/20177

2017/6

API First Browser Date Last Browser Date Days Notes
css.properties.align-content.flex_context.first_baseline Chrome6/5/2017 Chrome Android6/6/20171
css.properties.align-items.flex_context.first_baseline Chrome6/5/2017 Chrome Android6/6/20171
css.properties.align-self.flex_context.first_baseline Chrome6/5/2017 Chrome Android6/6/20171
css.properties.place-content πŸ“‹Chrome6/5/2017 Chrome Android6/6/20171
css.properties.place-content.flex_context Chrome6/5/2017 Chrome Android6/6/20171
Firefox: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.Firefox for Android: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.
css.properties.place-content.grid_context Chrome6/5/2017 Chrome Android6/6/20171
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 Chrome Android6/6/20171
css.properties.place-items.flex_context Chrome6/5/2017 Chrome Android6/6/20171
css.properties.place-items.grid_context Chrome6/5/2017 Chrome Android6/6/20171
css.properties.place-self πŸ“‹Chrome6/5/2017 Chrome Android6/6/20171
css.properties.place-self.flex_context Chrome6/5/2017 Chrome Android6/6/20171
css.properties.place-self.grid_context Chrome6/5/2017 Chrome Android6/6/20171
css.types.blend-mode πŸ“‹Chrome5/20/2014 Chrome Android6/6/20171113

2017/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.color-gamut πŸ“‹Chrome4/19/2017 Chrome Android4/25/20176
css.at-rules.media.color-gamut.p3 πŸ“‹Chrome4/19/2017 Chrome Android4/25/20176
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 πŸ“‹Chrome4/19/2017 Chrome Android4/25/20176
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 πŸ“‹Chrome4/19/2017 Chrome Android4/25/20176
Firefox: color-gamut: srgb is always true because Firefox does not support wide-gamut color. See bug 1626624.Firefox for Android: color-gamut: srgb is always true because Firefox for Android does not support wide-gamut color. See bug 1626624.
css.properties.display.flow-root Chrome4/19/2017 Chrome Android4/25/20176
css.properties.line-break πŸ“‹Chrome4/19/2017 Chrome Android4/25/20176

2017/3

API First Browser Date Last Browser Date Days Notes
css.properties.align-content.flex_context.baseline Chrome3/9/2017 Chrome Android3/16/20177
css.properties.align-content.flex_context.stretch Chrome3/9/2017 Chrome Android3/16/20177
css.properties.align-items.grid_context.start_end Chrome3/9/2017 Chrome Android3/16/20177
css.properties.align-self.flex_context.stretch πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.block-size πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.block-size.fit-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.block-size.max-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.block-size.min-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.caret-color πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.caret-color.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.caret-color.currentColor πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.caret-color.transparent πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.display.grid Chrome3/9/2017 Chrome Android3/16/20177
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 Chrome Android3/16/20177
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 Chrome Android3/16/20177
css.properties.gap.normal πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
Samsung Internet: This was added early so is out of sync with the equivalent Chromium version.
css.properties.grid.none πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-area πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-area.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-auto-columns πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
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 Chrome Android3/16/20177
css.properties.grid-auto-columns.max-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-auto-columns.min-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-auto-flow πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-auto-flow.column πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-auto-flow.dense πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-auto-flow.row πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-auto-rows πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
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 Chrome Android3/16/20177
css.properties.grid-auto-rows.max-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-auto-rows.min-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-column πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-column.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-column-end πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-column-end.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-column-start πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-column-start.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-row πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-row.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-row-end πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-row-end.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-row-start πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-row-start.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template.none πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-areas πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-areas.none πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-columns πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-columns.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-columns.fit-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-columns.max-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-columns.min-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-columns.minmax πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-columns.none πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-columns.repeat πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
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 Chrome Android3/16/20177
css.properties.grid-template-rows.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-rows.fit-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-rows.max-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-rows.min-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-rows.minmax πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-rows.none πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.grid-template-rows.repeat πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
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.inline-size πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.inline-size.fit-content πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.inline-size.max-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.inline-size.min-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.justify-content.flex_context.stretch Chrome3/9/2017 Chrome Android3/16/20177
css.properties.justify-items.grid_context πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.justify-self πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.justify-self.auto Chrome3/9/2017 Chrome Android3/16/20177
css.properties.justify-self.grid_context πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
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 Chrome Android3/16/20177
css.properties.justify-self.normal Chrome3/9/2017 Chrome Android3/16/20177
css.properties.justify-self.right Chrome3/9/2017 Chrome Android3/16/20177
css.properties.justify-self.stretch Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-block-size πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-block-size.fit-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-block-size.max-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-block-size.min-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-block-size.none πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-inline-size πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-inline-size.fit-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-inline-size.max-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-inline-size.min-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.max-inline-size.none πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-block-size πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-block-size.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-block-size.fit-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-block-size.max-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-block-size.min-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-inline-size πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-inline-size.auto πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-inline-size.fit-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-inline-size.max-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.min-inline-size.min-content Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration.currentColor πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration.dashed πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration.dotted πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration.double πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration.includes_color-and-style Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration.solid πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration.transparent πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration.wavy πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-color πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-color.currentColor πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-color.transparent πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-line πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-line.blink πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
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 πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-line.none πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-line.overline πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-line.underline πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-style πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-style.dashed πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-style.dotted πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-style.double πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-style.solid πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.text-decoration-style.wavy πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.selectors.first-child.no_parent_required Chrome3/9/2017 Chrome Android3/16/20177
css.selectors.last-child.no_parent_required Chrome3/9/2017 Chrome Android3/16/20177
css.selectors.nth-child.no_parent_required Chrome3/9/2017 Chrome Android3/16/20177
css.selectors.nth-last-child.no_parent_required Chrome3/9/2017 Chrome Android3/16/20177
css.selectors.only-child.no_parent_required Chrome3/9/2017 Chrome Android3/16/20177
css.selectors.placeholder πŸ“‹Chrome3/9/2017 Chrome Android3/16/20177
css.properties.align-content.grid_context πŸ“‹Chrome Android7/27/2016 Chrome3/9/2017225
css.properties.align-items.grid_context πŸ“‹Chrome Android7/27/2016 Chrome3/9/2017225
css.properties.align-self.grid_context πŸ“‹Chrome Android7/27/2016 Chrome3/9/2017225
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.justify-content.grid_context πŸ“‹Chrome Android7/27/2016 Chrome3/9/2017225

2017/2

API First Browser Date Last Browser Date Days Notes
css.properties.border-image-repeat.space πŸ“‹Chrome1/25/2017 Chrome Android2/1/20177
css.properties.font-family.system-ui Chrome1/25/2017 Chrome Android2/1/20177
Firefox: Supported on macOS only.
css.properties.offset-rotate πŸ“‹Chrome1/25/2017 Chrome Android2/1/20177
css.properties.overflow-anchor πŸ“‹Chrome1/25/2017 Chrome Android2/1/20177
css.properties.overflow-anchor.auto πŸ“‹Chrome1/25/2017 Chrome Android2/1/20177
css.properties.overflow-anchor.none πŸ“‹Chrome1/25/2017 Chrome Android2/1/20177
css.properties.position.position_sticky_table_elements Chrome1/25/2017 Chrome Android2/1/20177
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).
css.properties.position.sticky πŸ“‹Chrome1/25/2017 Chrome Android2/1/20177
css.properties.touch-action.pinch-zoom Chrome1/25/2017 Chrome Android2/1/20177
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.
css.types.basic-shape.path.offset-path πŸ“‹Chrome1/25/2017 Chrome Android2/1/20177

2016/12

API First Browser Date Last Browser Date Days Notes
css.properties.clip-path πŸ“‹Chrome12/1/2016 Chrome Android12/6/20165
Edge: Only supports clip paths defined by url().Internet Explorer: Only supports clip paths defined by url().
css.properties.clip-path.is_animatable Chrome12/1/2016 Chrome Android12/6/20165
css.properties.hyphens πŸ“‹Chrome12/1/2016 Chrome Android12/6/20165
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.hyphens.language_english Chrome12/1/2016 Chrome Android12/6/20165
Firefox: For English, Firefox uses an en-US dictionaryFirefox for Android: For English, Firefox for Android uses an en-US dictionarySafari: For English, Safari uses different en-GB and en-US dictionaries.Safari on iOS: For English, Safari on iOS uses different en-GB and en-US dictionaries.WebView on iOS: For English, WebView on iOS uses different en-GB and en-US dictionaries.
css.properties.offset πŸ“‹Chrome12/1/2016 Chrome Android12/6/20165
css.properties.offset-distance πŸ“‹Chrome12/1/2016 Chrome Android12/6/20165
css.properties.offset-path πŸ“‹Chrome12/1/2016 Chrome Android12/6/20165
Samsung Internet: path() is the only value type supported.
css.properties.touch-action.pan-down Chrome12/1/2016 Chrome Android12/6/20165
css.properties.touch-action.pan-left Chrome12/1/2016 Chrome Android12/6/20165
css.properties.touch-action.pan-right Chrome12/1/2016 Chrome Android12/6/20165
css.properties.touch-action.pan-up Chrome12/1/2016 Chrome Android12/6/20165

2016/10

API First Browser Date Last Browser Date Days Notes
css.properties.text-size-adjust πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
css.properties.text-size-adjust.auto πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
css.properties.text-size-adjust.none πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
css.properties.text-size-adjust.percentages πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
css.properties.user-select πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
css.selectors.defined πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
css.selectors.host πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
css.selectors.host-context πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
css.selectors.hostfunction πŸ“‹Chrome10/12/2016 Chrome Android10/19/20167
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.OpenType_COLRv0 Chrome8/31/2016 Chrome Android9/7/20167
css.properties.filter πŸ“‹Chrome8/31/2016 Chrome Android9/7/20167
Internet Explorer: Internet Explorer 4 to 9 implemented a non-standard filter property. The syntax was completely different from this one and is not documented here.
css.properties.filter.blur πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.properties.filter.brightness πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.properties.filter.contrast πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.properties.filter.drop-shadow πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.properties.filter.grayscale πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.properties.filter.hue-rotate πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.properties.filter.invert πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.properties.filter.opacity πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.properties.filter.saturate πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
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 Chrome Android9/7/20161624
css.properties.rx.auto πŸ“‹Chrome8/31/2016 Chrome Android9/7/20167
css.properties.ry.auto πŸ“‹Chrome8/31/2016 Chrome Android9/7/20167
css.properties.user-select.all Chrome8/31/2016 Chrome Android9/7/20167
css.types.filter-function πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.blur πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.brightness πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.contrast πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.drop-shadow πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.grayscale πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.hue-rotate πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.invert πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.opacity πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.saturate πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624
css.types.filter-function.sepia πŸ“‹Chrome3/28/2012 Chrome Android9/7/20161624

2016/7

API First Browser Date Last Browser Date Days Notes
css.properties.align-items.flex_context πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
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.contain πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.contain.content πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.contain.layout πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.contain.none πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.contain.paint πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.contain.size πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.contain.strict πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.contain.style πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
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.d πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
Safari: The property parses, but has no effect.Safari on iOS: The property parses, but has no effect.WebView on iOS: The property parses, but has no effect.
css.properties.d.none πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant.css_fonts_shorthand Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant.none πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-caps πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-caps.all-petite-caps πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-caps.all-small-caps πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-caps.normal πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-caps.petite-caps πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-caps.small-caps πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-caps.titling-caps πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-caps.unicase πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.diagonal-fractions πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.lining-nums πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.normal πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.oldstyle-nums πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.ordinal πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.proportional-nums πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.slashed-zero πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.stacked-fractions πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.font-variant-numeric.tabular-nums πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.justify-content.flex_context πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
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 πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.justify-items.center Chrome7/20/2016 Chrome Android7/27/20167
css.properties.justify-items.flex_context πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.justify-items.left Chrome7/20/2016 Chrome Android7/27/20167
css.properties.justify-items.legacy πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.properties.justify-items.right Chrome7/20/2016 Chrome Android7/27/20167
css.properties.position.absolutely_positioned_flex_children Chrome7/20/2016 Chrome Android7/27/20167
css.types.basic-shape.path πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167
css.types.basic-shape.path.d πŸ“‹Chrome7/20/2016 Chrome Android7/27/20167

2016/6

API First Browser Date Last Browser Date Days Notes
css.properties.break-before.multicol_context.column Chrome5/25/2016 Chrome Android6/8/201614
css.properties.break-inside.paged_context.avoid-page Chrome5/25/2016 Chrome Android6/8/201614
css.types.calc.nested Chrome5/25/2016 Chrome Android6/8/201614

2016/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.hover πŸ“‹Chrome10/7/2014 Chrome Android4/13/2016554
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 Chrome Android4/13/2016407
css.properties.break-after πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.auto Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.avoid Chrome4/13/2016 Chrome Android4/13/2016
Firefox: The value is recognized, but has no effect. See bug 1972340.Firefox for Android: The value is recognized, but has no effect. See bug 1972340.Safari: The value is recognized, but has no effect. See bug 294559.Safari on iOS: The value is recognized, but has no effect. See bug 294559.WebView on iOS: The value is recognized, but has no effect. See bug 294559.
css.properties.break-after.avoid-column Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.avoid-page Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.column Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.left Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.multicol_context πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
Firefox: Only supported in print mode. See bug 1675322.Firefox for Android: Only supported in print mode. See bug 1675322.
css.properties.break-after.multicol_context.column Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.page Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.paged_context πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.paged_context.avoid-page Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.paged_context.page Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.recto Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.right Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-after.verso Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.auto Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.avoid Chrome4/13/2016 Chrome Android4/13/2016
Firefox: The value is recognized, but has no effect. See bug 1972340.Firefox for Android: The value is recognized, but has no effect. See bug 1972340.Safari: The value is recognized, but has no effect. See bug 294559.Safari on iOS: The value is recognized, but has no effect. See bug 294559.WebView on iOS: The value is recognized, but has no effect. See bug 294559.
css.properties.break-before.avoid-column Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.avoid-page Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.column Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.left Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.multicol_context πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
Firefox: Only supported in print mode. See bug 1675322.Firefox for Android: Only supported in print mode. See bug 1675322.
css.properties.break-before.page Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.paged_context πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.paged_context.page Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.recto Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.right Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-before.verso Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-inside πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-inside.auto Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-inside.avoid Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-inside.avoid-column Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-inside.avoid-page Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-inside.multicol_context πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-inside.multicol_context.avoid-column Chrome4/13/2016 Chrome Android4/13/2016
css.properties.break-inside.paged_context πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.column-count πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
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 πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.column-fill.auto πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.column-fill.balance πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.column-gap.multicol_context πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.column-rule πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.column-rule-color πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.column-rule-style πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.column-rule-width πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.column-span πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.properties.column-width πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
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 πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
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 πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016
css.selectors.slotted πŸ“‹Chrome4/13/2016 Chrome Android4/13/2016

2016/3

API First Browser Date Last Browser Date Days Notes
css.properties.custom-property πŸ“‹Chrome3/2/2016 Chrome Android3/9/20167
css.properties.flex-grow.less_than_zero_animate Chrome3/2/2016 Chrome Android3/9/20167
Firefox: Before Firefox 32, Firefox wasn't able to animate values starting or stopping at 0.Firefox for Android: Before Firefox for Android 32, Firefox for Android wasn't able to animate values starting or stopping at 0.
css.selectors.attribute.case_insensitive_modifier Chrome3/2/2016 Chrome Android3/9/20167
css.types.var πŸ“‹Chrome3/2/2016 Chrome Android3/9/20167

2016/1

API First Browser Date Last Browser Date Days Notes
css.properties.font-feature-settings πŸ“‹Chrome1/20/2016 Chrome Android1/26/20166
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.text-combine-upright πŸ“‹Chrome1/20/2016 Chrome Android1/26/20166
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 Chrome Android1/26/20166
css.properties.text-combine-upright.none πŸ“‹Chrome1/20/2016 Chrome Android1/26/20166
css.properties.text-orientation πŸ“‹Chrome1/20/2016 Chrome Android1/26/20166
css.properties.text-orientation.mixed πŸ“‹Chrome1/20/2016 Chrome Android1/26/20166
css.properties.unicode-bidi.isolate πŸ“‹Chrome1/20/2016 Chrome Android1/26/20166
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 Chrome Android1/26/20166
css.properties.unicode-bidi.plaintext πŸ“‹Chrome1/20/2016 Chrome Android1/26/20166
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.writing-mode πŸ“‹Chrome1/20/2016 Chrome Android1/26/20166
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.horizontal-tb Chrome1/20/2016 Chrome Android1/26/20166
css.properties.writing-mode.lr Chrome1/20/2016 Chrome Android1/26/20166
css.properties.writing-mode.lr-tb Chrome1/20/2016 Chrome Android1/26/20166
css.properties.writing-mode.rl Chrome1/20/2016 Chrome Android1/26/20166
css.properties.writing-mode.rl-tb Chrome1/20/2016 Chrome Android1/26/20166
css.properties.writing-mode.tb Chrome1/20/2016 Chrome Android1/26/20166
css.properties.writing-mode.tb-rl Chrome1/20/2016 Chrome Android1/26/20166
css.properties.writing-mode.vertical-lr Chrome1/20/2016 Chrome Android1/26/20166
css.properties.writing-mode.vertical-rl Chrome1/20/2016 Chrome Android1/26/20166

2015/12

API First Browser Date Last Browser Date Days Notes
css.properties.row-gap πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.properties.row-gap.normal πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.properties.text-align-last πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
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 Chrome Android12/2/20151
css.properties.text-align-last.center πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.properties.text-align-last.end πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.properties.text-align-last.justify πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.properties.text-align-last.left πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.properties.text-align-last.right πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.properties.text-align-last.start πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.selectors.placeholder-shown πŸ“‹Chrome12/1/2015 Chrome Android12/2/20151
css.selectors.placeholder-shown.non_text_types Chrome12/1/2015 Chrome Android12/2/20151

2015/10

API First Browser Date Last Browser Date Days Notes
css.properties.height.fit-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.height.max-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.height.min-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.max-height.fit-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
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 Chrome Android10/14/20151
css.properties.max-height.min-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.max-width.fit-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
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 Chrome Android10/14/20151
css.properties.max-width.min-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.min-height.fit-content Chrome10/13/2015 Chrome Android10/14/20151
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 Chrome Android10/14/20151
css.properties.min-height.min-content Chrome10/13/2015 Chrome Android10/14/20151
css.properties.min-width.fit-content Chrome10/13/2015 Chrome Android10/14/20151
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 Chrome Android10/14/20151
css.properties.min-width.min-content Chrome10/13/2015 Chrome Android10/14/20151
css.properties.offset-rotate.auto πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.offset-rotate.reverse πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.width.fit-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.width.max-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151
css.properties.width.min-content πŸ“‹Chrome10/13/2015 Chrome Android10/14/20151

2015/9

API First Browser Date Last Browser Date Days Notes
css.at-rules.keyframes.ignore_important_declarations Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.ethiopic-halehame Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.ethiopic-halehame-am Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.korean-hangul-formal πŸ“‹Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.korean-hanja-formal πŸ“‹Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.korean-hanja-informal πŸ“‹Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.simp-chinese-formal πŸ“‹Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.simp-chinese-informal πŸ“‹Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.trad-chinese-formal πŸ“‹Chrome9/1/2015 Chrome Android9/1/2015
css.properties.list-style-type.trad-chinese-informal πŸ“‹Chrome9/1/2015 Chrome Android9/1/2015

2015/7

API First Browser Date Last Browser Date Days Notes
css.properties.word-break.keep-all πŸ“‹Chrome7/21/2015 Chrome Android7/29/20158

2015/5

API First Browser Date Last Browser Date Days Notes
css.at-rules.keyframes πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.animation πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
WebView Android: The animation-fill-mode property is not supported in Android browsers below 2.3.
css.properties.animation-delay πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
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 Chrome Android5/27/20158
css.properties.animation-duration πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
Internet Explorer: Once the element has loaded, changing the value of this property has no effect.
css.properties.animation-fill-mode πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.animation-iteration-count πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.animation-name πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.animation-play-state πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.animation-timing-function πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.cx πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.cy πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.r πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
css.properties.rx πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
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 πŸ“‹Chrome5/19/2015 Chrome Android5/27/20158
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.types.number.scientific_notation Chrome5/19/2015 Chrome Android5/27/20158

2015/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.display-mode πŸ“‹Chrome4/14/2015 Chrome Android4/15/20151
css.at-rules.media.display-mode.browser πŸ“‹Chrome4/14/2015 Chrome Android4/15/20151
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.minimal-ui πŸ“‹Chrome4/14/2015 Chrome Android4/15/20151
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 Chrome Android4/15/20151
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.font-size.rem_values Chrome11/12/2013 Chrome Android4/15/2015519
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.tab-size.length πŸ“‹Chrome4/14/2015 Chrome Android4/15/20151
css.properties.x πŸ“‹Chrome4/14/2015 Chrome Android4/15/20151
css.properties.y πŸ“‹Chrome4/14/2015 Chrome Android4/15/20151

2015/3

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.any-hover πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.at-rules.media.any-pointer πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.image-rendering.pixelated πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.isolation πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.isolation.auto πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.isolation.isolate πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.color πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.color-burn πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.color-dodge πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.darken πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.difference πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.exclusion πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.hard-light πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.hue πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.lighten πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.luminosity πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.multiply πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.normal πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.overlay πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.saturation πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.screen πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.properties.mix-blend-mode.soft-light πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158
css.types.global_keywords.unset πŸ“‹Chrome3/3/2015 Chrome Android3/11/20158

2015/1

API First Browser Date Last Browser Date Days Notes
css.selectors.invalid.form Chrome1/21/2015 Chrome Android1/21/2015
css.selectors.valid.form Chrome1/21/2015 Chrome Android1/21/2015
css.types.gradient.linear-gradient.interpolation_hints Chrome1/21/2015 Chrome Android1/21/2015
css.types.gradient.radial-gradient.interpolation_hints Chrome1/21/2015 Chrome Android1/21/2015
css.types.gradient.repeating-linear-gradient.interpolation_hints Chrome1/21/2015 Chrome Android1/21/2015
css.types.gradient.repeating-radial-gradient.interpolation_hints Chrome1/21/2015 Chrome Android1/21/2015

2014/11

API First Browser Date Last Browser Date Days Notes
css.selectors.indeterminate.radio Chrome Android11/12/2014 Chrome11/18/20146

2014/10

API First Browser Date Last Browser Date Days Notes
css.types.color.named-color.rebeccapurple Chrome10/7/2014 Chrome Android10/8/20141

2014/9

API First Browser Date Last Browser Date Days Notes
css.properties.all πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.cursor.zoom-in πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
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 Chrome Android9/3/20148
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.shape-image-threshold πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-margin πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.border-box πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.circle Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.content-box πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.gradient πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.image πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.inset Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.margin-box πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.none πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.padding-box πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.shape-outside.polygon Chrome8/26/2014 Chrome Android9/3/20148
css.properties.transition.allow-discrete πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.properties.transition.normal πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.selectors.backdrop πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.types.basic-shape πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.types.basic-shape.animation Chrome8/26/2014 Chrome Android9/3/20148
css.types.basic-shape.circle πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.types.basic-shape.ellipse πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.types.basic-shape.inset πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148
css.types.basic-shape.polygon πŸ“‹Chrome8/26/2014 Chrome Android9/3/20148

2014/7

API First Browser Date Last Browser Date Days Notes
css.at-rules.font-face.WOFF_2 πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
Safari: Supported only on macOS 10.12 (Sierra) and later.
css.properties.align-self.flex_context πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
Chrome: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome implements the new behavior beginning with Chrome 52.Chrome Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome Android implements the new behavior beginning with Chrome Android 52.Firefox: Before Firefox 27, only single-line flexbox is supported.Firefox for Android: Before Firefox for Android 27, only single-line flexbox is supported.Samsung Internet: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Samsung Internet implements the new behavior beginning with Samsung Internet 6.0.WebView Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. WebView Android implements the new behavior beginning with WebView Android 52.
css.properties.backface-visibility πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
css.properties.perspective πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
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 Chrome Android7/16/2014
css.properties.touch-action πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.manipulation Chrome7/16/2014 Chrome Android7/16/2014
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.none Chrome7/16/2014 Chrome Android7/16/2014
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-x Chrome7/16/2014 Chrome Android7/16/2014
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-y Chrome7/16/2014 Chrome Android7/16/2014
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.transform πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
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 Chrome Android7/16/2014
css.properties.transform-style πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
Safari: Before Safari 17, ::before and ::after pseudo elements were not included in the 3D rendering context (see bug 256430).
css.properties.will-change πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
css.properties.will-change.auto πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
css.properties.will-change.contents πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014
css.properties.will-change.scroll-position πŸ“‹Chrome7/16/2014 Chrome Android7/16/2014

2014/5

API First Browser Date Last Browser Date Days Notes
css.properties.background-blend-mode πŸ“‹Chrome5/20/2014 Chrome Android5/20/2014
css.properties.paint-order.fill πŸ“‹Chrome5/20/2014 Chrome Android5/20/2014
css.properties.paint-order.markers πŸ“‹Chrome5/20/2014 Chrome Android5/20/2014
css.properties.paint-order.normal πŸ“‹Chrome5/20/2014 Chrome Android5/20/2014
css.properties.paint-order.stroke πŸ“‹Chrome5/20/2014 Chrome Android5/20/2014

2014/4

API First Browser Date Last Browser Date Days Notes
css.properties.font-variant-ligatures πŸ“‹Chrome Android4/2/2014 Chrome4/8/20146
css.properties.text-transform.greek_accented_characters Chrome Android4/2/2014 Chrome4/8/20146

2014/2

API First Browser Date Last Browser Date Days Notes
css.properties.font-kerning πŸ“‹Chrome2/20/2014 Chrome Android2/26/20146
css.properties.font-kerning.auto πŸ“‹Chrome2/20/2014 Chrome Android2/26/20146
css.properties.font-kerning.none πŸ“‹Chrome2/20/2014 Chrome Android2/26/20146
css.properties.font-kerning.normal πŸ“‹Chrome2/20/2014 Chrome Android2/26/20146
css.properties.pointer-events.bounding-box πŸ“‹Chrome2/20/2014 Chrome Android2/26/20146
css.properties.text-underline-position πŸ“‹Chrome2/20/2014 Chrome Android2/26/20146
css.properties.text-underline-position.auto πŸ“‹Chrome2/20/2014 Chrome Android2/26/20146
css.properties.text-underline-position.under πŸ“‹Chrome2/20/2014 Chrome Android2/26/20146

2014/1

API First Browser Date Last Browser Date Days Notes
css.properties.object-fit πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
Edge: Only supported for <img> elements.
css.properties.object-fit.contain πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-fit.cover πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-fit.fill πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-fit.none πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-fit.scale-down πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-position πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
Edge: Only supported for <img> elements.
css.properties.object-position.bottom πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-position.center πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-position.left πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-position.right πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.properties.object-position.top πŸ“‹Chrome1/14/2014 Chrome Android1/15/20141
css.selectors.-webkit-slider-thumb Chrome1/14/2014 Chrome Android1/15/20141
css.selectors.backdrop.dialog Chrome1/14/2014 Chrome Android1/15/20141

2013/11

API First Browser Date Last Browser Date Days Notes
css.properties.background.border-box πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background.bottom πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background.center πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background.content-box πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background.left πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background.padding-box πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background.right πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background.top πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.background-color.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-bottom.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-bottom-color.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-color.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-left.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-left-color.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-right.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-right-color.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-top.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.border-top-color.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.color-interpolation.linearRGB πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant.turkic_is Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.common-ligatures πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.contextual πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.discretionary-ligatures πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.historical-ligatures πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.no-common-ligatures πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.no-contextual πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.no-discretionary-ligatures πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.no-historical-ligatures πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.none πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.font-variant-ligatures.normal πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.outline.currentColor πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.pointer-events.visibleFill πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.pointer-events.visiblePainted πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.pointer-events.visibleStroke πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.shape-rendering.crispEdges πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.shape-rendering.geometricPrecision πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.shape-rendering.optimizeSpeed πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.text-decoration.blink πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
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 πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.text-rendering.optimizeSpeed πŸ“‹Chrome11/12/2013 Chrome Android11/14/20132
css.properties.text-transform.turkic_is Chrome11/12/2013 Chrome Android11/14/20132
css.types.calc.number_values Chrome11/12/2013 Chrome Android11/14/20132

2013/10

API First Browser Date Last Browser Date Days Notes
css.properties.background-repeat.round πŸ“‹Chrome10/1/2013 Chrome Android10/2/20131
css.properties.background-repeat.space πŸ“‹Chrome10/1/2013 Chrome Android10/2/20131
css.properties.border-image-repeat.round πŸ“‹Chrome10/1/2013 Chrome Android10/2/20131
css.properties.text-transform.lowercase_sigma Chrome10/1/2013 Chrome Android10/2/20131

2013/8

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.color-index πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
css.at-rules.media.resolution πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.properties.align-content πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
css.properties.align-content.normal πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
css.properties.align-items πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
css.properties.align-self πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
css.properties.display.flex Chrome8/20/2013 Chrome Android8/21/20131
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 Chrome Android8/21/20131
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 Chrome Android8/21/20131
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 Chrome Android8/21/20131
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-direction πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
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 Chrome Android8/21/20131
css.properties.flex-grow πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
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 Chrome Android8/21/20131
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 Chrome Android8/21/20131
Internet Explorer: Partial support due to large number of bugs present. See Flexbugs.
css.properties.justify-content πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
css.properties.order πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.
css.types.flex πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
css.types.gradient.linear-gradient.premultiplied_gradients Chrome8/20/2013 Chrome Android8/21/20131
css.types.gradient.radial-gradient.premultiplied_gradients Chrome8/20/2013 Chrome Android8/21/20131
css.types.resolution πŸ“‹Chrome8/20/2013 Chrome Android8/21/20131
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.types.resolution.dpcm Chrome8/20/2013 Chrome Android8/21/20131
css.types.resolution.dpi Chrome8/20/2013 Chrome Android8/21/20131
css.types.resolution.dppx Chrome8/20/2013 Chrome Android8/21/20131

2013/7

API First Browser Date Last Browser Date Days Notes
css.at-rules.supports πŸ“‹Chrome7/9/2013 Chrome Android7/10/20131
css.properties.buffered-rendering Chrome7/9/2013 Chrome Android7/10/20131
css.properties.buffered-rendering.auto Chrome7/9/2013 Chrome Android7/10/20131
css.properties.buffered-rendering.dynamic Chrome7/9/2013 Chrome Android7/10/20131
css.properties.buffered-rendering.static Chrome7/9/2013 Chrome Android7/10/20131
css.properties.color-interpolation-filters.linearRGB πŸ“‹Chrome7/9/2013 Chrome Android7/10/20131
css.properties.color-interpolation-filters.sRGB πŸ“‹Chrome7/9/2013 Chrome Android7/10/20131
css.properties.content.element_replacement Chrome7/9/2013 Chrome Android7/10/20131
css.properties.counter-increment.list-item πŸ“‹Chrome7/9/2013 Chrome Android7/10/20131
css.properties.counter-reset.list-item πŸ“‹Chrome7/9/2013 Chrome Android7/10/20131
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.types.calc πŸ“‹Chrome3/26/2013 Chrome Android7/10/2013106
Firefox: Before Firefox 59 calc() is not supported in rgb() and other color functions.Firefox: Before Firefox 57 calc(1*2*3) is not parsed successfully.Firefox: Firefox 57 increased the number of places calc() could substitute another value. See bug 1350857.Firefox for Android: Before Firefox for Android 59 calc() is not supported in rgb() and other color functions.Firefox for Android: Before Firefox for Android 57 calc(1*2*3) is not parsed successfully.Firefox for Android: Firefox for Android 57 increased the number of places calc() could substitute another value. See bug 1350857.
css.types.calc.gradient_color_stops Chrome5/15/2012 Chrome Android7/10/2013421

2013/5

API First Browser Date Last Browser Date Days Notes
css.selectors.scope πŸ“‹Chrome5/21/2013 Chrome Android5/22/20131
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 Chrome Android5/22/20131
css.types.length.ch Chrome5/21/2013 Chrome Android5/22/20131
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.

2013/4

API First Browser Date Last Browser Date Days Notes
css.at-rules.media.nested-queries Chrome3/26/2013 Chrome Android4/3/20138
css.properties.content.gradient πŸ“‹Chrome3/26/2013 Chrome Android4/3/20138
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.transition πŸ“‹Chrome3/26/2013 Chrome Android4/3/20138
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 Chrome Android4/3/20138
css.properties.transition-duration πŸ“‹Chrome3/26/2013 Chrome Android4/3/20138
css.properties.transition-property πŸ“‹Chrome3/26/2013 Chrome Android4/3/20138
css.properties.transition-timing-function πŸ“‹Chrome3/26/2013 Chrome Android4/3/20138
css.properties.width.is_animatable Chrome3/26/2013 Chrome Android4/3/20138
css.selectors.-webkit-slider-runnable-track Chrome3/26/2013 Chrome Android4/3/20138
css.selectors.after.animation_and_transition_support Chrome3/26/2013 Chrome Android4/3/20138
css.selectors.before.animation_and_transition_support Chrome3/26/2013 Chrome Android4/3/20138
css.selectors.cue πŸ“‹Chrome3/26/2013 Chrome Android4/3/20138
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 Chrome Android4/3/20138
css.types.gradient πŸ“‹Chrome3/26/2013 Chrome Android4/3/20138
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 Chrome Android4/3/20138
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 Chrome Android4/3/20138
css.types.gradient.linear-gradient.unitless_0_angle Chrome3/26/2013 Chrome Android4/3/20138
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 Chrome Android4/3/20138
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 Chrome Android4/3/20138
css.types.gradient.repeating-linear-gradient πŸ“‹Chrome3/26/2013 Chrome Android4/3/20138
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 Chrome Android4/3/20138
css.types.gradient.repeating-linear-gradient.unitless_0_angle Chrome3/26/2013 Chrome Android4/3/20138
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 Chrome Android4/3/20138
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 Chrome Android4/3/20138
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.vmax Chrome3/26/2013 Chrome Android4/3/20138
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 Chrome Android4/3/20138
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.

2013/2

API First Browser Date Last Browser Date Days Notes
css.properties.-webkit-app-region Chrome1/10/2013 Chrome Android2/27/201348
css.properties.align-content.flex_context πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.align-items.flex_context.baseline Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.align-self.auto πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.align-self.flex_context.baseline πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.align-self.normal πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.align-self.stretch πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.animation-direction.alternate-reverse πŸ“‹Chrome5/15/2012 Chrome Android2/27/2013288
css.properties.animation-direction.reverse πŸ“‹Chrome5/15/2012 Chrome Android2/27/2013288
css.properties.background.background-clip Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.background.background-origin Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.background.background-size Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.background-position.side-relative_values Chrome2/21/2013 Chrome Android2/27/20136
css.properties.clip-path.basic_shape πŸ“‹Chrome11/6/2012 Chrome Android2/27/2013113
css.properties.clip-path.html_elements Chrome11/6/2012 Chrome Android2/27/2013113
css.properties.clip-path.svg_elements Chrome11/6/2012 Chrome Android2/27/2013113
css.properties.flex.auto πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex.none πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-basis.auto Chrome9/25/2012 Chrome Android2/27/2013155
css.properties.flex-direction.column πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-direction.column-reverse πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
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 Chrome Android2/27/2013211
css.properties.flex-direction.row-reverse πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
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 Chrome Android2/27/2013211
css.properties.flex-flow.column-reverse πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-flow.nowrap πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-flow.row πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-flow.row-reverse πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-flow.wrap πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-flow.wrap-reverse πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-wrap.nowrap πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-wrap.wrap πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.flex-wrap.wrap-reverse πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.justify-content.left Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.justify-content.normal Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.justify-content.right Chrome7/31/2012 Chrome Android2/27/2013211
css.properties.line-break.auto πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.line-break.loose πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.line-break.strict πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.mask-type πŸ“‹Chrome1/10/2013 Chrome Android2/27/201348
css.properties.mask-type.alpha πŸ“‹Chrome1/10/2013 Chrome Android2/27/201348
css.properties.mask-type.luminance πŸ“‹Chrome1/10/2013 Chrome Android2/27/201348
css.properties.min-height.auto Chrome7/31/2012 Chrome Android2/27/2013211
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 Chrome Android2/27/2013211
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.orphans πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.overflow-wrap πŸ“‹Chrome11/6/2012 Chrome Android2/27/2013113
css.properties.tab-size πŸ“‹Chrome7/31/2012 Chrome Android2/27/2013211
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 Chrome Android2/27/20136
css.properties.text-emphasis.currentColor πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis.dot πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis.double-circle πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis.filled πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis.none πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis.open πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis.sesame πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis.transparent πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis.triangle πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis-color.currentColor πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.text-emphasis-color.transparent πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.properties.transform-origin.svg_elements Chrome5/15/2012 Chrome Android2/27/2013288
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.properties.widows πŸ“‹Chrome2/21/2013 Chrome Android2/27/20136
css.selectors.-webkit-meter-inner-element Chrome11/6/2012 Chrome Android2/27/2013113
css.selectors.-webkit-progress-bar Chrome2/21/2013 Chrome Android2/27/20136
css.selectors.-webkit-progress-inner-element Chrome11/6/2012 Chrome Android2/27/2013113
css.selectors.-webkit-progress-value Chrome2/21/2013 Chrome Android2/27/20136
css.selectors.future πŸ“‹Chrome11/6/2012 Chrome Android2/27/2013113
css.selectors.past πŸ“‹Chrome11/6/2012 Chrome Android2/27/2013113
css.types.length.vh Chrome6/26/2012 Chrome Android2/27/2013246
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 Chrome Android2/27/2013246
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 Chrome Android2/27/20136

2012/6

API First Browser Date Last Browser Date Days Notes
css.at-rules.charset πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
Firefox: Firefox 1 supported an invalid syntax where the character encoding is not between single or double quotes.Internet Explorer: From Internet Explorer 5.5 to IE 7 (inclusive), Internet Explorer supported an invalid syntax where the character encoding is not between single or double quotes.
css.at-rules.font-face πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.font-face.WOFF πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.at-rules.font-face.font-family πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
css.at-rules.font-face.font-style πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
css.at-rules.font-face.font-variant Chrome1/25/2010 Chrome Android6/27/2012884
css.at-rules.font-face.font-weight πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
css.at-rules.font-face.src πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
css.at-rules.font-face.unicode-range πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.import πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.-webkit-device-pixel-ratio πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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.-webkit-transform-3d πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.at-rules.media.aspect-ratio πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.at-rules.media.color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.device-aspect-ratio πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.device-height πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.device-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.grid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.height πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.media_features Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.monochrome πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.media.orientation πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.at-rules.media.width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.namespace πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.at-rules.page πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.at-rules.page.size πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.-webkit-border-before Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-border-horizontal-spacing Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-border-vertical-spacing Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-box-reflect Chrome1/25/2010 Chrome Android6/27/2012884
css.properties.-webkit-column-break-after Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-column-break-before Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-column-break-inside Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-locale Chrome4/27/2011 Chrome Android6/27/2012427
css.properties.-webkit-logical-height Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-logical-width Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-margin-after Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-margin-before Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-mask-box-image Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-mask-composite Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-mask-position-x Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-mask-position-y Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-max-logical-height Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-max-logical-width Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-min-logical-height Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-min-logical-width Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.-webkit-perspective-origin-x Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.-webkit-perspective-origin-y Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.-webkit-rtl-ordering Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-tap-highlight-color Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.-webkit-text-combine Chrome2/3/2011 Chrome Android6/27/2012510
css.properties.-webkit-text-decorations-in-effect Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-text-fill-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-text-security Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-text-stroke πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
css.properties.-webkit-text-stroke-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-text-stroke-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-transform-origin-x Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-transform-origin-y Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.-webkit-transform-origin-z Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.-webkit-user-drag Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline.alphabetic Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline.baseline Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline.central Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline.ideographic Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline.mathematical Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline.middle Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline.text-after-edge Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.alignment-baseline.text-before-edge Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.animation.alternate πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.alternate-reverse πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.auto πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.backwards πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.both πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.ease πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.ease-in πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.ease-in-out πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.ease-out πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.forwards πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.infinite πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.linear πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.none πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.normal πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.paused πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.reverse πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.running πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.step-end πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation.step-start πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-direction.alternate πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-direction.normal πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-fill-mode.backwards πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-fill-mode.both πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-fill-mode.forwards πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-fill-mode.none πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-iteration-count.infinite πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-name.none πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-play-state.paused πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-play-state.running πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-timing-function.ease πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-timing-function.ease-in πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-timing-function.ease-in-out πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-timing-function.ease-out πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-timing-function.linear πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-timing-function.step-end πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.animation-timing-function.step-start πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.appearance.button πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.checkbox πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.listbox πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.menulist πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.menulist-button πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Firefox: See bug 1481615.Firefox for Android: See bug 1481615.
css.properties.appearance.meter πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.radio πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.searchfield πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.textarea πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.appearance.textfield πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.backface-visibility.hidden πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.backface-visibility.visible πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.background πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.SVG_image_as_background Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.fixed πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.background.local πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.multiple_backgrounds Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.no-repeat πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.repeat πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.repeat-x πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.repeat-y πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.round πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.scroll πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.space πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-attachment πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-attachment.fixed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 Chrome Android6/27/20121294
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.background-attachment.multiple_backgrounds Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-attachment.scroll πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-clip πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Chrome: Chrome accepts alternate synonyms to its values: padding, border, and content.Chrome Android: Chrome Android accepts alternate synonyms to its values: padding, border, and content.Edge: Since Edge 79, accepts alternate synonyms to its values: padding, border, and content.Firefox: Used the -moz-background-clip: padding | border syntax.Internet Explorer: In IE 7 and IE 8 of Internet Explorer, this property always behaved like background-clip: padding-box when overflow was hidden, auto, or scroll.Quest Browser: Quest Browser accepts alternate synonyms to its values: padding, border, and content.Opera: Opera accepts alternate synonyms to its values: padding, border, and content.Opera Android: Opera accepts alternate synonyms to its values: padding, border, and content.Safari: Safari accepts alternate synonyms to its values: padding, border, and content.Safari on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.Samsung Internet: Samsung Internet accepts alternate synonyms to its values: padding, border, and content.WebView Android: WebView Android accepts alternate synonyms to its values: padding, border, and content.WebView on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.
css.properties.background-clip.border-box πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-clip.content-box πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-image πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Firefox: If the browser.display.use_document_colors user preference in about:config is set to false, background images will not be displayed.Firefox for Android: If the browser.display.use_document_colors user preference in about:config is set to false, background images will not be displayed.
css.properties.background-image.gradients πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Chrome: Some versions support only experimental gradients prefixed with -webkit.Chrome Android: Some versions support only experimental gradients prefixed with -webkit.Firefox: Some versions support only experimental gradients prefixed with -moz.Firefox for Android: Some versions support only experimental gradients prefixed with -moz.Quest Browser: Some versions support only experimental gradients prefixed with -webkit.Opera: Some versions support only experimental gradients prefixed with -o.Opera Android: Some versions support only experimental gradients prefixed with -webkit.Safari: Some versions support only experimental gradients prefixed with -webkit.Safari on iOS: Some versions support only experimental gradients prefixed with -webkit.Samsung Internet: Some versions support only experimental gradients prefixed with -webkit.WebView Android: Some versions support only experimental gradients prefixed with -webkit.WebView on iOS: Some versions support only experimental gradients prefixed with -webkit.
css.properties.background-image.multiple_backgrounds Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-image.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-image.svg_images Chrome12/2/2010 Chrome Android6/27/2012573
Safari: Support of SVG in CSS background is incomplete.Safari on iOS: Support of SVG in CSS background is incomplete.WebView on iOS: Support of SVG in CSS background is incomplete.
css.properties.background-origin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-origin.content-box πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position.bottom πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position.center πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position.left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position.multiple_backgrounds Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position.right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position.top πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position-x πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-position-y πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-repeat πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-repeat.2-value Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.background-repeat.multiple_backgrounds Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-repeat.no-repeat πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-repeat.repeat πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-repeat.repeat-x πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-repeat.repeat-y πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-size πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
Chrome: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Chrome Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Quest Browser: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Opera Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera Android: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Safari: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Safari on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Samsung Internet: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.
css.properties.background-size.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.background-size.contain πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.background-size.cover πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.properties.baseline-shift πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.baseline-shift.baseline πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.baseline-shift.sub πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.baseline-shift.super πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.block-size.auto πŸ“‹Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.border πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-color.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-left-radius πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-left-radius.elliptical_corners Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-left-radius.percentages Chrome1/25/2010 Chrome Android6/27/2012884
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 Chrome Android6/27/2012884
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-right-radius.elliptical_corners Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-right-radius.percentages Chrome1/25/2010 Chrome Android6/27/2012884
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-style πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-style.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-width.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-width.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-bottom-width.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-collapse πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-collapse.collapse Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-collapse.separate Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-color.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-image πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
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 Chrome Android6/27/2012197
css.properties.border-image.gradient Chrome10/19/2010 Chrome Android6/27/2012617
css.properties.border-image.none πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.border-image.optional_border_image_slice Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.border-image.repeat πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.border-image.round πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.border-image.space πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.border-image.stretch πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.border-image-outset πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.border-image-repeat πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.border-image-repeat.repeat πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.border-image-repeat.stretch πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.border-image-slice πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
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 Chrome Android6/27/2012246
css.properties.border-image-source.none πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.border-image-width πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
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 Chrome Android6/27/2012197
css.properties.border-left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-color.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-style.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-width.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-width.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-left-width.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-radius πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
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 Chrome Android6/27/2012884
css.properties.border-radius.elliptical_borders Chrome12/11/2008 Chrome Android6/27/20121294
Chrome: Before Chrome 4, the slash / notation is unsupported. If two values are specified, then an elliptical border is drawn on all four corners. -webkit-border-radius: 40px 10px; is equivalent to border-radius: 40px / 10px;.Safari: Before Safari 5, the slash / notation is unsupported. If two values are specified, then an elliptical border is drawn on all four corners. -webkit-border-radius: 40px 10px; is equivalent to border-radius: 40px / 10px;.
css.properties.border-radius.percentages Chrome12/2/2010 Chrome Android6/27/2012573
Firefox: Before Firefox 4, <percentage> values are implemented in a non-standard way. Both horizontal and vertical radii were relative to the width of the border box.Opera: Before Opera 11.5, the implementation of <percentage> values was buggy.
css.properties.border-right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-color.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-style.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-width.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-width.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-right-width.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-spacing πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-style.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-color.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-left-radius πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-left-radius.elliptical_corners Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-left-radius.percentages Chrome1/25/2010 Chrome Android6/27/2012884
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 Chrome Android6/27/2012884
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-right-radius.elliptical_corners Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-right-radius.percentages Chrome1/25/2010 Chrome Android6/27/2012884
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-style πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-style.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-width.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-width.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-top-width.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-width.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-width.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.border-width.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.bottom πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-align Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-direction Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-flex Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-ordinal-group Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-orient Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-pack Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-shadow πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
Chrome: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Chrome Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Firefox: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Firefox for Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Internet Explorer: To use box-shadow in Internet Explorer 9 or later, you must set border-collapse to separate.Internet Explorer: Since version 5.5, Internet Explorer supports Microsoft's DropShadow and Shadow Filter. You can use this proprietary extension to cast a drop shadow (though the syntax and the effect are different from CSS3)Quest Browser: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Opera: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Opera Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Safari: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Safari on iOS: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Samsung Internet: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.WebView Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.WebView on iOS: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.
css.properties.box-shadow.inset Chrome12/11/2008 Chrome Android6/27/20121294
Internet Explorer: inset must be the last keyword in the declaration.
css.properties.box-shadow.multiple_shadows Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-shadow.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-shadow.spread_radius Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-sizing πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
Chrome: box-sizing is not respected when the height is calculated from window.getComputedStyle().Chrome Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox: Before Firefox 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox for Android: Before Firefox for Android 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Internet Explorer: box-sizing is not respected when the height is calculated from window.getComputedStyle().Quest Browser: box-sizing is not respected when the height is calculated from window.getComputedStyle().Opera Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Samsung Internet: box-sizing is not respected when the height is calculated from window.getComputedStyle().WebView Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().
css.properties.box-sizing.border-box πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.box-sizing.content-box πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.caption-side πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.caption-side.bottom Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.caption-side.top Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.clear πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.clear.both πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.clear.left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.clear.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.clear.right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.clip πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.clip-rule πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.clip-rule.evenodd πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.clip-rule.nonzero πŸ“‹Chrome10/25/2011 Chrome Android6/27/2012246
css.properties.color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-interpolation πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-interpolation.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-interpolation.sRGB πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-interpolation-filters πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-interpolation-filters.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-rendering Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-rendering.auto Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-rendering.optimizeQuality Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.color-rendering.optimizeSpeed Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-count.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-gap πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-gap.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-color.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-style.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-width.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-width.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-rule-width.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.column-span.all πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.column-span.none πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.column-width.auto Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.content πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.content.close-quote πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.content.no-close-quote πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.content.no-open-quote πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.content.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.content.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.content.open-quote πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.content.url πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.counter-increment πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.counter-increment.none πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.counter-reset πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.counter-reset.none πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.cursor πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.cursor.cell πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.cursor.col-resize πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.none πŸ“‹Chrome5/25/2010 Chrome Android6/27/2012764
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.cursor.url Chrome12/11/2008 Chrome Android6/27/20121294
Firefox: Firefox 4 added macOS support.
css.properties.cursor.url_positioning_syntax Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.direction πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.direction.ltr πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.direction.rtl πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.display πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.block πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.inline πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.inline-block Chrome12/11/2008 Chrome Android6/27/20121294
Internet Explorer: Until Internet Explorer 8, inline-block is only for natural inline elements.
css.properties.display.inline-table Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.list-item πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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.none.option_is_hidden Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table-caption Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table-cell Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table-column Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table-column-group Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table-footer-group Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table-header-group Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table-row Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.display.table-row-group Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.dominant-baseline πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.dominant-baseline.alphabetic πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.dominant-baseline.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.dominant-baseline.central πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.dominant-baseline.hanging πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.dominant-baseline.ideographic πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.dominant-baseline.mathematical πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.dominant-baseline.middle πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.empty-cells πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.empty-cells.hide πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.empty-cells.show πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.fill πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.fill.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.fill-opacity πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.fill-rule πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.fill-rule.evenodd πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.fill-rule.nonzero πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.filter.none πŸ“‹Chrome3/28/2012 Chrome Android6/27/201291
css.properties.float πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.float.left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.float.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.float.right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.flood-color πŸ“‹Chrome5/25/2010 Chrome Android6/27/2012764
css.properties.flood-color.currentColor πŸ“‹Chrome5/25/2010 Chrome Android6/27/2012764
css.properties.flood-color.transparent πŸ“‹Chrome5/25/2010 Chrome Android6/27/2012764
css.properties.flood-opacity πŸ“‹Chrome5/25/2010 Chrome Android6/27/2012764
css.properties.font πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font.caption Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font.icon Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font.menu Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font.message-box Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font.small-caption Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font.status-bar Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family.fangsong πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family.fantasy πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family.kai πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family.khmer-mul πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family.monospace πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family.nastaliq πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family.sans-serif πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-family.serif πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-feature-settings.normal πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.font-size πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-smooth Chrome5/25/2010 Chrome Android6/27/2012764
Firefox: Only works on macOS.
css.properties.font-style πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-style.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-style.oblique πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-variant πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Internet Explorer: Only supports the small-caps and normal keywords.
css.properties.font-variant.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.font-weight πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.font-weight.bold πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.font-weight.bolder πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.font-weight.lighter πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.font-weight.normal πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.height πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.height.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.hyphenate-character.auto πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.image-rendering πŸ“‹Chrome8/2/2011 Chrome Android6/27/2012330
css.properties.image-rendering.auto πŸ“‹Chrome8/2/2011 Chrome Android6/27/2012330
css.properties.image-rendering.crisp-edges πŸ“‹Chrome8/2/2011 Chrome Android6/27/2012330
css.properties.inline-size.auto πŸ“‹Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.left.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.letter-spacing πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.letter-spacing.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.letter-spacing.svg_elements Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.lighting-color πŸ“‹Chrome5/25/2010 Chrome Android6/27/2012764
css.properties.lighting-color.currentColor πŸ“‹Chrome5/25/2010 Chrome Android6/27/2012764
css.properties.lighting-color.transparent πŸ“‹Chrome5/25/2010 Chrome Android6/27/2012764
css.properties.line-break.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.line-clamp πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
Safari: Accidental exposure.Safari on iOS: Accidental exposure.WebView on iOS: Accidental exposure.
css.properties.line-height πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.line-height.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style.inside πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style.outside πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-image πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-position πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-position.outside πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.arabic-indic πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.armenian πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.bengali πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.cambodian πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.circle πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.cjk-earthly-branch πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.cjk-heavenly-stem πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.cjk-ideographic πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Opera: Until version 15, only decimal numbers display.Opera Android: Until version 15, only decimal numbers display.
css.properties.list-style-type.decimal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.decimal-leading-zero πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.devanagari πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.disc πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.ethiopic-halehame-ti-er Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.ethiopic-halehame-ti-et Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.georgian πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.gujarati πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.gurmukhi πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.hangul Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.hangul-consonant Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.hebrew πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.hiragana πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.hiragana-iroha πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.kannada πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.katakana πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.katakana-iroha πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.khmer πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.lao πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.lower-alpha πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.lower-armenian πŸ“‹Chrome8/2/2011 Chrome Android6/27/2012330
css.properties.list-style-type.lower-greek πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.lower-latin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.lower-roman πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.malayalam πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.mongolian πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.myanmar πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.oriya πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.persian πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.square πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.telugu πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.thai πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.tibetan πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.list-style-type.upper-alpha πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.upper-armenian πŸ“‹Chrome8/2/2011 Chrome Android6/27/2012330
css.properties.list-style-type.upper-latin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.upper-roman πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.list-style-type.urdu Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.margin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.margin.auto Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.margin-bottom.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.margin-left.auto Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.margin-right.auto Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.margin-top.auto Chrome12/11/2008 Chrome Android6/27/20121294
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.marker πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.marker.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.marker-end πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.marker-end.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.marker-mid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.marker-mid.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.marker-start πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.marker-start.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-border πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-border-outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-border-repeat πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-border-slice πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-border-source πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-border-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-clip.border Chrome12/11/2008 Chrome Android6/27/20121294
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 Chrome Android6/27/20121294
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 Chrome Android6/27/20121294
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 Chrome Android6/27/20121294
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 Chrome Android6/27/20121294
css.properties.mask-image.svg_masks Chrome12/2/2010 Chrome Android6/27/2012573
css.properties.mask-origin.border Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-origin.content Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.mask-origin.padding Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.max-height πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Firefox: CSS 2.1 leaves the behavior of max-height with table undefined. Firefox supports applying max-height to table elements.Opera: CSS 2.1 leaves the behavior of max-height with table undefined. Opera supports applying max-height to table elements.
css.properties.max-height.none πŸ“‹Chrome3/28/2012 Chrome Android6/27/201291
css.properties.max-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.min-height πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.medium πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-color.transparent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-offset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.dashed πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.dotted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.double πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.groove πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.inset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.outset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.ridge πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-style.solid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-width.thick πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.outline-width.thin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow.hidden πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow.scroll πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow.visible πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-wrap.break-word πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-wrap.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-x πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-x.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-x.scroll πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-x.visible πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-y πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-y.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-y.scroll πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.overflow-y.visible πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.padding πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.padding-bottom πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.padding-left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.padding-right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.padding-top πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-after πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-after.always πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-after.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-after.avoid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-after.left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-after.right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-before πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-before.always πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-before.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-before.avoid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-before.left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-before.right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-inside πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-inside.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.page-break-inside.avoid πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Firefox: Until Firefox 25, page-break-inside: avoid did not work with the height of a block.Firefox for Android: Until Firefox for Android 25, page-break-inside: avoid did not work with the height of a block.
css.properties.perspective.none πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.perspective-origin.bottom πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.perspective-origin.center πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.perspective-origin.left πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.perspective-origin.right πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.perspective-origin.top πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.pointer-events πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.pointer-events.all πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.pointer-events.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.pointer-events.fill πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.pointer-events.html_elements Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.pointer-events.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.pointer-events.painted πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.pointer-events.stroke πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.pointer-events.visible πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.position πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.position.absolute πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.position.static πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.quotes πŸ“‹Chrome4/27/2011 Chrome Android6/27/2012427
css.properties.quotes.none πŸ“‹Chrome4/27/2011 Chrome Android6/27/2012427
css.properties.resize πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Firefox for Android: The property is recognized, but has no effect. See bug 1776834.Safari on iOS: The property is recognized, but has no effect. See bug 211994.WebView on iOS: The property is recognized, but has no effect. See bug 211994.
css.properties.resize.block_level_support Chrome1/25/2010 Chrome Android6/27/2012884
Firefox: resize doesn't have any effect on <iframe>. See bug 680823)
css.properties.resize.both πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.resize.horizontal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.resize.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.resize.vertical πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.right.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.shape-rendering πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.shape-rendering.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stop-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stop-opacity πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-dasharray πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-dasharray.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-dashoffset πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-linecap πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-linecap.butt πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-linecap.round πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-linecap.square πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-linejoin πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-linejoin.bevel πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-linejoin.miter πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-linejoin.round πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-miterlimit πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-opacity πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.stroke-width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.table-layout πŸ“‹Chrome9/16/2011 Chrome Android6/27/2012285
css.properties.table-layout.auto πŸ“‹Chrome9/16/2011 Chrome Android6/27/2012285
css.properties.table-layout.fixed πŸ“‹Chrome9/16/2011 Chrome Android6/27/2012285
css.properties.text-align πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-align.center πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-align.end πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-align.justify πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-align.left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-align.match-parent πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
css.properties.text-align.right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-align.start πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-anchor πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-anchor.end πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-anchor.middle πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-anchor.start πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-decoration πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-decoration.line-through πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-decoration.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-decoration.overline πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-decoration.underline πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-indent πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-orientation.sideways πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.text-orientation.upright πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.text-overflow πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-overflow.ellipsis πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-rendering πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
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 Chrome Android6/27/2012884
Chrome: Chrome treats auto as optimizeSpeed.Chrome Android: Chrome Android treats auto as optimizeSpeed.Edge: Edge treats auto as optimizeSpeed.Firefox: If the font size is 20 pixels or higher, Firefox treats auto as optimizeLegibility. For smaller text, Firefox treats auto as optimizeSpeed. The 20-pixel threshold can be changed with the browser.display.auto_quality_min_font_size preference.Firefox for Android: If the font size is 20 pixels or higher, Firefox treats auto as optimizeLegibility. For smaller text, Firefox treats auto as optimizeSpeed. The 20-pixel threshold can be changed with the browser.display.auto_quality_min_font_size preference.Quest Browser: Quest Browser treats auto as optimizeSpeed.Opera: Opera treats auto as optimizeSpeed.Opera Android: Opera Android treats auto as optimizeSpeed.Safari: Safari treats auto as optimizeSpeed. See bug 41363.Safari on iOS: Safari on iOS treats auto as optimizeSpeed. See bug 41363.Samsung Internet: Samsung Internet treats auto as optimizeSpeed.WebView Android: WebView Android treats auto as optimizeSpeed.WebView on iOS: WebView on iOS treats auto as optimizeSpeed. See bug 41363.
css.properties.text-rendering.geometricPrecision Chrome8/2/2011 Chrome Android6/27/2012330
Chrome: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Chrome Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Edge: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Firefox: Firefox treats geometricPrecision the same as optimizeLegibility.Firefox for Android: Firefox treats geometricPrecision the same as optimizeLegibility.Quest Browser: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Opera: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Opera Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Samsung Internet: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.WebView Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.
css.properties.text-shadow πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
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 πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.text-transform πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-transform.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-transform.uppercase πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.text-transform.uppercase_eszett Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.top πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transform.3d Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.transform.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transform-origin.bottom πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transform-origin.center πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transform-origin.left πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transform-origin.right πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transform-origin.three_value_syntax Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.transform-origin.top πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transform-style.flat πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.transform-style.preserve-3d πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.properties.transition.all πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition.ease πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition.ease-in πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition.ease-in-out πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition.ease-out πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition.linear πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition.step-end πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition.step-start πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-property.IDENT_value Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-property.all πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-property.none πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-timing-function.ease πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-timing-function.ease-in πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-timing-function.ease-in-out πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-timing-function.ease-out πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-timing-function.linear πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-timing-function.step-end πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.transition-timing-function.step-start πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.unicode-bidi πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.unicode-bidi.bidi-override πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.unicode-bidi.embed πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.unicode-bidi.normal πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.properties.user-modify Chrome12/11/2008 Chrome Android6/27/20121294
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 Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.user-select.auto Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.user-select.none Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.user-select.text Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vector-effect πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.vector-effect.non-scaling-stroke πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.vector-effect.none πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.properties.vertical-align πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vertical-align.baseline πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vertical-align.bottom πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vertical-align.middle πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vertical-align.sub πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vertical-align.super πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vertical-align.text-bottom πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vertical-align.text-top πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.vertical-align.top πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.visibility πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.visibility.visible πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.white-space πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.white-space.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.white-space.nowrap πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.white-space.pre πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.white-space.pre-line πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.white-space.pre-wrap πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.width πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.width.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.word-break πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.word-break.break-word πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.word-break.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.word-spacing πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.word-spacing.normal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.word-spacing.svg_elements Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.z-index πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.z-index.auto πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.z-index.negative_values Chrome12/11/2008 Chrome Android6/27/20121294
css.properties.zoom πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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-inner-spin-button Chrome9/2/2010 Chrome Android6/27/2012664
css.selectors.-webkit-meter-bar Chrome6/7/2011 Chrome Android6/27/2012386
css.selectors.-webkit-meter-even-less-good-value Chrome6/7/2011 Chrome Android6/27/2012386
css.selectors.-webkit-meter-optimum-value Chrome6/7/2011 Chrome Android6/27/2012386
css.selectors.-webkit-meter-suboptimum-value Chrome6/7/2011 Chrome Android6/27/2012386
css.selectors.-webkit-resizer Chrome5/21/2009 Chrome Android6/27/20121133
css.selectors.-webkit-scrollbar Chrome5/21/2009 Chrome Android6/27/20121133
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 Chrome Android6/27/20121133
css.selectors.-webkit-scrollbar-corner Chrome5/21/2009 Chrome Android6/27/20121133
css.selectors.-webkit-scrollbar-thumb Chrome5/21/2009 Chrome Android6/27/20121133
css.selectors.-webkit-scrollbar-track Chrome5/21/2009 Chrome Android6/27/20121133
css.selectors.-webkit-scrollbar-track-piece Chrome5/21/2009 Chrome Android6/27/20121133
css.selectors.-webkit-search-cancel-button Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.-webkit-search-results-button Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.active πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.active.non_a_elements Chrome12/11/2008 Chrome Android6/27/20121294
Safari on iOS: By default, Safari on iOS does not use the :active state unless there is a touchstart event handler on the relevant element or on the <body> element.WebView on iOS: By default, WebView on iOS does not use the :active state unless there is a touchstart event handler on the relevant element or on the <body> element.
css.selectors.after πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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.attribute πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.before πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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.checked πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.class πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.default πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
css.selectors.descendant πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.disabled πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.enabled πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.first πŸ“‹Chrome3/28/2012 Chrome Android6/27/201291
css.selectors.first-child πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
Internet Explorer: Internet Explorer 7 doesn't update :first-child styles when elements are added dynamically.Internet Explorer: In Internet Explorer 8, if an element is inserted dynamically by clicking on a link, then the :first-child style isn't applied until the link loses focus.
css.selectors.first-letter πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.first-line πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.hover πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.hover.all_elements Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.in-range πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.indeterminate.checkbox Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.indeterminate.progress Chrome9/2/2010 Chrome Android6/27/2012664
css.selectors.invalid πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
css.selectors.lang πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.last-child πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.last-of-type πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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.left πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.selectors.link πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.link.not_match_link Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.list πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.namespace πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.next-sibling πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.nth-child πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Opera: Before Opera 15, Opera does not handle dynamically inserted elements for :nth-child().Opera Android: Before Opera 15, Opera does not handle dynamically inserted elements for :nth-child().
css.selectors.nth-last-child πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
css.selectors.nth-last-of-type πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.nth-of-type πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.only-child πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.selectors.only-of-type πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.optional πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
css.selectors.out-of-range πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
css.selectors.read-only πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.read-write πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.required πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
css.selectors.right πŸ“‹Chrome9/2/2010 Chrome Android6/27/2012664
css.selectors.root πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.selection πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.subsequent-sibling πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.target πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.type πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.type.namespaces Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.universal πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.universal.namespaces Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.valid πŸ“‹Chrome3/8/2011 Chrome Android6/27/2012477
css.selectors.visited πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.visited.not_match_link Chrome12/11/2008 Chrome Android6/27/20121294
css.selectors.visited.privacy_measures Chrome9/2/2010 Chrome Android6/27/2012664
css.types.angle πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.types.angle.deg Chrome5/21/2009 Chrome Android6/27/20121133
css.types.angle.grad Chrome5/21/2009 Chrome Android6/27/20121133
css.types.angle.rad Chrome5/21/2009 Chrome Android6/27/20121133
css.types.angle.turn Chrome5/21/2009 Chrome Android6/27/20121133
css.types.angle-percentage πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.types.attr πŸ“‹Chrome5/21/2009 Chrome Android6/27/20121133
css.types.color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.color.currentcolor πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.color.hsl πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.color.named-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.color.rgb πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.color.rgb_hexadecimal_notation πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.color.system-color πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.color.transparent Chrome12/11/2008 Chrome Android6/27/20121294
css.types.counter πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.counters πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.dimension πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.easing-function πŸ“‹Chrome1/25/2010 Chrome Android6/27/2012884
css.types.easing-function.cubic-bezier πŸ“‹Chrome12/13/2011 Chrome Android6/27/2012197
css.types.easing-function.steps πŸ“‹Chrome12/2/2010 Chrome Android6/27/2012573
css.types.global_keywords Chrome12/11/2008 Chrome Android6/27/20121294
css.types.global_keywords.inherit πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.global_keywords.initial πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.image πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.image.cross-fade πŸ“‹Chrome2/8/2012 Chrome Android6/27/2012140
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.
css.types.integer πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.length πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.length.em Chrome12/11/2008 Chrome Android6/27/20121294
css.types.length.ex Chrome12/11/2008 Chrome Android6/27/20121294
css.types.length.rem Chrome1/25/2010 Chrome Android6/27/2012884
css.types.length-percentage πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.line-style πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.number πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.overflow πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.position πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.position.keyword_value_syntax Chrome12/11/2008 Chrome Android6/27/20121294
css.types.ratio πŸ“‹Chrome9/15/2009 Chrome Android6/27/20121016
css.types.shape πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.shape.rect Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.string.unicode_escaped_characters Chrome12/11/2008 Chrome Android6/27/20121294
css.types.time πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
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 πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Firefox: Before Firefox 16, the translation values of matrix() could be <length>s, in addition to the standard <number>.
css.types.transform-function.matrix3d πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
Firefox: Before Firefox 16, the translation values of matrix3d() could be <length>s, in addition to the standard <number>.
css.types.transform-function.perspective πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.transform-function.rotate πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.rotate3d πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.transform-function.rotateX πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.transform-function.rotateY πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.transform-function.rotateZ πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.transform-function.scale πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.scale3d πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.transform-function.scaleX πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.scaleY πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.scaleZ πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.transform-function.skew πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
Firefox: Firefox 14 removed experimental support for skew(), but it was reintroduced in Firefox 15.
css.types.transform-function.skewX πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.skewY πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.translate πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.translate3d πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.transform-function.translateX πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.translateY πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294
css.types.transform-function.translateZ πŸ“‹Chrome6/7/2011 Chrome Android6/27/2012386
css.types.url πŸ“‹Chrome12/11/2008 Chrome Android6/27/20121294