"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
Below is a list of features that are in Chrome and Edge, ordered reverse chronologically by when they became stable (i.e, available in the last browser).
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.animation-trigger π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.animation-trigger.none π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.text-indent.each-line π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.text-indent.hanging π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger.auto π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger.none π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger.normal π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger-name π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger-name.none π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger-source π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger-source.auto π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.timeline-trigger-source.none π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.trigger-scope π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.trigger-scope.all π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 | |
| css.properties.trigger-scope.none π | Chrome | 3/10/2026 | Edge | 3/12/2026 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.column-height π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.column-height.auto π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.column-wrap π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.column-wrap.auto π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.column-wrap.nowrap π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.column-wrap.wrap π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.columns.column-height π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.text-justify π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | 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 π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.text-justify.inter-character π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.text-justify.inter-word π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.text-justify.none π | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 | |
| css.properties.word-spacing.percentages | Chrome | 2/10/2026 | Edge | 2/14/2026 | 4 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.container.scroll-state_queries.scrolled π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.background-position-x.side-relative_values | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.background-position-y.side-relative_values | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.caret-shape π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.caret-shape.auto π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.caret-shape.bar π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.caret-shape.block π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.caret-shape.underscore π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.position-anchor.none | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.position-area.block-end π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.position-try.flip-y π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.position-try.self-x-end π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.position-try-fallbacks.flip-y π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.properties.position-try-fallbacks.self-x-end π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | 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 π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 | |
| css.types.color.color.colorSpace_parameter_accepts_display-p3-linear_value π | Chrome | 1/13/2026 | Edge | 1/21/2026 | 8 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.container.anchor_position_queries π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.at-rules.container.anchor_position_queries.fallback π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.at-rules.container.anchor_position_queries.fallback.any_value π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.container-type.anchored π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.font-language-override π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.font-language-override.normal π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-area.span-self-x-end π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-area.span-self-x-start π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-area.span-self-y-end π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-area.span-self-y-start π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-try.span-self-x-end π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-try.span-self-x-start π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-try.span-self-y-end π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-try.span-self-y-start π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-try-fallbacks.span-self-x-end π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-try-fallbacks.span-self-x-start π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-try-fallbacks.span-self-y-end π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.properties.position-try-fallbacks.span-self-y-start π | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 | |
| css.selectors.nesting.at-scope | Chrome | 12/2/2025 | Edge | 12/5/2025 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.container.style_queries_for_custom_properties.range_syntax π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.properties.interest-delay π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.properties.interest-delay.normal π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.properties.interest-delay-end π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.properties.interest-delay-end.normal π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.properties.interest-delay-start π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.properties.interest-delay-start.normal π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.selectors.interest-source π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.selectors.interest-target π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.selectors.target-after π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.selectors.target-before π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 | |
| css.types.if.style.range_syntax π | Chrome | 10/28/2025 | Edge | 10/31/2025 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.font-face.font-feature-settings π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | 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 π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.caret-animation π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.caret-animation.auto π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.caret-animation.manual π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.scroll-target-group π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.scroll-target-group.auto π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.scroll-target-group.none π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.text-autospace π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.text-autospace.no-autospace π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.text-autospace.normal π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.view-transition-group π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.view-transition-group.contain | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.view-transition-group.nearest | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.properties.view-transition-group.normal | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.selectors.view-transition-group-children π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.types.calc.typed_division_produces_unitless_number π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 | |
| css.types.sign.typed_division_produces_unitless_number π | Chrome | 9/2/2025 | Edge | 9/5/2025 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.function π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.at-rules.function.result π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-end-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-end-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-end-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-end-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-end-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-end-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-end-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-start-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-start-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-start-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-start-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-start-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-start-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-block-start-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-left-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-left-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-left-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-left-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-left-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-left-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-left-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-right-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-right-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-right-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-right-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-right-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-right-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-right-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-bottom-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-end-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-end-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-end-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-end-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-end-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-end-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-end-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-start-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-start-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-start-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-start-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-start-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-start-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-end-start-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-end-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-end-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-end-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-end-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-end-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-end-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-end-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-start-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-start-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-start-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-start-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-start-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-start-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-inline-start-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-left-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-left-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-left-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-left-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-left-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-left-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-left-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-right-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-right-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-right-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-right-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-right-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-right-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-right-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-end-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-end-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-end-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-end-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-end-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-end-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-end-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-start-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-start-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-start-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-start-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-start-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-start-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-start-start-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-left-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-left-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-left-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-left-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-left-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-left-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-left-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-right-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-right-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-right-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-right-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-right-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-right-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-right-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-shape π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-shape.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-shape.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-shape.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-shape.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-shape.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.properties.corner-top-shape.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.corner-shape-value π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.corner-shape-value.bevel π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.corner-shape-value.notch π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.corner-shape-value.round π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.corner-shape-value.scoop π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.corner-shape-value.square π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.corner-shape-value.squircle π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.corner-shape-value.superellipse π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.dashed-function π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.superellipse π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 | |
| css.types.type π | Chrome | 8/5/2025 | Edge | 8/7/2025 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.horizontal-viewport-segments π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.at-rules.media.vertical-viewport-segments π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.block-size.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.flex.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.flex-basis.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.height.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.inline-size.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.max-block-size.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.max-height.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.max-inline-size.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.max-width.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.min-block-size.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.min-height.stretch | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.min-inline-size.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.min-width.stretch | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.properties.width.stretch π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.abs π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.env.viewport-segment-bottom π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.env.viewport-segment-height π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.env.viewport-segment-left π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.env.viewport-segment-right π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.env.viewport-segment-top π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.env.viewport-segment-width π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.progress π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.sibling-count π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.sibling-index π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 | |
| css.types.sign π | Chrome | 6/24/2025 | Edge | 6/26/2025 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.reading-flow π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.reading-flow.flex-flow π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.reading-flow.flex-visual π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.reading-flow.grid-columns π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.reading-flow.grid-order π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.reading-flow.grid-rows π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.reading-flow.normal π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.reading-flow.source-order π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.reading-order π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.view-transition-name.match-element π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.types.if π | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.types.if.style | Chrome | 5/27/2025 | Edge | 5/29/2025 | 2 | |
| css.properties.dynamic-range-limit π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 | |
| css.properties.dynamic-range-limit.constrained π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 | |
| css.properties.dynamic-range-limit.dynamic-range-limit-mix_values π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 | |
| css.properties.dynamic-range-limit.no-limit π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 | |
| css.properties.dynamic-range-limit.standard π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 | |
| css.properties.print-color-adjust π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 | 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 π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 | |
| css.properties.print-color-adjust.exact π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 | |
| css.types.dynamic-range-limit-mix π | Chrome | 4/29/2025 | Edge | 5/1/2025 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.appearance.base-select π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.interactivity π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.interactivity.auto π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.interactivity.inert π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-block π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-block.auto π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-block.clip π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-block.hidden π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-block.overlay | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-block.scroll π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-block.visible π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-inline π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-inline.auto π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-inline.clip π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-inline.hidden π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-inline.overlay π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-inline.scroll π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.overflow-inline.visible π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.scroll-marker-group π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.scroll-marker-group.after π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.scroll-marker-group.before π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.properties.scroll-marker-group.none π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.after.nested_marker π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.before.nested_marker π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.column π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.column.nested_scroll-marker | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.picker π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.block-end π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.block-start π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.down π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.inline-end π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.inline-start π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.left π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.right π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.star π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-button.up π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-marker π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.scroll-marker-group π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.selectors.target-current π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.types.basic-shape.shape π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.types.gradient.conic-gradient.single_color_stop π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.types.gradient.linear-gradient.single_color_stop π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.types.gradient.radial-gradient.single_color_stop π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.types.gradient.repeating-conic-gradient.single_color_stop π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.types.gradient.repeating-linear-gradient.single_color_stop π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 | |
| css.types.gradient.repeating-radial-gradient.single_color_stop π | Chrome | 4/1/2025 | Edge | 4/4/2025 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.container.scroll-state_queries π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.at-rules.container.scroll-state_queries.scrollable π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.at-rules.container.scroll-state_queries.snapped π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.at-rules.container.scroll-state_queries.stuck π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.container-type.scroll-state π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.scroll-initial-target π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.scroll-initial-target.nearest π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.scroll-initial-target.none π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box.auto π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box.none π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box.normal π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box.text π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box.trim-both π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box.trim-end π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box.trim-start π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box-edge π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box-edge.auto π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box-edge.text π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box-trim π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box-trim.none π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box-trim.trim-both π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box-trim.trim-end π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.properties.text-box-trim.trim-start π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.selectors.checkmark π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.selectors.open π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | 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 π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.declaration-value π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.angle π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.color π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.custom-ident π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.ident π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.image π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.integer π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.length π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.length-percentage π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.number π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.percentage π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.resolution π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.string π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.time π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.transform-function π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.attr.type_function.url π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.text-edge π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.text-edge.alphabetic π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.text-edge.cap π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.text-edge.ex π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 | |
| css.types.text-edge.text π | Chrome | 2/4/2025 | Edge | 2/6/2025 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.device-posture π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.bottom.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.inset.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.inset-block.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.inset-block-end.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.inset-block-start.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.inset-inline.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.inset-inline-end.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.inset-inline-start.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.left.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-block.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-block-end.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-block-start.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-bottom.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-inline.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-inline-end.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-inline-start.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-left.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-right.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.margin-top.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.right.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.top.anchor-size π | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.writing-mode.sideways-lr | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.properties.writing-mode.sideways-rl | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 | |
| css.types.anchor-size.inset_margin | Chrome | 1/14/2025 | Edge | 1/17/2025 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.page.bottom-center π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.bottom-left π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.bottom-left-corner π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.bottom-right π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.bottom-right-corner π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.left-bottom π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.left-middle π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.left-top π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.right-bottom π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.right-middle π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.right-top π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.top-center π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.top-left π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.top-left-corner π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.top-right π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.at-rules.page.top-right-corner π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.properties.anchor-scope π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.properties.anchor-scope.all π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.properties.anchor-scope.none π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.properties.font-variant-emoji π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.properties.font-variant-emoji.emoji π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.properties.font-variant-emoji.normal π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.properties.font-variant-emoji.text π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.properties.font-variant-emoji.unicode π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | |
| css.selectors.details-content π | Chrome | 11/12/2024 | Edge | 11/14/2024 | 2 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.box-decoration-break π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | 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 π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | 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 π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | 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 π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.justify-self.block_context π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap.auto π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap.stable π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap-mode π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap-mode.nowrap | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap-mode.wrap | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap-style π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap-style.auto π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap-style.balance π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap-style.pretty π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 | |
| css.properties.text-wrap-style.stable π | Chrome | 10/15/2024 | Edge | 10/17/2024 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.prefers-color-scheme.respects-inherited-scheme | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | 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 π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.interpolate-size π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.interpolate-size.allow-keywords π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.interpolate-size.numeric-only π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.center π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.none π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-bottom π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-left π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-right π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-self-block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-self-block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-self-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-self-inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-self-inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-self-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-top π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-x-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-x-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-y-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.span-y-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-area.start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.bottom π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.center π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.left π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.right π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.self-block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.self-block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.self-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.self-inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.self-inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.self-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-all π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-bottom π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-left π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-right π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-self-block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-self-block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-self-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-self-inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-self-inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-self-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-top π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-x-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-x-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-y-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.span-y-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.top π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.x-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.x-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.y-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try.y-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.bottom π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.center π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.left π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.right π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.self-block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.self-block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.self-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.self-inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.self-inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.self-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-all π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-bottom π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-left π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-right π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-self-block-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-self-block-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-self-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-self-inline-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-self-inline-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-self-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-top π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-x-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-x-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-y-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.span-y-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.top π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.x-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.x-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.y-end π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.properties.position-try-fallbacks.y-start π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 | |
| css.types.calc-size π | Chrome | 9/17/2024 | Edge | 9/19/2024 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.position-try-fallbacks π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | |
| css.properties.position-try-fallbacks.flip-block π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | |
| css.properties.position-try-fallbacks.flip-inline π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | |
| css.properties.position-try-fallbacks.flip-start π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | |
| css.properties.position-try-fallbacks.none π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | |
| css.properties.position-try-fallbacks.position-area π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | 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 π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | 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 π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | |
| css.properties.ruby-align.space-around π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | |
| css.properties.ruby-align.space-between π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 | |
| css.properties.ruby-align.start π | Chrome | 8/20/2024 | Edge | 8/22/2024 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.font-size-adjust π | Chrome | 7/23/2024 | Edge | 7/25/2024 | 2 | 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 π | Chrome | 7/23/2024 | Edge | 7/25/2024 | 2 | |
| css.properties.font-size-adjust.none π | Chrome | 7/23/2024 | Edge | 7/25/2024 | 2 | |
| css.properties.font-size-adjust.two-values | Chrome | 7/23/2024 | Edge | 7/25/2024 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.view-transition π | Chrome | 6/11/2024 | Edge | 6/13/2024 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.position-try π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.align-items.anchor-center π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.align-self.anchor-center π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.anchor-name π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.anchor-name.none π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.block-size.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.bottom.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.height.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.inline-size.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.inset.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.inset-block.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.inset-block-end.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.inset-block-start.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.inset-inline.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.inset-inline-end.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.inset-inline-start.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.justify-items.anchor-center π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.justify-self.anchor-center π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.left.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.max-block-size.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.max-height.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.max-inline-size.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.max-width.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.min-block-size.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.min-height.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.min-inline-size.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.min-width.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.place-items.anchor-center π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.place-self.anchor-center π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-anchor.auto π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | 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 π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try.flip-block π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try.flip-inline π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try.flip-start π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try.none π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try-order π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try-order.most-block-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try-order.most-height π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try-order.most-inline-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try-order.most-width π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-try-order.normal π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-visibility π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-visibility.always π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-visibility.anchors-visible π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.position-visibility.no-overflow π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.right.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.top.anchor π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.view-transition-class π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.view-transition-class.none π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.properties.width.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.selectors.active-view-transition π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.selectors.active-view-transition-type π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.selectors.state π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | 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 π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.types.anchor-size π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.types.color.hsl.relative_syntax π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | 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 π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | 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 π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.types.mod.mixed_type_parameters π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.types.rem π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.types.rem.mixed_type_parameters π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.types.round π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 | |
| css.types.round.mixed_type_parameters π | Chrome | 5/14/2024 | Edge | 5/17/2024 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.direction.vertical_slider_direction | Chrome | 4/16/2024 | Edge | 4/18/2024 | 2 | 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 | Chrome | 4/16/2024 | Edge | 4/18/2024 | 2 | 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 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.display-mode.picture-in-picture π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.align-content.block_context π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.align-content.multicol_context π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.field-sizing π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.field-sizing.content π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.field-sizing.fixed π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.paint-order π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | 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 π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.text-spacing-trim.normal π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.text-spacing-trim.space-all π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.text-spacing-trim.space-first π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.properties.text-spacing-trim.trim-start π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 | |
| css.types.color.light-dark π | Chrome | 3/19/2024 | Edge | 3/22/2024 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.import.supports π | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | |
| css.properties.align-self.position_absolute_context π | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | |
| css.properties.justify-self.position_absolute_context π | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | |
| css.properties.place-self.position_absolute_context π | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | |
| css.selectors.backdrop.inherit_from_originating_element | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | |
| css.types.color.oklab.relative_syntax π | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | 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 π | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | 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 | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | |
| css.types.color.rgb.relative_syntax π | Chrome | 2/20/2024 | Edge | 2/23/2024 | 3 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.font-palette.animation_computed | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.font-palette.palette-mix_function π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.scrollbar-color π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.scrollbar-color.auto π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.scrollbar-width π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.scrollbar-width.auto π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.scrollbar-width.none π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.scrollbar-width.thin π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.text-decoration.grammar-error π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.text-decoration.spelling-error π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.text-decoration-line.grammar-error π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.properties.text-decoration-line.spelling-error π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.selectors.grammar-error π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.selectors.spelling-error π | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.types.color.hsl.mixed_type_parameters | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 | |
| css.types.color.hwb.mixed_type_parameters | Chrome | 1/23/2024 | Edge | 1/25/2024 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.scripting π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.background-clip.text π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | 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 π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | 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 π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-clip.border-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-clip.content-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-clip.fill-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-clip.no-clip | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-clip.padding-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-clip.stroke-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-clip.view-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-composite π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | 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 π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-composite.exclude π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-composite.intersect π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-composite.subtract π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-image π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | 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 π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-mode.alpha π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-mode.luminance π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-mode.match-source π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-origin π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-origin.border-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-origin.content-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-origin.fill-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-origin.padding-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-origin.stroke-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-origin.view-box | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-position π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-repeat π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.properties.mask-size π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.selectors.dir π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.selectors.nesting π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | 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 π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.types.hypot π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.types.log π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.types.pow π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 | |
| css.types.sqrt π | Chrome | 12/5/2023 | Edge | 12/7/2023 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.clip-path.border-box π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.properties.clip-path.content-box π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.properties.clip-path.fill-box π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | 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 π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.properties.clip-path.padding-box π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.properties.clip-path.stroke-box π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | 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 π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.properties.word-break.auto-phrase π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | 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 π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.selectors.user-valid π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.types.basic-shape.rect π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | 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 π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | 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 | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.types.color.color.relative_syntax π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | 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 π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | |
| css.types.color.lch.relative_syntax π | Chrome | 10/31/2023 | Edge | 11/2/2023 | 2 | 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). |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.prefers-reduced-transparency π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.at-rules.scope π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.clear.inline-end π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.clear.inline-start π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.float.inline-end π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.float.inline-start π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.resize.block | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.resize.inline | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.transform-box.border-box π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.transform-box.content-box π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.properties.transform-box.stroke-box π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.types.length.cap | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 | |
| css.types.length.rcap π | Chrome | 10/10/2023 | Edge | 10/13/2023 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.starting-style π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.contain-intrinsic-size.auto_none | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.content-visibility.is_transitionable π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.display.is_transitionable π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.font-variant-position π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.font-variant-position.normal π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.font-variant-position.sub π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | 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 π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | 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 π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.grid-template-rows.subgrid π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.overlay π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.overlay.auto π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.overlay.none π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.text-wrap.pretty π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.transition.transition-behavior | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.transition-behavior π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.transition-behavior.allow-discrete π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.transition-behavior.normal π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.transition-behavior.transitionable_content-visibility π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 | |
| css.properties.transition-behavior.transitionable_display π | Chrome | 9/12/2023 | Edge | 9/15/2023 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.content-visibility.keyframe_animatable π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.display.keyframe_animatable π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.auto π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.border-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.bottom π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.center π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.content-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.fill-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.left π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.normal π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.padding-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.right π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.stroke-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.top π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset.view-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-anchor π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-anchor.auto π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-anchor.bottom π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-anchor.center π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-anchor.left π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-anchor.right π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-anchor.top π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.basic_shape π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.border-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.content-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.fill-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.padding-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.ray π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.stroke-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.url π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-path.view-box π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-position π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-position.auto π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-position.bottom π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-position.center π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-position.left π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-position.normal π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-position.right π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.offset-position.top π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.timeline-scope π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.properties.timeline-scope.none π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.types.color.lab.mixed_type_parameters | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.types.color.lch.mixed_type_parameters | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.types.color.oklab.mixed_type_parameters | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.types.color.oklch.mixed_type_parameters | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.types.ray π | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.types.ray.position | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 | |
| css.types.ray.size | Chrome | 8/15/2023 | Edge | 8/21/2023 | 6 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.keyframes.named_range_keyframes π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.align-content.flex_context.safe_unsafe | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-range.normal π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-range-end π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-range-end.normal π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-range-start π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-range-start.normal π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-timeline π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-timeline.auto π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-timeline.none π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.animation-timeline.scroll π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.display.multi-keyword_values | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.justify-content.flex_context.safe_unsafe | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.scroll-timeline-axis π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.scroll-timeline-axis.inline π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.scroll-timeline-axis.x π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.scroll-timeline-axis.y π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.scroll-timeline-name π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values. |
| css.properties.view-timeline.none π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline-axis π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values. |
| css.properties.view-timeline-axis.block π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline-axis.inline π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline-axis.x π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline-axis.y π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline-inset π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline-inset.auto π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline-name π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.properties.view-timeline-name.none π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | |
| css.types.color.system-color.accentcolor_accentcolortext π | Chrome | 7/18/2023 | Edge | 7/21/2023 | 3 | 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 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.text-wrap π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.text-wrap.balance π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.text-wrap.nowrap π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.text-wrap.wrap π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space.collapse π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space.preserve π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space.preserve-breaks π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space.shorthand_values | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | 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 π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space-collapse π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space-collapse.break-spaces π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space-collapse.collapse π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space-collapse.preserve π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.properties.white-space-collapse.preserve-breaks π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.selectors.backdrop.popover | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.selectors.popover-open π | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | |
| css.types.overflow.overlay | Chrome | 5/30/2023 | Edge | 6/2/2023 | 3 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.overflow-block π | Chrome | 5/2/2023 | Edge | 5/5/2023 | 3 | |
| css.at-rules.media.overflow-inline π | Chrome | 5/2/2023 | Edge | 5/5/2023 | 3 | |
| css.at-rules.media.update π | Chrome | 5/2/2023 | Edge | 5/5/2023 | 3 | |
| css.properties.background-image.image-set π | Chrome | 5/2/2023 | Edge | 5/5/2023 | 3 | 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 π | Chrome | 5/2/2023 | Edge | 5/5/2023 | 3 | 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 π | Chrome | 5/2/2023 | Edge | 5/5/2023 | 3 | |
| css.types.image.image-set π | Chrome | 5/2/2023 | Edge | 5/5/2023 | 3 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.animation-composition π | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.animation-composition.accumulate π | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.animation-composition.add π | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.animation-composition.replace π | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_afrikaans | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_albanian | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_amharic | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_czech | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_dutch | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_ethiopic_script_mul | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_galician | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_georgian | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_italian | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_latvian | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_lithuanian | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_modern_greek | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_russian | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_slovak | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_swedish | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 | |
| css.properties.hyphens.language_ukrainian | Chrome | 4/4/2023 | Edge | 4/6/2023 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.container.style_queries_for_custom_properties π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | 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 π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.at-rules.font-feature-values.annotation | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.at-rules.font-feature-values.character-variant | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.at-rules.font-feature-values.historical-forms | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.at-rules.font-feature-values.ornaments | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.at-rules.font-feature-values.styleset | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.at-rules.font-feature-values.stylistic | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.at-rules.font-feature-values.swash | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.baseline-source π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.baseline-source.auto π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.baseline-source.first π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.baseline-source.last π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant.historical-forms π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates.annotation π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates.character_variant π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates.historical-forms π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates.normal π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates.ornaments π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates.styleset π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates.stylistic π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.font-variant-alternates.swash π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.view-transition-name π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.properties.view-transition-name.none π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.selectors.nth-child.of_syntax | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.selectors.nth-last-child.of_syntax | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.acos π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.asin π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.atan π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.atan2 π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.color.color π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | 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 | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.color.color-mix π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.color.lab π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.color.lch π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.color.oklab π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.color.oklch π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.cos π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.conic-gradient.hue_interpolation_method | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.conic-gradient.interpolation_color_space | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.linear-gradient.hue_interpolation_method | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.linear-gradient.interpolation_color_space | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.radial-gradient.hue_interpolation_method | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.radial-gradient.interpolation_color_space | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.repeating-conic-gradient.hue_interpolation_method | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.repeating-conic-gradient.interpolation_color_space | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.repeating-linear-gradient.hue_interpolation_method | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.repeating-linear-gradient.interpolation_color_space | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.repeating-radial-gradient.hue_interpolation_method | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.gradient.repeating-radial-gradient.interpolation_color_space | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.length.rch π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.length.rex π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.length.ric π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.length.rlh π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.sin π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 | |
| css.types.tan π | Chrome | 3/7/2023 | Edge | 3/13/2023 | 6 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.font-variant.sub π | Chrome | 2/7/2023 | Edge | 2/9/2023 | 2 | |
| css.properties.font-variant.super π | Chrome | 2/7/2023 | Edge | 2/9/2023 | 2 | |
| css.properties.initial-letter π | Chrome | 2/7/2023 | Edge | 2/9/2023 | 2 | 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 π | Chrome | 2/7/2023 | Edge | 2/9/2023 | 2 | |
| css.selectors.autofill π | Chrome | 2/7/2023 | Edge | 2/9/2023 | 2 | 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 π | Chrome | 2/7/2023 | Edge | 2/9/2023 | 2 | |
| css.types.calc-keyword.e | Chrome | 2/7/2023 | Edge | 2/9/2023 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.container.normal π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.display.math | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.font-family.math | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.font-size.math | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.hyphenate-limit-chars π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.hyphenate-limit-chars.auto π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.math-depth π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.math-depth.auto-add π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.math-shift π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.math-shift.compact π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.math-shift.normal π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.math-style π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.math-style.compact π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.math-style.normal π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.properties.text-transform.math-auto π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.selectors.view-transition π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.selectors.view-transition-group π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.selectors.view-transition-image-pair π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.selectors.view-transition-new π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.selectors.view-transition-old π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.types.calc-keyword.pi | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 | |
| css.types.length.lh π | Chrome | 1/10/2023 | Edge | 1/12/2023 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.font-face.src.drop_invalid_item | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | 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 | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.at-rules.font-face.src.tech_keyword | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.at-rules.supports.font-format | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.at-rules.supports.font-tech | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.properties.align-items.flex_context.last_baseline | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.properties.align-self.flex_context.last_baseline | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.types.length.vb | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.types.length.vi | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.types.length.viewport_percentage_units_dynamic | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.types.length.viewport_percentage_units_large | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 | |
| css.types.length.viewport_percentage_units_small | Chrome | 11/29/2022 | Edge | 12/5/2022 | 6 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.overflow.replaced_elements π | Edge | 7/29/2015 | Chrome | 11/29/2022 | 2680 | |
| css.properties.overflow-x.replaced_elements π | Edge | 7/29/2015 | Chrome | 11/29/2022 | 2680 | |
| css.properties.overflow-y.replaced_elements π | Edge | 7/29/2015 | Chrome | 11/29/2022 | 2680 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.grid-template-columns.animation | Chrome | 10/25/2022 | Edge | 10/27/2022 | 2 | |
| css.properties.grid-template-rows.animation | Chrome | 10/25/2022 | Edge | 10/27/2022 | 2 | |
| css.properties.forced-color-adjust.preserve-parent-color π | Chrome | 9/27/2022 | Edge | 10/3/2022 | 6 | |
| css.properties.hyphenate-character π | Chrome | 9/27/2022 | Edge | 10/3/2022 | 6 | |
| css.types.length.ic | Chrome | 9/27/2022 | Edge | 10/3/2022 | 6 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.container π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.at-rules.media.display-mode.window-controls-overlay π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.contain.inline-size π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container.inline-size π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container.none π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container.scroll-state π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container.size π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container-name π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container-name.none π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container-type π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container-type.inline-size π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container-type.normal π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.properties.container-type.size π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.selectors.has π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.selectors.highlight π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | 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 π | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.selectors.selection.text-decoration | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 | |
| css.types.length.container_query_length_units | Edge | 9/1/2022 | Chrome | 9/2/2022 | 1 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.or_syntax | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.at-rules.media.range_syntax | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | 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 π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.object-view-box π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.object-view-box.none π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.overflow-clip-margin.border-box π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.overflow-clip-margin.content-box π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.overflow-clip-margin.padding-box π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.rotate π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.rotate.none π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.rotate.x_y_z_angle | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.scale π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.scale.none π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.translate π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 | |
| css.properties.translate.none π | Chrome | 8/2/2022 | Edge | 8/5/2022 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.break-after.multicol_context.avoid | Chrome | 5/24/2022 | Edge | 5/31/2022 | 7 | |
| css.properties.break-after.multicol_context.avoid-column | Chrome | 5/24/2022 | Edge | 5/31/2022 | 7 | |
| css.properties.break-before.multicol_context.avoid | Chrome | 5/24/2022 | Edge | 5/31/2022 | 7 | |
| css.properties.break-before.multicol_context.avoid-column | Chrome | 5/24/2022 | Edge | 5/31/2022 | 7 | |
| css.types.color.system-color.mark π | Chrome | 5/24/2022 | Edge | 5/31/2022 | 7 | |
| css.types.color.system-color.marktext π | Chrome | 5/24/2022 | Edge | 5/31/2022 | 7 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.font-palette-values π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.at-rules.font-palette-values.base-palette π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.at-rules.font-palette-values.font-family π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.at-rules.font-palette-values.override-colors π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.properties.font-palette π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.properties.font-palette.dark π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.properties.font-palette.light π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.properties.font-palette.normal π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.types.color.hwb π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.types.color.system-color.buttonborder π | Chrome | 4/26/2022 | Edge | 4/28/2022 | 2 | |
| css.properties.mix-blend-mode.plus-lighter π | Chrome | 3/29/2022 | Edge | 4/1/2022 | 3 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.import.layer π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.at-rules.layer π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-color π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-position π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-position.over | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-position.under | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style.circle π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style.dot π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style.double-circle π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style.filled π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style.none π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style.open π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style.sesame π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.properties.text-emphasis-style.triangle π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.types.calc-keyword π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.types.calc-keyword.NaN | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.types.calc-keyword.infinity | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 | |
| css.types.global_keywords.revert-layer π | Chrome | 3/1/2022 | Edge | 3/3/2022 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.font-face.OpenType_COLRv1 | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 | |
| css.at-rules.media.dynamic-range π | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 | |
| css.at-rules.media.video-dynamic-range π | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 | |
| css.properties.color-scheme.only | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 | |
| css.properties.contain-intrinsic-block-size.none π | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 | |
| css.properties.contain-intrinsic-height.none π | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 | |
| css.properties.contain-intrinsic-inline-size.none π | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 | |
| css.properties.contain-intrinsic-size.none π | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 | |
| css.properties.contain-intrinsic-width.none π | Chrome | 2/1/2022 | Edge | 2/3/2022 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.font-synthesis π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis.none π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis.small-caps | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis.style | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis.weight | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-small-caps π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-small-caps.auto π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-small-caps.none π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-style π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-style.auto π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-style.none π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-weight π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-weight.auto π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.properties.font-synthesis-weight.none π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 | |
| css.types.transform-function.perspective.none π | Chrome | 1/4/2022 | Edge | 1/6/2022 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.prefers-contrast π | Chrome | 11/15/2021 | Edge | 11/19/2021 | 4 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.contain-intrinsic-block-size π | Chrome | 10/19/2021 | Edge | 10/21/2021 | 2 | |
| css.properties.contain-intrinsic-height π | Chrome | 10/19/2021 | Edge | 10/21/2021 | 2 | |
| css.properties.contain-intrinsic-inline-size π | Chrome | 10/19/2021 | Edge | 10/21/2021 | 2 | |
| css.properties.contain-intrinsic-width π | Chrome | 10/19/2021 | Edge | 10/21/2021 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.flex.content π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.flex.fit-content π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.flex.max-content π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.flex.min-content π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.flex-basis.content | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.flex-basis.fit-content | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.flex-basis.max-content | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.flex-basis.min-content | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.outline π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | 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 π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.scrollbar-gutter.auto π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.scrollbar-gutter.stable π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.types.env.keyboard-inset-bottom π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.types.env.keyboard-inset-height π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.types.env.keyboard-inset-left π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.types.env.keyboard-inset-right π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.types.env.keyboard-inset-top π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.types.env.keyboard-inset-width π | Chrome | 9/21/2021 | Edge | 9/24/2021 | 3 | |
| css.properties.accent-color π | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | 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 | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | |
| css.properties.align-content.flex_context.start_end | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | 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 | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | |
| css.properties.align-self.flex_context.start_end | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | Opera: Before version 79, this value is recognized, but has no effect. |
| css.properties.justify-content.flex_context.left_right | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | 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 | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | |
| css.types.env.titlebar-area-height π | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | 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 π | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | 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 π | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | 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 π | Chrome | 8/31/2021 | Edge | 9/2/2021 | 2 | Chrome: Before version 93, Linux is unsupported.Chrome Android: Before version 93, Linux is unsupported.Edge: Before version 93, Linux is unsupported. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.font-face.size-adjust π | Chrome | 7/20/2021 | Edge | 7/22/2021 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.counter-style π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.additive-symbols π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.fallback π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.negative π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.pad π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.prefix π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.range π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.speak-as π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.suffix π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.at-rules.counter-style.symbols π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | 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 π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.afar | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.amharic | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.amharic-abegede | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.asterisks | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.binary | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.cjk-decimal π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-abegede | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-abegede-am-et | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-abegede-gez | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-abegede-ti-er | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-abegede-ti-et | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-halehame-aa-er | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-halehame-aa-et | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-halehame-am-et | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-halehame-gez | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-halehame-om-et | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-halehame-sid-et | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-halehame-so-et | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-halehame-tig | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.ethiopic-numeric π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | 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 | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.japanese-formal π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.japanese-informal π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.lower-hexadecimal | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.lower-norwegian | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.octal | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.oromo | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.sidama | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.somali | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.tamil π | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.tigre | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.tigrinya-er | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.tigrinya-er-abegede | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.tigrinya-et | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.tigrinya-et-abegede | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.upper-greek | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.upper-hexadecimal | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 | |
| css.properties.list-style-type.upper-norwegian | Chrome | 5/25/2021 | Edge | 5/27/2021 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.overflow.clip π | Chrome | 4/13/2021 | Edge | 4/15/2021 | 2 | |
| css.properties.overflow-clip-margin π | Chrome | 4/13/2021 | Edge | 4/15/2021 | 2 | 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 π | Chrome | 4/13/2021 | Edge | 4/15/2021 | 2 | |
| css.properties.overflow-y.clip π | Chrome | 4/13/2021 | Edge | 4/15/2021 | 2 | |
| css.types.overflow.clip | Chrome | 4/13/2021 | Edge | 4/15/2021 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.border-end-end-radius π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.properties.border-end-start-radius π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.properties.border-start-end-radius π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.properties.border-start-start-radius π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.properties.filter.svg_elements | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.properties.list-style-type.disclosure-closed π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.properties.list-style-type.disclosure-open π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.properties.text-decoration-thickness π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | 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 π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.selectors.target-text π | Chrome | 3/2/2021 | Edge | 3/4/2021 | 2 | |
| css.at-rules.media.forced-colors π | Edge | 1/15/2020 | Chrome | 3/2/2021 | 412 | |
| css.properties.forced-color-adjust π | Edge | 1/15/2020 | Chrome | 3/2/2021 | 412 | |
| css.properties.forced-color-adjust.auto π | Edge | 1/15/2020 | Chrome | 3/2/2021 | 412 | |
| css.properties.forced-color-adjust.none π | Edge | 1/15/2020 | Chrome | 3/2/2021 | 412 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.aspect-ratio π | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | |
| css.properties.aspect-ratio.auto π | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | |
| css.properties.clip-path.path | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | |
| css.properties.hyphens.auto | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS. |
| css.properties.hyphens.manual | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS. |
| css.properties.hyphens.none | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS. |
| css.selectors.is π | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | 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 | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | |
| css.selectors.not.selector_list | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | |
| css.selectors.where π | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | |
| css.selectors.where.forgiving_selector_list | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 | |
| css.types.basic-shape.path.clip-path π | Chrome | 1/19/2021 | Edge | 1/21/2021 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.font-face.ascent-override π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.at-rules.font-face.descent-override π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.at-rules.font-face.line-gap-override π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.currentColor π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.dashed π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.dotted π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.double π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.groove π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.hidden π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.inset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.medium π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.none π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.outset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.ridge π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.solid π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.thick π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.thin π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block.transparent π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-color π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-color.currentColor π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-color.transparent π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.dashed π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.dotted π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.double π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.groove π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.hidden π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.inset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.none π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.outset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.ridge π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-style.solid π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-width π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-width.medium π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-width.thick π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-block-width.thin π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.currentColor π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.dashed π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.dotted π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.double π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.groove π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.hidden π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.inset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.medium π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.none π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.outset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.ridge π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.solid π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.thick π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.thin π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline.transparent π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-color π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-color.currentColor π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-color.transparent π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.dashed π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.dotted π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.double π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.groove π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.hidden π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.inset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.none π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.outset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.ridge π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-style.solid π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-width π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-width.medium π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-width.thick π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.border-inline-width.thin π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_armenian | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_assamese | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_basque | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_belarusian | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_bengali | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_bulgarian | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_croatian | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_cyrillic_mongolian | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_danish | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_estonian | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_ethiopic_script_und | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_french | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_german_reformed_orthography | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_german_swiss_orthography | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_german_traditional_orthography | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_gujarati | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_hindi | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_hungarian | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_irish | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_kannada | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_latin | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_malayalam | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_marathi | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_norwegian_nn | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_norwegian_no | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_old_slavonic | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_oriya | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_portuguese | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_punjabi | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_slovenian | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_spanish | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_tamil | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_telugu | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_turkmen | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.hyphens.language_welsh | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-block π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-block.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-block-end π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-block-end.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-block-start π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-block-start.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-inline π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-inline.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-inline-end π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-inline-end.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-inline-start π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.inset-inline-start.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.margin-block π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.margin-block.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.margin-inline π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.margin-inline.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.padding-block π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.padding-inline π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.quotes.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | 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 π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-decoration.from-font π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-decoration.includes_thickness | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-decoration-thickness.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-decoration-thickness.from-font π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-decoration-thickness.percentage | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-underline-offset π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-underline-offset.auto π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-underline-offset.percentage π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 | |
| css.properties.text-underline-position.from-font π | Chrome | 11/17/2020 | Edge | 11/19/2020 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.selectors.focus-visible π | Edge | 10/9/2020 | Chrome | 10/20/2020 | 11 | |
| css.selectors.marker π | Edge | 10/9/2020 | Chrome | 10/20/2020 | 11 | 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 | Edge | 10/9/2020 | Chrome | 10/20/2020 | 11 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.prefers-reduced-data π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.at-rules.page.page-orientation π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.at-rules.property π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.at-rules.property.inherits π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.at-rules.property.initial-value π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.at-rules.property.syntax π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.properties.content-visibility π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.properties.content-visibility.auto π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | 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 π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.properties.content-visibility.visible π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.properties.counter-set π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.properties.counter-set.list-item π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.properties.counter-set.none π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.properties.page π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 | |
| css.properties.page.auto π | Chrome | 8/25/2020 | Edge | 8/27/2020 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.appearance π | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 | |
| css.properties.column-gap.flex_context π | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 | |
| css.properties.gap.flex_context π | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 | |
| css.properties.row-gap.flex_context π | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 | |
| css.properties.ruby-position π | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 | 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 | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 | 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 | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 | |
| css.properties.ruby-position.under | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 | |
| css.types.global_keywords.revert π | Edge | 7/16/2020 | Chrome | 7/27/2020 | 11 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.page.size.jis-b4 π | Chrome | 5/19/2020 | Edge | 5/21/2020 | 2 | |
| css.at-rules.page.size.jis-b5 π | Chrome | 5/19/2020 | Edge | 5/21/2020 | 2 | |
| css.at-rules.supports.selector | Chrome | 5/19/2020 | Edge | 5/21/2020 | 2 | |
| css.properties.appearance.auto π | Chrome | 5/19/2020 | Edge | 5/21/2020 | 2 | |
| css.properties.contain-intrinsic-size π | Chrome | 5/19/2020 | Edge | 5/21/2020 | 2 | |
| css.properties.line-break.anywhere π | Chrome | 5/19/2020 | Edge | 5/21/2020 | 2 | |
| css.selectors.xr-overlay π | Chrome | 5/19/2020 | Edge | 5/21/2020 | 2 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.color-scheme π | Chrome | 4/7/2020 | Edge | 4/13/2020 | 6 | |
| css.properties.color-scheme.dark | Chrome | 4/7/2020 | Edge | 4/13/2020 | 6 | |
| css.properties.color-scheme.light | Chrome | 4/7/2020 | Edge | 4/13/2020 | 6 | |
| css.properties.color-scheme.normal | Chrome | 4/7/2020 | Edge | 4/13/2020 | 6 | |
| css.properties.image-orientation π | Chrome | 4/7/2020 | Edge | 4/13/2020 | 6 | |
| css.properties.image-orientation.from-image π | Chrome | 4/7/2020 | Edge | 4/13/2020 | 6 | |
| css.properties.image-orientation.none π | Chrome | 4/7/2020 | Edge | 4/13/2020 | 6 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.offset-path.none π | Chrome | 2/4/2020 | Edge | 2/7/2020 | 3 | |
| css.properties.overflow-wrap.anywhere π | Chrome | 2/4/2020 | Edge | 2/7/2020 | 3 | |
| css.properties.speak π | Chrome | 2/4/2020 | Edge | 2/7/2020 | 3 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.font-face.OpenType_CBDT_CBLC | Chrome | 4/17/2018 | Edge | 1/15/2020 | 638 | |
| css.at-rules.font-face.OpenType_COLRv0 | Chrome | 8/31/2016 | Edge | 1/15/2020 | 1232 | |
| css.at-rules.font-face.OpenType_SBIX | Chrome | 4/17/2018 | Edge | 1/15/2020 | 638 | |
| css.at-rules.font-face.font-display π | Chrome | 7/25/2017 | Edge | 1/15/2020 | 904 | |
| css.at-rules.keyframes.ignore_important_declarations | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.at-rules.media.calc π | Chrome | 4/17/2018 | Edge | 1/15/2020 | 638 | |
| css.at-rules.media.color-gamut π | Chrome | 4/19/2017 | Edge | 1/15/2020 | 1001 | |
| css.at-rules.media.color-gamut.p3 π | Chrome | 4/19/2017 | Edge | 1/15/2020 | 1001 | 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 π | Chrome | 4/19/2017 | Edge | 1/15/2020 | 1001 | 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 π | Chrome | 4/19/2017 | Edge | 1/15/2020 | 1001 | 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.at-rules.media.color-index π | Chrome | 8/20/2013 | Edge | 1/15/2020 | 2339 | |
| css.at-rules.media.display-mode π | Chrome | 4/14/2015 | Edge | 1/15/2020 | 1737 | |
| css.at-rules.media.display-mode.browser π | Chrome | 4/14/2015 | Edge | 1/15/2020 | 1737 | Firefox for Android: display-mode: browser is always true.Safari: In a Safari browser window, display-mode: browser is always true, even in a macOS Full Screen window or when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In the Safari app, display-mode: browser is always true, even when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).WebView on iOS: In the Safari app, display-mode: browser is always true, even when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment). |
| css.at-rules.media.display-mode.fullscreen π | Chrome | 12/1/2015 | Edge | 1/15/2020 | 1506 | Firefox: In Firefox's "Full Screen" user interface, browser tabs and other user interface appear but display-mode: fullscreen is true.Safari: In a Safari browser window, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In the Safari app, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In an installed web application with the display manifest member set to standalone, display-mode: fullscreen is true, even though the system status bar is visible. See bug 264218.WebView on iOS: In the Safari app, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).WebView on iOS: In an installed web application with the display manifest member set to standalone, display-mode: fullscreen is true, even though the system status bar is visible. See bug 264218. |
| css.at-rules.media.display-mode.minimal-ui π | Chrome | 4/14/2015 | Edge | 1/15/2020 | 1737 | 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 π | Chrome | 4/14/2015 | Edge | 1/15/2020 | 1737 | Firefox: display-mode: standalone is never true.Safari on iOS: In an installed web application with the display manifest member set to standalone, display-mode: standalone is false and display-mode: fullscreen is true. See bug 264218.WebView on iOS: In an installed web application with the display manifest member set to standalone, display-mode: standalone is false and display-mode: fullscreen is true. See bug 264218. |
| css.at-rules.media.media_query_values | Chrome | 4/17/2018 | Edge | 1/15/2020 | 638 | |
| css.at-rules.media.monochrome π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.at-rules.media.prefers-color-scheme π | Chrome | 7/30/2019 | Edge | 1/15/2020 | 169 | |
| css.at-rules.media.prefers-reduced-motion π | Chrome | 4/23/2019 | Edge | 1/15/2020 | 267 | |
| css.at-rules.page.size π | Chrome | 10/25/2011 | Edge | 1/15/2020 | 3004 | |
| css.properties.-webkit-app-region | Chrome | 1/10/2013 | Edge | 1/15/2020 | 2561 | |
| css.properties.-webkit-border-before | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-border-horizontal-spacing | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-border-vertical-spacing | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-box-reflect | Chrome | 1/25/2010 | Edge | 1/15/2020 | 3642 | |
| css.properties.-webkit-column-break-after | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-column-break-before | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-column-break-inside | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-locale | Chrome | 4/27/2011 | Edge | 1/15/2020 | 3185 | |
| css.properties.-webkit-logical-height | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-logical-width | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-margin-after | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-margin-before | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-mask-box-image | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-max-logical-height | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-max-logical-width | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-min-logical-height | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-min-logical-width | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.-webkit-perspective-origin-x | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.properties.-webkit-perspective-origin-y | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.properties.-webkit-rtl-ordering | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-text-combine | Chrome | 2/3/2011 | Edge | 1/15/2020 | 3268 | |
| css.properties.-webkit-text-decorations-in-effect | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-text-security | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-transform-origin-x | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-transform-origin-y | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.-webkit-transform-origin-z | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.properties.-webkit-user-drag | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.align-content.flex_context.baseline | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.align-content.flex_context.first_baseline | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.align-content.flex_context.space-evenly | Chrome | 7/25/2017 | Edge | 1/15/2020 | 904 | |
| css.properties.align-content.flex_context.stretch | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.align-items.flex_context.baseline | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | |
| css.properties.align-items.flex_context.first_baseline | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.align-items.grid_context.start_end | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.align-self.auto π | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | |
| css.properties.align-self.flex_context.baseline π | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | |
| css.properties.align-self.flex_context.first_baseline | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.align-self.flex_context.stretch π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.align-self.normal π | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | |
| css.properties.align-self.stretch π | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | |
| css.properties.alignment-baseline π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.alignment-baseline.alphabetic | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.alignment-baseline.baseline | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.alignment-baseline.central | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.alignment-baseline.ideographic | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.alignment-baseline.mathematical | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.alignment-baseline.middle | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.alignment-baseline.text-after-edge | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.alignment-baseline.text-before-edge | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.all π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.animation.paused π | Chrome | 9/15/2009 | Edge | 1/15/2020 | 3774 | |
| css.properties.animation.running π | Chrome | 9/15/2009 | Edge | 1/15/2020 | 3774 | |
| css.properties.animation-timing-function.jump | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.backdrop-filter π | Chrome | 7/30/2019 | Edge | 1/15/2020 | 169 | |
| css.properties.backdrop-filter.none π | Chrome | 7/30/2019 | Edge | 1/15/2020 | 169 | |
| css.properties.background-blend-mode π | Chrome | 5/20/2014 | Edge | 1/15/2020 | 2066 | |
| css.properties.background-position.bottom π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.background-position.center π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.background-position.left π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.background-position.right π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.background-position.top π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.baseline-shift π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.baseline-shift.baseline π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.baseline-shift.sub π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.baseline-shift.super π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.block-size π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.block-size.auto π | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.block-size.fit-content π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.block-size.max-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.block-size.min-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.border-block-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.currentColor π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.dashed π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.dotted π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.double π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.groove π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.hidden π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.inset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.medium π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.outset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.ridge π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.solid π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.thick π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.thin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end.transparent π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-color π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-color.currentColor π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-color.transparent π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.dashed π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.dotted π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.double π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.groove π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.hidden π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.inset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.outset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.ridge π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-style.solid π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-width π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-width.medium π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-width.thick π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-end-width.thin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.currentColor π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.dashed π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.dotted π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.double π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.groove π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.hidden π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.inset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.medium π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.outset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.ridge π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.solid π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.thick π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.thin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start.transparent π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-color π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-color.currentColor π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-color.transparent π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.dashed π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.dotted π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.double π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.groove π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.hidden π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.inset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.outset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.ridge π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-style.solid π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-width π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-width.medium π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-width.thick π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-block-start-width.thin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-collapse.collapse | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.border-collapse.separate | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.border-inline-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.currentColor π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.dashed π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.dotted π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.double π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.groove π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.hidden π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.inset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.medium π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.outset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.ridge π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.solid π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.thick π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.thin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end.transparent π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-color π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-color.currentColor π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-color.transparent π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.dashed π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.dotted π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.double π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.groove π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.hidden π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.inset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.outset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.ridge π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-style.solid π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-width π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-width.medium π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-width.thick π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-end-width.thin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.currentColor π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.dashed π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.dotted π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.double π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.groove π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.hidden π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.inset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.medium π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.outset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.ridge π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.solid π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.thick π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.thin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start.transparent π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-color π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-color.currentColor π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-color.transparent π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.dashed π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.dotted π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.double π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.groove π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.hidden π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.inset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.outset π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.ridge π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-style.solid π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-width π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-width.medium π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-width.thick π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.border-inline-start-width.thin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.break-after.auto | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-after.avoid | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | 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 | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-after.avoid-page | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-after.column | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-after.left | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-after.page | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-after.recto | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-after.right | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-after.verso | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.auto | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.avoid | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | 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 | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.avoid-page | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.column | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.left | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.page | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.recto | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.right | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-before.verso | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-inside.auto | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-inside.avoid | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-inside.avoid-column | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.break-inside.avoid-page | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.properties.buffered-rendering | Chrome | 7/9/2013 | Edge | 1/15/2020 | 2381 | |
| css.properties.buffered-rendering.auto | Chrome | 7/9/2013 | Edge | 1/15/2020 | 2381 | |
| css.properties.buffered-rendering.dynamic | Chrome | 7/9/2013 | Edge | 1/15/2020 | 2381 | |
| css.properties.buffered-rendering.static | Chrome | 7/9/2013 | Edge | 1/15/2020 | 2381 | |
| css.properties.caption-side.bottom | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.caption-side.top | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.caret-color π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.caret-color.auto π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.caret-color.currentColor π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.caret-color.transparent π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.clip.auto | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.clip-path π | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | Edge: Only supports clip paths defined by url().Internet Explorer: Only supports clip paths defined by url(). |
| css.properties.clip-path.basic_shape π | Chrome | 11/6/2012 | Edge | 1/15/2020 | 2626 | |
| css.properties.clip-path.html_elements | Chrome | 11/6/2012 | Edge | 1/15/2020 | 2626 | |
| css.properties.clip-path.is_animatable | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | |
| css.properties.clip-rule π | Chrome | 10/25/2011 | Edge | 1/15/2020 | 3004 | |
| css.properties.clip-rule.evenodd π | Chrome | 10/25/2011 | Edge | 1/15/2020 | 3004 | |
| css.properties.clip-rule.nonzero π | Chrome | 10/25/2011 | Edge | 1/15/2020 | 3004 | |
| css.properties.color-interpolation π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.color-interpolation.auto π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.color-interpolation.linearRGB π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.color-interpolation.sRGB π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.color-interpolation-filters π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.color-interpolation-filters.auto π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.color-interpolation-filters.linearRGB π | Chrome | 7/9/2013 | Edge | 1/15/2020 | 2381 | |
| css.properties.color-interpolation-filters.sRGB π | Chrome | 7/9/2013 | Edge | 1/15/2020 | 2381 | |
| css.properties.color-rendering | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.color-rendering.auto | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.color-rendering.optimizeQuality | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.color-rendering.optimizeSpeed | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.contain π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.contain.content π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.contain.layout π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.contain.none π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.contain.paint π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.contain.size π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.contain.strict π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.contain.style π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | 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.content.alt_text | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.content.element_replacement | Chrome | 7/9/2013 | Edge | 1/15/2020 | 2381 | |
| css.properties.cursor.grabbing π | Chrome | 7/24/2018 | Edge | 1/15/2020 | 540 | Chrome: Chrome 22 added Windows support.Chrome Android: Chrome Android 25 added Windows support.Edge: Edge 79 added Windows support.Quest Browser: Quest Browser 5.0 added Windows support.Opera: Opera 15 added Windows support.Opera Android: Opera Android 14 added Windows support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.Samsung Internet: Samsung Internet 1.5 added Windows support.WebView Android: WebView Android 4.4 added Windows support.WebView on iOS: If this value is used, the iPad will display the default pointer instead. |
| css.properties.cursor.url_positioning_syntax | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | Firefox: Firefox 4 added macOS support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead. |
| css.properties.cx π | Chrome | 5/19/2015 | Edge | 1/15/2020 | 1702 | |
| css.properties.cy π | Chrome | 5/19/2015 | Edge | 1/15/2020 | 1702 | |
| css.properties.d π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | 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 π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.display.contents π | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.properties.display.contents.contents_unusual π | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.properties.display.flow-root | Chrome | 4/19/2017 | Edge | 1/15/2020 | 1001 | |
| css.properties.display.list-item.legend-support | Chrome | 12/4/2018 | Edge | 1/15/2020 | 407 | |
| css.properties.display.none.option_is_hidden | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.dominant-baseline π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.dominant-baseline.alphabetic π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.dominant-baseline.auto π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.dominant-baseline.central π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.dominant-baseline.hanging π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.dominant-baseline.ideographic π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.dominant-baseline.mathematical π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.dominant-baseline.middle π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.flex-grow.less_than_zero_animate | Chrome | 3/2/2016 | Edge | 1/15/2020 | 1414 | 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.properties.font.font-width_keyword_values | Chrome | 7/25/2017 | Edge | 1/15/2020 | 904 | |
| css.properties.font-family.system-ui | Chrome | 1/25/2017 | Edge | 1/15/2020 | 1085 | Firefox: Supported on macOS only. |
| css.properties.font-kerning π | Chrome | 2/20/2014 | Edge | 1/15/2020 | 2155 | |
| css.properties.font-kerning.auto π | Chrome | 2/20/2014 | Edge | 1/15/2020 | 2155 | |
| css.properties.font-kerning.none π | Chrome | 2/20/2014 | Edge | 1/15/2020 | 2155 | |
| css.properties.font-kerning.normal π | Chrome | 2/20/2014 | Edge | 1/15/2020 | 2155 | |
| css.properties.font-size.xxx-large | Chrome | 12/10/2019 | Edge | 1/15/2020 | 36 | |
| css.properties.font-smooth | Chrome | 5/25/2010 | Edge | 1/15/2020 | 3522 | Firefox: Only works on macOS. |
| css.properties.font-style.oblique-angle π | Chrome | 10/17/2017 | Edge | 1/15/2020 | 820 | Chrome: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Chrome Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Edge: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Quest Browser: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Samsung Internet: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876. |
| css.properties.font-variant.css_fonts_shorthand | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant.none π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-caps π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-caps.all-petite-caps π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-caps.all-small-caps π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-caps.normal π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-caps.petite-caps π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-caps.small-caps π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-caps.titling-caps π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-caps.unicase π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-east-asian π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.full-width π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.jis04 π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.jis78 π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.jis83 π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.jis90 π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.normal π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.proportional-width π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.ruby π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.simplified π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-east-asian.traditional π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.font-variant-ligatures π | Chrome | 4/8/2014 | Edge | 1/15/2020 | 2108 | |
| css.properties.font-variant-ligatures.common-ligatures π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.contextual π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.discretionary-ligatures π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.historical-ligatures π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.no-common-ligatures π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.no-contextual π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.no-discretionary-ligatures π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.no-historical-ligatures π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.none π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-ligatures.normal π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.font-variant-numeric π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.diagonal-fractions π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.lining-nums π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.normal π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.oldstyle-nums π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.ordinal π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.proportional-nums π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.slashed-zero π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.stacked-fractions π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.font-variant-numeric.tabular-nums π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.grid-auto-flow.column π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-auto-flow.dense π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-auto-flow.row π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template.none π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-areas.none π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-columns.auto π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-columns.max-content π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-columns.min-content π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-columns.none π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-rows.auto π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-rows.max-content π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-rows.min-content π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.grid-template-rows.none π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.height.fit-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.height.max-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.height.min-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.hyphenate-character.auto π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.hyphens π | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | 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.image-rendering π | Chrome | 8/2/2011 | Edge | 1/15/2020 | 3088 | |
| css.properties.image-rendering.auto π | Chrome | 8/2/2011 | Edge | 1/15/2020 | 3088 | |
| css.properties.image-rendering.crisp-edges π | Chrome | 8/2/2011 | Edge | 1/15/2020 | 3088 | |
| css.properties.image-rendering.pixelated π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.inline-size π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.inline-size.auto π | Chrome | 12/2/2010 | Edge | 1/15/2020 | 3331 | |
| css.properties.inline-size.fit-content π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.inline-size.max-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.inline-size.min-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.isolation π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.isolation.auto π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.isolation.isolate π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.justify-content.flex_context.space-evenly | Chrome | 7/25/2017 | Edge | 1/15/2020 | 904 | |
| css.properties.justify-content.flex_context.stretch | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.justify-content.left | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | |
| css.properties.justify-content.normal | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | |
| css.properties.justify-content.right | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | |
| css.properties.justify-items.center | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.justify-items.left | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.justify-items.legacy π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.justify-items.right | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.properties.justify-self.auto | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.justify-self.left | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.justify-self.normal | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.justify-self.right | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.justify-self.stretch | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.line-break.auto π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.line-break.loose π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.line-break.normal π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.line-break.strict π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.list-style-type.arabic-indic π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.bengali π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.cambodian π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.cjk-earthly-branch π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.cjk-heavenly-stem π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.cjk-ideographic π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | Opera: Until version 15, only decimal numbers display.Opera Android: Until version 15, only decimal numbers display. |
| css.properties.list-style-type.devanagari π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.ethiopic-halehame | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.ethiopic-halehame-am | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.ethiopic-halehame-ti-er | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.ethiopic-halehame-ti-et | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.gujarati π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.gurmukhi π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.hangul | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.hangul-consonant | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.kannada π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.khmer π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.korean-hangul-formal π | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.korean-hanja-formal π | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.korean-hanja-informal π | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.lao π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.lower-armenian π | Chrome | 8/2/2011 | Edge | 1/15/2020 | 3088 | |
| css.properties.list-style-type.malayalam π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.mongolian π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.myanmar π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.oriya π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.persian π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.simp-chinese-formal π | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.simp-chinese-informal π | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.string | Chrome | 12/10/2019 | Edge | 1/15/2020 | 36 | |
| css.properties.list-style-type.telugu π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.thai π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.tibetan π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.list-style-type.trad-chinese-formal π | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.trad-chinese-informal π | Chrome | 9/1/2015 | Edge | 1/15/2020 | 1597 | |
| css.properties.list-style-type.upper-armenian π | Chrome | 8/2/2011 | Edge | 1/15/2020 | 3088 | |
| css.properties.list-style-type.urdu | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.margin-block-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.margin-block-end.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.margin-block-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.margin-block-start.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.margin-inline-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.margin-inline-end.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.margin-inline-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.margin-inline-start.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.mask-border π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-border-outset π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-border-repeat π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-border-slice π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-border-source π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-border-width π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-clip.border | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | 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 | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | 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 | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | 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 | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | 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-origin.border | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-origin.content | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-origin.padding | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.mask-type π | Chrome | 1/10/2013 | Edge | 1/15/2020 | 2561 | |
| css.properties.mask-type.alpha π | Chrome | 1/10/2013 | Edge | 1/15/2020 | 2561 | |
| css.properties.mask-type.luminance π | Chrome | 1/10/2013 | Edge | 1/15/2020 | 2561 | |
| css.properties.max-block-size π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-block-size.fit-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-block-size.max-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-block-size.min-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-block-size.none π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-height.fit-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | 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 π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.max-height.min-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.max-inline-size π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-inline-size.fit-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-inline-size.max-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-inline-size.min-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-inline-size.none π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.max-width.fit-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | 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 π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.max-width.min-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.min-block-size π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-block-size.auto π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-block-size.fit-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-block-size.max-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-block-size.min-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-height.fit-content | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | 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 | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.min-height.min-content | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.min-inline-size π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-inline-size.auto π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-inline-size.fit-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-inline-size.max-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-inline-size.min-content | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.min-width.fit-content | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | 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 | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.min-width.min-content | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.mix-blend-mode π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.color π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.color-burn π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.color-dodge π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.darken π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.difference π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.exclusion π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.hard-light π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.hue π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.lighten π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.luminosity π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.multiply π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.normal π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.overlay π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.saturation π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.screen π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.soft-light π | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.mix-blend-mode.svg_elements | Chrome | 3/3/2015 | Edge | 1/15/2020 | 1779 | |
| css.properties.object-fit π | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | Edge: Only supported for <img> elements. |
| css.properties.object-fit.contain π | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | |
| css.properties.object-fit.cover π | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | |
| css.properties.object-fit.fill π | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | |
| css.properties.object-fit.none π | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | |
| css.properties.object-fit.scale-down π | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | |
| css.properties.object-position π | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | Edge: Only supported for <img> elements. |
| css.properties.offset π | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | |
| css.properties.offset.none π | Chrome | 9/5/2017 | Edge | 1/15/2020 | 862 | |
| css.properties.offset-distance π | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | |
| css.properties.offset-path π | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | Samsung Internet: path() is the only value type supported. |
| css.properties.offset-path.path | Chrome | 1/23/2018 | Edge | 1/15/2020 | 722 | |
| css.properties.offset-rotate π | Chrome | 1/25/2017 | Edge | 1/15/2020 | 1085 | |
| css.properties.offset-rotate.auto π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.offset-rotate.reverse π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.opacity.percentages | Chrome | 10/22/2019 | Edge | 1/15/2020 | 85 | |
| css.properties.outline.auto π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.overflow.multiple_keywords | Chrome | 7/24/2018 | Edge | 1/15/2020 | 540 | |
| css.properties.overflow-anchor π | Chrome | 1/25/2017 | Edge | 1/15/2020 | 1085 | |
| css.properties.overflow-anchor.auto π | Chrome | 1/25/2017 | Edge | 1/15/2020 | 1085 | |
| css.properties.overflow-anchor.none π | Chrome | 1/25/2017 | Edge | 1/15/2020 | 1085 | |
| css.properties.overscroll-behavior.auto π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.overscroll-behavior.contain π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.properties.overscroll-behavior.none π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect). |
| css.properties.overscroll-behavior-block π | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.overscroll-behavior-block.auto π | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.overscroll-behavior-block.contain π | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.overscroll-behavior-block.none π | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.overscroll-behavior-inline π | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.overscroll-behavior-inline.auto π | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.overscroll-behavior-inline.contain π | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.overscroll-behavior-inline.none π | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.overscroll-behavior-x.none π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect). |
| css.properties.overscroll-behavior-y.none π | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect). |
| css.properties.padding-block-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.padding-block-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.padding-inline-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.padding-inline-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.paint-order.fill π | Chrome | 5/20/2014 | Edge | 1/15/2020 | 2066 | |
| css.properties.paint-order.markers π | Chrome | 5/20/2014 | Edge | 1/15/2020 | 2066 | |
| css.properties.paint-order.normal π | Chrome | 5/20/2014 | Edge | 1/15/2020 | 2066 | |
| css.properties.paint-order.stroke π | Chrome | 5/20/2014 | Edge | 1/15/2020 | 2066 | |
| css.properties.place-content π | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.place-content.flex_context | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | 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 | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | 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 π | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.place-items.flex_context | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.place-items.grid_context | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.place-self π | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.place-self.flex_context | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.place-self.grid_context | Chrome | 6/5/2017 | Edge | 1/15/2020 | 954 | |
| css.properties.pointer-events.bounding-box π | Chrome | 2/20/2014 | Edge | 1/15/2020 | 2155 | |
| css.properties.r π | Chrome | 5/19/2015 | Edge | 1/15/2020 | 1702 | |
| css.properties.resize π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | 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 | Chrome | 1/25/2010 | Edge | 1/15/2020 | 3642 | |
| css.properties.resize.both π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.resize.horizontal π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.resize.none π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.resize.vertical π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.rx π | Chrome | 5/19/2015 | Edge | 1/15/2020 | 1702 | Safari: Before Safari 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.Safari on iOS: Before Safari on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.WebView on iOS: Before WebView on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090. |
| css.properties.rx.auto π | Chrome | 8/31/2016 | Edge | 1/15/2020 | 1232 | |
| css.properties.ry π | Chrome | 5/19/2015 | Edge | 1/15/2020 | 1702 | Safari: Before Safari 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.Safari on iOS: Before Safari on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.WebView on iOS: Before WebView on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090. |
| css.properties.ry.auto π | Chrome | 8/31/2016 | Edge | 1/15/2020 | 1232 | |
| css.properties.scroll-behavior π | Chrome | 9/5/2017 | Edge | 1/15/2020 | 862 | |
| css.properties.scroll-behavior.auto π | Chrome | 9/5/2017 | Edge | 1/15/2020 | 862 | |
| css.properties.scroll-behavior.smooth π | Chrome | 9/5/2017 | Edge | 1/15/2020 | 862 | |
| css.properties.scroll-margin π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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 π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-margin-block-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-margin-block-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-margin-bottom π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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 π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-margin-inline-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-margin-inline-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-margin-left π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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 π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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 π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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 π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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 π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-block π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-block.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-block-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-block-end.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-block-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-block-start.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-bottom π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379. |
| css.properties.scroll-padding-bottom.auto π | Chrome | 10/22/2019 | Edge | 1/15/2020 | 85 | |
| css.properties.scroll-padding-inline π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-inline.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-inline-end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-inline-end.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-inline-start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-inline-start.auto π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-padding-left π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379. |
| css.properties.scroll-padding-left.auto π | Chrome | 10/22/2019 | Edge | 1/15/2020 | 85 | |
| css.properties.scroll-padding-right π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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.auto π | Chrome | 10/22/2019 | Edge | 1/15/2020 | 85 | |
| css.properties.scroll-padding-top π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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.auto π | Chrome | 10/22/2019 | Edge | 1/15/2020 | 85 | |
| css.properties.scroll-snap-align π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-align.center π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-align.end π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-align.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-align.start π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-stop π | Chrome | 6/4/2019 | Edge | 1/15/2020 | 225 | |
| css.properties.scroll-snap-stop.always π | Chrome | 6/4/2019 | Edge | 1/15/2020 | 225 | |
| css.properties.scroll-snap-stop.normal π | Chrome | 6/4/2019 | Edge | 1/15/2020 | 225 | |
| css.properties.scroll-snap-type π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | 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 π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-type.both π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-type.inline π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-type.none π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-type.x π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.scroll-snap-type.y π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.properties.shape-image-threshold π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-image-threshold.percentages | Chrome | 10/22/2019 | Edge | 1/15/2020 | 85 | |
| css.properties.shape-margin π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.border-box π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.circle | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.content-box π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.gradient π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.image π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.inset | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.margin-box π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.none π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.padding-box π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-outside.polygon | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.properties.shape-rendering π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.shape-rendering.auto π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.shape-rendering.crispEdges π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.shape-rendering.geometricPrecision π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.shape-rendering.optimizeSpeed π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.tab-size π | Chrome | 7/31/2012 | Edge | 1/15/2020 | 2724 | 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.tab-size.length π | Chrome | 4/14/2015 | Edge | 1/15/2020 | 1737 | |
| css.properties.text-align.center π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.text-align.end π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.text-align.left π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.text-align.match-parent π | Chrome | 12/13/2011 | Edge | 1/15/2020 | 2955 | |
| css.properties.text-align.right π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.text-align.start π | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.properties.text-align-last.end π | Chrome | 12/1/2015 | Edge | 1/15/2020 | 1506 | |
| css.properties.text-align-last.start π | Chrome | 12/1/2015 | Edge | 1/15/2020 | 1506 | |
| css.properties.text-combine-upright π | Chrome | 1/20/2016 | Edge | 1/15/2020 | 1456 | 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 π | Chrome | 1/20/2016 | Edge | 1/15/2020 | 1456 | |
| css.properties.text-combine-upright.none π | Chrome | 1/20/2016 | Edge | 1/15/2020 | 1456 | |
| css.properties.text-decoration.currentColor π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration.dashed π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration.dotted π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration.double π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration.includes_color-and-style | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration.solid π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration.transparent π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration.wavy π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-color π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-color.currentColor π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-color.transparent π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-line π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-line.blink π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | 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 π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-line.none π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-line.overline π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-line.underline π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-skip-ink π | Chrome | 1/23/2018 | Edge | 1/15/2020 | 722 | |
| css.properties.text-decoration-skip-ink.auto π | Chrome | 1/23/2018 | Edge | 1/15/2020 | 722 | |
| css.properties.text-decoration-skip-ink.none π | Chrome | 1/23/2018 | Edge | 1/15/2020 | 722 | |
| css.properties.text-decoration-style π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-style.dashed π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-style.dotted π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-style.double π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-style.solid π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-decoration-style.wavy π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.properties.text-emphasis.circle π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.currentColor π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.dot π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.double-circle π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.filled π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.none π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.open π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.sesame π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.transparent π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis.triangle π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis-color.currentColor π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis-color.transparent π | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.properties.text-emphasis-position.left | Chrome | 10/17/2017 | Edge | 1/15/2020 | 820 | |
| css.properties.text-emphasis-position.right | Chrome | 10/17/2017 | Edge | 1/15/2020 | 820 | |
| css.properties.text-orientation π | Chrome | 1/20/2016 | Edge | 1/15/2020 | 1456 | |
| css.properties.text-orientation.mixed π | Chrome | 1/20/2016 | Edge | 1/15/2020 | 1456 | |
| css.properties.text-orientation.sideways π | Chrome | 6/7/2011 | Edge | 1/15/2020 | 3144 | |
| css.properties.text-orientation.upright π | Chrome | 6/7/2011 | Edge | 1/15/2020 | 3144 | |
| css.properties.text-rendering π | Chrome | 1/25/2010 | Edge | 1/15/2020 | 3642 | 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 | Chrome | 1/25/2010 | Edge | 1/15/2020 | 3642 | 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 | Chrome | 8/2/2011 | Edge | 1/15/2020 | 3088 | Chrome: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Chrome Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Edge: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Firefox: Firefox treats geometricPrecision the same as optimizeLegibility.Firefox for Android: Firefox treats geometricPrecision the same as optimizeLegibility.Quest Browser: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Opera: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Opera Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Samsung Internet: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.WebView Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system. |
| css.properties.text-rendering.optimizeLegibility π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.text-rendering.optimizeSpeed π | Chrome | 11/12/2013 | Edge | 1/15/2020 | 2255 | |
| css.properties.text-size-adjust π | Chrome | 10/12/2016 | Edge | 1/15/2020 | 1190 | |
| css.properties.text-size-adjust.auto π | Chrome | 10/12/2016 | Edge | 1/15/2020 | 1190 | |
| css.properties.text-size-adjust.none π | Chrome | 10/12/2016 | Edge | 1/15/2020 | 1190 | |
| css.properties.text-transform.greek_accented_characters | Chrome | 4/8/2014 | Edge | 1/15/2020 | 2108 | |
| css.properties.text-underline-position.auto π | Chrome | 2/20/2014 | Edge | 1/15/2020 | 2155 | |
| css.properties.text-underline-position.left π | Chrome | 12/4/2018 | Edge | 1/15/2020 | 407 | |
| css.properties.text-underline-position.right π | Chrome | 12/4/2018 | Edge | 1/15/2020 | 407 | |
| css.properties.text-underline-position.under π | Chrome | 2/20/2014 | Edge | 1/15/2020 | 2155 | |
| css.properties.touch-action.pan-down | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | |
| css.properties.touch-action.pan-left | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | |
| css.properties.touch-action.pan-right | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | |
| css.properties.touch-action.pan-up | Chrome | 12/1/2016 | Edge | 1/15/2020 | 1140 | |
| css.properties.transform-box π | Chrome | 1/23/2018 | Edge | 1/15/2020 | 722 | |
| css.properties.transform-box.fill-box π | Chrome | 1/23/2018 | Edge | 1/15/2020 | 722 | |
| css.properties.transform-box.view-box π | Chrome | 1/23/2018 | Edge | 1/15/2020 | 722 | |
| css.properties.transition-timing-function.jump | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.properties.unicode-bidi.isolate π | Chrome | 1/20/2016 | Edge | 1/15/2020 | 1456 | 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 π | Chrome | 1/20/2016 | Edge | 1/15/2020 | 1456 | |
| css.properties.unicode-bidi.plaintext π | Chrome | 1/20/2016 | Edge | 1/15/2020 | 1456 | Firefox: Before Firefox 50, the plaintext value was ignored for vertical writing modes (bug 1302734).Firefox: Before Firefox 15, plaintext didn't do anything to an inline element. The specification changed and the implementation was changed in Firefox 15.Firefox for Android: Before Firefox for Android 50, the plaintext value was ignored for vertical writing modes (bug 1302734).Firefox for Android: Before Firefox for Android 15, plaintext didn't do anything to an inline element. The specification changed and the implementation was changed in Firefox for Android 15. |
| css.properties.user-select π | Chrome | 10/12/2016 | Edge | 1/15/2020 | 1190 | |
| css.properties.user-select.all | Chrome | 8/31/2016 | Edge | 1/15/2020 | 1232 | |
| css.properties.vector-effect π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.vector-effect.non-scaling-stroke π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.vector-effect.none π | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.properties.white-space.break-spaces π | Chrome | 7/30/2019 | Edge | 1/15/2020 | 169 | |
| css.properties.width.fit-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.width.max-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.width.min-content π | Chrome | 10/13/2015 | Edge | 1/15/2020 | 1555 | |
| css.properties.will-change π | Chrome | 7/16/2014 | Edge | 1/15/2020 | 2009 | |
| css.properties.will-change.auto π | Chrome | 7/16/2014 | Edge | 1/15/2020 | 2009 | |
| css.properties.will-change.contents π | Chrome | 7/16/2014 | Edge | 1/15/2020 | 2009 | |
| css.properties.will-change.scroll-position π | Chrome | 7/16/2014 | Edge | 1/15/2020 | 2009 | |
| css.properties.x π | Chrome | 4/14/2015 | Edge | 1/15/2020 | 1737 | |
| css.properties.y π | Chrome | 4/14/2015 | Edge | 1/15/2020 | 1737 | |
| css.selectors.-webkit-inner-spin-button | Chrome | 9/2/2010 | Edge | 1/15/2020 | 3422 | |
| css.selectors.-webkit-meter-bar | Chrome | 6/7/2011 | Edge | 1/15/2020 | 3144 | |
| css.selectors.-webkit-meter-even-less-good-value | Chrome | 6/7/2011 | Edge | 1/15/2020 | 3144 | |
| css.selectors.-webkit-meter-inner-element | Chrome | 11/6/2012 | Edge | 1/15/2020 | 2626 | |
| css.selectors.-webkit-meter-optimum-value | Chrome | 6/7/2011 | Edge | 1/15/2020 | 3144 | |
| css.selectors.-webkit-meter-suboptimum-value | Chrome | 6/7/2011 | Edge | 1/15/2020 | 3144 | |
| css.selectors.-webkit-progress-bar | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.selectors.-webkit-progress-inner-element | Chrome | 11/6/2012 | Edge | 1/15/2020 | 2626 | |
| css.selectors.-webkit-progress-value | Chrome | 2/21/2013 | Edge | 1/15/2020 | 2519 | |
| css.selectors.-webkit-resizer | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.selectors.-webkit-scrollbar | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | 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 | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.selectors.-webkit-scrollbar-corner | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.selectors.-webkit-scrollbar-thumb | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.selectors.-webkit-scrollbar-track | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.selectors.-webkit-scrollbar-track-piece | Chrome | 5/21/2009 | Edge | 1/15/2020 | 3891 | |
| css.selectors.-webkit-search-cancel-button | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.selectors.-webkit-search-results-button | Chrome | 12/11/2008 | Edge | 1/15/2020 | 4052 | |
| css.selectors.-webkit-slider-runnable-track | Chrome | 3/26/2013 | Edge | 1/15/2020 | 2486 | |
| css.selectors.-webkit-slider-thumb | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | |
| css.selectors.any-link π | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.selectors.any-link.not_match_link | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.selectors.attribute.case_insensitive_modifier | Chrome | 3/2/2016 | Edge | 1/15/2020 | 1414 | |
| css.selectors.backdrop π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.selectors.backdrop.dialog | Chrome | 1/14/2014 | Edge | 1/15/2020 | 2192 | |
| css.selectors.cue π | Chrome | 3/26/2013 | Edge | 1/15/2020 | 2486 | 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 | Chrome | 3/26/2013 | Edge | 1/15/2020 | 2486 | |
| css.selectors.default π | Chrome | 3/8/2011 | Edge | 1/15/2020 | 3235 | |
| css.selectors.defined π | Chrome | 10/12/2016 | Edge | 1/15/2020 | 1190 | |
| css.selectors.first-child.no_parent_required | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.selectors.focus-within π | Chrome | 7/25/2017 | Edge | 1/15/2020 | 904 | |
| css.selectors.future π | Chrome | 11/6/2012 | Edge | 1/15/2020 | 2626 | |
| css.selectors.host π | Chrome | 10/12/2016 | Edge | 1/15/2020 | 1190 | |
| css.selectors.host-context π | Chrome | 10/12/2016 | Edge | 1/15/2020 | 1190 | |
| css.selectors.hostfunction π | Chrome | 10/12/2016 | Edge | 1/15/2020 | 1190 | Safari: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy.Safari on iOS: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy.WebView on iOS: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy. |
| css.selectors.indeterminate.radio | Chrome | 11/18/2014 | Edge | 1/15/2020 | 1884 | |
| css.selectors.invalid.form | Chrome | 1/21/2015 | Edge | 1/15/2020 | 1820 | |
| css.selectors.last-child.no_parent_required | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.selectors.nth-child.no_parent_required | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.selectors.nth-last-child.no_parent_required | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.selectors.only-child.no_parent_required | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.selectors.part π | Chrome | 3/12/2019 | Edge | 1/15/2020 | 309 | |
| css.selectors.past π | Chrome | 11/6/2012 | Edge | 1/15/2020 | 2626 | |
| css.selectors.placeholder π | Chrome | 3/9/2017 | Edge | 1/15/2020 | 1042 | |
| css.selectors.placeholder-shown π | Chrome | 12/1/2015 | Edge | 1/15/2020 | 1506 | |
| css.selectors.placeholder-shown.non_text_types | Chrome | 12/1/2015 | Edge | 1/15/2020 | 1506 | |
| css.selectors.scope π | Chrome | 5/21/2013 | Edge | 1/15/2020 | 2430 | 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 | Chrome | 5/21/2013 | Edge | 1/15/2020 | 2430 | |
| css.selectors.slotted π | Chrome | 4/13/2016 | Edge | 1/15/2020 | 1372 | |
| css.selectors.valid.form | Chrome | 1/21/2015 | Edge | 1/15/2020 | 1820 | |
| css.types.basic-shape π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.types.basic-shape.animation | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.types.basic-shape.circle π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.types.basic-shape.ellipse π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.types.basic-shape.inset π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.types.basic-shape.path π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.types.basic-shape.path.d π | Chrome | 7/20/2016 | Edge | 1/15/2020 | 1274 | |
| css.types.basic-shape.path.offset-path π | Chrome | 1/25/2017 | Edge | 1/15/2020 | 1085 | |
| css.types.basic-shape.polygon π | Chrome | 8/26/2014 | Edge | 1/15/2020 | 1968 | |
| css.types.blend-mode π | Chrome | 5/20/2014 | Edge | 1/15/2020 | 2066 | |
| css.types.clamp π | Chrome | 12/10/2019 | Edge | 1/15/2020 | 36 | |
| css.types.color.hsl.alpha_parameter | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.types.color.hsl.space_separated_parameters | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.types.color.rgb.alpha_parameter | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.types.color.rgb.float_values | Chrome | 4/17/2018 | Edge | 1/15/2020 | 638 | |
| css.types.color.rgb.space_separated_parameters | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.types.color.rgb_hexadecimal_notation.alpha_hexadecimal_notation | Chrome | 10/17/2017 | Edge | 1/15/2020 | 820 | |
| css.types.easing-function.steps.jump | Chrome | 9/10/2019 | Edge | 1/15/2020 | 127 | |
| css.types.env π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.types.env.safe-area-inset-bottom π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.types.env.safe-area-inset-left π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.types.env.safe-area-inset-right π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.types.env.safe-area-inset-top π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.types.gradient.conic-gradient π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.types.gradient.conic-gradient.doubleposition | Chrome | 1/29/2019 | Edge | 1/15/2020 | 351 | |
| css.types.gradient.linear-gradient.doubleposition | Chrome | 12/4/2018 | Edge | 1/15/2020 | 407 | |
| css.types.gradient.linear-gradient.interpolation_hints | Chrome | 1/21/2015 | Edge | 1/15/2020 | 1820 | |
| css.types.gradient.linear-gradient.premultiplied_gradients | Chrome | 8/20/2013 | Edge | 1/15/2020 | 2339 | |
| css.types.gradient.radial-gradient.doubleposition | Chrome | 12/4/2018 | Edge | 1/15/2020 | 407 | |
| css.types.gradient.radial-gradient.interpolation_hints | Chrome | 1/21/2015 | Edge | 1/15/2020 | 1820 | |
| css.types.gradient.radial-gradient.premultiplied_gradients | Chrome | 8/20/2013 | Edge | 1/15/2020 | 2339 | |
| css.types.gradient.repeating-conic-gradient π | Chrome | 9/4/2018 | Edge | 1/15/2020 | 498 | |
| css.types.gradient.repeating-linear-gradient.doubleposition | Chrome | 12/4/2018 | Edge | 1/15/2020 | 407 | |
| css.types.gradient.repeating-linear-gradient.interpolation_hints | Chrome | 1/21/2015 | Edge | 1/15/2020 | 1820 | |
| css.types.gradient.repeating-radial-gradient.doubleposition | Chrome | 12/4/2018 | Edge | 1/15/2020 | 407 | |
| css.types.gradient.repeating-radial-gradient.interpolation_hints | Chrome | 1/21/2015 | Edge | 1/15/2020 | 1820 | |
| css.types.image.cross-fade π | Chrome | 2/8/2012 | Edge | 1/15/2020 | 2898 | 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.image.paint π | Chrome | 3/6/2018 | Edge | 1/15/2020 | 680 | |
| css.types.length.Q | Chrome | 12/6/2017 | Edge | 1/15/2020 | 770 | |
| css.types.max π | Chrome | 12/10/2019 | Edge | 1/15/2020 | 36 | |
| css.types.min π | Chrome | 12/10/2019 | Edge | 1/15/2020 | 36 | |
| css.types.resolution.x | Chrome | 7/24/2018 | Edge | 1/15/2020 | 540 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.font-optical-sizing π | Edge | 4/30/2018 | Chrome | 12/10/2019 | 589 | |
| css.properties.font-optical-sizing.auto π | Edge | 4/30/2018 | Chrome | 12/10/2019 | 589 | |
| css.properties.font-optical-sizing.none π | Edge | 4/30/2018 | Chrome | 12/10/2019 | 589 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.selectors.fullscreen π | Edge | 7/29/2015 | Chrome | 12/4/2018 | 1224 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.-webkit-mask-composite | Chrome | 12/11/2008 | Edge | 10/2/2018 | 3582 | |
| css.properties.-webkit-mask-position-x | Chrome | 12/11/2008 | Edge | 10/2/2018 | 3582 | |
| css.properties.-webkit-mask-position-y | Chrome | 12/11/2008 | Edge | 10/2/2018 | 3582 | |
| css.properties.font-stretch.percentage | Chrome | 10/17/2017 | Edge | 10/2/2018 | 350 | |
| css.properties.mask-image.multiple_mask_images | Chrome | 12/11/2008 | Edge | 10/2/2018 | 3582 | |
| css.properties.mask-image.svg_masks | Chrome | 12/2/2010 | Edge | 10/2/2018 | 2861 | |
| css.properties.overflow-wrap π | Chrome | 11/6/2012 | Edge | 10/2/2018 | 2156 | |
| css.properties.overscroll-behavior π | Chrome | 12/6/2017 | Edge | 10/2/2018 | 300 | |
| css.properties.overscroll-behavior-x π | Chrome | 12/6/2017 | Edge | 10/2/2018 | 300 | |
| css.properties.overscroll-behavior-x.auto π | Chrome | 12/6/2017 | Edge | 10/2/2018 | 300 | |
| css.properties.overscroll-behavior-x.contain π | Chrome | 12/6/2017 | Edge | 10/2/2018 | 300 | |
| css.properties.overscroll-behavior-y π | Chrome | 12/6/2017 | Edge | 10/2/2018 | 300 | |
| css.properties.overscroll-behavior-y.auto π | Chrome | 12/6/2017 | Edge | 10/2/2018 | 300 | |
| css.properties.overscroll-behavior-y.contain π | Chrome | 12/6/2017 | Edge | 10/2/2018 | 300 | |
| css.properties.text-transform.uppercase_eszett | Chrome | 12/11/2008 | Edge | 10/2/2018 | 3582 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.selectors.backdrop.fullscreen | Edge | 7/29/2015 | Chrome | 9/4/2018 | 1133 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.cursor.grab | Edge | 8/2/2016 | Chrome | 7/24/2018 | 721 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.font-face.font-stretch π | Chrome | 10/17/2017 | Edge | 4/30/2018 | 195 | |
| css.at-rules.font-face.src.format_variations | Chrome | 4/17/2018 | Edge | 4/30/2018 | 13 | |
| css.properties.font-variation-settings π | Chrome | 10/17/2017 | Edge | 4/30/2018 | 195 | 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 π | Chrome | 10/17/2017 | Edge | 4/30/2018 | 195 | |
| css.properties.font-weight.number | Chrome | 10/17/2017 | Edge | 4/30/2018 | 195 | |
| css.properties.line-clamp π | Chrome | 9/2/2010 | Edge | 4/30/2018 | 2797 | Safari: Accidental exposure.Safari on iOS: Accidental exposure.WebView on iOS: Accidental exposure. |
| css.properties.transform-origin.svg_elements | Chrome | 5/15/2012 | Edge | 4/30/2018 | 2176 | 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.column-gap.grid_context π | Edge | 10/17/2017 | Chrome | 4/17/2018 | 182 | |
| css.properties.column-gap.multicol_context.calc_values | Edge | 10/17/2017 | Chrome | 4/17/2018 | 182 | |
| css.properties.column-gap.multicol_context.percentage_values | Edge | 10/17/2017 | Chrome | 4/17/2018 | 182 | |
| css.properties.gap.grid_context π | Edge | 10/17/2017 | Chrome | 4/17/2018 | 182 | |
| css.properties.gap.grid_context.calc_values | Edge | 10/17/2017 | Chrome | 4/17/2018 | 182 | |
| css.properties.gap.grid_context.percentage_values | Edge | 10/17/2017 | Chrome | 4/17/2018 | 182 | |
| css.properties.gap.multicol_context π | Edge | 10/17/2017 | Chrome | 4/17/2018 | 182 | |
| css.properties.row-gap.grid_context π | Edge | 10/17/2017 | Chrome | 4/17/2018 | 182 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.media.any-hover π | Chrome | 3/3/2015 | Edge | 10/17/2017 | 959 | |
| css.properties.align-content.grid_context π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.align-items.grid_context π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.align-self.grid_context π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | Internet Explorer: Internet Explorer 10 and 11 have the property -ms-grid-row-align, which acts in a similar way to align-self. |
| css.properties.display.grid | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | 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 | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | 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 π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.gap.normal π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | Samsung Internet: This was added early so is out of sync with the equivalent Chromium version. |
| css.properties.grid.none π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-area π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-area.auto π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-auto-columns π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | 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 π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-auto-columns.max-content π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-auto-columns.min-content π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-auto-flow π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-auto-rows π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | 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 π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-auto-rows.max-content π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-auto-rows.min-content π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-column π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-column.auto π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-column-end π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-column-end.auto π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-column-start π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-column-start.auto π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-row π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-row.auto π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-row-end π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-row-end.auto π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-row-start π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-row-start.auto π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template-areas π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template-columns π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template-columns.fit-content π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template-columns.minmax π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template-columns.repeat π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | 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 π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template-rows.fit-content π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template-rows.minmax π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.grid-template-rows.repeat π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | Firefox: repeat(auto-fill, ...) and repeat(auto-fit, ...) only support one repeated column (see bug 1341507).Firefox: calc() doesn't work in repeat() (see bug 1350069).Firefox for Android: repeat(auto-fill, ...) and repeat(auto-fit, ...) only support one repeated column (see bug 1341507).Firefox for Android: calc() doesn't work in repeat() (see bug 1350069). |
| css.properties.justify-content.grid_context π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.justify-items.grid_context π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.justify-self π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | |
| css.properties.justify-self.grid_context π | Chrome | 3/9/2017 | Edge | 10/17/2017 | 222 | Internet Explorer: Internet Explorer 10 and 11 have the property -ms-grid-column-align, which acts in a similar way to justify-self. |
| css.properties.object-position.bottom π | Chrome | 1/14/2014 | Edge | 10/17/2017 | 1372 | |
| css.properties.object-position.center π | Chrome | 1/14/2014 | Edge | 10/17/2017 | 1372 | |
| css.properties.object-position.left π | Chrome | 1/14/2014 | Edge | 10/17/2017 | 1372 | |
| css.properties.object-position.right π | Chrome | 1/14/2014 | Edge | 10/17/2017 | 1372 | |
| css.properties.object-position.top π | Chrome | 1/14/2014 | Edge | 10/17/2017 | 1372 | |
| css.properties.position.position_sticky_table_elements | Chrome | 1/25/2017 | Edge | 10/17/2017 | 265 | 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 π | Chrome | 1/25/2017 | Edge | 10/17/2017 | 265 | |
| css.properties.row-gap π | Chrome | 12/1/2015 | Edge | 10/17/2017 | 686 | |
| css.properties.row-gap.normal π | Chrome | 12/1/2015 | Edge | 10/17/2017 | 686 | |
| css.types.calc.nested | Chrome | 5/25/2016 | Edge | 10/17/2017 | 510 | |
| css.types.length.vmax | Chrome | 3/26/2013 | Edge | 10/17/2017 | 1666 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.font-stretch π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | 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 π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | |
| css.properties.font-stretch.expanded π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | |
| css.properties.font-stretch.extra-condensed π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | |
| css.properties.font-stretch.extra-expanded π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | |
| css.properties.font-stretch.normal π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | |
| css.properties.font-stretch.semi-condensed π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | |
| css.properties.font-stretch.semi-expanded π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | |
| css.properties.font-stretch.ultra-condensed π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 | |
| css.properties.font-stretch.ultra-expanded π | Edge | 7/29/2015 | Chrome | 7/25/2017 | 727 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.line-break π | Edge | 8/2/2016 | Chrome | 4/19/2017 | 260 | |
| css.properties.-webkit-text-stroke π | Chrome | 1/25/2010 | Edge | 4/5/2017 | 2627 | |
| css.properties.-webkit-text-stroke-color π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.-webkit-text-stroke-width π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.background.border-box π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background.bottom π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background.center π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background.content-box π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background.fixed π | Chrome | 10/25/2011 | Edge | 4/5/2017 | 1989 | |
| css.properties.background.left π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background.padding-box π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background.right π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background.top π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.background-color.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-bottom.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-bottom-color.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-color.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-left.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-left-color.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-right.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-right-color.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-top.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.border-top-color.currentColor π | Chrome | 11/12/2013 | Edge | 4/5/2017 | 1240 | |
| css.properties.custom-property π | Chrome | 3/2/2016 | Edge | 4/5/2017 | 399 | |
| css.properties.display.table-caption | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.fill π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.fill.none π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.fill-opacity π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.fill-rule π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.fill-rule.evenodd π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.fill-rule.nonzero π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.font-feature-settings π | Chrome | 1/20/2016 | Edge | 4/5/2017 | 441 | Firefox: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox: From Firefox 129 the -webkit-font-feature-settings alias has been added to support sites that are still supporting the vendor prefix.Firefox: From Firefox 4 to Firefox 14 (inclusive), Firefox supported an older, slightly different syntax. See OpenType Font Feature support in Firefox 4.Firefox for Android: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox for Android 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox for Android 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox for Android: From Firefox for Android 129 the -webkit-font-feature-settings alias has been added to support sites that are still supporting the vendor prefix.Firefox for Android: From Firefox for Android 4 to Firefox for Android 14 (inclusive), Firefox for Android supported an older, slightly different syntax. See OpenType Font Feature support in Firefox for Android 4. |
| css.properties.font-feature-settings.normal π | Chrome | 12/13/2011 | Edge | 4/5/2017 | 1940 | |
| css.properties.marker π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.marker.none π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.marker-end π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.marker-end.none π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.marker-mid π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.marker-mid.none π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.marker-start π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.marker-start.none π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.outline-offset π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius. |
| css.properties.stop-color π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stop-opacity π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke.none π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-dasharray π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-dasharray.none π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-dashoffset π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-linecap π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-linecap.butt π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-linecap.round π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-linecap.square π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-linejoin π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-linejoin.bevel π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-linejoin.miter π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-linejoin.round π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-miterlimit π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-opacity π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.properties.stroke-width π | Chrome | 12/11/2008 | Edge | 4/5/2017 | 3037 | |
| css.types.var π | Chrome | 3/2/2016 | Edge | 4/5/2017 | 399 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.border-image-repeat.space π | Edge | 7/29/2015 | Chrome | 1/25/2017 | 546 | |
| css.properties.touch-action.pinch-zoom | Edge | 7/29/2015 | Chrome | 1/25/2017 | 546 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.hyphens.language_english | Edge | 7/29/2015 | Chrome | 12/1/2016 | 491 | 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. |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.text-size-adjust.percentages π | Edge | 7/29/2015 | Chrome | 10/12/2016 | 441 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.filter π | Edge | 7/29/2015 | Chrome | 8/31/2016 | 399 | 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.at-rules.font-face.WOFF_2 π | Chrome | 7/16/2014 | Edge | 8/2/2016 | 748 | Safari: Supported only on macOS 10.12 (Sierra) and later. |
| css.properties.text-anchor π | Chrome | 12/11/2008 | Edge | 8/2/2016 | 2791 | |
| css.properties.text-anchor.end π | Chrome | 12/11/2008 | Edge | 8/2/2016 | 2791 | |
| css.properties.text-anchor.middle π | Chrome | 12/11/2008 | Edge | 8/2/2016 | 2791 | |
| css.properties.text-anchor.start π | Chrome | 12/11/2008 | Edge | 8/2/2016 | 2791 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.align-items.flex_context π | Edge | 7/29/2015 | Chrome | 7/20/2016 | 357 | 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.justify-content.flex_context π | Edge | 7/29/2015 | Chrome | 7/20/2016 | 357 | 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 π | Edge | 7/29/2015 | Chrome | 7/20/2016 | 357 | |
| css.properties.justify-items.flex_context π | Edge | 7/29/2015 | Chrome | 7/20/2016 | 357 | |
| css.properties.position.absolutely_positioned_flex_children | Edge | 7/29/2015 | Chrome | 7/20/2016 | 357 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.break-before.multicol_context.column | Edge | 7/29/2015 | Chrome | 5/25/2016 | 301 | |
| css.properties.break-inside.paged_context.avoid-page | Edge | 7/29/2015 | Chrome | 5/25/2016 | 301 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.break-after π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-after.multicol_context π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | 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 | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-after.paged_context π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-after.paged_context.avoid-page | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-after.paged_context.page | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-before π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-before.multicol_context π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | Firefox: Only supported in print mode. See bug 1675322.Firefox for Android: Only supported in print mode. See bug 1675322. |
| css.properties.break-before.paged_context π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-before.paged_context.page | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-inside π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-inside.multicol_context π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-inside.multicol_context.avoid-column | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.break-inside.paged_context π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.column-count π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | 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 π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.column-fill.auto π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.column-fill.balance π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.column-gap.multicol_context π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em. |
| css.properties.column-rule π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em. |
| css.properties.column-rule-color π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.column-rule-style π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.column-rule-width π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.column-span π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | |
| css.properties.column-width π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | 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 π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 | 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 π | Edge | 7/29/2015 | Chrome | 4/13/2016 | 259 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.writing-mode π | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | 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 | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | |
| css.properties.writing-mode.lr | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | |
| css.properties.writing-mode.lr-tb | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | |
| css.properties.writing-mode.rl | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | |
| css.properties.writing-mode.rl-tb | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | |
| css.properties.writing-mode.tb | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | |
| css.properties.writing-mode.tb-rl | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | |
| css.properties.writing-mode.vertical-lr | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 | |
| css.properties.writing-mode.vertical-rl | Edge | 7/29/2015 | Chrome | 1/20/2016 | 175 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.properties.text-align-last π | Edge | 7/29/2015 | Chrome | 12/1/2015 | 125 | 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 π | Edge | 7/29/2015 | Chrome | 12/1/2015 | 125 | |
| css.properties.text-align-last.center π | Edge | 7/29/2015 | Chrome | 12/1/2015 | 125 | |
| css.properties.text-align-last.justify π | Edge | 7/29/2015 | Chrome | 12/1/2015 | 125 | |
| css.properties.text-align-last.left π | Edge | 7/29/2015 | Chrome | 12/1/2015 | 125 | |
| css.properties.text-align-last.right π | Edge | 7/29/2015 | Chrome | 12/1/2015 | 125 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.selectors.in-range π | Chrome | 3/8/2011 | Edge | 11/12/2015 | 1710 | Chrome: Before Chrome 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome 52, it was changed to only match enabled read-write inputs.Chrome Android: Before Chrome Android 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome Android 52, it was changed to only match enabled read-write inputs.Firefox: Before Firefox 50, :in-range matched disabled and read-only inputs (see bug 1264157). In Firefox 50, it was changed to only match enabled read-write inputs.Quest Browser: Before Quest Browser 5.0, :in-range matched disabled and read-only inputs (see bug 41248615). In Quest Browser 5.0, it was changed to only match enabled read-write inputs.Opera: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Opera Android: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Safari: In Safari, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Safari on iOS: In Safari on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Samsung Internet: Before version 6.0, :in-range matched disabled and read-only inputs (see bug 41248615). In version 6.0, it was changed to only match enabled read-write inputs.WebView Android: Before version 52, :in-range matched disabled and read-only inputs (see bug 41248615). In version 52, it was changed to only match enabled read-write inputs.WebView on iOS: In WebView on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs. |
| css.selectors.out-of-range π | Chrome | 3/8/2011 | Edge | 11/12/2015 | 1710 | |
| css.selectors.read-only π | Chrome | 12/11/2008 | Edge | 11/12/2015 | 2527 | |
| css.selectors.read-write π | Chrome | 12/11/2008 | Edge | 11/12/2015 | 2527 | |
| css.types.global_keywords.initial π | Chrome | 12/11/2008 | Edge | 11/12/2015 | 2527 | |
| css.types.global_keywords.unset π | Chrome | 3/3/2015 | Edge | 11/12/2015 | 254 |
| API | First Browser | Date | Last Browser | Date | Days | Notes |
|---|---|---|---|---|---|---|
| css.at-rules.charset π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.font-face.WOFF π | Chrome | 9/2/2010 | Edge | 7/29/2015 | 1791 | |
| css.at-rules.font-face.font-family π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.at-rules.font-face.font-style π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.at-rules.font-face.font-variant | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.at-rules.font-face.font-weight π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.at-rules.font-face.src π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.at-rules.font-face.unicode-range π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.import π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.keyframes π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | |
| css.at-rules.media π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.media.-webkit-device-pixel-ratio π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.at-rules.media.any-pointer π | Chrome | 3/3/2015 | Edge | 7/29/2015 | 148 | |
| css.at-rules.media.aspect-ratio π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.at-rules.media.color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.media.device-aspect-ratio π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.media.device-height π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.media.device-width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.media.grid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.media.height π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.media.hover π | Chrome | 10/7/2014 | Edge | 7/29/2015 | 295 | 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.media_features | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.media.nested-queries | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.at-rules.media.orientation π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.at-rules.media.pointer π | Chrome | 3/3/2015 | Edge | 7/29/2015 | 148 | |
| css.at-rules.media.resolution π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.at-rules.media.width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.namespace π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.at-rules.page π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.at-rules.supports π | Chrome | 7/9/2013 | Edge | 7/29/2015 | 750 | |
| css.properties.-webkit-tap-highlight-color | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.-webkit-text-fill-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.align-content π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.properties.align-content.flex_context π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.align-content.normal π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.properties.align-items π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.properties.align-self π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.properties.align-self.flex_context π | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | Chrome: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome implements the new behavior beginning with Chrome 52.Chrome Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome Android implements the new behavior beginning with Chrome Android 52.Firefox: Before Firefox 27, only single-line flexbox is supported.Firefox for Android: Before Firefox for Android 27, only single-line flexbox is supported.Samsung Internet: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Samsung Internet implements the new behavior beginning with Samsung Internet 6.0.WebView Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. WebView Android implements the new behavior beginning with WebView Android 52. |
| css.properties.animation π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | WebView Android: The animation-fill-mode property is not supported in Android browsers below 2.3. |
| css.properties.animation.alternate π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.alternate-reverse π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.auto π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.backwards π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.both π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.ease π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.ease-in π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.ease-in-out π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.ease-out π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.forwards π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.infinite π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.linear π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.none π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.normal π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.reverse π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.step-end π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation.step-start π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-delay π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | 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 π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | |
| css.properties.animation-direction.alternate π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-direction.alternate-reverse π | Chrome | 5/15/2012 | Edge | 7/29/2015 | 1170 | |
| css.properties.animation-direction.normal π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-direction.reverse π | Chrome | 5/15/2012 | Edge | 7/29/2015 | 1170 | |
| css.properties.animation-duration π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | Internet Explorer: Once the element has loaded, changing the value of this property has no effect. |
| css.properties.animation-fill-mode π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | |
| css.properties.animation-fill-mode.backwards π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-fill-mode.both π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-fill-mode.forwards π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-fill-mode.none π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-iteration-count π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | |
| css.properties.animation-iteration-count.infinite π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-name π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | |
| css.properties.animation-name.none π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-play-state π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | |
| css.properties.animation-play-state.paused π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-play-state.running π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-timing-function π | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | |
| css.properties.animation-timing-function.ease π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-timing-function.ease-in π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-timing-function.ease-in-out π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-timing-function.ease-out π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-timing-function.linear π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-timing-function.step-end π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.animation-timing-function.step-start π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.appearance.button π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.checkbox π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.listbox π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.menulist π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.menulist-button π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Firefox: See bug 1481615.Firefox for Android: See bug 1481615. |
| css.properties.appearance.meter π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.radio π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.searchfield π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.textarea π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.appearance.textfield π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.backface-visibility π | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | |
| css.properties.backface-visibility.hidden π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.backface-visibility.visible π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.background π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.SVG_image_as_background | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.background-clip | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.background.background-origin | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.background.background-size | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.background.local π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.multiple_backgrounds | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.no-repeat π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.repeat π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.repeat-x π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.repeat-y π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.round π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.scroll π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.space π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-attachment π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-attachment.fixed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-attachment.scroll π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-clip π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-clip.content-box π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-image π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-image.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-image.svg_images | Chrome | 12/2/2010 | Edge | 7/29/2015 | 1700 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-origin.content-box π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-position π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-position.multiple_backgrounds | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-position.side-relative_values | Chrome | 2/21/2013 | Edge | 7/29/2015 | 888 | |
| css.properties.background-position-x π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-position-y π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-repeat π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-repeat.2-value | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.background-repeat.multiple_backgrounds | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-repeat.no-repeat π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-repeat.repeat π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-repeat.repeat-x π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-repeat.repeat-y π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-repeat.round π | Chrome | 10/1/2013 | Edge | 7/29/2015 | 666 | |
| css.properties.background-repeat.space π | Chrome | 10/1/2013 | Edge | 7/29/2015 | 666 | |
| css.properties.background-size π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.background-size.contain π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.background-size.cover π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.properties.border π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-left-radius π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-left-radius.percentages | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-right-radius.percentages | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-style.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-width.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-width.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-bottom-width.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-collapse π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-image π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | 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 | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.border-image.gradient | Chrome | 10/19/2010 | Edge | 7/29/2015 | 1744 | |
| css.properties.border-image.none π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.border-image.optional_border_image_slice | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.border-image.repeat π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.border-image.round π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.border-image.space π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.border-image.stretch π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.border-image-outset π | Chrome | 10/25/2011 | Edge | 7/29/2015 | 1373 | |
| css.properties.border-image-repeat π | Chrome | 10/25/2011 | Edge | 7/29/2015 | 1373 | |
| css.properties.border-image-repeat.repeat π | Chrome | 10/25/2011 | Edge | 7/29/2015 | 1373 | |
| css.properties.border-image-repeat.round π | Chrome | 10/1/2013 | Edge | 7/29/2015 | 666 | |
| css.properties.border-image-repeat.stretch π | Chrome | 10/25/2011 | Edge | 7/29/2015 | 1373 | |
| css.properties.border-image-slice π | Chrome | 10/25/2011 | Edge | 7/29/2015 | 1373 | 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 π | Chrome | 10/25/2011 | Edge | 7/29/2015 | 1373 | |
| css.properties.border-image-source.none π | Chrome | 10/25/2011 | Edge | 7/29/2015 | 1373 | |
| css.properties.border-image-width π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | 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 π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.properties.border-left π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-style.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-width.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-width.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-left-width.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-radius π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.properties.border-radius.elliptical_borders | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 | Chrome | 12/2/2010 | Edge | 7/29/2015 | 1700 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-style.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-width.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-width.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-right-width.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-spacing π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-style.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-left-radius π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-left-radius.percentages | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-right-radius.percentages | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-style.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-width.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-width.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-top-width.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-width.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-width.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.border-width.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.bottom π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-align | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-direction | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-flex | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-ordinal-group | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-orient | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-pack | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-shadow π | Chrome | 3/8/2011 | Edge | 7/29/2015 | 1604 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Internet Explorer: inset must be the last keyword in the declaration. |
| css.properties.box-shadow.multiple_shadows | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-shadow.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-shadow.spread_radius | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-sizing π | Chrome | 3/8/2011 | Edge | 7/29/2015 | 1604 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.box-sizing.content-box π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.caption-side π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.clear π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.clear.both π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.clear.left π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.clear.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.clear.right π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.clip π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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-path.svg_elements | Chrome | 11/6/2012 | Edge | 7/29/2015 | 995 | |
| css.properties.color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-count.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-gap π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-gap.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-style.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-width.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-width.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-rule-width.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.column-span.all π | Chrome | 9/2/2010 | Edge | 7/29/2015 | 1791 | |
| css.properties.column-span.none π | Chrome | 9/2/2010 | Edge | 7/29/2015 | 1791 | |
| css.properties.column-width.auto | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.content π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.content.close-quote π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.content.gradient π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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.content.no-close-quote π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.content.no-open-quote π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.content.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.content.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.content.open-quote π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.content.url π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.counter-increment π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.counter-increment.list-item π | Chrome | 7/9/2013 | Edge | 7/29/2015 | 750 | |
| css.properties.counter-increment.none π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.counter-reset π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.counter-reset.list-item π | Chrome | 7/9/2013 | Edge | 7/29/2015 | 750 | Chrome: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Chrome Android: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Quest Browser: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Opera: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Opera Android: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.Safari: Overriding the initial value of the implicit list-item counter results in incorrect values for the counter() function used to generate content, as it is not fully implemented; see bug 260436.Safari on iOS: Overriding the initial value of the implicit list-item counter results in incorrect values for the counter() function used to generate content, as it is not fully implemented; see bug 260436.Samsung Internet: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.WebView Android: Overriding the initial value of the implicit list-item counter has no effect when the default marker string for list items (::marker) is generated; see bug 338233131.WebView on iOS: Overriding the initial value of the implicit list-item counter results in incorrect values for the counter() function used to generate content, as it is not fully implemented; see bug 260436. |
| css.properties.counter-reset.none π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.cursor π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.cursor.cell π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.cursor.col-resize π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 5/25/2010 | Edge | 7/29/2015 | 1891 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.cursor.url | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Firefox: Firefox 4 added macOS support. |
| css.properties.cursor.vertical-text π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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-in π | Chrome | 8/26/2014 | Edge | 7/29/2015 | 337 | 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 π | Chrome | 8/26/2014 | Edge | 7/29/2015 | 337 | 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 π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.direction.ltr π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.direction.rtl π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.display π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.block π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.flex | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.inline-block | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Internet Explorer: Until Internet Explorer 8, inline-block is only for natural inline elements. |
| css.properties.display.inline-flex | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | Firefox: Firefox 28 added multi-line flexbox support.Firefox for Android: Firefox for Android 28 added multi-line flexbox support. |
| css.properties.display.inline-table | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.list-item π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Chrome: Chrome 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.Chrome Android: Chrome Android 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.Quest Browser: Quest Browser 5.0 stopped creating layout objects for elements inside an <iframe> with display:none applied.Opera: Opera 52 stopped creating layout objects for elements inside an <iframe> with display:none applied.Opera Android: Opera Android 47 stopped creating layout objects for elements inside an <iframe> with display:none applied.Samsung Internet: Chrome 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.WebView Android: WebView Android 65 stopped creating layout objects for elements inside an <iframe> with display:none applied. |
| css.properties.display.table | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.table-cell | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.table-column | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.table-column-group | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.table-footer-group | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.table-header-group | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.table-row | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.display.table-row-group | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.empty-cells π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.empty-cells.hide π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.empty-cells.show π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.filter.blur π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.brightness π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.contrast π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.drop-shadow π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.grayscale π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.hue-rotate π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.invert π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.none π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.opacity π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.filter.saturate π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | 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 π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.flex π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | 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.auto π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex.none π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-basis π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Internet Explorer: When a non- auto flex-basis is specified, Internet Explorer 10 and 11 always uses a content-box box model to calculate the size of a flex item, even if box-sizing: border-box is applied to the element. See Flexbug #7 for more info. |
| css.properties.flex-basis.auto | Chrome | 9/25/2012 | Edge | 7/29/2015 | 1037 | |
| css.properties.flex-direction π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | 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-direction.column π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-direction.column-reverse π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | 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 π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-direction.row-reverse π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | 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 π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.properties.flex-flow.column π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-flow.column-reverse π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-flow.nowrap π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-flow.row π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-flow.row-reverse π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-flow.wrap π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-flow.wrap-reverse π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-grow π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | 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 π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | 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 π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | Internet Explorer: Partial support due to large number of bugs present. See Flexbugs. |
| css.properties.flex-wrap.nowrap π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-wrap.wrap π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.flex-wrap.wrap-reverse π | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | |
| css.properties.float π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.float.left π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.float.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.float.right π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.flood-color π | Chrome | 5/25/2010 | Edge | 7/29/2015 | 1891 | |
| css.properties.flood-color.currentColor π | Chrome | 5/25/2010 | Edge | 7/29/2015 | 1891 | |
| css.properties.flood-color.transparent π | Chrome | 5/25/2010 | Edge | 7/29/2015 | 1891 | |
| css.properties.flood-opacity π | Chrome | 5/25/2010 | Edge | 7/29/2015 | 1891 | |
| css.properties.font π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font.caption | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font.icon | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font.menu | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font.message-box | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font.small-caption | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font.status-bar | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family.fangsong π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family.fantasy π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family.kai π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family.khmer-mul π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family.monospace π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family.nastaliq π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family.sans-serif π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-family.serif π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-size π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-size.rem_values | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | Firefox: Before Firefox 57, animations using em units are not affected by changes to the font-size of the animated element's parent (bug 1254424).Firefox: Before Firefox 57, some language settings' inherited font-size is smaller than expected (bug 1391341). |
| css.properties.font-style π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-style.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-style.oblique π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-variant π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Internet Explorer: Only supports the small-caps and normal keywords. |
| css.properties.font-variant.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.font-variant.turkic_is | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | |
| css.properties.font-weight π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.font-weight.bold π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.font-weight.bolder π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.font-weight.lighter π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.font-weight.normal π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.height π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.height.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.justify-content π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.properties.left π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.left.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.letter-spacing π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.letter-spacing.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.letter-spacing.svg_elements | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.lighting-color π | Chrome | 5/25/2010 | Edge | 7/29/2015 | 1891 | |
| css.properties.lighting-color.currentColor π | Chrome | 5/25/2010 | Edge | 7/29/2015 | 1891 | |
| css.properties.lighting-color.transparent π | Chrome | 5/25/2010 | Edge | 7/29/2015 | 1891 | |
| css.properties.line-height π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.line-height.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style.inside π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style.outside π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-image π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-position π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-position.outside π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.armenian π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.circle π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.decimal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.decimal-leading-zero π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.disc π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.georgian π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.hebrew π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.hiragana π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.hiragana-iroha π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.katakana π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.katakana-iroha π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.lower-alpha π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.lower-greek π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.lower-latin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.lower-roman π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.square π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.upper-alpha π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.upper-latin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.list-style-type.upper-roman π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.margin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.margin.auto | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.margin-bottom.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.margin-left.auto | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.margin-right.auto | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.margin-top.auto | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode. |
| css.properties.max-height π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.max-height.none π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.properties.max-width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.min-height π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Firefox: CSS 2.1 leaves the behavior of min-height with table undefined. Firefox supports applying min-height to table elements.Firefox for Android: CSS 2.1 leaves the behavior of min-height with table undefined. Firefox for Android supports applying min-height to table elements.Internet Explorer: In Internet Explorer 10 and 11, a min-height declaration on a column-direction flex container doesn't apply to the container's flex items. See Flexbug #3 for more info.Opera: CSS 2.1 leaves the behavior of min-height with table undefined. Opera supports applying min-height to table elements. |
| css.properties.min-height.auto | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Firefox: CSS 2.1 leaves the behavior of min-width with table undefined. Firefox supports applying min-width to table elements.Firefox for Android: CSS 2.1 leaves the behavior of min-width with table undefined. Firefox for Android supports applying min-width to table elements.Opera: CSS 2.1 leaves the behavior of min-width with table undefined. Opera supports applying min-width to table elements. |
| css.properties.min-width.auto | Chrome | 7/31/2012 | Edge | 7/29/2015 | 1093 | Chrome: Chrome uses auto as the initial value for min-width.Chrome Android: Chrome Android uses auto as the initial value for min-width.Edge: Edge uses auto as the initial value for min-width.Firefox: Firefox 18 and later (until the value was removed), used auto as the initial value for min-width.Firefox for Android: Firefox for Android 18 and later (until the value was removed), used auto as the initial value for min-width.Quest Browser: Quest Browser uses auto as the initial value for min-width.Opera: Opera uses auto as the initial value for min-width.Opera Android: Opera Android uses auto as the initial value for min-width.Samsung Internet: Samsung Internet uses auto as the initial value for min-width.WebView Android: WebView Android uses auto as the initial value for min-width. |
| css.properties.opacity π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.order π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported. |
| css.properties.orphans π | Chrome | 2/21/2013 | Edge | 7/29/2015 | 888 | |
| css.properties.outline.currentColor π | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | |
| css.properties.outline.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.medium π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.dashed π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.dotted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.double π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.groove π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.inset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.outset π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.ridge π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-style.solid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-width.thick π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.outline-width.thin π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow.hidden π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow.scroll π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow.visible π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-wrap.break-word π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-wrap.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-x π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-x.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-x.scroll π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-x.visible π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-y π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-y.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-y.scroll π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.overflow-y.visible π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.padding π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.padding-bottom π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.padding-left π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.padding-right π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.padding-top π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-after π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-after.always π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-after.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-after.avoid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-after.left π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-after.right π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-before π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-before.always π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-before.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-before.avoid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-before.left π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-before.right π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-inside π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-inside.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.page-break-inside.avoid π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | 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.none π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.perspective-origin π | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | |
| css.properties.perspective-origin.bottom π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.perspective-origin.center π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.perspective-origin.left π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.perspective-origin.right π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.perspective-origin.top π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.pointer-events π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.pointer-events.all π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.pointer-events.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.pointer-events.fill π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.pointer-events.html_elements | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.pointer-events.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.pointer-events.painted π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.pointer-events.stroke π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.pointer-events.visible π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.pointer-events.visibleFill π | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | |
| css.properties.pointer-events.visiblePainted π | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | |
| css.properties.pointer-events.visibleStroke π | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | |
| css.properties.position π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.position.absolute π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.position.static π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.quotes π | Chrome | 4/27/2011 | Edge | 7/29/2015 | 1554 | |
| css.properties.quotes.none π | Chrome | 4/27/2011 | Edge | 7/29/2015 | 1554 | |
| css.properties.right π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.right.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.table-layout π | Chrome | 9/16/2011 | Edge | 7/29/2015 | 1412 | |
| css.properties.table-layout.auto π | Chrome | 9/16/2011 | Edge | 7/29/2015 | 1412 | |
| css.properties.table-layout.fixed π | Chrome | 9/16/2011 | Edge | 7/29/2015 | 1412 | |
| css.properties.text-align π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-align.justify π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-decoration π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-decoration.blink π | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | Chrome: The blink value does not have any effect.Chrome Android: The blink value does not have any effect.Firefox: The blink value does not have any effect.Firefox for Android: The blink value does not have any effect.Quest Browser: The blink value does not have any effect.Opera: The blink value does not have any effect.Opera Android: The blink value does not have any effect.Safari: The blink value does not have any effect.Safari on iOS: The blink value does not have any effect.Samsung Internet: The blink value does not have any effect.WebView Android: The blink value does not have any effect.WebView on iOS: The blink value does not have any effect. |
| css.properties.text-decoration.line-through π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-decoration.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-decoration.overline π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-decoration.underline π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-indent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-overflow π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-overflow.ellipsis π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-shadow π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | 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 π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.text-transform π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-transform.lowercase_sigma | Chrome | 10/1/2013 | Edge | 7/29/2015 | 666 | |
| css.properties.text-transform.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-transform.turkic_is | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | |
| css.properties.text-transform.uppercase π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.text-underline-position π | Chrome | 2/20/2014 | Edge | 7/29/2015 | 524 | |
| css.properties.top π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.touch-action π | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events. |
| css.properties.touch-action.manipulation | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events. |
| css.properties.touch-action.none | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events. |
| css.properties.touch-action.pan-x | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events. |
| css.properties.touch-action.pan-y | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events. |
| css.properties.transform π | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | 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.3d | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.transform.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transform-origin π | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | |
| css.properties.transform-origin.bottom π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transform-origin.center π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transform-origin.left π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transform-origin.right π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transform-origin.three_value_syntax | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.transform-origin.top π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transform-style π | Chrome | 7/16/2014 | Edge | 7/29/2015 | 378 | Safari: Before Safari 17, ::before and ::after pseudo elements were not included in the 3D rendering context (see bug 256430). |
| css.properties.transform-style.flat π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.transform-style.preserve-3d π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.properties.transition π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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.all π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition.allow-discrete π | Chrome | 8/26/2014 | Edge | 7/29/2015 | 337 | |
| css.properties.transition.ease π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition.ease-in π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition.ease-in-out π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition.ease-out π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition.linear π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition.normal π | Chrome | 8/26/2014 | Edge | 7/29/2015 | 337 | |
| css.properties.transition.step-end π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition.step-start π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-delay π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.properties.transition-duration π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.properties.transition-property π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.properties.transition-property.IDENT_value | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-property.all π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-property.none π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-timing-function π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.properties.transition-timing-function.ease π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-timing-function.ease-in π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-timing-function.ease-in-out π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-timing-function.ease-out π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-timing-function.linear π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-timing-function.step-end π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.transition-timing-function.step-start π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.unicode-bidi π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.unicode-bidi.bidi-override π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.unicode-bidi.embed π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.unicode-bidi.normal π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.properties.user-modify | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.user-select.auto | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.user-select.none | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.user-select.text | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align.baseline π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align.bottom π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align.middle π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align.sub π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align.super π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align.text-bottom π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align.text-top π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.vertical-align.top π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.visibility π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.visibility.visible π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.white-space π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.white-space.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.white-space.nowrap π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.white-space.pre π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.white-space.pre-line π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.white-space.pre-wrap π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.widows π | Chrome | 2/21/2013 | Edge | 7/29/2015 | 888 | |
| css.properties.width π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.width.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.width.is_animatable | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.properties.word-break π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.word-break.break-word π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.word-break.keep-all π | Chrome | 7/21/2015 | Edge | 7/29/2015 | 8 | |
| css.properties.word-break.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.word-spacing π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.word-spacing.normal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.word-spacing.svg_elements | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.z-index π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.z-index.auto π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.z-index.negative_values | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.properties.zoom π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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.active π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.active.non_a_elements | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Firefox: Before Firefox 57, Firefox had a bug where ::after pseudo-elements were still generated, even if the content property value were set to normal or none.Firefox: Before Firefox 3.5, only the CSS level 2 behavior of :after was supported, which disallowed position, float, list-style-* and some display properties.Firefox for Android: Before Firefox for Android 57, Firefox for Android had a bug where ::after pseudo-elements were still generated, even if the content property value were set to normal or none.Firefox for Android: Before Firefox for Android 4.5, only the CSS level 2 behavior of :after was supported, which disallowed position, float, list-style-* and some display properties. |
| css.selectors.after.animation_and_transition_support | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.selectors.attribute π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.before π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Firefox: Before Firefox 57, Firefox had a bug where ::before pseudo-elements were still generated, even if the content property value were set to normal or none.Firefox: Before Firefox 3.5, only the CSS level 2 behavior of :before was supported, which disallowed position, float, list-style-* and some display properties.Firefox for Android: Before Firefox 57, Firefox had a bug where ::before pseudo-elements were still generated, even if the content property value were set to normal or none. |
| css.selectors.before.animation_and_transition_support | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.selectors.checked π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode. |
| css.selectors.class π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.descendant π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.disabled π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.enabled π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.first π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.selectors.first-child π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.first-line π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.hover π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.hover.all_elements | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.indeterminate π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.indeterminate.checkbox | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.indeterminate.progress | Chrome | 9/2/2010 | Edge | 7/29/2015 | 1791 | |
| css.selectors.invalid π | Chrome | 3/8/2011 | Edge | 7/29/2015 | 1604 | |
| css.selectors.lang π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.last-child π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.last-of-type π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 9/2/2010 | Edge | 7/29/2015 | 1791 | |
| css.selectors.link π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.link.not_match_link | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.list π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.namespace π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.next-sibling π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.nth-child π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.selectors.nth-last-of-type π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.selectors.only-of-type π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 3/8/2011 | Edge | 7/29/2015 | 1604 | |
| css.selectors.required π | Chrome | 3/8/2011 | Edge | 7/29/2015 | 1604 | |
| css.selectors.right π | Chrome | 9/2/2010 | Edge | 7/29/2015 | 1791 | |
| css.selectors.root π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.selection π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.subsequent-sibling π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode. |
| css.selectors.target π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.type π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.type.namespaces | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.universal π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.universal.namespaces | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.valid π | Chrome | 3/8/2011 | Edge | 7/29/2015 | 1604 | |
| css.selectors.visited π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.visited.not_match_link | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.selectors.visited.privacy_measures | Chrome | 9/2/2010 | Edge | 7/29/2015 | 1791 | |
| css.types.angle π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.types.angle.deg | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.types.angle.grad | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.types.angle.rad | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.types.angle.turn | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.types.angle-percentage π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.types.attr π | Chrome | 5/21/2009 | Edge | 7/29/2015 | 2260 | |
| css.types.calc π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 | Chrome | 5/15/2012 | Edge | 7/29/2015 | 1170 | |
| css.types.calc.number_values | Chrome | 11/12/2013 | Edge | 7/29/2015 | 624 | |
| css.types.color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.color.currentcolor π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.color.hsl π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.color.named-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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.rebeccapurple | Chrome | 10/7/2014 | Edge | 7/29/2015 | 295 | |
| css.types.color.named-color.transparent π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.color.rgb π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.color.rgb_hexadecimal_notation π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.color.system-color π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.color.transparent | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.counter π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.counters π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.dimension π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.easing-function π | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.types.easing-function.cubic-bezier π | Chrome | 12/13/2011 | Edge | 7/29/2015 | 1324 | |
| css.types.easing-function.steps π | Chrome | 12/2/2010 | Edge | 7/29/2015 | 1700 | |
| css.types.filter-function π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.blur π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.brightness π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.contrast π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.drop-shadow π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.grayscale π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.hue-rotate π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.invert π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.opacity π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.saturate π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.filter-function.sepia π | Chrome | 3/28/2012 | Edge | 7/29/2015 | 1218 | |
| css.types.flex π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.types.global_keywords | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.global_keywords.inherit π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.gradient π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.types.gradient.linear-gradient.unitless_0_angle | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.types.gradient.repeating-linear-gradient π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | |
| css.types.gradient.repeating-linear-gradient.unitless_0_angle | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 π | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | Firefox: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Before Firefox for Android 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false. |
| css.types.image π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.integer π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.length π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.length.ch | Chrome | 5/21/2013 | Edge | 7/29/2015 | 799 | Firefox: From Firefox 1 to Firefox 3, ch was the width of the M character.Firefox: From Firefox 1 to Firefox 3, ch did not work with border-width and outline-width CSS properties. |
| css.types.length.em | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.length.ex | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.length.rem | Chrome | 1/25/2010 | Edge | 7/29/2015 | 2011 | |
| css.types.length.vh | Chrome | 6/26/2012 | Edge | 7/29/2015 | 1128 | 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 | Chrome | 3/26/2013 | Edge | 7/29/2015 | 855 | 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 | Chrome | 6/26/2012 | Edge | 7/29/2015 | 1128 | Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page. |
| css.types.length-percentage π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.line-style π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.number π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.number.scientific_notation | Chrome | 5/19/2015 | Edge | 7/29/2015 | 71 | |
| css.types.overflow π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.position π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.position.four_value_syntax | Chrome | 2/21/2013 | Edge | 7/29/2015 | 888 | |
| css.types.position.keyword_value_syntax | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.ratio π | Chrome | 9/15/2009 | Edge | 7/29/2015 | 2143 | |
| css.types.resolution π | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.types.resolution.dpcm | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.types.resolution.dpi | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.types.resolution.dppx | Chrome | 8/20/2013 | Edge | 7/29/2015 | 708 | |
| css.types.shape π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.shape.rect | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.string.unicode_escaped_characters | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.time π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | 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 π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.matrix3d π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.perspective π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.rotate π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.rotate3d π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.rotateX π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.rotateY π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.rotateZ π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.scale π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.scale3d π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.scaleX π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.scaleY π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.scaleZ π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.skew π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | Firefox: Firefox 14 removed experimental support for skew(), but it was reintroduced in Firefox 15. |
| css.types.transform-function.skewX π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.skewY π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.translate π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.translate3d π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.transform-function.translateX π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.translateY π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 | |
| css.types.transform-function.translateZ π | Chrome | 6/7/2011 | Edge | 7/29/2015 | 1513 | |
| css.types.url π | Chrome | 12/11/2008 | Edge | 7/29/2015 | 2421 |