Time to Stable

For a given set of browsers, what APIs are in all of them and how many days it take for the API to land in the first browser to the last.

Example Comparisons
Browsers
Features

Summary

A count of the number of APIs that landed in A first and B last.
Last in ChromeLast in Edge
First in Chrome 3378
First in Edge 118

Average time for an API to become available across Chrome and Edge

3496 APIs took an average of 1066.27 days to become available to use.

API breakdown:

Average time to landing by year of first landing

If a feature landed in the earliest browser in 20XX it took Y days on average to become available in the last browser (when considering Chrome and Edge). TTA (time to available).
CSS APIsCSS TTA
2008 8202626.38
2009 832435.19
2010 872723.94
2011 761909.91
2012 711529.27
2013 1381456.73
2014 751563.72
2015 163987.53
2016 991244.63
2017 205732.96
2018 231511.78
2019 33136.12
2020 18511.62
2021 1122.18
2022 1122.78
2023 3053.70
2024 2742.31
2025 3512.35
2026 766.05

The Tortoise and the Hare

There is a natural tension on the web with respect to browser engines. Every engine has their own set of priorities which define the level of investment that they choose to make and on which areas they choose to make it.

A developer naturally wants their experiences to be available to the widest audience possible and these differing priorities create an unevenness on the platform (a lumpiness) making it harder for developers to build experiences that work everywhere.

This section highlights where browsers are pushing and pulling on the platform.

Sprinters

This table is designed to show which browsers are pushing on the platform the most.

Adding features to quickly is not always desired because developers are unlikely to adopt those features in their sites or apps.

For a given year, if a feature landed in Browser X first, how many days it take on average to be available in Chrome and Edge. TTA (time to available).
Year CSSCSS TTA
2008
  Chrome 8202626.38
2009
  Chrome 832435.19
2010
  Chrome 872723.94
2011
  Chrome 761909.91
2012
  Chrome 711529.27
2013
  Chrome 1381456.73
2014
  Chrome 751563.72
2015
  Chrome 931387.06
  Edge 70456.71
2016
  Chrome 971260.18
  Edge 2490.50
2017
  Chrome 197755.34
  Edge 8182.00
2018
  Chrome 228510.76
  Edge 3589.00
2019
  Chrome 33136.12
2020
  Chrome 1692.18
  Edge 16111.25
2021
  Chrome 1122.18
2022
  Edge 191.00
  Chrome 933.14
2023
  Chrome 3053.70
2024
  Chrome 2742.31
2025
  Chrome 3512.35
2026
  Chrome 766.05

Plodders

This table is designed to show which browsers are pulling on the platform the most.

For a feature that first landed in year X, how many days did it take on average for the last browser to catch up across Chrome and Edge. TTA (time to available).
Year CSS countCSS TTA
2008
  Edge 8202626.38
2009
  Edge 832435.19
2010
  Edge 872723.94
2011
  Edge 761909.91
2012
  Edge 711529.27
2013
  Edge 1381456.73
2014
  Edge 751563.72
2015
  Edge 931387.06
  Chrome 70456.71
2016
  Edge 971260.18
  Chrome 2490.50
2017
  Edge 197755.34
  Chrome 8182.00
2018
  Edge 228510.76
  Chrome 3589.00
2019
  Edge 33136.12
2020
  Edge 1692.18
  Chrome 16111.25
2021
  Edge 1122.18
2022
  Chrome 191.00
  Edge 933.14
2023
  Edge 3053.70
2024
  Edge 2742.31
2025
  Edge 3512.35
2026
  Edge 766.05

Stable APIs

Below is a list of features that are in Chrome and Edge

Raw Data

Quick Links:

CSS Data

API First Browser Date Last Browser Date Days Notes
css.at-rules.charset 📋Chrome5/21/2009 Edge7/29/20152260
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.container 📋Edge9/1/2022 Chrome9/2/20221
css.at-rules.container.anchor_position_queries 📋Chrome12/2/2025 Edge12/5/20253
css.at-rules.container.anchor_position_queries.fallback 📋Chrome12/2/2025 Edge12/5/20253
css.at-rules.container.anchor_position_queries.fallback.any_value 📋Chrome12/2/2025 Edge12/5/20253
css.at-rules.container.scroll-state_queries 📋Chrome2/4/2025 Edge2/6/20252
css.at-rules.container.scroll-state_queries.scrollable 📋Chrome2/4/2025 Edge2/6/20252
css.at-rules.container.scroll-state_queries.scrolled 📋Chrome1/13/2026 Edge1/21/20268
css.at-rules.container.scroll-state_queries.snapped 📋Chrome2/4/2025 Edge2/6/20252
css.at-rules.container.scroll-state_queries.stuck 📋Chrome2/4/2025 Edge2/6/20252
css.at-rules.container.style_queries_for_custom_properties 📋Chrome3/7/2023 Edge3/13/20236
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.container.style_queries_for_custom_properties.range_syntax 📋Chrome10/28/2025 Edge10/31/20253
css.at-rules.counter-style 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.additive-symbols 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.fallback 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.negative 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.pad 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.prefix 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.range 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.speak-as 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.suffix 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.counter-style.symbols 📋Chrome5/25/2021 Edge5/27/20212
Chrome: Does not support <image> as a value for the symbols descriptor.Chrome Android: Does not support <image> as a value for the symbols descriptor.Edge: Does not support <image> as a value for the symbols descriptor.Firefox: Does not support <image> as a value for the symbols descriptor.Firefox for Android: Does not support <image> as a value for the symbols descriptor.Quest Browser: Does not support <image> as a value for the symbols descriptor.Opera: Does not support <image> as a value for the symbols descriptor.Opera Android: Does not support <image> as a value for the symbols descriptor.Samsung Internet: Does not support <image> as a value for the symbols descriptor.WebView Android: Does not support <image> as a value for the symbols descriptor.
css.at-rules.counter-style.system 📋Chrome5/25/2021 Edge5/27/20212
css.at-rules.font-face 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.font-face.OpenType_CBDT_CBLC Chrome4/17/2018 Edge1/15/2020638
css.at-rules.font-face.OpenType_COLRv0 Chrome8/31/2016 Edge1/15/20201232
css.at-rules.font-face.OpenType_COLRv1 Chrome2/1/2022 Edge2/3/20222
css.at-rules.font-face.OpenType_SBIX Chrome4/17/2018 Edge1/15/2020638
css.at-rules.font-face.WOFF 📋Chrome9/2/2010 Edge7/29/20151791
css.at-rules.font-face.WOFF_2 📋Chrome7/16/2014 Edge8/2/2016748
Safari: Supported only on macOS 10.12 (Sierra) and later.
css.at-rules.font-face.ascent-override 📋Chrome11/17/2020 Edge11/19/20202
css.at-rules.font-face.descent-override 📋Chrome11/17/2020 Edge11/19/20202
css.at-rules.font-face.font-display 📋Chrome7/25/2017 Edge1/15/2020904
css.at-rules.font-face.font-family 📋Chrome1/25/2010 Edge7/29/20152011
css.at-rules.font-face.font-feature-settings 📋Chrome9/2/2025 Edge9/5/20253
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-stretch 📋Chrome10/17/2017 Edge4/30/2018195
css.at-rules.font-face.font-style 📋Chrome1/25/2010 Edge7/29/20152011
css.at-rules.font-face.font-variant Chrome1/25/2010 Edge7/29/20152011
css.at-rules.font-face.font-variation-settings 📋Chrome9/2/2025 Edge9/5/20253
css.at-rules.font-face.font-weight 📋Chrome1/25/2010 Edge7/29/20152011
css.at-rules.font-face.line-gap-override 📋Chrome11/17/2020 Edge11/19/20202
css.at-rules.font-face.size-adjust 📋Chrome7/20/2021 Edge7/22/20212
css.at-rules.font-face.src 📋Chrome1/25/2010 Edge7/29/20152011
css.at-rules.font-face.src.drop_invalid_item Chrome11/29/2022 Edge12/5/20226
Chrome: Chrome drops invalid item for tech() but not other invalid valuesChrome Android: Chrome Android drops invalid item for tech() but not other invalid valuesEdge: Edge drops invalid item for tech() but not other invalid valuesOpera: Opera drops invalid item for tech() but not other invalid valuesOpera Android: Opera Android drops invalid item for tech() but not other invalid valuesSamsung Internet: Samsung Internet drops invalid item for tech() but not other invalid valuesWebView Android: WebView Android drops invalid item for tech() but not other invalid values
css.at-rules.font-face.src.format_keyword Chrome11/29/2022 Edge12/5/20226
css.at-rules.font-face.src.format_variations Chrome4/17/2018 Edge4/30/201813
css.at-rules.font-face.src.tech_keyword Chrome11/29/2022 Edge12/5/20226
css.at-rules.font-face.unicode-range 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.font-feature-values 📋Chrome3/7/2023 Edge3/13/20236
css.at-rules.font-feature-values.annotation Chrome3/7/2023 Edge3/13/20236
css.at-rules.font-feature-values.character-variant Chrome3/7/2023 Edge3/13/20236
css.at-rules.font-feature-values.historical-forms Chrome3/7/2023 Edge3/13/20236
css.at-rules.font-feature-values.ornaments Chrome3/7/2023 Edge3/13/20236
css.at-rules.font-feature-values.styleset Chrome3/7/2023 Edge3/13/20236
css.at-rules.font-feature-values.stylistic Chrome3/7/2023 Edge3/13/20236
css.at-rules.font-feature-values.swash Chrome3/7/2023 Edge3/13/20236
css.at-rules.font-palette-values 📋Chrome4/26/2022 Edge4/28/20222
css.at-rules.font-palette-values.base-palette 📋Chrome4/26/2022 Edge4/28/20222
css.at-rules.font-palette-values.font-family 📋Chrome4/26/2022 Edge4/28/20222
css.at-rules.font-palette-values.override-colors 📋Chrome4/26/2022 Edge4/28/20222
css.at-rules.function 📋Chrome8/5/2025 Edge8/7/20252
css.at-rules.function.result 📋Chrome8/5/2025 Edge8/7/20252
css.at-rules.import 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.import.layer 📋Chrome3/1/2022 Edge3/3/20222
css.at-rules.import.supports 📋Chrome2/20/2024 Edge2/23/20243
css.at-rules.keyframes 📋Chrome5/19/2015 Edge7/29/201571
css.at-rules.keyframes.ignore_important_declarations Chrome9/1/2015 Edge1/15/20201597
css.at-rules.keyframes.named_range_keyframes 📋Chrome7/18/2023 Edge7/21/20233
css.at-rules.layer 📋Chrome3/1/2022 Edge3/3/20222
css.at-rules.media 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.media.-webkit-device-pixel-ratio 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Implemented as an alias for -moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for -moz-device-pixel-ratio.
css.at-rules.media.-webkit-max-device-pixel-ratio 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Implemented as an alias for max--moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for max--moz-device-pixel-ratio.
css.at-rules.media.-webkit-min-device-pixel-ratio 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Implemented as an alias for min--moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for min--moz-device-pixel-ratio.
css.at-rules.media.-webkit-transform-3d 📋Chrome5/21/2009 Edge7/29/20152260
css.at-rules.media.any-hover 📋Chrome3/3/2015 Edge10/17/2017959
css.at-rules.media.any-pointer 📋Chrome3/3/2015 Edge7/29/2015148
css.at-rules.media.aspect-ratio 📋Chrome9/15/2009 Edge7/29/20152143
css.at-rules.media.calc 📋Chrome4/17/2018 Edge1/15/2020638
css.at-rules.media.color 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.media.color-gamut 📋Chrome4/19/2017 Edge1/15/20201001
css.at-rules.media.color-gamut.p3 📋Chrome4/19/2017 Edge1/15/20201001
Firefox: color-gamut: p3 is always false because Firefox does not support wide-gamut color. See bug 1626624.Firefox for Android: color-gamut: p3 is always false because Firefox for Android does not support wide-gamut color. See bug 1626624.
css.at-rules.media.color-gamut.rec2020 📋Chrome4/19/2017 Edge1/15/20201001
Firefox: color-gamut: rec2020 is always false because Firefox does not support wide-gamut color. See bug 1626624.Firefox for Android: color-gamut: rec2020 is always false because Firefox for Android does not support wide-gamut color. See bug 1626624.
css.at-rules.media.color-gamut.srgb 📋Chrome4/19/2017 Edge1/15/20201001
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 📋Chrome8/20/2013 Edge1/15/20202339
css.at-rules.media.device-aspect-ratio 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.media.device-height 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.media.device-posture 📋Chrome1/14/2025 Edge1/17/20253
css.at-rules.media.device-width 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.media.display-mode 📋Chrome4/14/2015 Edge1/15/20201737
css.at-rules.media.display-mode.browser 📋Chrome4/14/2015 Edge1/15/20201737
Firefox for Android: display-mode: browser is always true.Safari: In a Safari browser window, display-mode: browser is always true, even in a macOS Full Screen window or when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In the Safari app, display-mode: browser is always true, even when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).WebView on iOS: In the Safari app, display-mode: browser is always true, even when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).
css.at-rules.media.display-mode.fullscreen 📋Chrome12/1/2015 Edge1/15/20201506
Firefox: In Firefox's "Full Screen" user interface, browser tabs and other user interface appear but display-mode: fullscreen is true.Safari: In a Safari browser window, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In the Safari app, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In an installed web application with the display manifest member set to standalone, display-mode: fullscreen is true, even though the system status bar is visible. See bug 264218.WebView on iOS: In the Safari app, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).WebView on iOS: In an installed web application with the display manifest member set to standalone, display-mode: fullscreen is true, even though the system status bar is visible. See bug 264218.
css.at-rules.media.display-mode.minimal-ui 📋Chrome4/14/2015 Edge1/15/20201737
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.picture-in-picture 📋Chrome3/19/2024 Edge3/22/20243
css.at-rules.media.display-mode.standalone 📋Chrome4/14/2015 Edge1/15/20201737
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.display-mode.window-controls-overlay 📋Edge9/1/2022 Chrome9/2/20221
css.at-rules.media.dynamic-range 📋Chrome2/1/2022 Edge2/3/20222
css.at-rules.media.forced-colors 📋Edge1/15/2020 Chrome3/2/2021412
css.at-rules.media.grid 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.media.height 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.media.horizontal-viewport-segments 📋Chrome6/24/2025 Edge6/26/20252
css.at-rules.media.hover 📋Chrome10/7/2014 Edge7/29/2015295
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 Chrome12/11/2008 Edge7/29/20152421
css.at-rules.media.media_query_values Chrome4/17/2018 Edge1/15/2020638
css.at-rules.media.monochrome 📋Chrome12/11/2008 Edge1/15/20204052
css.at-rules.media.nested-queries Chrome3/26/2013 Edge7/29/2015855
css.at-rules.media.or_syntax Chrome8/2/2022 Edge8/5/20223
css.at-rules.media.orientation 📋Chrome9/15/2009 Edge7/29/20152143
css.at-rules.media.overflow-block 📋Chrome5/2/2023 Edge5/5/20233
css.at-rules.media.overflow-inline 📋Chrome5/2/2023 Edge5/5/20233
css.at-rules.media.pointer 📋Chrome3/3/2015 Edge7/29/2015148
css.at-rules.media.prefers-color-scheme 📋Chrome7/30/2019 Edge1/15/2020169
css.at-rules.media.prefers-color-scheme.respects-inherited-scheme Chrome9/17/2024 Edge9/19/20242
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.at-rules.media.prefers-contrast 📋Chrome11/15/2021 Edge11/19/20214
css.at-rules.media.prefers-reduced-data 📋Chrome8/25/2020 Edge8/27/20202
css.at-rules.media.prefers-reduced-motion 📋Chrome4/23/2019 Edge1/15/2020267
css.at-rules.media.prefers-reduced-transparency 📋Chrome10/10/2023 Edge10/13/20233
css.at-rules.media.range_syntax Chrome8/2/2022 Edge8/5/20223
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.resolution 📋Chrome8/20/2013 Edge7/29/2015708
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.at-rules.media.scan 📋Chrome8/2/2022 Edge8/5/20223
css.at-rules.media.scripting 📋Chrome12/5/2023 Edge12/7/20232
css.at-rules.media.update 📋Chrome5/2/2023 Edge5/5/20233
css.at-rules.media.vertical-viewport-segments 📋Chrome6/24/2025 Edge6/26/20252
css.at-rules.media.video-dynamic-range 📋Chrome2/1/2022 Edge2/3/20222
css.at-rules.media.width 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.namespace 📋Chrome12/11/2008 Edge7/29/20152421
css.at-rules.page 📋Chrome5/21/2009 Edge7/29/20152260
css.at-rules.page.bottom-center 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.bottom-left 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.bottom-left-corner 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.bottom-right 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.bottom-right-corner 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.left-bottom 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.left-middle 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.left-top 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.page-orientation 📋Chrome8/25/2020 Edge8/27/20202
css.at-rules.page.right-bottom 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.right-middle 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.right-top 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.size 📋Chrome10/25/2011 Edge1/15/20203004
css.at-rules.page.size.jis-b4 📋Chrome5/19/2020 Edge5/21/20202
css.at-rules.page.size.jis-b5 📋Chrome5/19/2020 Edge5/21/20202
css.at-rules.page.top-center 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.top-left 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.top-left-corner 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.top-right 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.page.top-right-corner 📋Chrome11/12/2024 Edge11/14/20242
css.at-rules.position-try 📋Chrome5/14/2024 Edge5/17/20243
css.at-rules.property 📋Chrome8/25/2020 Edge8/27/20202
css.at-rules.property.inherits 📋Chrome8/25/2020 Edge8/27/20202
css.at-rules.property.initial-value 📋Chrome8/25/2020 Edge8/27/20202
css.at-rules.property.syntax 📋Chrome8/25/2020 Edge8/27/20202
css.at-rules.scope 📋Chrome10/10/2023 Edge10/13/20233
css.at-rules.starting-style 📋Chrome9/12/2023 Edge9/15/20233
css.at-rules.supports 📋Chrome7/9/2013 Edge7/29/2015750
css.at-rules.supports.font-format Chrome11/29/2022 Edge12/5/20226
css.at-rules.supports.font-tech Chrome11/29/2022 Edge12/5/20226
css.at-rules.supports.selector Chrome5/19/2020 Edge5/21/20202
css.at-rules.view-transition 📋Chrome6/11/2024 Edge6/13/20242
css.properties.-webkit-app-region Chrome1/10/2013 Edge1/15/20202561
css.properties.-webkit-border-before Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-border-horizontal-spacing Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-border-vertical-spacing Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-box-reflect Chrome1/25/2010 Edge1/15/20203642
css.properties.-webkit-column-break-after Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-column-break-before Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-column-break-inside Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-locale Chrome4/27/2011 Edge1/15/20203185
css.properties.-webkit-logical-height Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-logical-width Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-margin-after Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-margin-before Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-mask-box-image Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-mask-composite Chrome12/11/2008 Edge10/2/20183582
css.properties.-webkit-mask-position-x Chrome12/11/2008 Edge10/2/20183582
css.properties.-webkit-mask-position-y Chrome12/11/2008 Edge10/2/20183582
css.properties.-webkit-max-logical-height Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-max-logical-width Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-min-logical-height Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-min-logical-width Chrome12/2/2010 Edge1/15/20203331
css.properties.-webkit-perspective-origin-x Chrome5/21/2009 Edge1/15/20203891
css.properties.-webkit-perspective-origin-y Chrome5/21/2009 Edge1/15/20203891
css.properties.-webkit-rtl-ordering Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-tap-highlight-color Chrome12/13/2011 Edge7/29/20151324
css.properties.-webkit-text-combine Chrome2/3/2011 Edge1/15/20203268
css.properties.-webkit-text-decorations-in-effect Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-text-fill-color 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.-webkit-text-security Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-text-stroke 📋Chrome1/25/2010 Edge4/5/20172627
css.properties.-webkit-text-stroke-color 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.-webkit-text-stroke-width 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.-webkit-transform-origin-x Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-transform-origin-y Chrome12/11/2008 Edge1/15/20204052
css.properties.-webkit-transform-origin-z Chrome5/21/2009 Edge1/15/20203891
css.properties.-webkit-user-drag Chrome12/11/2008 Edge1/15/20204052
css.properties.accent-color 📋Chrome8/31/2021 Edge9/2/20212
Chrome Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Quest Browser: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Opera Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Safari: Safari does not maintain minimum contrast for legibility of the control. See bug 244233.Safari on iOS: Safari on iOS does not maintain minimum contrast for legibility of the control. See bug 244233.Samsung Internet: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.WebView Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.WebView on iOS: WebView on iOS does not maintain minimum contrast for legibility of the control. See bug 244233.
css.properties.accent-color.auto Chrome8/31/2021 Edge9/2/20212
css.properties.align-content 📋Chrome8/20/2013 Edge7/29/2015708
css.properties.align-content.block_context 📋Chrome3/19/2024 Edge3/22/20243
css.properties.align-content.flex_context 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.align-content.flex_context.baseline Chrome3/9/2017 Edge1/15/20201042
css.properties.align-content.flex_context.first_baseline Chrome6/5/2017 Edge1/15/2020954
css.properties.align-content.flex_context.safe_unsafe Chrome7/18/2023 Edge7/21/20233
Chrome: Before version 115, this value is recognized, but has no effect.Chrome Android: Before version 115, this value is recognized, but has no effect.Edge: Before version 115, this value is recognized, but has no effect.Opera: Before version 101, this value is recognized, but has no effect.Opera Android: Before version 77, this value is recognized, but has no effect.Samsung Internet: Before version 23.0, this value is recognized, but has no effect.WebView Android: Before version 115, this value is recognized, but has no effect.
css.properties.align-content.flex_context.space-evenly Chrome7/25/2017 Edge1/15/2020904
css.properties.align-content.flex_context.start_end Chrome8/31/2021 Edge9/2/20212
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-content.flex_context.stretch Chrome3/9/2017 Edge1/15/20201042
css.properties.align-content.grid_context 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.align-content.multicol_context 📋Chrome3/19/2024 Edge3/22/20243
css.properties.align-content.normal 📋Chrome8/20/2013 Edge7/29/2015708
css.properties.align-items 📋Chrome8/20/2013 Edge7/29/2015708
css.properties.align-items.anchor-center 📋Chrome5/14/2024 Edge5/17/20243
css.properties.align-items.flex_context 📋Edge7/29/2015 Chrome7/20/2016357
Chrome: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome implements the new behavior beginning with Chrome 52.Chrome Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome Android implements the new behavior beginning with Chrome Android 52.Firefox: Multi-line flexbox has been supported since Firefox 28.Firefox for Android: Multi-line flexbox has been supported since Firefox for Android 28.Internet Explorer: In Internet Explorer 10 and 11, if column flex items have align-items: center; set on them and their content is too large, then they will overflow the bounds of their container. See Flexbug #2.Opera: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Opera implements the new behavior beginning with Opera 39.Opera Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Opera Android implements the new behavior beginning with Opera Android 41.Samsung Internet: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Samsung Internet implements the new behavior beginning with Samsung Internet 6.0.WebView Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. WebView Android implements the new behavior beginning with WebView Android 52.
css.properties.align-items.flex_context.baseline Chrome7/31/2012 Edge1/15/20202724
css.properties.align-items.flex_context.first_baseline Chrome6/5/2017 Edge1/15/2020954
css.properties.align-items.flex_context.last_baseline Chrome11/29/2022 Edge12/5/20226
css.properties.align-items.flex_context.safe_unsafe Chrome7/18/2023 Edge7/21/20233
Chrome: Before version 115, this value is recognized, but has no effect.Chrome Android: Before version 115, this value is recognized, but has no effect.Edge: Before version 115, this value is recognized, but has no effect.Opera: Before version 101, this value is recognized, but has no effect.Opera Android: Before version 77, this value is recognized, but has no effect.Samsung Internet: Before version 23.0, this value is recognized, but has no effect.WebView Android: Before version 115, this value is recognized, but has no effect.
css.properties.align-items.flex_context.start_end Chrome8/31/2021 Edge9/2/20212
css.properties.align-items.grid_context 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.align-items.grid_context.start_end Chrome3/9/2017 Edge1/15/20201042
css.properties.align-self 📋Chrome8/20/2013 Edge7/29/2015708
css.properties.align-self.anchor-center 📋Chrome5/14/2024 Edge5/17/20243
css.properties.align-self.auto 📋Chrome7/31/2012 Edge1/15/20202724
css.properties.align-self.flex_context 📋Chrome7/16/2014 Edge7/29/2015378
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.align-self.flex_context.baseline 📋Chrome7/31/2012 Edge1/15/20202724
css.properties.align-self.flex_context.first_baseline Chrome6/5/2017 Edge1/15/2020954
css.properties.align-self.flex_context.last_baseline Chrome11/29/2022 Edge12/5/20226
css.properties.align-self.flex_context.safe_unsafe Chrome7/18/2023 Edge7/21/20233
Chrome: Before version 115, this value is recognized, but has no effect.Chrome Android: Before version 115, this value is recognized, but has no effect.Edge: Before version 115, this value is recognized, but has no effect.Opera: Before version 101, this value is recognized, but has no effect.Opera Android: Before version 77, this value is recognized, but has no effect.Samsung Internet: Before version 23.0, this value is recognized, but has no effect.WebView Android: Before version 115, this value is recognized, but has no effect.
css.properties.align-self.flex_context.start_end Chrome8/31/2021 Edge9/2/20212
Opera: Before version 79, this value is recognized, but has no effect.
css.properties.align-self.flex_context.stretch 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.align-self.grid_context 📋Chrome3/9/2017 Edge10/17/2017222
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.align-self.normal 📋Chrome7/31/2012 Edge1/15/20202724
css.properties.align-self.position_absolute_context 📋Chrome2/20/2024 Edge2/23/20243
css.properties.align-self.stretch 📋Chrome7/31/2012 Edge1/15/20202724
css.properties.alignment-baseline 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.alignment-baseline.alphabetic Chrome12/11/2008 Edge1/15/20204052
css.properties.alignment-baseline.baseline Chrome12/11/2008 Edge1/15/20204052
css.properties.alignment-baseline.central Chrome12/11/2008 Edge1/15/20204052
css.properties.alignment-baseline.ideographic Chrome12/11/2008 Edge1/15/20204052
css.properties.alignment-baseline.mathematical Chrome12/11/2008 Edge1/15/20204052
css.properties.alignment-baseline.middle Chrome12/11/2008 Edge1/15/20204052
css.properties.alignment-baseline.text-after-edge Chrome12/11/2008 Edge1/15/20204052
css.properties.alignment-baseline.text-before-edge Chrome12/11/2008 Edge1/15/20204052
css.properties.all 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.anchor-name 📋Chrome5/14/2024 Edge5/17/20243
css.properties.anchor-name.none 📋Chrome5/14/2024 Edge5/17/20243
css.properties.anchor-scope 📋Chrome11/12/2024 Edge11/14/20242
css.properties.anchor-scope.all 📋Chrome11/12/2024 Edge11/14/20242
css.properties.anchor-scope.none 📋Chrome11/12/2024 Edge11/14/20242
css.properties.animation 📋Chrome5/19/2015 Edge7/29/201571
WebView Android: The animation-fill-mode property is not supported in Android browsers below 2.3.
css.properties.animation.alternate 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.alternate-reverse 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.animation-timeline_included Chrome7/18/2023 Edge7/21/20233
Chrome: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Chrome Android: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Edge: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Opera: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Opera Android: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.Samsung Internet: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.WebView Android: Support is currently reset-only. Including animation resets a previously-declared animation-timeline value to auto, but animation-timeline cannot be set via animation.
css.properties.animation.auto 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.backwards 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.both 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.ease 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.ease-in 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.ease-in-out 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.ease-out 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.forwards 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.infinite 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.linear 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.none 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.normal 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.paused 📋Chrome9/15/2009 Edge1/15/20203774
css.properties.animation.reverse 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.running 📋Chrome9/15/2009 Edge1/15/20203774
css.properties.animation.step-end 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation.step-start 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-composition 📋Chrome4/4/2023 Edge4/6/20232
css.properties.animation-composition.accumulate 📋Chrome4/4/2023 Edge4/6/20232
css.properties.animation-composition.add 📋Chrome4/4/2023 Edge4/6/20232
css.properties.animation-composition.replace 📋Chrome4/4/2023 Edge4/6/20232
css.properties.animation-delay 📋Chrome5/19/2015 Edge7/29/201571
Firefox: Before Firefox 57, Firefox does not repaint elements outside the viewport that are animated into the viewport with a delay. This bug affects only some platforms, such as Windows.
css.properties.animation-direction 📋Chrome5/19/2015 Edge7/29/201571
css.properties.animation-direction.alternate 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-direction.alternate-reverse 📋Chrome5/15/2012 Edge7/29/20151170
css.properties.animation-direction.normal 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-direction.reverse 📋Chrome5/15/2012 Edge7/29/20151170
css.properties.animation-duration 📋Chrome5/19/2015 Edge7/29/201571
Internet Explorer: Once the element has loaded, changing the value of this property has no effect.
css.properties.animation-duration.auto 📋Chrome7/18/2023 Edge7/21/20233
Firefox: Firefox does not currently support the auto value and only accepts values in seconds or milliseconds. It's recommended that 1ms is used until auto is supported.Firefox for Android: Firefox for Android does not currently support the auto value and only accepts values in seconds or milliseconds. It's recommended that 1ms is used until auto is supported.
css.properties.animation-fill-mode 📋Chrome5/19/2015 Edge7/29/201571
css.properties.animation-fill-mode.backwards 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-fill-mode.both 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-fill-mode.forwards 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-fill-mode.none 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-iteration-count 📋Chrome5/19/2015 Edge7/29/201571
css.properties.animation-iteration-count.infinite 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-name 📋Chrome5/19/2015 Edge7/29/201571
css.properties.animation-name.none 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-play-state 📋Chrome5/19/2015 Edge7/29/201571
css.properties.animation-play-state.paused 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-play-state.running 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-range 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-range.normal 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-range-end 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-range-end.normal 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-range-start 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-range-start.normal 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-timeline 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-timeline.auto 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-timeline.none 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-timeline.scroll 📋Chrome7/18/2023 Edge7/21/20233
Firefox: Zero scroll range is treated as 100% but should be 0% (see bug 1780865).Firefox: Supports the deprecated horizontal and vertical axis values, and not the x and y values.
css.properties.animation-timeline.view 📋Chrome7/18/2023 Edge7/21/20233
css.properties.animation-timing-function 📋Chrome5/19/2015 Edge7/29/201571
css.properties.animation-timing-function.ease 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-timing-function.ease-in 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-timing-function.ease-in-out 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-timing-function.ease-out 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-timing-function.jump Chrome9/10/2019 Edge1/15/2020127
css.properties.animation-timing-function.linear 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-timing-function.step-end 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-timing-function.step-start 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-trigger 📋Chrome3/10/2026 Edge3/12/20262
css.properties.animation-trigger.none 📋Chrome3/10/2026 Edge3/12/20262
css.properties.appearance 📋Edge7/16/2020 Chrome7/27/202011
css.properties.appearance.auto 📋Chrome5/19/2020 Edge5/21/20202
css.properties.appearance.base-select 📋Chrome4/1/2025 Edge4/4/20253
css.properties.appearance.button 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.checkbox 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.listbox 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.menulist 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.menulist-button 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: See bug 1481615.Firefox for Android: See bug 1481615.
css.properties.appearance.meter 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.none 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Doesn't work with <input type="checkbox"> and <input type="radio">.Firefox for Android: Doesn't work with <input type="checkbox"> and <input type="radio">.
css.properties.appearance.progress-bar 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.radio 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.searchfield 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.textarea 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.appearance.textfield 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.aspect-ratio 📋Chrome1/19/2021 Edge1/21/20212
css.properties.aspect-ratio.auto 📋Chrome1/19/2021 Edge1/21/20212
css.properties.backdrop-filter 📋Chrome7/30/2019 Edge1/15/2020169
Firefox: Before Firefox 123, the property was not supported on systems with unknown GPU vendor (see bug 1868737).Firefox for Android: Before Firefox for Android 123, the property was not supported on systems with unknown GPU vendor (see bug 1868737).
css.properties.backdrop-filter.none 📋Chrome7/30/2019 Edge1/15/2020169
css.properties.backface-visibility 📋Chrome7/16/2014 Edge7/29/2015378
css.properties.backface-visibility.hidden 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.backface-visibility.visible 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.background 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.SVG_image_as_background Chrome12/11/2008 Edge7/29/20152421
css.properties.background.background-clip Chrome7/31/2012 Edge7/29/20151093
css.properties.background.background-origin Chrome7/31/2012 Edge7/29/20151093
css.properties.background.background-size Chrome7/31/2012 Edge7/29/20151093
css.properties.background.border-box 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.bottom 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.center 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.content-box 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.fixed 📋Chrome10/25/2011 Edge4/5/20171989
css.properties.background.left 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.local 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.multiple_backgrounds Chrome12/11/2008 Edge7/29/20152421
css.properties.background.no-repeat 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.padding-box 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.repeat 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.repeat-x 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.repeat-y 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.right 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.round 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.scroll 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.space 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background.top 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-attachment 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-attachment.fixed 📋Chrome12/11/2008 Edge7/29/20152421
Safari: fixed is recognized but has no effect. See related bug 219324.Safari on iOS: fixed is recognized but has no effect. See bug 275247.WebView on iOS: fixed is recognized but has no effect. See bug 275247.
css.properties.background-attachment.local 📋Chrome12/11/2008 Edge7/29/20152421
Safari: local is recognized but has no effect. See bug 219324.Safari on iOS: local is recognized but has no effect. See bug 219324.Safari on iOS: If -webkit-overflow-scrolling: touch is set, then local has no effect.WebView on iOS: local is recognized but has no effect. See bug 219324.WebView on iOS: If -webkit-overflow-scrolling: touch is set, then local has no effect.
css.properties.background-attachment.multiple_backgrounds Chrome12/11/2008 Edge7/29/20152421
css.properties.background-attachment.scroll 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-blend-mode 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.background-clip 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: Chrome accepts alternate synonyms to its values: padding, border, and content.Chrome Android: Chrome Android accepts alternate synonyms to its values: padding, border, and content.Edge: Since Edge 79, accepts alternate synonyms to its values: padding, border, and content.Firefox: Used the -moz-background-clip: padding | border syntax.Internet Explorer: In IE 7 and IE 8 of Internet Explorer, this property always behaved like background-clip: padding-box when overflow was hidden, auto, or scroll.Quest Browser: Quest Browser accepts alternate synonyms to its values: padding, border, and content.Opera: Opera accepts alternate synonyms to its values: padding, border, and content.Opera Android: Opera accepts alternate synonyms to its values: padding, border, and content.Safari: Safari accepts alternate synonyms to its values: padding, border, and content.Safari on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.Samsung Internet: Samsung Internet accepts alternate synonyms to its values: padding, border, and content.WebView Android: WebView Android accepts alternate synonyms to its values: padding, border, and content.WebView on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.
css.properties.background-clip.border-box 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-clip.content-box 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: In IE 7 and IE 9 of Internet Explorer, it always behaved like background-clip: padding-box if overflow: hidden | auto | scroll
css.properties.background-clip.padding-box 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-clip.text 📋Chrome12/5/2023 Edge12/7/20232
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.background-color 📋Chrome12/11/2008 Edge7/29/20152421
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.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-image 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: If the browser.display.use_document_colors user preference in about:config is set to false, background images will not be displayed.Firefox for Android: If the browser.display.use_document_colors user preference in about:config is set to false, background images will not be displayed.
css.properties.background-image.gradients 📋Chrome12/11/2008 Edge7/29/20152421
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.image-set 📋Chrome5/2/2023 Edge5/5/20233
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.background-image.multiple_backgrounds Chrome12/11/2008 Edge7/29/20152421
css.properties.background-image.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-image.svg_images Chrome12/2/2010 Edge7/29/20151700
Safari: Support of SVG in CSS background is incomplete.Safari on iOS: Support of SVG in CSS background is incomplete.WebView on iOS: Support of SVG in CSS background is incomplete.
css.properties.background-origin 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: Chrome accepts alternate synonyms to its values: padding, border, and content.Chrome Android: Chrome Android accepts alternate synonyms to its values: padding, border, and content.Edge: Since Edge 79, accepts alternate synonyms to its values: padding, border, and content.Firefox: Used the -moz-background-clip: padding | border syntax.Internet Explorer: In IE 7 and before, Internet explorer was behaving as if background-origin: border-box was set. In Internet Explorer 8, as if background-origin: padding-box, the regular default value, was set.Quest Browser: Quest Browser accepts alternate synonyms to its values: padding, border, and content.Opera: Opera accepts alternate synonyms to its values: padding, border, and content.Opera Android: Opera accepts alternate synonyms to its values: padding, border, and content.Safari: Webkit accepts alternate synonyms to its values: padding, border, and content.Safari on iOS: Webkit accepts alternate synonyms to its values: padding, border, and content.Samsung Internet: Samsung Internet accepts alternate synonyms to its values: padding, border, and content.WebView Android: WebView accepts alternate synonyms to its values: padding, border, and content.WebView on iOS: Webkit accepts alternate synonyms to its values: padding, border, and content.
css.properties.background-origin.border-box 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-origin.content-box 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: In IE 7 and IE 9 of Internet Explorer, it always behaved like background-clip: padding if overflow: hidden | auto | scroll.
css.properties.background-origin.padding-box 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-position 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-position.bottom 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.background-position.center 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.background-position.left 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.background-position.multiple_backgrounds Chrome12/11/2008 Edge7/29/20152421
css.properties.background-position.right 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.background-position.side-relative_values Chrome2/21/2013 Edge7/29/2015888
css.properties.background-position.top 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.background-position-x 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-position-x.side-relative_values Chrome1/13/2026 Edge1/21/20268
css.properties.background-position-y 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-position-y.side-relative_values Chrome1/13/2026 Edge1/21/20268
css.properties.background-repeat 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-repeat.2-value Chrome9/15/2009 Edge7/29/20152143
css.properties.background-repeat.multiple_backgrounds Chrome12/11/2008 Edge7/29/20152421
css.properties.background-repeat.no-repeat 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-repeat.repeat 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-repeat.repeat-x 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-repeat.repeat-y 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-repeat.round 📋Chrome10/1/2013 Edge7/29/2015666
css.properties.background-repeat.space 📋Chrome10/1/2013 Edge7/29/2015666
css.properties.background-size 📋Chrome9/15/2009 Edge7/29/20152143
Chrome: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Chrome Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Quest Browser: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Opera Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera Android: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Safari: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Safari on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Samsung Internet: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.
css.properties.background-size.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.background-size.contain 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.background-size.cover 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.baseline-shift 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.baseline-shift.baseline 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.baseline-shift.sub 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.baseline-shift.super 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.baseline-source 📋Chrome3/7/2023 Edge3/13/20236
css.properties.baseline-source.auto 📋Chrome3/7/2023 Edge3/13/20236
css.properties.baseline-source.first 📋Chrome3/7/2023 Edge3/13/20236
css.properties.baseline-source.last 📋Chrome3/7/2023 Edge3/13/20236
css.properties.block-size 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.block-size.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.block-size.auto 📋Chrome12/2/2010 Edge1/15/20203331
css.properties.block-size.fit-content 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.block-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.block-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.block-size.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.border 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-block 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.currentColor 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.dashed 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.dotted 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.double 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.groove 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.hidden 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.inset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.medium 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.none 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.outset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.ridge 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.solid 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.thick 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.thin 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block.transparent 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-color 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-color.currentColor 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-color.transparent 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.currentColor 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.dashed 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.dotted 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.double 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.groove 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.hidden 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.inset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.medium 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.outset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.ridge 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.solid 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.thick 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.thin 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end.transparent 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-color 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-color.currentColor 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-color.transparent 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.dashed 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.dotted 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.double 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.groove 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.hidden 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.inset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.outset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.ridge 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-style.solid 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-width 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-width.medium 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-width.thick 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-end-width.thin 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.currentColor 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.dashed 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.dotted 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.double 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.groove 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.hidden 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.inset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.medium 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.outset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.ridge 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.solid 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.thick 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.thin 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start.transparent 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-color 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-color.currentColor 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-color.transparent 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.dashed 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.dotted 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.double 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.groove 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.hidden 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.inset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.outset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.ridge 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-style.solid 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-width 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-width.medium 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-width.thick 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-start-width.thin 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-block-style 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.dashed 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.dotted 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.double 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.groove 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.hidden 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.inset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.none 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.outset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.ridge 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-style.solid 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-width 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-width.medium 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-width.thick 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-block-width.thin 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-bottom 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-bottom.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-color 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-color.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-bottom-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-left-radius 📋Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-left-radius.elliptical_corners Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-left-radius.percentages Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-right-radius 📋Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-right-radius.elliptical_corners Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-right-radius.percentages Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-style 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-style.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-style.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-width 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-width.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-width.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-bottom-width.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-collapse 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-collapse.collapse Chrome12/11/2008 Edge1/15/20204052
css.properties.border-collapse.separate Chrome12/11/2008 Edge1/15/20204052
css.properties.border-color 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-color.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-end-end-radius 📋Chrome3/2/2021 Edge3/4/20212
css.properties.border-end-start-radius 📋Chrome3/2/2021 Edge3/4/20212
css.properties.border-image 📋Chrome12/13/2011 Edge7/29/20151324
Chrome: Before Chrome 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Chrome Android: Before Chrome Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Edge: Before Edge 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Firefox: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox: Until Firefox 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox: From Firefox 48 until Firefox 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox: Until Firefox 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox: Before Firefox 15, an earlier version of the specification was implemented, prefixed.Firefox for Android: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox for Android: Until Firefox for Android 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox for Android: From Firefox for Android 48 until Firefox for Android 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox for Android: Until Firefox for Android 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox for Android: Before Firefox for Android 15, an earlier version of the specification was implemented, prefixed.Quest Browser: Before Quest Browser false, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera: Before Opera 98, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera Android: A border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Samsung Internet: Before Samsung Internet 23.0, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).WebView Android: Before WebView 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).
css.properties.border-image.fill Chrome12/13/2011 Edge7/29/20151324
css.properties.border-image.gradient Chrome10/19/2010 Edge7/29/20151744
css.properties.border-image.none 📋Chrome12/13/2011 Edge7/29/20151324
css.properties.border-image.optional_border_image_slice Chrome12/13/2011 Edge7/29/20151324
css.properties.border-image.repeat 📋Chrome12/13/2011 Edge7/29/20151324
css.properties.border-image.round 📋Chrome12/13/2011 Edge7/29/20151324
css.properties.border-image.space 📋Chrome12/13/2011 Edge7/29/20151324
css.properties.border-image.stretch 📋Chrome12/13/2011 Edge7/29/20151324
css.properties.border-image-outset 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-repeat 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-repeat.repeat 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-repeat.round 📋Chrome10/1/2013 Edge7/29/2015666
css.properties.border-image-repeat.space 📋Edge7/29/2015 Chrome1/25/2017546
css.properties.border-image-repeat.stretch 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-slice 📋Chrome10/25/2011 Edge7/29/20151373
Firefox: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox: Until Firefox 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox: From Firefox 48 until Firefox 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox: Until Firefox 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox for Android: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox for Android: Until Firefox for Android 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox for Android: From Firefox for Android 48 until Firefox for Android 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox for Android: Until Firefox for Android 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).
css.properties.border-image-source 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-source.none 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-width 📋Chrome12/13/2011 Edge7/29/20151324
Chrome: Before Chrome 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Chrome Android: Before Chrome Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Edge: Before Edge 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Quest Browser: Before Quest Browser false, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera: Before Opera 98, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera Android: Before Opera Android 75, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Samsung Internet: Before Samsung Internet 23.0, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).WebView Android: Before WebView Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).
css.properties.border-image-width.auto 📋Chrome12/13/2011 Edge7/29/20151324
css.properties.border-inline 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.currentColor 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.dashed 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.dotted 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.double 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.groove 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.hidden 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.inset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.medium 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.none 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.outset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.ridge 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.solid 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.thick 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.thin 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline.transparent 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-color 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-color.currentColor 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-color.transparent 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.currentColor 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.dashed 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.dotted 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.double 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.groove 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.hidden 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.inset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.medium 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.outset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.ridge 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.solid 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.thick 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.thin 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end.transparent 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-color 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-color.currentColor 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-color.transparent 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.dashed 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.dotted 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.double 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.groove 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.hidden 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.inset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.outset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.ridge 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-style.solid 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-width 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-width.medium 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-width.thick 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-end-width.thin 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.currentColor 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.dashed 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.dotted 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.double 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.groove 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.hidden 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.inset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.medium 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.outset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.ridge 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.solid 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.thick 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.thin 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start.transparent 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-color 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-color.currentColor 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-color.transparent 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.dashed 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.dotted 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.double 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.groove 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.hidden 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.inset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.outset 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.ridge 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-style.solid 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-width 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-width.medium 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-width.thick 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-start-width.thin 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.border-inline-style 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.dashed 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.dotted 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.double 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.groove 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.hidden 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.inset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.none 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.outset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.ridge 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-style.solid 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-width 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-width.medium 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-width.thick 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-inline-width.thin 📋Chrome11/17/2020 Edge11/19/20202
css.properties.border-left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-left.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-color 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-color.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-left-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.
css.properties.border-left-style.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-style.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-width 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-width.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-width.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-left-width.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-radius 📋Chrome1/25/2010 Edge7/29/20152011
Chrome: Chrome ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox: To conform to the CSS3 standard, Firefox 4 changes the handling of <percentage> values to match the specification. You can specify an ellipse as a border on an arbitrary sized element with border-radius: 50%;. Firefox 4 also makes rounded corners clip content and images if overflow: visible is not set.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-style was solid. This has been fixed in Firefox 50.Opera: Before Opera 11.60, replaced elements with border-radius do not have rounded corners.Safari: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.Safari on iOS: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.WebView on iOS: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.
css.properties.border-radius.4_values_for_4_corners Chrome1/25/2010 Edge7/29/20152011
css.properties.border-radius.elliptical_borders Chrome12/11/2008 Edge7/29/20152421
Chrome: Before Chrome 4, the slash / notation is unsupported. If two values are specified, then an elliptical border is drawn on all four corners. -webkit-border-radius: 40px 10px; is equivalent to border-radius: 40px / 10px;.Safari: Before Safari 5, the slash / notation is unsupported. If two values are specified, then an elliptical border is drawn on all four corners. -webkit-border-radius: 40px 10px; is equivalent to border-radius: 40px / 10px;.
css.properties.border-radius.percentages Chrome12/2/2010 Edge7/29/20151700
Firefox: Before Firefox 4, <percentage> values are implemented in a non-standard way. Both horizontal and vertical radii were relative to the width of the border box.Opera: Before Opera 11.5, the implementation of <percentage> values was buggy.
css.properties.border-right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-right.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-color 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-color.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-right-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.
css.properties.border-right-style.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-style.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-width 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-width.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-width.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-right-width.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-spacing 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-start-end-radius 📋Chrome3/2/2021 Edge3/4/20212
css.properties.border-start-start-radius 📋Chrome3/2/2021 Edge3/4/20212
css.properties.border-style 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-style.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-style.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-top.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-color 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-color.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-top-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-left-radius 📋Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-left-radius.elliptical_corners Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-left-radius.percentages Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-right-radius 📋Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-right-radius.elliptical_corners Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-right-radius.percentages Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-style 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-top-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners (with border-radius) were always rendered as if border-top-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-style.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-style.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-width 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-width.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-width.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-top-width.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-width 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-width.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-width.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.border-width.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.bottom 📋Chrome12/11/2008 Edge7/29/20152421
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.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.bottom.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.bottom.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.box-align Chrome12/11/2008 Edge7/29/20152421
css.properties.box-decoration-break 📋Chrome10/15/2024 Edge10/17/20242
Chrome: This property is only supported for inline elements.Chrome Android: This property is only supported for inline elements.Edge: This property is only supported for inline elements.Quest Browser: This property is only supported for inline elements.Safari: This property is only supported for inline elements.Safari on iOS: This property is only supported for inline elements.Samsung Internet: This property is only supported for inline elements.WebView Android: This property is only supported for inline elements.WebView on iOS: This property is only supported for inline elements.
css.properties.box-decoration-break.clone 📋Chrome10/15/2024 Edge10/17/20242
Chrome: This value was only supported with the -webkit- prefix.Chrome Android: This value was only supported with the -webkit- prefix.Edge: This value was only supported with the -webkit- prefix.Quest Browser: This value was only supported with the -webkit- prefix.Opera: This value was only supported with the -webkit- prefix.Opera Android: This value was only supported with the -webkit- prefix.Samsung Internet: This value was only supported with the -webkit- prefix.WebView Android: This value was only supported with the -webkit- prefix.
css.properties.box-decoration-break.slice 📋Chrome10/15/2024 Edge10/17/20242
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-direction Chrome12/11/2008 Edge7/29/20152421
css.properties.box-flex Chrome12/11/2008 Edge7/29/20152421
css.properties.box-ordinal-group Chrome12/11/2008 Edge7/29/20152421
css.properties.box-orient Chrome12/11/2008 Edge7/29/20152421
css.properties.box-pack Chrome12/11/2008 Edge7/29/20152421
css.properties.box-shadow 📋Chrome3/8/2011 Edge7/29/20151604
Chrome: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Chrome Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Firefox: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Firefox for Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Internet Explorer: To use box-shadow in Internet Explorer 9 or later, you must set border-collapse to separate.Internet Explorer: Since version 5.5, Internet Explorer supports Microsoft's DropShadow and Shadow Filter. You can use this proprietary extension to cast a drop shadow (though the syntax and the effect are different from CSS3)Quest Browser: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Opera: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Opera Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Safari: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Safari on iOS: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Samsung Internet: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.WebView Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.WebView on iOS: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.
css.properties.box-shadow.inset Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: inset must be the last keyword in the declaration.
css.properties.box-shadow.multiple_shadows Chrome12/11/2008 Edge7/29/20152421
css.properties.box-shadow.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.box-shadow.spread_radius Chrome12/11/2008 Edge7/29/20152421
css.properties.box-sizing 📋Chrome3/8/2011 Edge7/29/20151604
Chrome: box-sizing is not respected when the height is calculated from window.getComputedStyle().Chrome Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox: Before Firefox 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox for Android: Before Firefox for Android 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Internet Explorer: box-sizing is not respected when the height is calculated from window.getComputedStyle().Quest Browser: box-sizing is not respected when the height is calculated from window.getComputedStyle().Opera Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Samsung Internet: box-sizing is not respected when the height is calculated from window.getComputedStyle().WebView Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().
css.properties.box-sizing.border-box 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.box-sizing.content-box 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.break-after 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.break-after.auto Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.avoid Chrome4/13/2016 Edge1/15/20201372
Firefox: The value is recognized, but has no effect. See bug 1972340.Firefox for Android: The value is recognized, but has no effect. See bug 1972340.Safari: The value is recognized, but has no effect. See bug 294559.Safari on iOS: The value is recognized, but has no effect. See bug 294559.WebView on iOS: The value is recognized, but has no effect. See bug 294559.
css.properties.break-after.avoid-column Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.avoid-page Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.column Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.left Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.multicol_context 📋Edge7/29/2015 Chrome4/13/2016259
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.avoid Chrome5/24/2022 Edge5/31/20227
css.properties.break-after.multicol_context.avoid-column Chrome5/24/2022 Edge5/31/20227
css.properties.break-after.multicol_context.column Edge7/29/2015 Chrome4/13/2016259
css.properties.break-after.page Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.paged_context 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.break-after.paged_context.avoid-page Edge7/29/2015 Chrome4/13/2016259
css.properties.break-after.paged_context.page Edge7/29/2015 Chrome4/13/2016259
css.properties.break-after.recto Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.right Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.verso Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.break-before.auto Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.avoid Chrome4/13/2016 Edge1/15/20201372
Firefox: The value is recognized, but has no effect. See bug 1972340.Firefox for Android: The value is recognized, but has no effect. See bug 1972340.Safari: The value is recognized, but has no effect. See bug 294559.Safari on iOS: The value is recognized, but has no effect. See bug 294559.WebView on iOS: The value is recognized, but has no effect. See bug 294559.
css.properties.break-before.avoid-column Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.avoid-page Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.column Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.left Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.multicol_context 📋Edge7/29/2015 Chrome4/13/2016259
Firefox: Only supported in print mode. See bug 1675322.Firefox for Android: Only supported in print mode. See bug 1675322.
css.properties.break-before.multicol_context.avoid Chrome5/24/2022 Edge5/31/20227
css.properties.break-before.multicol_context.avoid-column Chrome5/24/2022 Edge5/31/20227
css.properties.break-before.multicol_context.column Edge7/29/2015 Chrome5/25/2016301
css.properties.break-before.page Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.paged_context 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.break-before.paged_context.page Edge7/29/2015 Chrome4/13/2016259
css.properties.break-before.recto Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.right Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.verso Chrome4/13/2016 Edge1/15/20201372
css.properties.break-inside 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.break-inside.auto Chrome4/13/2016 Edge1/15/20201372
css.properties.break-inside.avoid Chrome4/13/2016 Edge1/15/20201372
css.properties.break-inside.avoid-column Chrome4/13/2016 Edge1/15/20201372
css.properties.break-inside.avoid-page Chrome4/13/2016 Edge1/15/20201372
css.properties.break-inside.multicol_context 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.break-inside.multicol_context.avoid-column Edge7/29/2015 Chrome4/13/2016259
css.properties.break-inside.paged_context 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.break-inside.paged_context.avoid-page Edge7/29/2015 Chrome5/25/2016301
css.properties.buffered-rendering Chrome7/9/2013 Edge1/15/20202381
css.properties.buffered-rendering.auto Chrome7/9/2013 Edge1/15/20202381
css.properties.buffered-rendering.dynamic Chrome7/9/2013 Edge1/15/20202381
css.properties.buffered-rendering.static Chrome7/9/2013 Edge1/15/20202381
css.properties.caption-side 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.caption-side.bottom Chrome12/11/2008 Edge1/15/20204052
css.properties.caption-side.top Chrome12/11/2008 Edge1/15/20204052
css.properties.caret-animation 📋Chrome9/2/2025 Edge9/5/20253
css.properties.caret-animation.auto 📋Chrome9/2/2025 Edge9/5/20253
css.properties.caret-animation.manual 📋Chrome9/2/2025 Edge9/5/20253
css.properties.caret-color 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.caret-color.auto 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.caret-color.currentColor 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.caret-color.transparent 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.caret-shape 📋Chrome1/13/2026 Edge1/21/20268
css.properties.caret-shape.auto 📋Chrome1/13/2026 Edge1/21/20268
css.properties.caret-shape.bar 📋Chrome1/13/2026 Edge1/21/20268
css.properties.caret-shape.block 📋Chrome1/13/2026 Edge1/21/20268
css.properties.caret-shape.underscore 📋Chrome1/13/2026 Edge1/21/20268
css.properties.clear 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.clear.both 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.clear.inline-end 📋Chrome10/10/2023 Edge10/13/20233
css.properties.clear.inline-start 📋Chrome10/10/2023 Edge10/13/20233
css.properties.clear.left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.clear.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.clear.right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.clip 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: Before Internet Explorer 7, Internet Explorer incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).Safari: Safari incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).Safari on iOS: Safari on iOS incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).WebView on iOS: WebView on iOS incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).
css.properties.clip.auto Chrome12/11/2008 Edge1/15/20204052
css.properties.clip-path 📋Chrome12/1/2016 Edge1/15/20201140
Edge: Only supports clip paths defined by url().Internet Explorer: Only supports clip paths defined by url().
css.properties.clip-path.basic_shape 📋Chrome11/6/2012 Edge1/15/20202626
css.properties.clip-path.border-box 📋Chrome10/31/2023 Edge11/2/20232
css.properties.clip-path.content-box 📋Chrome10/31/2023 Edge11/2/20232
css.properties.clip-path.fill-box 📋Chrome10/31/2023 Edge11/2/20232
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.html_elements Chrome11/6/2012 Edge1/15/20202626
css.properties.clip-path.is_animatable Chrome12/1/2016 Edge1/15/20201140
css.properties.clip-path.margin-box 📋Chrome10/31/2023 Edge11/2/20232
css.properties.clip-path.padding-box 📋Chrome10/31/2023 Edge11/2/20232
css.properties.clip-path.path Chrome1/19/2021 Edge1/21/20212
css.properties.clip-path.stroke-box 📋Chrome10/31/2023 Edge11/2/20232
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.svg_elements Chrome11/6/2012 Edge7/29/2015995
css.properties.clip-path.view-box 📋Chrome10/31/2023 Edge11/2/20232
css.properties.clip-rule 📋Chrome10/25/2011 Edge1/15/20203004
css.properties.clip-rule.evenodd 📋Chrome10/25/2011 Edge1/15/20203004
css.properties.clip-rule.nonzero 📋Chrome10/25/2011 Edge1/15/20203004
css.properties.color 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.color-interpolation 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.color-interpolation.auto 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.color-interpolation.linearRGB 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.color-interpolation.sRGB 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.color-interpolation-filters 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.color-interpolation-filters.auto 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.color-interpolation-filters.linearRGB 📋Chrome7/9/2013 Edge1/15/20202381
css.properties.color-interpolation-filters.sRGB 📋Chrome7/9/2013 Edge1/15/20202381
css.properties.color-rendering Chrome12/11/2008 Edge1/15/20204052
css.properties.color-rendering.auto Chrome12/11/2008 Edge1/15/20204052
css.properties.color-rendering.optimizeQuality Chrome12/11/2008 Edge1/15/20204052
css.properties.color-rendering.optimizeSpeed Chrome12/11/2008 Edge1/15/20204052
css.properties.color-scheme 📋Chrome4/7/2020 Edge4/13/20206
css.properties.color-scheme.dark Chrome4/7/2020 Edge4/13/20206
css.properties.color-scheme.light Chrome4/7/2020 Edge4/13/20206
css.properties.color-scheme.normal Chrome4/7/2020 Edge4/13/20206
css.properties.color-scheme.only Chrome2/1/2022 Edge2/3/20222
css.properties.column-count 📋Edge7/29/2015 Chrome4/13/2016259
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-count.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-fill 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.column-fill.auto 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.column-fill.balance 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.column-gap 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-gap.flex_context 📋Edge7/16/2020 Chrome7/27/202011
css.properties.column-gap.grid_context 📋Edge10/17/2017 Chrome4/17/2018182
css.properties.column-gap.multicol_context 📋Edge7/29/2015 Chrome4/13/2016259
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.column-gap.multicol_context.calc_values Edge10/17/2017 Chrome4/17/2018182
css.properties.column-gap.multicol_context.percentage_values Edge10/17/2017 Chrome4/17/2018182
css.properties.column-gap.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-height 📋Chrome2/10/2026 Edge2/14/20264
css.properties.column-height.auto 📋Chrome2/10/2026 Edge2/14/20264
css.properties.column-rule 📋Edge7/29/2015 Chrome4/13/2016259
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.column-rule.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-color 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.column-rule-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.column-rule-style.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-style.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-width 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.column-rule-width.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-width.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-rule-width.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.column-span 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.column-span.all 📋Chrome9/2/2010 Edge7/29/20151791
css.properties.column-span.none 📋Chrome9/2/2010 Edge7/29/20151791
css.properties.column-width 📋Edge7/29/2015 Chrome4/13/2016259
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-width.auto Chrome12/11/2008 Edge7/29/20152421
css.properties.column-wrap 📋Chrome2/10/2026 Edge2/14/20264
css.properties.column-wrap.auto 📋Chrome2/10/2026 Edge2/14/20264
css.properties.column-wrap.nowrap 📋Chrome2/10/2026 Edge2/14/20264
css.properties.column-wrap.wrap 📋Chrome2/10/2026 Edge2/14/20264
css.properties.columns 📋Edge7/29/2015 Chrome4/13/2016259
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 📋Edge7/29/2015 Chrome4/13/2016259
css.properties.columns.column-height 📋Chrome2/10/2026 Edge2/14/20264
css.properties.contain 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.contain.content 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.contain.inline-size 📋Edge9/1/2022 Chrome9/2/20221
css.properties.contain.layout 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.contain.none 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.contain.paint 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.contain.size 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.contain.strict 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.contain.style 📋Chrome7/20/2016 Edge1/15/20201274
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.contain-intrinsic-block-size 📋Chrome10/19/2021 Edge10/21/20212
css.properties.contain-intrinsic-block-size.none 📋Chrome2/1/2022 Edge2/3/20222
css.properties.contain-intrinsic-height 📋Chrome10/19/2021 Edge10/21/20212
css.properties.contain-intrinsic-height.none 📋Chrome2/1/2022 Edge2/3/20222
css.properties.contain-intrinsic-inline-size 📋Chrome10/19/2021 Edge10/21/20212
css.properties.contain-intrinsic-inline-size.none 📋Chrome2/1/2022 Edge2/3/20222
css.properties.contain-intrinsic-size 📋Chrome5/19/2020 Edge5/21/20202
css.properties.contain-intrinsic-size.auto_none Chrome9/12/2023 Edge9/15/20233
css.properties.contain-intrinsic-size.none 📋Chrome2/1/2022 Edge2/3/20222
css.properties.contain-intrinsic-width 📋Chrome10/19/2021 Edge10/21/20212
css.properties.contain-intrinsic-width.none 📋Chrome2/1/2022 Edge2/3/20222
css.properties.container 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container.inline-size 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container.none 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container.normal 📋Chrome1/10/2023 Edge1/12/20232
css.properties.container.scroll-state 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container.size 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container-name 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container-name.none 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container-type 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container-type.anchored 📋Chrome12/2/2025 Edge12/5/20253
css.properties.container-type.inline-size 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container-type.normal 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container-type.scroll-state 📋Chrome2/4/2025 Edge2/6/20252
css.properties.container-type.size 📋Edge9/1/2022 Chrome9/2/20221
css.properties.container-type.weak_containment 📋Chrome9/17/2024 Edge9/19/20242
css.properties.content 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.content.alt_text Chrome9/10/2019 Edge1/15/2020127
css.properties.content.close-quote 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.content.element_replacement Chrome7/9/2013 Edge1/15/20202381
css.properties.content.gradient 📋Chrome3/26/2013 Edge7/29/2015855
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.image-set 📋Chrome5/2/2023 Edge5/5/20233
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.no-close-quote 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.content.no-open-quote 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.content.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.content.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.content.open-quote 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.content.url 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.content-visibility 📋Chrome8/25/2020 Edge8/27/20202
css.properties.content-visibility.auto 📋Chrome8/25/2020 Edge8/27/20202
Safari: Skipped content is not findable via find-in-page.Safari on iOS: Skipped content is not findable via find-in-page.WebView on iOS: Skipped content is not findable via find-in-page.
css.properties.content-visibility.hidden 📋Chrome8/25/2020 Edge8/27/20202
css.properties.content-visibility.is_transitionable 📋Chrome9/12/2023 Edge9/15/20233
css.properties.content-visibility.keyframe_animatable 📋Chrome8/15/2023 Edge8/21/20236
css.properties.content-visibility.visible 📋Chrome8/25/2020 Edge8/27/20202
css.properties.corner-block-end-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-end-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-end-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-end-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-end-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-end-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-end-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-start-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-start-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-start-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-start-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-start-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-start-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-block-start-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-left-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-left-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-left-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-left-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-left-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-left-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-left-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-right-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-right-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-right-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-right-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-right-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-right-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-right-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-bottom-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-end-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-end-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-end-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-end-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-end-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-end-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-end-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-start-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-start-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-start-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-start-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-start-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-start-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-end-start-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-end-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-end-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-end-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-end-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-end-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-end-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-end-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-start-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-start-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-start-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-start-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-start-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-start-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-inline-start-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-left-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-left-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-left-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-left-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-left-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-left-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-left-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-right-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-right-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-right-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-right-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-right-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-right-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-right-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-end-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-end-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-end-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-end-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-end-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-end-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-end-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-start-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-start-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-start-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-start-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-start-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-start-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-start-start-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-left-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-left-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-left-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-left-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-left-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-left-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-left-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-right-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-right-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-right-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-right-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-right-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-right-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-right-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-shape 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-shape.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-shape.notch 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-shape.round 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-shape.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-shape.square 📋Chrome8/5/2025 Edge8/7/20252
css.properties.corner-top-shape.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.properties.counter-increment 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.counter-increment.list-item 📋Chrome7/9/2013 Edge7/29/2015750
css.properties.counter-increment.none 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.counter-reset 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.counter-reset.list-item 📋Chrome7/9/2013 Edge7/29/2015750
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 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.counter-set 📋Chrome8/25/2020 Edge8/27/20202
css.properties.counter-set.list-item 📋Chrome8/25/2020 Edge8/27/20202
css.properties.counter-set.none 📋Chrome8/25/2020 Edge8/27/20202
css.properties.cursor 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Starting in Firefox 67, the maximum size allowed for custom cursors is 32x32 pixels due to cursors being misused by certain malicious sites.Internet Explorer: In Internet Explorer 11, when cursor is applied to an element and this element is underneath an open <select> menu and the user hovers over a <select> menu item that's on top of said element, the cursor for said element will be displayed rather than the <select>'s normal cursor. See bug 817822.Safari on iOS: This property is only supported on iPads with an external pointing device.Safari on iOS: Unsupported values use the default pointer as a fallback.WebView on iOS: This property is only supported on iPads with an external pointing device.WebView on iOS: Unsupported values use the default pointer as a fallback.
css.properties.cursor.alias 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.all-scroll 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.cursor.cell 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.cursor.col-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.context-menu 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: This cursor is only supported on macOS and Linux.Chrome Android: This cursor is only supported on macOS and Linux.Firefox: This cursor is only supported on macOS and Linux.Quest Browser: This cursor is only supported on macOS and Linux.Opera Android: This cursor is only supported on macOS and Linux.Safari on iOS: If this value is used, the iPad will display the default pointer instead.Samsung Internet: This cursor is only supported on macOS and Linux.WebView Android: This cursor is only supported on macOS and Linux.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.copy 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.crosshair 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.default 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.e-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ew-resize 📋Chrome12/11/2008 Edge7/29/20152421
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.grab Edge8/2/2016 Chrome7/24/2018721
Chrome: Chrome also continues to support the prefixed versions.Chrome: Chrome 22 added Windows support.Chrome Android: Chrome Android also continues to support the prefixed versions.Chrome Android: Chrome Android 25 added Windows support.Quest Browser: Quest Browser also continues to support the prefixed versions.Quest Browser: Quest Browser 5.0 added Windows support.Opera: Opera also continues to support the prefixed versions.Opera: Opera 22 added Windows support.Opera Android: Opera also continues to support the prefixed versions.Opera Android: Opera 22 added Windows support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView Android: WebView Android also continues to support the prefixed versions.WebView Android: WebView Android 4.4 added Windows support.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.grabbing 📋Chrome7/24/2018 Edge1/15/2020540
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.help 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.move 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.n-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ne-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nesw-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.no-drop 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.none 📋Chrome5/25/2010 Edge7/29/20151891
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.not-allowed 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ns-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nw-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nwse-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.pointer 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.progress 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.row-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.s-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.se-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.sw-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.text 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.cursor.url Chrome12/11/2008 Edge7/29/20152421
Firefox: Firefox 4 added macOS support.
css.properties.cursor.url_positioning_syntax Chrome12/11/2008 Edge1/15/20204052
Firefox: Firefox 4 added macOS support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.vertical-text 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.w-resize 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.wait 📋Chrome12/11/2008 Edge7/29/20152421
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 📋Chrome8/26/2014 Edge7/29/2015337
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.zoom-out 📋Chrome8/26/2014 Edge7/29/2015337
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.custom-property 📋Chrome3/2/2016 Edge4/5/2017399
css.properties.cx 📋Chrome5/19/2015 Edge1/15/20201702
css.properties.cy 📋Chrome5/19/2015 Edge1/15/20201702
css.properties.d 📋Chrome7/20/2016 Edge1/15/20201274
Safari: The property parses, but has no effect.Safari on iOS: The property parses, but has no effect.WebView on iOS: The property parses, but has no effect.
css.properties.d.none 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.direction 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.direction.ltr 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.direction.rtl 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.direction.vertical_slider_direction Chrome4/16/2024 Edge4/18/20242
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.display 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.display.block 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.display.contents 📋Chrome3/6/2018 Edge1/15/2020680
css.properties.display.contents.contents_unusual 📋Chrome3/6/2018 Edge1/15/2020680
css.properties.display.flex Chrome8/20/2013 Edge7/29/2015708
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.flow-root Chrome4/19/2017 Edge1/15/20201001
css.properties.display.grid Chrome3/9/2017 Edge10/17/2017222
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 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.display.inline-block Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: Until Internet Explorer 8, inline-block is only for natural inline elements.
css.properties.display.inline-flex Chrome8/20/2013 Edge7/29/2015708
Firefox: Firefox 28 added multi-line flexbox support.Firefox for Android: Firefox for Android 28 added multi-line flexbox support.
css.properties.display.inline-grid Chrome3/9/2017 Edge10/17/2017222
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-table Chrome12/11/2008 Edge7/29/20152421
css.properties.display.is_transitionable 📋Chrome9/12/2023 Edge9/15/20233
css.properties.display.keyframe_animatable 📋Chrome8/15/2023 Edge8/21/20236
css.properties.display.list-item 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.display.list-item.legend-support Chrome12/4/2018 Edge1/15/2020407
css.properties.display.math Chrome1/10/2023 Edge1/12/20232
css.properties.display.multi-keyword_values Chrome7/18/2023 Edge7/21/20233
css.properties.display.none 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: Chrome 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.Chrome Android: Chrome Android 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.Quest Browser: Quest Browser 5.0 stopped creating layout objects for elements inside an <iframe> with display:none applied.Opera: Opera 52 stopped creating layout objects for elements inside an <iframe> with display:none applied.Opera Android: Opera Android 47 stopped creating layout objects for elements inside an <iframe> with display:none applied.Samsung Internet: Chrome 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.WebView Android: WebView Android 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.
css.properties.display.none.option_is_hidden Chrome12/11/2008 Edge1/15/20204052
css.properties.display.table Chrome12/11/2008 Edge7/29/20152421
css.properties.display.table-caption Chrome12/11/2008 Edge4/5/20173037
css.properties.display.table-cell Chrome12/11/2008 Edge7/29/20152421
css.properties.display.table-column Chrome12/11/2008 Edge7/29/20152421
css.properties.display.table-column-group Chrome12/11/2008 Edge7/29/20152421
css.properties.display.table-footer-group Chrome12/11/2008 Edge7/29/20152421
css.properties.display.table-header-group Chrome12/11/2008 Edge7/29/20152421
css.properties.display.table-row Chrome12/11/2008 Edge7/29/20152421
css.properties.display.table-row-group Chrome12/11/2008 Edge7/29/20152421
css.properties.dominant-baseline 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.dominant-baseline.alphabetic 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.dominant-baseline.auto 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.dominant-baseline.central 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.dominant-baseline.hanging 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.dominant-baseline.ideographic 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.dominant-baseline.mathematical 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.dominant-baseline.middle 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.dynamic-range-limit 📋Chrome4/29/2025 Edge5/1/20252
css.properties.dynamic-range-limit.constrained 📋Chrome4/29/2025 Edge5/1/20252
css.properties.dynamic-range-limit.dynamic-range-limit-mix_values 📋Chrome4/29/2025 Edge5/1/20252
css.properties.dynamic-range-limit.no-limit 📋Chrome4/29/2025 Edge5/1/20252
css.properties.dynamic-range-limit.standard 📋Chrome4/29/2025 Edge5/1/20252
css.properties.empty-cells 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.empty-cells.hide 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.empty-cells.show 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.field-sizing 📋Chrome3/19/2024 Edge3/22/20243
css.properties.field-sizing.content 📋Chrome3/19/2024 Edge3/22/20243
css.properties.field-sizing.fixed 📋Chrome3/19/2024 Edge3/22/20243
css.properties.fill 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.fill.none 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.fill-opacity 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.fill-rule 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.fill-rule.evenodd 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.fill-rule.nonzero 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.filter 📋Edge7/29/2015 Chrome8/31/2016399
Internet Explorer: Internet Explorer 4 to 9 implemented a non-standard filter property. The syntax was completely different from this one and is not documented here.
css.properties.filter.blur 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.brightness 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.contrast 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.drop-shadow 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.grayscale 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.hue-rotate 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.invert 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.none 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.opacity 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.saturate 📋Chrome3/28/2012 Edge7/29/20151218
Chrome: In Chrome 18 to 19, the saturate() function only takes integers instead of decimal or percentage values. From Chrome 20, this bug is fixed.
css.properties.filter.sepia 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.svg_elements Chrome3/2/2021 Edge3/4/20212
css.properties.flex 📋Chrome8/20/2013 Edge7/29/2015708
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 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex.content 📋Chrome9/21/2021 Edge9/24/20213
css.properties.flex.fit-content 📋Chrome9/21/2021 Edge9/24/20213
css.properties.flex.max-content 📋Chrome9/21/2021 Edge9/24/20213
css.properties.flex.min-content 📋Chrome9/21/2021 Edge9/24/20213
css.properties.flex.none 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.flex-basis 📋Chrome8/20/2013 Edge7/29/2015708
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Internet Explorer: When a non-auto flex-basis is specified, Internet Explorer 10 and 11 always uses a content-box box model to calculate the size of a flex item, even if box-sizing: border-box is applied to the element. See Flexbug #7 for more info.
css.properties.flex-basis.auto Chrome9/25/2012 Edge7/29/20151037
css.properties.flex-basis.content Chrome9/21/2021 Edge9/24/20213
css.properties.flex-basis.fit-content Chrome9/21/2021 Edge9/24/20213
css.properties.flex-basis.max-content Chrome9/21/2021 Edge9/24/20213
css.properties.flex-basis.min-content Chrome9/21/2021 Edge9/24/20213
css.properties.flex-basis.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.flex-direction 📋Chrome8/20/2013 Edge7/29/2015708
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 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-direction.column-reverse 📋Chrome7/31/2012 Edge7/29/20151093
Firefox: Before Firefox 81, overflow with column-reverse was unsupported. See bug 1042151.Firefox for Android: Before Firefox for Android 81, overflow with column-reverse was unsupported. See bug 1042151.
css.properties.flex-direction.row 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-direction.row-reverse 📋Chrome7/31/2012 Edge7/29/20151093
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 📋Chrome8/20/2013 Edge7/29/2015708
css.properties.flex-flow.column 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.column-reverse 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.nowrap 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.row 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.row-reverse 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.wrap 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.wrap-reverse 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-grow 📋Chrome8/20/2013 Edge7/29/2015708
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-grow.less_than_zero_animate Chrome3/2/2016 Edge1/15/20201414
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.flex-shrink 📋Chrome8/20/2013 Edge7/29/2015708
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox: Before Firefox 32, Firefox wasn't able to animate values starting or stopping at 0.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Firefox for Android: Before Firefox for Android 32, Firefox for Android wasn't able to animate values starting or stopping at 0.Internet Explorer: Internet Explorer 10 uses 0 instead of 1 as the initial value for the flex-shrink property. A workaround is to always set an explicit value for flex-shrink. See Flexbug #6 for more info.
css.properties.flex-wrap 📋Chrome8/20/2013 Edge7/29/2015708
Internet Explorer: Partial support due to large number of bugs present. See Flexbugs.
css.properties.flex-wrap.nowrap 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-wrap.wrap 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-wrap.wrap-reverse 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.float 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.float.inline-end 📋Chrome10/10/2023 Edge10/13/20233
css.properties.float.inline-start 📋Chrome10/10/2023 Edge10/13/20233
css.properties.float.left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.float.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.float.right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.flood-color 📋Chrome5/25/2010 Edge7/29/20151891
css.properties.flood-color.currentColor 📋Chrome5/25/2010 Edge7/29/20151891
css.properties.flood-color.transparent 📋Chrome5/25/2010 Edge7/29/20151891
css.properties.flood-opacity 📋Chrome5/25/2010 Edge7/29/20151891
css.properties.font 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font.caption Chrome12/11/2008 Edge7/29/20152421
css.properties.font.font-width_keyword_values Chrome7/25/2017 Edge1/15/2020904
css.properties.font.icon Chrome12/11/2008 Edge7/29/20152421
css.properties.font.menu Chrome12/11/2008 Edge7/29/20152421
css.properties.font.message-box Chrome12/11/2008 Edge7/29/20152421
css.properties.font.small-caption Chrome12/11/2008 Edge7/29/20152421
css.properties.font.status-bar Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Not supported on option elements. See bug 1536148.Safari: Setting font-family: initial behaves like font-family: inherit. See bug 200709.Safari on iOS: Setting font-family: initial behaves like font-family: inherit. See bug 200709.WebView on iOS: Setting font-family: initial behaves like font-family: inherit. See bug 200709.
css.properties.font-family.cursive 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.fangsong 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.fantasy 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.kai 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.khmer-mul 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.math Chrome1/10/2023 Edge1/12/20232
css.properties.font-family.monospace 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.nastaliq 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.sans-serif 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.serif 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-family.system-ui Chrome1/25/2017 Edge1/15/20201085
Firefox: Supported on macOS only.
css.properties.font-feature-settings 📋Chrome1/20/2016 Edge4/5/2017441
Firefox: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox: From Firefox 129 the -webkit-font-feature-settings alias has been added to support sites that are still supporting the vendor prefix.Firefox: From Firefox 4 to Firefox 14 (inclusive), Firefox supported an older, slightly different syntax. See OpenType Font Feature support in Firefox 4.Firefox for Android: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox for Android 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox for Android 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox for Android: From Firefox for Android 129 the -webkit-font-feature-settings alias has been added to support sites that are still supporting the vendor prefix.Firefox for Android: From Firefox for Android 4 to Firefox for Android 14 (inclusive), Firefox for Android supported an older, slightly different syntax. See OpenType Font Feature support in Firefox for Android 4.
css.properties.font-feature-settings.normal 📋Chrome12/13/2011 Edge4/5/20171940
css.properties.font-kerning 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.font-kerning.auto 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.font-kerning.none 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.font-kerning.normal 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.font-language-override 📋Chrome12/2/2025 Edge12/5/20253
css.properties.font-language-override.normal 📋Chrome12/2/2025 Edge12/5/20253
css.properties.font-optical-sizing 📋Edge4/30/2018 Chrome12/10/2019589
css.properties.font-optical-sizing.auto 📋Edge4/30/2018 Chrome12/10/2019589
css.properties.font-optical-sizing.none 📋Edge4/30/2018 Chrome12/10/2019589
css.properties.font-palette 📋Chrome4/26/2022 Edge4/28/20222
css.properties.font-palette.animation_computed Chrome1/23/2024 Edge1/25/20242
css.properties.font-palette.dark 📋Chrome4/26/2022 Edge4/28/20222
css.properties.font-palette.light 📋Chrome4/26/2022 Edge4/28/20222
css.properties.font-palette.normal 📋Chrome4/26/2022 Edge4/28/20222
css.properties.font-palette.palette-mix_function 📋Chrome1/23/2024 Edge1/25/20242
css.properties.font-size 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-size.math Chrome1/10/2023 Edge1/12/20232
css.properties.font-size.rem_values Chrome11/12/2013 Edge7/29/2015624
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-size.xxx-large Chrome12/10/2019 Edge1/15/202036
css.properties.font-size-adjust 📋Chrome7/23/2024 Edge7/25/20242
Firefox: Before Firefox 40, font-size-adjust: 0 was incorrectly interpreted as font-size-adjust: none (bug 1144885).Firefox: Only supported on Windows.Firefox for Android: Before Firefox for Android 40, font-size-adjust: 0 was incorrectly interpreted as font-size-adjust: none (bug 1144885).
css.properties.font-size-adjust.from-font 📋Chrome7/23/2024 Edge7/25/20242
css.properties.font-size-adjust.none 📋Chrome7/23/2024 Edge7/25/20242
css.properties.font-size-adjust.two-values Chrome7/23/2024 Edge7/25/20242
css.properties.font-smooth Chrome5/25/2010 Edge1/15/20203522
Firefox: Only works on macOS.
css.properties.font-stretch 📋Edge7/29/2015 Chrome7/25/2017727
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 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-stretch.expanded 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-stretch.extra-condensed 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-stretch.extra-expanded 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-stretch.normal 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-stretch.percentage Chrome10/17/2017 Edge10/2/2018350
css.properties.font-stretch.semi-condensed 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-stretch.semi-expanded 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-stretch.ultra-condensed 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-stretch.ultra-expanded 📋Edge7/29/2015 Chrome7/25/2017727
css.properties.font-style 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 44, oblique was not distinguished from italic.Firefox for Android: Before Firefox for Android 44, oblique was not distinguished from italic.
css.properties.font-style.italic 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-style.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-style.oblique 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-style.oblique-angle 📋Chrome10/17/2017 Edge1/15/2020820
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-synthesis 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis.none 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis.small-caps Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis.style Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis.weight Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-small-caps 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-small-caps.auto 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-small-caps.none 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-style 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-style.auto 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-style.none 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-weight 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-weight.auto 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-synthesis-weight.none 📋Chrome1/4/2022 Edge1/6/20222
css.properties.font-variant 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: Only supports the small-caps and normal keywords.
css.properties.font-variant.css_fonts_shorthand Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant.historical-forms 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant.none 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.font-variant.sub 📋Chrome2/7/2023 Edge2/9/20232
css.properties.font-variant.super 📋Chrome2/7/2023 Edge2/9/20232
css.properties.font-variant.turkic_is Chrome11/12/2013 Edge7/29/2015624
css.properties.font-variant-alternates 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-alternates.annotation 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-alternates.character_variant 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-alternates.historical-forms 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-alternates.normal 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-alternates.ornaments 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-alternates.styleset 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-alternates.stylistic 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-alternates.swash 📋Chrome3/7/2023 Edge3/13/20236
css.properties.font-variant-caps 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-caps.all-petite-caps 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-caps.all-small-caps 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-caps.normal 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-caps.petite-caps 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-caps.small-caps 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-caps.titling-caps 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-caps.unicase 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-east-asian 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.full-width 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.jis04 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.jis78 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.jis83 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.jis90 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.normal 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.proportional-width 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.ruby 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.simplified 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-east-asian.traditional 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.font-variant-emoji 📋Chrome11/12/2024 Edge11/14/20242
css.properties.font-variant-emoji.emoji 📋Chrome11/12/2024 Edge11/14/20242
css.properties.font-variant-emoji.normal 📋Chrome11/12/2024 Edge11/14/20242
css.properties.font-variant-emoji.text 📋Chrome11/12/2024 Edge11/14/20242
css.properties.font-variant-emoji.unicode 📋Chrome11/12/2024 Edge11/14/20242
css.properties.font-variant-ligatures 📋Chrome4/8/2014 Edge1/15/20202108
css.properties.font-variant-ligatures.common-ligatures 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.contextual 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.discretionary-ligatures 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.historical-ligatures 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.no-common-ligatures 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.no-contextual 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.no-discretionary-ligatures 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.no-historical-ligatures 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.none 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-ligatures.normal 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.font-variant-numeric 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.diagonal-fractions 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.lining-nums 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.normal 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.oldstyle-nums 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.ordinal 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.proportional-nums 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.slashed-zero 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.stacked-fractions 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-numeric.tabular-nums 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.font-variant-position 📋Chrome9/12/2023 Edge9/15/20233
css.properties.font-variant-position.normal 📋Chrome9/12/2023 Edge9/15/20233
css.properties.font-variant-position.sub 📋Chrome9/12/2023 Edge9/15/20233
Chrome: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Chrome Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Edge: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Opera: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Opera Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Safari: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).Safari on iOS: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).Samsung Internet: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).WebView Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).WebView on iOS: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).
css.properties.font-variant-position.super 📋Chrome9/12/2023 Edge9/15/20233
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.font-variation-settings 📋Chrome10/17/2017 Edge4/30/2018195
Safari: Requires macOS 10.13 High Sierra or later.Safari on iOS: Requires iOS 11 or later.WebView on iOS: Requires iOS 11 or later.
css.properties.font-variation-settings.normal 📋Chrome10/17/2017 Edge4/30/2018195
css.properties.font-weight 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.font-weight.bold 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.font-weight.bolder 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.font-weight.lighter 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.font-weight.normal 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.font-weight.number Chrome10/17/2017 Edge4/30/2018195
css.properties.forced-color-adjust 📋Edge1/15/2020 Chrome3/2/2021412
css.properties.forced-color-adjust.auto 📋Edge1/15/2020 Chrome3/2/2021412
css.properties.forced-color-adjust.none 📋Edge1/15/2020 Chrome3/2/2021412
css.properties.forced-color-adjust.preserve-parent-color 📋Chrome9/27/2022 Edge10/3/20226
css.properties.gap 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.gap.flex_context 📋Edge7/16/2020 Chrome7/27/202011
css.properties.gap.grid_context 📋Edge10/17/2017 Chrome4/17/2018182
css.properties.gap.grid_context.calc_values Edge10/17/2017 Chrome4/17/2018182
css.properties.gap.grid_context.percentage_values Edge10/17/2017 Chrome4/17/2018182
css.properties.gap.multicol_context 📋Edge10/17/2017 Chrome4/17/2018182
css.properties.gap.normal 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid 📋Chrome3/9/2017 Edge10/17/2017222
Samsung Internet: This was added early so is out of sync with the equivalent Chromium version.
css.properties.grid.none 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-area 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-area.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-auto-columns 📋Chrome3/9/2017 Edge10/17/2017222
Firefox: Does not accept multiple track-size values. See bug 1339672.Firefox for Android: Does not accept multiple track-size values. See bug 1339672.
css.properties.grid-auto-columns.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-auto-columns.max-content 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-auto-columns.min-content 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-auto-flow 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-auto-flow.column 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-auto-flow.dense 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-auto-flow.row 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-auto-rows 📋Chrome3/9/2017 Edge10/17/2017222
Firefox: Does not accept multiple track-size values. See bug 1339672.Firefox for Android: Does not accept multiple track-size values. See bug 1339672.
css.properties.grid-auto-rows.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-auto-rows.max-content 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-auto-rows.min-content 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-column 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-column.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-column-end 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-column-end.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-column-start 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-column-start.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-row 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-row.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-row-end 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-row-end.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-row-start 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-row-start.auto 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template.none 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-areas 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template-areas.none 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-columns 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template-columns.animation Chrome10/25/2022 Edge10/27/20222
css.properties.grid-template-columns.auto 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-columns.fit-content 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template-columns.max-content 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-columns.min-content 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-columns.minmax 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template-columns.none 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-columns.repeat 📋Chrome3/9/2017 Edge10/17/2017222
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-columns.subgrid 📋Chrome9/12/2023 Edge9/15/20233
css.properties.grid-template-rows 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template-rows.animation Chrome10/25/2022 Edge10/27/20222
css.properties.grid-template-rows.auto 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-rows.fit-content 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template-rows.max-content 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-rows.min-content 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-rows.minmax 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.grid-template-rows.none 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.grid-template-rows.repeat 📋Chrome3/9/2017 Edge10/17/2017222
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.subgrid 📋Chrome9/12/2023 Edge9/15/20233
css.properties.height 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.height.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.height.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.height.fit-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.height.max-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.height.min-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.height.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.hyphenate-character 📋Chrome9/27/2022 Edge10/3/20226
css.properties.hyphenate-character.auto 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.hyphenate-limit-chars 📋Chrome1/10/2023 Edge1/12/20232
css.properties.hyphenate-limit-chars.auto 📋Chrome1/10/2023 Edge1/12/20232
css.properties.hyphens 📋Chrome12/1/2016 Edge1/15/20201140
Edge: Only works if the specified language is the same as the language of the underlying OS.Internet Explorer: Only works if the specified language is the same as the language of the underlying OS.
css.properties.hyphens.auto Chrome1/19/2021 Edge1/21/20212
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.language_afrikaans Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_albanian Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_amharic Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_armenian Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_assamese Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_basque Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_belarusian Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_bengali Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_bulgarian Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_croatian Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_cyrillic_mongolian Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_czech Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_danish Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_dutch Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_english Edge7/29/2015 Chrome12/1/2016491
Firefox: For English, Firefox uses an en-US dictionaryFirefox for Android: For English, Firefox for Android uses an en-US dictionarySafari: For English, Safari uses different en-GB and en-US dictionaries.Safari on iOS: For English, Safari on iOS uses different en-GB and en-US dictionaries.WebView on iOS: For English, WebView on iOS uses different en-GB and en-US dictionaries.
css.properties.hyphens.language_estonian Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_ethiopic_script_mul Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_ethiopic_script_und Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_french Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_galician Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_georgian Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_german_reformed_orthography Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_german_swiss_orthography Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_german_traditional_orthography Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_gujarati Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_hindi Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_hungarian Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_irish Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_italian Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_kannada Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_latin Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_latvian Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_lithuanian Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_malayalam Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_marathi Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_modern_greek Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_norwegian_nn Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_norwegian_no Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_old_slavonic Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_oriya Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_portuguese Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_punjabi Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_russian Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_slovak Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_slovenian Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_spanish Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_swedish Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_tamil Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_telugu Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_turkmen Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.language_ukrainian Chrome4/4/2023 Edge4/6/20232
css.properties.hyphens.language_welsh Chrome11/17/2020 Edge11/19/20202
css.properties.hyphens.manual Chrome1/19/2021 Edge1/21/20212
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.none Chrome1/19/2021 Edge1/21/20212
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.image-orientation 📋Chrome4/7/2020 Edge4/13/20206
css.properties.image-orientation.from-image 📋Chrome4/7/2020 Edge4/13/20206
css.properties.image-orientation.none 📋Chrome4/7/2020 Edge4/13/20206
css.properties.image-rendering 📋Chrome8/2/2011 Edge1/15/20203088
css.properties.image-rendering.auto 📋Chrome8/2/2011 Edge1/15/20203088
css.properties.image-rendering.crisp-edges 📋Chrome8/2/2011 Edge1/15/20203088
css.properties.image-rendering.pixelated 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.initial-letter 📋Chrome2/7/2023 Edge2/9/20232
Safari: See bug 229090 for the unprefixed property.Safari on iOS: See bug 229090 for the unprefixed property.Safari on iOS: Does not support decimal values. See bug 296785.WebView on iOS: See bug 229090 for the unprefixed property.WebView on iOS: Does not support decimal values. See bug 296785.
css.properties.initial-letter.normal 📋Chrome2/7/2023 Edge2/9/20232
css.properties.inline-size 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.inline-size.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.inline-size.auto 📋Chrome12/2/2010 Edge1/15/20203331
css.properties.inline-size.fit-content 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.inline-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.inline-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.inline-size.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.inset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.inset.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.inset.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-block 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-block.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.inset-block.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.inset-block.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-block-end 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-block-end.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.inset-block-end.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.inset-block-end.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-block-start 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-block-start.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.inset-block-start.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.inset-block-start.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-inline 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-inline.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.inset-inline.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.inset-inline.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-inline-end 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-inline-end.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.inset-inline-end.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.inset-inline-end.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-inline-start 📋Chrome11/17/2020 Edge11/19/20202
css.properties.inset-inline-start.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.inset-inline-start.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.inset-inline-start.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.interactivity 📋Chrome4/1/2025 Edge4/4/20253
css.properties.interactivity.auto 📋Chrome4/1/2025 Edge4/4/20253
css.properties.interactivity.inert 📋Chrome4/1/2025 Edge4/4/20253
css.properties.interest-delay 📋Chrome10/28/2025 Edge10/31/20253
css.properties.interest-delay.normal 📋Chrome10/28/2025 Edge10/31/20253
css.properties.interest-delay-end 📋Chrome10/28/2025 Edge10/31/20253
css.properties.interest-delay-end.normal 📋Chrome10/28/2025 Edge10/31/20253
css.properties.interest-delay-start 📋Chrome10/28/2025 Edge10/31/20253
css.properties.interest-delay-start.normal 📋Chrome10/28/2025 Edge10/31/20253
css.properties.interpolate-size 📋Chrome9/17/2024 Edge9/19/20242
css.properties.interpolate-size.allow-keywords 📋Chrome9/17/2024 Edge9/19/20242
css.properties.interpolate-size.numeric-only 📋Chrome9/17/2024 Edge9/19/20242
css.properties.isolation 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.isolation.auto 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.isolation.isolate 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.justify-content 📋Chrome8/20/2013 Edge7/29/2015708
css.properties.justify-content.flex_context 📋Edge7/29/2015 Chrome7/20/2016357
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-content.flex_context.left_right Chrome8/31/2021 Edge9/2/20212
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.safe_unsafe Chrome7/18/2023 Edge7/21/20233
Chrome: Before version 115, this value is recognized, but has no effect.Chrome Android: Before version 115, this value is recognized, but has no effect.Edge: Before version 115, this value is recognized, but has no effect.Opera: Before version 101, this value is recognized, but has no effect.Opera Android: Before version 77, this value is recognized, but has no effect.Samsung Internet: Before version 23.0, this value is recognized, but has no effect.WebView Android: Before version 115, this value is recognized, but has no effect.
css.properties.justify-content.flex_context.space-evenly Chrome7/25/2017 Edge1/15/2020904
css.properties.justify-content.flex_context.start_end Chrome8/31/2021 Edge9/2/20212
css.properties.justify-content.flex_context.stretch Chrome3/9/2017 Edge1/15/20201042
css.properties.justify-content.grid_context 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.justify-content.left Chrome7/31/2012 Edge1/15/20202724
css.properties.justify-content.normal Chrome7/31/2012 Edge1/15/20202724
css.properties.justify-content.right Chrome7/31/2012 Edge1/15/20202724
css.properties.justify-items 📋Edge7/29/2015 Chrome7/20/2016357
css.properties.justify-items.anchor-center 📋Chrome5/14/2024 Edge5/17/20243
css.properties.justify-items.block_context 📋Chrome10/15/2024 Edge10/17/20242
css.properties.justify-items.center Chrome7/20/2016 Edge1/15/20201274
css.properties.justify-items.flex_context 📋Edge7/29/2015 Chrome7/20/2016357
css.properties.justify-items.grid_context 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.justify-items.left Chrome7/20/2016 Edge1/15/20201274
css.properties.justify-items.legacy 📋Chrome7/20/2016 Edge1/15/20201274
css.properties.justify-items.right Chrome7/20/2016 Edge1/15/20201274
css.properties.justify-self 📋Chrome3/9/2017 Edge10/17/2017222
css.properties.justify-self.anchor-center 📋Chrome5/14/2024 Edge5/17/20243
css.properties.justify-self.auto Chrome3/9/2017 Edge1/15/20201042
css.properties.justify-self.block_context 📋Chrome10/15/2024 Edge10/17/20242
css.properties.justify-self.grid_context 📋Chrome3/9/2017 Edge10/17/2017222
Internet Explorer: Internet Explorer 10 and 11 have the property -ms-grid-column-align, which acts in a similar way to justify-self.
css.properties.justify-self.left Chrome3/9/2017 Edge1/15/20201042
css.properties.justify-self.normal Chrome3/9/2017 Edge1/15/20201042
css.properties.justify-self.position_absolute_context 📋Chrome2/20/2024 Edge2/23/20243
css.properties.justify-self.right Chrome3/9/2017 Edge1/15/20201042
css.properties.justify-self.stretch Chrome3/9/2017 Edge1/15/20201042
css.properties.left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.left.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.left.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.left.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.letter-spacing 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.letter-spacing.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.letter-spacing.svg_elements Chrome12/11/2008 Edge7/29/20152421
css.properties.lighting-color 📋Chrome5/25/2010 Edge7/29/20151891
css.properties.lighting-color.currentColor 📋Chrome5/25/2010 Edge7/29/20151891
css.properties.lighting-color.transparent 📋Chrome5/25/2010 Edge7/29/20151891
css.properties.line-break 📋Edge8/2/2016 Chrome4/19/2017260
css.properties.line-break.anywhere 📋Chrome5/19/2020 Edge5/21/20202
css.properties.line-break.auto 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.line-break.loose 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.line-break.normal 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.line-break.strict 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.line-clamp 📋Chrome9/2/2010 Edge4/30/20182797
Safari: Accidental exposure.Safari on iOS: Accidental exposure.WebView on iOS: Accidental exposure.
css.properties.line-height 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.line-height.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style.inside 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style.outside 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-image 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 86, this property did not accept an <image> type, and required the URL of an image.Firefox for Android: Before Firefox for Android 86, this property did not accept an <image> type, and required the URL of an image.
css.properties.list-style-image.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-position 📋Chrome12/11/2008 Edge7/29/20152421
Safari: In Safari, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.Safari on iOS: In Safari on iOS, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.WebView on iOS: In WebView on iOS, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.
css.properties.list-style-position.inside 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-position.outside 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.afar Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.amharic Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.amharic-abegede Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.arabic-indic 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.armenian 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.asterisks Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.bengali 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.binary Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.cambodian 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.circle 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.cjk-decimal 📋Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.cjk-earthly-branch 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.cjk-heavenly-stem 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.cjk-ideographic 📋Chrome12/11/2008 Edge1/15/20204052
Opera: Until version 15, only decimal numbers display.Opera Android: Until version 15, only decimal numbers display.
css.properties.list-style-type.decimal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.decimal-leading-zero 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.devanagari 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.disc 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.disclosure-closed 📋Chrome3/2/2021 Edge3/4/20212
css.properties.list-style-type.disclosure-open 📋Chrome3/2/2021 Edge3/4/20212
css.properties.list-style-type.ethiopic Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-abegede Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-abegede-am-et Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-abegede-gez Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-abegede-ti-er Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-abegede-ti-et Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-halehame Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.ethiopic-halehame-aa-er Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-halehame-aa-et Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-halehame-am Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.ethiopic-halehame-am-et Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-halehame-gez Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-halehame-om-et Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-halehame-sid-et Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-halehame-so-et Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-halehame-ti-er Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.ethiopic-halehame-ti-et Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.ethiopic-halehame-tig Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.ethiopic-numeric 📋Chrome5/25/2021 Edge5/27/20212
Firefox: Before Firefox 38, Firefox added a dot as suffix of the number for ethiopic-numeric (for example, ፫. instead of ፫). The specification later defined the absence of a suffix, which Firefox 38 followed.Firefox for Android: Before Firefox for Android 38, Firefox for Android added a dot as suffix of the number for ethiopic-numeric (for example, ፫. instead of ፫). The specification later defined the absence of a suffix, which Firefox for Android 38 followed.
css.properties.list-style-type.footnotes Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.georgian 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.gujarati 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.gurmukhi 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.hangul Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.hangul-consonant Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.hebrew 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.hiragana 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.hiragana-iroha 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.japanese-formal 📋Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.japanese-informal 📋Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.kannada 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.katakana 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.katakana-iroha 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.khmer 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.korean-hangul-formal 📋Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.korean-hanja-formal 📋Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.korean-hanja-informal 📋Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.lao 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.lower-alpha 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.lower-armenian 📋Chrome8/2/2011 Edge1/15/20203088
css.properties.list-style-type.lower-greek 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.lower-hexadecimal Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.lower-latin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.lower-norwegian Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.lower-roman 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.malayalam 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.mongolian 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.myanmar 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.octal Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.oriya 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.oromo Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.persian 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.sidama Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.simp-chinese-formal 📋Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.simp-chinese-informal 📋Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.somali Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.square 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.string Chrome12/10/2019 Edge1/15/202036
css.properties.list-style-type.tamil 📋Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.telugu 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.thai 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.tibetan 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.list-style-type.tigre Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.tigrinya-er Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.tigrinya-er-abegede Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.tigrinya-et Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.tigrinya-et-abegede Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.trad-chinese-formal 📋Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.trad-chinese-informal 📋Chrome9/1/2015 Edge1/15/20201597
css.properties.list-style-type.upper-alpha 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.upper-armenian 📋Chrome8/2/2011 Edge1/15/20203088
css.properties.list-style-type.upper-greek Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.upper-hexadecimal Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.upper-latin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.upper-norwegian Chrome5/25/2021 Edge5/27/20212
css.properties.list-style-type.upper-roman 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.list-style-type.urdu Chrome9/2/2010 Edge1/15/20203422
css.properties.margin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.margin.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin.auto Chrome12/11/2008 Edge7/29/20152421
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-block 📋Chrome11/17/2020 Edge11/19/20202
css.properties.margin-block.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-block.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.margin-block-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.margin-block-end.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-block-end.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.margin-block-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.margin-block-start.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-block-start.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.margin-bottom 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.margin-bottom.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-bottom.auto 📋Chrome12/11/2008 Edge7/29/20152421
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-inline 📋Chrome11/17/2020 Edge11/19/20202
css.properties.margin-inline.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-inline.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.margin-inline-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.margin-inline-end.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-inline-end.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.margin-inline-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.margin-inline-start.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-inline-start.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.margin-left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.margin-left.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-left.auto Chrome12/11/2008 Edge7/29/20152421
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.margin-right.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-right.auto Chrome12/11/2008 Edge7/29/20152421
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-top 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.margin-top.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.margin-top.auto Chrome12/11/2008 Edge7/29/20152421
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.marker 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.marker.none 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.marker-end 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.marker-end.none 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.marker-mid 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.marker-mid.none 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.marker-start 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.marker-start.none 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.mask 📋Chrome12/5/2023 Edge12/7/20232
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-border 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-border-outset 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-border-repeat 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-border-slice 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-border-source 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-border-width 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-clip 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-clip.border Chrome12/11/2008 Edge1/15/20204052
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.border-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-clip.content Chrome12/11/2008 Edge1/15/20204052
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-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-clip.fill-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-clip.no-clip Chrome12/5/2023 Edge12/7/20232
css.properties.mask-clip.padding Chrome12/11/2008 Edge1/15/20204052
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-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-clip.stroke-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-clip.text Chrome12/11/2008 Edge1/15/20204052
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.view-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-composite 📋Chrome12/5/2023 Edge12/7/20232
Chrome: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Chrome Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Edge: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Opera: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Opera Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Safari: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Safari on iOS: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Samsung Internet: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.WebView Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.WebView on iOS: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.
css.properties.mask-composite.add 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-composite.exclude 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-composite.intersect 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-composite.subtract 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-image 📋Chrome12/5/2023 Edge12/7/20232
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-image.multiple_mask_images Chrome12/11/2008 Edge10/2/20183582
css.properties.mask-image.svg_masks Chrome12/2/2010 Edge10/2/20182861
css.properties.mask-mode 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-mode.alpha 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-mode.luminance 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-mode.match-source 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-origin 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-origin.border Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-origin.border-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-origin.content Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-origin.content-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-origin.fill-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-origin.padding Chrome12/11/2008 Edge1/15/20204052
css.properties.mask-origin.padding-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-origin.stroke-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-origin.view-box Chrome12/5/2023 Edge12/7/20232
css.properties.mask-position 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-repeat 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-size 📋Chrome12/5/2023 Edge12/7/20232
css.properties.mask-type 📋Chrome1/10/2013 Edge1/15/20202561
css.properties.mask-type.alpha 📋Chrome1/10/2013 Edge1/15/20202561
css.properties.mask-type.luminance 📋Chrome1/10/2013 Edge1/15/20202561
css.properties.math-depth 📋Chrome1/10/2023 Edge1/12/20232
css.properties.math-depth.auto-add 📋Chrome1/10/2023 Edge1/12/20232
css.properties.math-shift 📋Chrome1/10/2023 Edge1/12/20232
css.properties.math-shift.compact 📋Chrome1/10/2023 Edge1/12/20232
css.properties.math-shift.normal 📋Chrome1/10/2023 Edge1/12/20232
css.properties.math-style 📋Chrome1/10/2023 Edge1/12/20232
css.properties.math-style.compact 📋Chrome1/10/2023 Edge1/12/20232
css.properties.math-style.normal 📋Chrome1/10/2023 Edge1/12/20232
css.properties.max-block-size 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.max-block-size.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.max-block-size.fit-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-block-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-block-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-block-size.none 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.max-block-size.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.max-height 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: CSS 2.1 leaves the behavior of max-height with table undefined. Firefox supports applying max-height to table elements.Opera: CSS 2.1 leaves the behavior of max-height with table undefined. Opera supports applying max-height to table elements.
css.properties.max-height.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.max-height.fit-content 📋Chrome10/13/2015 Edge1/15/20201555
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.max-height.max-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.max-height.min-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.max-height.none 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.max-height.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.max-inline-size 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.max-inline-size.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.max-inline-size.fit-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-inline-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-inline-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-inline-size.none 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.max-inline-size.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.max-width 📋Chrome12/11/2008 Edge7/29/20152421
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.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.max-width.fit-content 📋Chrome10/13/2015 Edge1/15/20201555
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.max-width.max-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.max-width.min-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.max-width.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.max-width.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.min-block-size 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.min-block-size.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.min-block-size.auto 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.min-block-size.fit-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-block-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-block-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-block-size.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.min-height 📋Chrome12/11/2008 Edge7/29/20152421
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.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.min-height.auto Chrome7/31/2012 Edge7/29/20151093
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-height.fit-content Chrome10/13/2015 Edge1/15/20201555
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.min-height.max-content Chrome10/13/2015 Edge1/15/20201555
css.properties.min-height.min-content Chrome10/13/2015 Edge1/15/20201555
css.properties.min-height.stretch Chrome6/24/2025 Edge6/26/20252
css.properties.min-inline-size 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.min-inline-size.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.min-inline-size.auto 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.min-inline-size.fit-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-inline-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-inline-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-inline-size.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.min-width 📋Chrome12/11/2008 Edge7/29/20152421
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.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.min-width.auto Chrome7/31/2012 Edge7/29/20151093
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.min-width.fit-content Chrome10/13/2015 Edge1/15/20201555
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.min-width.max-content Chrome10/13/2015 Edge1/15/20201555
css.properties.min-width.min-content Chrome10/13/2015 Edge1/15/20201555
css.properties.min-width.stretch Chrome6/24/2025 Edge6/26/20252
css.properties.mix-blend-mode 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.color 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.color-burn 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.color-dodge 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.darken 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.difference 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.exclusion 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.hard-light 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.hue 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.lighten 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.luminosity 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.multiply 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.normal 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.overlay 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.plus-lighter 📋Chrome3/29/2022 Edge4/1/20223
css.properties.mix-blend-mode.saturation 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.screen 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.soft-light 📋Chrome3/3/2015 Edge1/15/20201779
css.properties.mix-blend-mode.svg_elements Chrome3/3/2015 Edge1/15/20201779
css.properties.object-fit 📋Chrome1/14/2014 Edge1/15/20202192
Edge: Only supported for <img> elements.
css.properties.object-fit.contain 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-fit.cover 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-fit.fill 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-fit.none 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-fit.scale-down 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-position 📋Chrome1/14/2014 Edge1/15/20202192
Edge: Only supported for <img> elements.
css.properties.object-position.bottom 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-position.center 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-position.left 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-position.right 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-position.top 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-view-box 📋Chrome8/2/2022 Edge8/5/20223
css.properties.object-view-box.none 📋Chrome8/2/2022 Edge8/5/20223
css.properties.offset 📋Chrome12/1/2016 Edge1/15/20201140
css.properties.offset.auto 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.border-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.bottom 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.center 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.content-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.fill-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.left 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.none 📋Chrome9/5/2017 Edge1/15/2020862
css.properties.offset.normal 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.padding-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.right 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.stroke-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.top 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset.view-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-anchor 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-anchor.auto 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-anchor.bottom 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-anchor.center 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-anchor.left 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-anchor.right 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-anchor.top 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-distance 📋Chrome12/1/2016 Edge1/15/20201140
css.properties.offset-path 📋Chrome12/1/2016 Edge1/15/20201140
Samsung Internet: path() is the only value type supported.
css.properties.offset-path.basic_shape 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-path.border-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-path.content-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-path.fill-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-path.none 📋Chrome2/4/2020 Edge2/7/20203
css.properties.offset-path.padding-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-path.path Chrome1/23/2018 Edge1/15/2020722
css.properties.offset-path.ray 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-path.stroke-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-path.url 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-path.view-box 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-position 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-position.auto 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-position.bottom 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-position.center 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-position.left 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-position.normal 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-position.right 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-position.top 📋Chrome8/15/2023 Edge8/21/20236
css.properties.offset-rotate 📋Chrome1/25/2017 Edge1/15/20201085
css.properties.offset-rotate.auto 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.offset-rotate.reverse 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.opacity 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.opacity.percentages Chrome10/22/2019 Edge1/15/202085
css.properties.order 📋Chrome8/20/2013 Edge7/29/2015708
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 📋Chrome2/21/2013 Edge7/29/2015888
css.properties.outline 📋Chrome9/21/2021 Edge9/24/20213
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.outline.auto 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.outline.currentColor 📋Chrome11/12/2013 Edge7/29/2015624
css.properties.outline.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-color 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-offset 📋Chrome12/11/2008 Edge4/5/20173037
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.outline-style 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.outline-style.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.dashed 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.dotted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.double 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.groove 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.inset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.outset 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.ridge 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-style.solid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-width 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.outline-width.medium 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-width.thick 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.outline-width.thin 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: After Firefox 3.6, the overflow property is correctly applied to table group elements (<thead>, <tbody>, <tfoot>).Internet Explorer: From version 4 to 6, Internet Explorer enlarges an element with overflow: visible (default value) to fit the content inside it. height and width behave like min-height and min-width, respectively.
css.properties.overflow.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow.clip 📋Chrome4/13/2021 Edge4/15/20212
css.properties.overflow.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow.multiple_keywords Chrome7/24/2018 Edge1/15/2020540
css.properties.overflow.replaced_elements 📋Edge7/29/2015 Chrome11/29/20222680
css.properties.overflow.scroll 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow.visible 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-anchor 📋Chrome1/25/2017 Edge1/15/20201085
css.properties.overflow-anchor.auto 📋Chrome1/25/2017 Edge1/15/20201085
css.properties.overflow-anchor.none 📋Chrome1/25/2017 Edge1/15/20201085
css.properties.overflow-block 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-block.auto 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-block.clip 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-block.hidden 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-block.overlay Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-block.scroll 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-block.visible 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-clip-margin 📋Chrome4/13/2021 Edge4/15/20212
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-clip-margin.border-box 📋Chrome8/2/2022 Edge8/5/20223
css.properties.overflow-clip-margin.content-box 📋Chrome8/2/2022 Edge8/5/20223
css.properties.overflow-clip-margin.padding-box 📋Chrome8/2/2022 Edge8/5/20223
css.properties.overflow-inline 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-inline.auto 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-inline.clip 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-inline.hidden 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-inline.overlay 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-inline.scroll 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-inline.visible 📋Chrome4/1/2025 Edge4/4/20253
css.properties.overflow-wrap 📋Chrome11/6/2012 Edge10/2/20182156
css.properties.overflow-wrap.anywhere 📋Chrome2/4/2020 Edge2/7/20203
css.properties.overflow-wrap.break-word 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-wrap.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-x 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-x.auto 📋Chrome12/11/2008 Edge7/29/20152421
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.clip 📋Chrome4/13/2021 Edge4/15/20212
css.properties.overflow-x.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-x.replaced_elements 📋Edge7/29/2015 Chrome11/29/20222680
css.properties.overflow-x.scroll 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-x.visible 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-y 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-y.auto 📋Chrome12/11/2008 Edge7/29/20152421
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.clip 📋Chrome4/13/2021 Edge4/15/20212
css.properties.overflow-y.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-y.replaced_elements 📋Edge7/29/2015 Chrome11/29/20222680
css.properties.overflow-y.scroll 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overflow-y.visible 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.overlay 📋Chrome9/12/2023 Edge9/15/20233
css.properties.overlay.auto 📋Chrome9/12/2023 Edge9/15/20233
css.properties.overlay.none 📋Chrome9/12/2023 Edge9/15/20233
css.properties.overscroll-behavior 📋Chrome12/6/2017 Edge10/2/2018300
css.properties.overscroll-behavior.auto 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.overscroll-behavior.contain 📋Chrome12/6/2017 Edge1/15/2020770
css.properties.overscroll-behavior.none 📋Chrome12/6/2017 Edge1/15/2020770
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-block 📋Chrome9/10/2019 Edge1/15/2020127
css.properties.overscroll-behavior-block.auto 📋Chrome9/10/2019 Edge1/15/2020127
css.properties.overscroll-behavior-block.contain 📋Chrome9/10/2019 Edge1/15/2020127
css.properties.overscroll-behavior-block.none 📋Chrome9/10/2019 Edge1/15/2020127
css.properties.overscroll-behavior-inline 📋Chrome9/10/2019 Edge1/15/2020127
css.properties.overscroll-behavior-inline.auto 📋Chrome9/10/2019 Edge1/15/2020127
css.properties.overscroll-behavior-inline.contain 📋Chrome9/10/2019 Edge1/15/2020127
css.properties.overscroll-behavior-inline.none 📋Chrome9/10/2019 Edge1/15/2020127
css.properties.overscroll-behavior-x 📋Chrome12/6/2017 Edge10/2/2018300
css.properties.overscroll-behavior-x.auto 📋Chrome12/6/2017 Edge10/2/2018300
css.properties.overscroll-behavior-x.contain 📋Chrome12/6/2017 Edge10/2/2018300
css.properties.overscroll-behavior-x.none 📋Chrome12/6/2017 Edge1/15/2020770
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-y 📋Chrome12/6/2017 Edge10/2/2018300
css.properties.overscroll-behavior-y.auto 📋Chrome12/6/2017 Edge10/2/2018300
css.properties.overscroll-behavior-y.contain 📋Chrome12/6/2017 Edge10/2/2018300
css.properties.overscroll-behavior-y.none 📋Chrome12/6/2017 Edge1/15/2020770
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.padding 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.padding-block 📋Chrome11/17/2020 Edge11/19/20202
css.properties.padding-block-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.padding-block-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.padding-bottom 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.padding-inline 📋Chrome11/17/2020 Edge11/19/20202
css.properties.padding-inline-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.padding-inline-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.padding-left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.padding-right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.padding-top 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page 📋Chrome8/25/2020 Edge8/27/20202
css.properties.page.auto 📋Chrome8/25/2020 Edge8/27/20202
css.properties.page-break-after 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-after.always 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-after.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-after.avoid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-after.left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-after.right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-before 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-before.always 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-before.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-before.avoid 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-before.left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-before.right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-inside 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-inside.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.page-break-inside.avoid 📋Chrome12/11/2008 Edge7/29/20152421
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.paint-order 📋Chrome3/19/2024 Edge3/22/20243
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.paint-order.fill 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.paint-order.markers 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.paint-order.normal 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.paint-order.stroke 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.perspective 📋Chrome7/16/2014 Edge7/29/2015378
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 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.perspective-origin 📋Chrome7/16/2014 Edge7/29/2015378
css.properties.perspective-origin.bottom 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.perspective-origin.center 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.perspective-origin.left 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.perspective-origin.right 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.perspective-origin.top 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.place-content 📋Chrome6/5/2017 Edge1/15/2020954
css.properties.place-content.flex_context Chrome6/5/2017 Edge1/15/2020954
Firefox: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.Firefox for Android: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.
css.properties.place-content.grid_context Chrome6/5/2017 Edge1/15/2020954
Firefox: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.Firefox for Android: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.
css.properties.place-items 📋Chrome6/5/2017 Edge1/15/2020954
css.properties.place-items.anchor-center 📋Chrome5/14/2024 Edge5/17/20243
css.properties.place-items.flex_context Chrome6/5/2017 Edge1/15/2020954
css.properties.place-items.grid_context Chrome6/5/2017 Edge1/15/2020954
css.properties.place-self 📋Chrome6/5/2017 Edge1/15/2020954
css.properties.place-self.anchor-center 📋Chrome5/14/2024 Edge5/17/20243
css.properties.place-self.flex_context Chrome6/5/2017 Edge1/15/2020954
css.properties.place-self.grid_context Chrome6/5/2017 Edge1/15/2020954
css.properties.place-self.position_absolute_context 📋Chrome2/20/2024 Edge2/23/20243
css.properties.pointer-events 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.pointer-events.all 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.pointer-events.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.pointer-events.bounding-box 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.pointer-events.fill 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.pointer-events.html_elements Chrome5/21/2009 Edge7/29/20152260
css.properties.pointer-events.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.pointer-events.painted 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.pointer-events.stroke 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.pointer-events.visible 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.pointer-events.visibleFill 📋Chrome11/12/2013 Edge7/29/2015624
css.properties.pointer-events.visiblePainted 📋Chrome11/12/2013 Edge7/29/2015624
css.properties.pointer-events.visibleStroke 📋Chrome11/12/2013 Edge7/29/2015624
css.properties.position 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.position.absolute 📋Chrome12/11/2008 Edge7/29/20152421
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.absolutely_positioned_flex_children Edge7/29/2015 Chrome7/20/2016357
css.properties.position.fixed 📋Chrome12/11/2008 Edge7/29/20152421
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.position_sticky_table_elements Chrome1/25/2017 Edge10/17/2017265
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.relative 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.position.static 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.position.sticky 📋Chrome1/25/2017 Edge10/17/2017265
css.properties.position-anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-anchor.auto 📋Chrome5/14/2024 Edge5/17/20243
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-anchor.none Chrome1/13/2026 Edge1/21/20268
css.properties.position-area 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.block-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.block-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.bottom 📋Chrome1/13/2026 Edge1/21/20268
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.center 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.inline-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.inline-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.left 📋Chrome1/13/2026 Edge1/21/20268
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.none 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.right 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-block-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-block-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-inline-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-inline-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-x-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-x-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-y-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-y-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.span-all 📋Chrome1/13/2026 Edge1/21/20268
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.span-block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-bottom 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-left 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-right 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-self-block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-self-block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-self-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-self-inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-self-inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-self-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-self-x-end 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-area.span-self-x-start 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-area.span-self-y-end 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-area.span-self-y-start 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-area.span-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-top 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-x-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-x-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-y-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.span-y-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-area.top 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.x-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.x-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.y-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.y-start 📋Chrome1/13/2026 Edge1/21/20268
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 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try.block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.bottom 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.center 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.flip-block 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try.flip-inline 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try.flip-start 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try.flip-x 📋Chrome1/13/2026 Edge1/21/20268
css.properties.position-try.flip-y 📋Chrome1/13/2026 Edge1/21/20268
css.properties.position-try.inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.left 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.none 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try.right 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.self-block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.self-block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.self-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.self-inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.self-inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.self-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.self-x-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-x-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-y-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-y-start 📋Chrome1/13/2026 Edge1/21/20268
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.span-all 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-bottom 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-left 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-right 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-self-block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-self-block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-self-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-self-inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-self-inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-self-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-self-x-end 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-try.span-self-x-start 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-try.span-self-y-end 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-try.span-self-y-start 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-try.span-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-top 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-x-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-x-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-y-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.span-y-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.top 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.x-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.x-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.y-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try.y-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks 📋Chrome8/20/2024 Edge8/22/20242
css.properties.position-try-fallbacks.block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.bottom 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.center 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.flip-block 📋Chrome8/20/2024 Edge8/22/20242
css.properties.position-try-fallbacks.flip-inline 📋Chrome8/20/2024 Edge8/22/20242
css.properties.position-try-fallbacks.flip-start 📋Chrome8/20/2024 Edge8/22/20242
css.properties.position-try-fallbacks.flip-x 📋Chrome1/13/2026 Edge1/21/20268
css.properties.position-try-fallbacks.flip-y 📋Chrome1/13/2026 Edge1/21/20268
css.properties.position-try-fallbacks.inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.left 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.none 📋Chrome8/20/2024 Edge8/22/20242
css.properties.position-try-fallbacks.position-area 📋Chrome8/20/2024 Edge8/22/20242
Chrome: inset-area values had to be wrapped inside an inset-area() function.Chrome Android: inset-area values had to be wrapped inside an inset-area() function.Edge: inset-area values had to be wrapped inside an inset-area() function.Opera: inset-area values had to be wrapped inside an inset-area() function.Opera Android: inset-area values had to be wrapped inside an inset-area() function.Samsung Internet: inset-area values had to be wrapped inside an inset-area() function.WebView Android: inset-area values had to be wrapped inside an inset-area() function.
css.properties.position-try-fallbacks.right 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.self-block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.self-block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.self-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.self-inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.self-inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.self-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.self-x-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-x-start 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-y-end 📋Chrome1/13/2026 Edge1/21/20268
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-y-start 📋Chrome1/13/2026 Edge1/21/20268
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.span-all 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-bottom 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-left 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-right 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-self-block-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-self-block-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-self-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-self-inline-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-self-inline-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-self-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-self-x-end 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-try-fallbacks.span-self-x-start 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-try-fallbacks.span-self-y-end 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-try-fallbacks.span-self-y-start 📋Chrome12/2/2025 Edge12/5/20253
css.properties.position-try-fallbacks.span-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-top 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-x-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-x-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-y-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.span-y-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.top 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.x-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.x-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.y-end 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-fallbacks.y-start 📋Chrome9/17/2024 Edge9/19/20242
css.properties.position-try-order 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try-order.most-block-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try-order.most-height 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try-order.most-inline-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try-order.most-width 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-try-order.normal 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-visibility 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-visibility.always 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-visibility.anchors-visible 📋Chrome5/14/2024 Edge5/17/20243
css.properties.position-visibility.no-overflow 📋Chrome5/14/2024 Edge5/17/20243
css.properties.print-color-adjust 📋Chrome4/29/2025 Edge5/1/20252
Chrome: Chrome does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Chrome: Before version 26, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Chrome Android: Chrome Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Chrome Android: Before version 26, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Edge: Edge does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Edge: Before version 79, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Quest Browser: Quest Browser does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Quest Browser: Before version 5.0, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Opera: Opera does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Opera: Before version 15, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Opera Android: Opera Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Opera Android: Before version 14, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Safari: Safari does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Safari on iOS: Safari on iOS does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Samsung Internet: Samsung Internet does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Samsung Internet: Before version 1.5, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.WebView Android: WebView Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.WebView Android: Before version 4.4, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.WebView on iOS: WebView on iOS does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.
css.properties.print-color-adjust.economy 📋Chrome4/29/2025 Edge5/1/20252
css.properties.print-color-adjust.exact 📋Chrome4/29/2025 Edge5/1/20252
css.properties.quotes 📋Chrome4/27/2011 Edge7/29/20151554
css.properties.quotes.auto 📋Chrome11/17/2020 Edge11/19/20202
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.quotes.none 📋Chrome4/27/2011 Edge7/29/20151554
css.properties.r 📋Chrome5/19/2015 Edge1/15/20201702
css.properties.reading-flow 📋Chrome5/27/2025 Edge5/29/20252
css.properties.reading-flow.flex-flow 📋Chrome5/27/2025 Edge5/29/20252
css.properties.reading-flow.flex-visual 📋Chrome5/27/2025 Edge5/29/20252
css.properties.reading-flow.grid-columns 📋Chrome5/27/2025 Edge5/29/20252
css.properties.reading-flow.grid-order 📋Chrome5/27/2025 Edge5/29/20252
css.properties.reading-flow.grid-rows 📋Chrome5/27/2025 Edge5/29/20252
css.properties.reading-flow.normal 📋Chrome5/27/2025 Edge5/29/20252
css.properties.reading-flow.source-order 📋Chrome5/27/2025 Edge5/29/20252
css.properties.reading-order 📋Chrome5/27/2025 Edge5/29/20252
css.properties.resize 📋Chrome12/11/2008 Edge1/15/20204052
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 Chrome10/10/2023 Edge10/13/20233
css.properties.resize.block_level_support Chrome1/25/2010 Edge1/15/20203642
Firefox: resize doesn't have any effect on <iframe>. See bug 680823)
css.properties.resize.both 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.resize.horizontal 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.resize.inline Chrome10/10/2023 Edge10/13/20233
css.properties.resize.none 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.resize.vertical 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.right.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.right.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.right.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.rotate 📋Chrome8/2/2022 Edge8/5/20223
css.properties.rotate.none 📋Chrome8/2/2022 Edge8/5/20223
css.properties.rotate.x_y_z_angle Chrome8/2/2022 Edge8/5/20223
css.properties.row-gap 📋Chrome12/1/2015 Edge10/17/2017686
css.properties.row-gap.flex_context 📋Edge7/16/2020 Chrome7/27/202011
css.properties.row-gap.grid_context 📋Edge10/17/2017 Chrome4/17/2018182
css.properties.row-gap.normal 📋Chrome12/1/2015 Edge10/17/2017686
css.properties.ruby-align 📋Chrome8/20/2024 Edge8/22/20242
Internet Explorer: Internet Explorer 9 and later supports an earlier draft of CSS Ruby with non-standard values for this property: auto, left, center, right, distribute-letter, distribute-space, and line-edge.
css.properties.ruby-align.center 📋Chrome8/20/2024 Edge8/22/20242
css.properties.ruby-align.space-around 📋Chrome8/20/2024 Edge8/22/20242
css.properties.ruby-align.space-between 📋Chrome8/20/2024 Edge8/22/20242
css.properties.ruby-align.start 📋Chrome8/20/2024 Edge8/22/20242
css.properties.ruby-position 📋Edge7/16/2020 Chrome7/27/202011
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 Edge7/16/2020 Chrome7/27/202011
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 Edge7/16/2020 Chrome7/27/202011
css.properties.ruby-position.under Edge7/16/2020 Chrome7/27/202011
css.properties.rx 📋Chrome5/19/2015 Edge1/15/20201702
Safari: Before Safari 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.Safari on iOS: Before Safari on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.WebView on iOS: Before WebView on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.
css.properties.rx.auto 📋Chrome8/31/2016 Edge1/15/20201232
css.properties.ry 📋Chrome5/19/2015 Edge1/15/20201702
Safari: Before Safari 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.Safari on iOS: Before Safari on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.WebView on iOS: Before WebView on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.
css.properties.ry.auto 📋Chrome8/31/2016 Edge1/15/20201232
css.properties.scale 📋Chrome8/2/2022 Edge8/5/20223
css.properties.scale.none 📋Chrome8/2/2022 Edge8/5/20223
css.properties.scroll-behavior 📋Chrome9/5/2017 Edge1/15/2020862
css.properties.scroll-behavior.auto 📋Chrome9/5/2017 Edge1/15/2020862
css.properties.scroll-behavior.smooth 📋Chrome9/5/2017 Edge1/15/2020862
css.properties.scroll-initial-target 📋Chrome2/4/2025 Edge2/6/20252
css.properties.scroll-initial-target.nearest 📋Chrome2/4/2025 Edge2/6/20252
css.properties.scroll-initial-target.none 📋Chrome2/4/2025 Edge2/6/20252
css.properties.scroll-margin 📋Chrome9/4/2018 Edge1/15/2020498
Firefox: The scroll-margin property can cause an element's visibility to be incorrectly calculated for element.focus(). See bug 1708303.Firefox for Android: The scroll-margin property can cause an element's visibility to be incorrectly calculated for element.focus(). See bug 1708303.Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-block 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-margin-block-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-margin-block-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-margin-bottom 📋Chrome9/4/2018 Edge1/15/2020498
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-inline 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-margin-inline-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-margin-inline-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-margin-left 📋Chrome9/4/2018 Edge1/15/2020498
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-right 📋Chrome9/4/2018 Edge1/15/2020498
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-top 📋Chrome9/4/2018 Edge1/15/2020498
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-marker-group 📋Chrome4/1/2025 Edge4/4/20253
css.properties.scroll-marker-group.after 📋Chrome4/1/2025 Edge4/4/20253
css.properties.scroll-marker-group.before 📋Chrome4/1/2025 Edge4/4/20253
css.properties.scroll-marker-group.none 📋Chrome4/1/2025 Edge4/4/20253
css.properties.scroll-padding 📋Chrome9/4/2018 Edge1/15/2020498
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-block 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-block.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-block-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-block-end.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-block-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-block-start.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-bottom 📋Chrome9/4/2018 Edge1/15/2020498
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 📋Chrome10/22/2019 Edge1/15/202085
css.properties.scroll-padding-inline 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-inline.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-inline-end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-inline-end.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-inline-start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-inline-start.auto 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-padding-left 📋Chrome9/4/2018 Edge1/15/2020498
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 📋Chrome10/22/2019 Edge1/15/202085
css.properties.scroll-padding-right 📋Chrome9/4/2018 Edge1/15/2020498
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 📋Chrome10/22/2019 Edge1/15/202085
css.properties.scroll-padding-top 📋Chrome9/4/2018 Edge1/15/2020498
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 📋Chrome10/22/2019 Edge1/15/202085
css.properties.scroll-snap-align 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-align.center 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-align.end 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-align.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-align.start 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-stop 📋Chrome6/4/2019 Edge1/15/2020225
css.properties.scroll-snap-stop.always 📋Chrome6/4/2019 Edge1/15/2020225
css.properties.scroll-snap-stop.normal 📋Chrome6/4/2019 Edge1/15/2020225
css.properties.scroll-snap-type 📋Chrome9/4/2018 Edge1/15/2020498
Edge: Edge supports an earlier draft of CSS Scroll Snap without axis values.Firefox: On macOS Monterey, scroll snapping does not complete reliably. See bug 1749352.Firefox: An earlier draft of CSS Scroll Snap without axis values.Firefox for Android: An earlier draft of CSS Scroll Snap without axis values.Internet Explorer: Internet Explorer supports an earlier draft of CSS Scroll Snap without axis values.Safari: Older Safari versions support an earlier draft of CSS Scroll Snap without axis values.Safari on iOS: Older Safari on iOS versions support an earlier draft of CSS Scroll Snap without axis values.WebView on iOS: Older WebView on iOS versions support an earlier draft of CSS Scroll Snap without axis values.
css.properties.scroll-snap-type.block 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-type.both 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-type.inline 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-type.none 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-type.x 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-snap-type.y 📋Chrome9/4/2018 Edge1/15/2020498
css.properties.scroll-target-group 📋Chrome9/2/2025 Edge9/5/20253
css.properties.scroll-target-group.auto 📋Chrome9/2/2025 Edge9/5/20253
css.properties.scroll-target-group.none 📋Chrome9/2/2025 Edge9/5/20253
css.properties.scroll-timeline 📋Chrome7/18/2023 Edge7/21/20233
Firefox: The syntax of the shorthand property uses the fixed order of name and then the axis.Firefox: Supports the deprecated horizontal and vertical axis values, and not the x and y values.Firefox: The @scroll-timeline at-rule is replaced with the longhand properties scroll-timeline-name and scroll-timeline-axis and the shorthand property scroll-timeline.
css.properties.scroll-timeline.none 📋Chrome7/18/2023 Edge7/21/20233
css.properties.scroll-timeline-axis 📋Chrome7/18/2023 Edge7/21/20233
Firefox: The syntax of the shorthand property uses the fixed order of name and then the axis.Firefox: Supports the deprecated horizontal and vertical values, and not the x and y values.Firefox: The @scroll-timeline at-rule is replaced with the longhand properties scroll-timeline-name and scroll-timeline-axis and the shorthand property scroll-timeline.
css.properties.scroll-timeline-axis.block 📋Chrome7/18/2023 Edge7/21/20233
css.properties.scroll-timeline-axis.inline 📋Chrome7/18/2023 Edge7/21/20233
css.properties.scroll-timeline-axis.x 📋Chrome7/18/2023 Edge7/21/20233
css.properties.scroll-timeline-axis.y 📋Chrome7/18/2023 Edge7/21/20233
css.properties.scroll-timeline-name 📋Chrome7/18/2023 Edge7/21/20233
Firefox: The syntax of the shorthand property uses the fixed order of name and then the axis.Firefox: The @scroll-timeline at-rule is replaced with the longhand properties scroll-timeline-name and scroll-timeline-axis and the shorthand property scroll-timeline.
css.properties.scroll-timeline-name.none 📋Chrome7/18/2023 Edge7/21/20233
css.properties.scrollbar-color 📋Chrome1/23/2024 Edge1/25/20242
css.properties.scrollbar-color.auto 📋Chrome1/23/2024 Edge1/25/20242
css.properties.scrollbar-gutter 📋Chrome9/21/2021 Edge9/24/20213
css.properties.scrollbar-gutter.auto 📋Chrome9/21/2021 Edge9/24/20213
css.properties.scrollbar-gutter.stable 📋Chrome9/21/2021 Edge9/24/20213
css.properties.scrollbar-width 📋Chrome1/23/2024 Edge1/25/20242
css.properties.scrollbar-width.auto 📋Chrome1/23/2024 Edge1/25/20242
css.properties.scrollbar-width.none 📋Chrome1/23/2024 Edge1/25/20242
css.properties.scrollbar-width.thin 📋Chrome1/23/2024 Edge1/25/20242
css.properties.shape-image-threshold 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-image-threshold.percentages Chrome10/22/2019 Edge1/15/202085
css.properties.shape-margin 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.border-box 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.circle Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.content-box 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.gradient 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.image 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.inset Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.margin-box 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.none 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.padding-box 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.polygon Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-rendering 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.shape-rendering.auto 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.shape-rendering.crispEdges 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.shape-rendering.geometricPrecision 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.shape-rendering.optimizeSpeed 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.speak 📋Chrome2/4/2020 Edge2/7/20203
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.
css.properties.stop-color 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stop-opacity 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke.none 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-dasharray 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-dasharray.none 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-dashoffset 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-linecap 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-linecap.butt 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-linecap.round 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-linecap.square 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-linejoin 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-linejoin.bevel 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-linejoin.miter 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-linejoin.round 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-miterlimit 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-opacity 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.stroke-width 📋Chrome12/11/2008 Edge4/5/20173037
css.properties.tab-size 📋Chrome7/31/2012 Edge1/15/20202724
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 📋Chrome4/14/2015 Edge1/15/20201737
css.properties.table-layout 📋Chrome9/16/2011 Edge7/29/20151412
css.properties.table-layout.auto 📋Chrome9/16/2011 Edge7/29/20151412
css.properties.table-layout.fixed 📋Chrome9/16/2011 Edge7/29/20151412
css.properties.text-align 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-align.center 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.text-align.end 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.text-align.justify 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-align.left 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.text-align.match-parent 📋Chrome12/13/2011 Edge1/15/20202955
css.properties.text-align.right 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.text-align.start 📋Chrome12/11/2008 Edge1/15/20204052
css.properties.text-align-last 📋Edge7/29/2015 Chrome12/1/2015125
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 📋Edge7/29/2015 Chrome12/1/2015125
css.properties.text-align-last.center 📋Edge7/29/2015 Chrome12/1/2015125
css.properties.text-align-last.end 📋Chrome12/1/2015 Edge1/15/20201506
css.properties.text-align-last.justify 📋Edge7/29/2015 Chrome12/1/2015125
css.properties.text-align-last.left 📋Edge7/29/2015 Chrome12/1/2015125
css.properties.text-align-last.right 📋Edge7/29/2015 Chrome12/1/2015125
css.properties.text-align-last.start 📋Chrome12/1/2015 Edge1/15/20201506
css.properties.text-anchor 📋Chrome12/11/2008 Edge8/2/20162791
css.properties.text-anchor.end 📋Chrome12/11/2008 Edge8/2/20162791
css.properties.text-anchor.middle 📋Chrome12/11/2008 Edge8/2/20162791
css.properties.text-anchor.start 📋Chrome12/11/2008 Edge8/2/20162791
css.properties.text-autospace 📋Chrome9/2/2025 Edge9/5/20253
css.properties.text-autospace.no-autospace 📋Chrome9/2/2025 Edge9/5/20253
css.properties.text-autospace.normal 📋Chrome9/2/2025 Edge9/5/20253
css.properties.text-box 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box.auto 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box.none 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box.normal 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box.text 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box.trim-both 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box.trim-end 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box.trim-start 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box-edge 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box-edge.auto 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box-edge.text 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box-trim 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box-trim.none 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box-trim.trim-both 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box-trim.trim-end 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-box-trim.trim-start 📋Chrome2/4/2025 Edge2/6/20252
css.properties.text-combine-upright 📋Chrome1/20/2016 Edge1/15/20201456
Chrome: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Chrome Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Firefox: Before version 81, Firefox implemented the property as animatable. This was corrected to spec in 81.Firefox for Android: Before version 81, Firefox for Android implemented the property as animatable. This was corrected to spec in 81.Quest Browser: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Opera: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Opera Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Safari: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Safari on iOS: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Samsung Internet: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.WebView Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.WebView on iOS: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.
css.properties.text-combine-upright.all 📋Chrome1/20/2016 Edge1/15/20201456
css.properties.text-combine-upright.none 📋Chrome1/20/2016 Edge1/15/20201456
css.properties.text-decoration 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-decoration.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.text-decoration.blink 📋Chrome11/12/2013 Edge7/29/2015624
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.currentColor 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration.dashed 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration.dotted 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration.double 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration.from-font 📋Chrome11/17/2020 Edge11/19/20202
css.properties.text-decoration.grammar-error 📋Chrome1/23/2024 Edge1/25/20242
css.properties.text-decoration.includes_color-and-style Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration.includes_thickness Chrome11/17/2020 Edge11/19/20202
css.properties.text-decoration.line-through 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-decoration.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-decoration.overline 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-decoration.solid 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration.spelling-error 📋Chrome1/23/2024 Edge1/25/20242
css.properties.text-decoration.transparent 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration.underline 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-decoration.wavy 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-color 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-color.currentColor 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-color.transparent 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-line 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-line.blink 📋Chrome3/9/2017 Edge1/15/20201042
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.grammar-error 📋Chrome1/23/2024 Edge1/25/20242
css.properties.text-decoration-line.line-through 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-line.none 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-line.overline 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-line.spelling-error 📋Chrome1/23/2024 Edge1/25/20242
css.properties.text-decoration-line.underline 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-skip-ink 📋Chrome1/23/2018 Edge1/15/2020722
css.properties.text-decoration-skip-ink.auto 📋Chrome1/23/2018 Edge1/15/2020722
css.properties.text-decoration-skip-ink.none 📋Chrome1/23/2018 Edge1/15/2020722
css.properties.text-decoration-style 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-style.dashed 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-style.dotted 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-style.double 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-style.solid 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-style.wavy 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.text-decoration-thickness 📋Chrome3/2/2021 Edge3/4/20212
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.properties.text-decoration-thickness.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.text-decoration-thickness.from-font 📋Chrome11/17/2020 Edge11/19/20202
css.properties.text-decoration-thickness.percentage Chrome11/17/2020 Edge11/19/20202
css.properties.text-emphasis 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis.circle 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.currentColor 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.dot 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.double-circle 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.filled 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.none 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.open 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.sesame 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.transparent 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.triangle 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis-color 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-color.currentColor 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis-color.transparent 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis-position 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-position.left Chrome10/17/2017 Edge1/15/2020820
css.properties.text-emphasis-position.over Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-position.right Chrome10/17/2017 Edge1/15/2020820
css.properties.text-emphasis-position.under Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style.circle 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style.dot 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style.double-circle 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style.filled 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style.none 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style.open 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style.sesame 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-emphasis-style.triangle 📋Chrome3/1/2022 Edge3/3/20222
css.properties.text-indent 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-indent.each-line 📋Chrome3/10/2026 Edge3/12/20262
css.properties.text-indent.hanging 📋Chrome3/10/2026 Edge3/12/20262
css.properties.text-justify 📋Chrome2/10/2026 Edge2/14/20264
Edge: Standard values inter-character and none are supported. The deprecated distribute value is also supported.Internet Explorer: Standard values inter-character and none are supported. The deprecated distribute value is also supported.
css.properties.text-justify.auto 📋Chrome2/10/2026 Edge2/14/20264
css.properties.text-justify.inter-character 📋Chrome2/10/2026 Edge2/14/20264
css.properties.text-justify.inter-word 📋Chrome2/10/2026 Edge2/14/20264
css.properties.text-justify.none 📋Chrome2/10/2026 Edge2/14/20264
css.properties.text-orientation 📋Chrome1/20/2016 Edge1/15/20201456
css.properties.text-orientation.mixed 📋Chrome1/20/2016 Edge1/15/20201456
css.properties.text-orientation.sideways 📋Chrome6/7/2011 Edge1/15/20203144
css.properties.text-orientation.upright 📋Chrome6/7/2011 Edge1/15/20203144
css.properties.text-overflow 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Until Firefox 10, handling of text-overflow on blocks with inline overflow on both horizontal sides was incorrect. Before Firefox 10, if only one value was specified (such as text-overflow: ellipsis;), text was ellipsed on both sides of the block, instead of only the end edge based on the block's text direction.Firefox for Android: Until Firefox for Android 10, handling of text-overflow on blocks with inline overflow on both horizontal sides was incorrect. Before Firefox for Android 10, if only one value was specified (such as text-overflow: ellipsis;), text was ellipsed on both sides of the block, instead of only the end edge based on the block's text direction.
css.properties.text-overflow.clip 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-overflow.ellipsis 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-rendering 📋Chrome1/25/2010 Edge1/15/20203642
Chrome: This property is only supported on Windows and Linux.Chrome: Initial versions had bugs on Windows and Linux that broke font substitution, small-caps, letter-spacing or caused text to overlap. See bug 40156511, bug 40430936, bug 40444347, bug 40286561.Chrome Android: This property is only supported on Windows and Linux.Chrome Android: Initial versions had bugs on Windows and Linux that broke font substitution, small-caps, letter-spacing or caused text to overlap. See bug 40156511, bug 40430936, bug 40444347, bug 40286561.Edge: This property is only supported on Windows and Linux.Edge: Initial versions had bugs on Windows and Linux that broke font substitution, small-caps, letter-spacing or caused text to overlap. See bug 40156511, bug 40430936, bug 40444347, bug 40286561.Firefox: This property is only supported on Windows and Linux.Firefox: The optimizeSpeed option has no effect on Firefox 4 because the standard code for text rendering is already fast and there is not a faster code path at this time. See bug 595688 for details.Quest Browser: This property is only supported on Windows and Linux.Quest Browser: Initial versions had bugs on Windows and Linux that broke font substitution, small-caps, letter-spacing or caused text to overlap. See bug 40156511, bug 40430936, bug 40444347, bug 40286561.Samsung Internet: This property is only supported on Windows and Linux. Samsung Internet is not on Windows or Linux.WebView Android: From version 3 to 4.3, there is a serious bug where text-rendering: optimizeLegibility causes custom web fonts to not render. This was fixed in version 4.4.
css.properties.text-rendering.auto Chrome1/25/2010 Edge1/15/20203642
Chrome: Chrome treats auto as optimizeSpeed.Chrome Android: Chrome Android treats auto as optimizeSpeed.Edge: Edge treats auto as optimizeSpeed.Firefox: If the font size is 20 pixels or higher, Firefox treats auto as optimizeLegibility. For smaller text, Firefox treats auto as optimizeSpeed. The 20-pixel threshold can be changed with the browser.display.auto_quality_min_font_size preference.Firefox for Android: If the font size is 20 pixels or higher, Firefox treats auto as optimizeLegibility. For smaller text, Firefox treats auto as optimizeSpeed. The 20-pixel threshold can be changed with the browser.display.auto_quality_min_font_size preference.Quest Browser: Quest Browser treats auto as optimizeSpeed.Opera: Opera treats auto as optimizeSpeed.Opera Android: Opera Android treats auto as optimizeSpeed.Safari: Safari treats auto as optimizeSpeed. See bug 41363.Safari on iOS: Safari on iOS treats auto as optimizeSpeed. See bug 41363.Samsung Internet: Samsung Internet treats auto as optimizeSpeed.WebView Android: WebView Android treats auto as optimizeSpeed.WebView on iOS: WebView on iOS treats auto as optimizeSpeed. See bug 41363.
css.properties.text-rendering.geometricPrecision Chrome8/2/2011 Edge1/15/20203088
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 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.text-rendering.optimizeSpeed 📋Chrome11/12/2013 Edge1/15/20202255
css.properties.text-shadow 📋Chrome5/21/2009 Edge7/29/20152260
Firefox: Firefox versions before 57 have a bug whereby transitions will not work when transitioning from a text-shadow with a color specified to a text-shadow without a color specified (bug 726550).Firefox: From Firefox 4, the blur radius is capped at 300 for performance reasons.Firefox: Firefox theoretically supports infinite text-shadows (don't try it).Firefox: If the <color> value is unspecified, then Firefox uses the value of the element's color property.Firefox for Android: Firefox for Android versions before 57 have a bug whereby transitions will not work when transitioning from a text-shadow with a color specified to a text-shadow without a color specified (bug 726550).Firefox for Android: From Firefox for Android 4, the blur radius is capped at 300 for performance reasons.Firefox for Android: Firefox for Android theoretically supports infinite text-shadows (don't try it).Firefox for Android: If the <color> value is unspecified, then Firefox for Android uses the value of the element's color property.Opera: Opera supports a maximum of 6-9 text-shadows for performance reasons. The blur radius is limited to 100px.Opera: Opera 9.5 to 10.1 adheres to the old, reverse painting order (in CSS2, the first specified shadow is on the bottom).Safari: In Safari, any shadows that do not explicitly specify a color are transparent.Safari: Safari 1.1 to 3.2 only supports one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari 4.0 (WebKit 528) and later support multiple text-shadows.Safari on iOS: In Safari, any shadows that do not explicitly specify a color are transparent.Safari on iOS: Safari iOS 1 and 2 only support one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari iOS 3 (WebKit 528) and later support multiple text-shadows.WebView on iOS: In Safari, any shadows that do not explicitly specify a color are transparent.WebView on iOS: Safari iOS 1 and 2 only support one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari iOS 3 (WebKit 528) and later support multiple text-shadows.
css.properties.text-shadow.none 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.text-size-adjust 📋Chrome10/12/2016 Edge1/15/20201190
css.properties.text-size-adjust.auto 📋Chrome10/12/2016 Edge1/15/20201190
css.properties.text-size-adjust.none 📋Chrome10/12/2016 Edge1/15/20201190
css.properties.text-size-adjust.percentages 📋Edge7/29/2015 Chrome10/12/2016441
css.properties.text-spacing-trim 📋Chrome3/19/2024 Edge3/22/20243
css.properties.text-spacing-trim.normal 📋Chrome3/19/2024 Edge3/22/20243
css.properties.text-spacing-trim.space-all 📋Chrome3/19/2024 Edge3/22/20243
css.properties.text-spacing-trim.space-first 📋Chrome3/19/2024 Edge3/22/20243
css.properties.text-spacing-trim.trim-start 📋Chrome3/19/2024 Edge3/22/20243
css.properties.text-transform 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Chrome Android: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Quest Browser: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Opera: Since Opera 15, the text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Safari: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.Samsung Internet: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.WebView Android: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.WebView on iOS: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.
css.properties.text-transform.capitalize 📋Chrome12/11/2008 Edge7/29/20152421
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.greek_accented_characters Chrome4/8/2014 Edge1/15/20202108
css.properties.text-transform.lowercase 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-transform.lowercase_sigma Chrome10/1/2013 Edge7/29/2015666
css.properties.text-transform.math-auto 📋Chrome1/10/2023 Edge1/12/20232
css.properties.text-transform.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-transform.turkic_is Chrome11/12/2013 Edge7/29/2015624
css.properties.text-transform.uppercase 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.text-transform.uppercase_eszett Chrome12/11/2008 Edge10/2/20183582
css.properties.text-underline-offset 📋Chrome11/17/2020 Edge11/19/20202
css.properties.text-underline-offset.auto 📋Chrome11/17/2020 Edge11/19/20202
css.properties.text-underline-offset.percentage 📋Chrome11/17/2020 Edge11/19/20202
css.properties.text-underline-position 📋Chrome2/20/2014 Edge7/29/2015524
css.properties.text-underline-position.auto 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.text-underline-position.from-font 📋Chrome11/17/2020 Edge11/19/20202
css.properties.text-underline-position.left 📋Chrome12/4/2018 Edge1/15/2020407
css.properties.text-underline-position.right 📋Chrome12/4/2018 Edge1/15/2020407
css.properties.text-underline-position.under 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.text-wrap 📋Chrome5/30/2023 Edge6/2/20233
css.properties.text-wrap.auto 📋Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap.balance 📋Chrome5/30/2023 Edge6/2/20233
css.properties.text-wrap.nowrap 📋Chrome5/30/2023 Edge6/2/20233
css.properties.text-wrap.pretty 📋Chrome9/12/2023 Edge9/15/20233
css.properties.text-wrap.stable 📋Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap.wrap 📋Chrome5/30/2023 Edge6/2/20233
css.properties.text-wrap-mode 📋Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap-mode.nowrap Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap-mode.wrap Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap-style 📋Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap-style.auto 📋Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap-style.balance 📋Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap-style.pretty 📋Chrome10/15/2024 Edge10/17/20242
css.properties.text-wrap-style.stable 📋Chrome10/15/2024 Edge10/17/20242
css.properties.timeline-scope 📋Chrome8/15/2023 Edge8/21/20236
css.properties.timeline-scope.none 📋Chrome8/15/2023 Edge8/21/20236
css.properties.timeline-trigger 📋Chrome3/10/2026 Edge3/12/20262
css.properties.timeline-trigger.auto 📋Chrome3/10/2026 Edge3/12/20262
css.properties.timeline-trigger.none 📋Chrome3/10/2026 Edge3/12/20262
css.properties.timeline-trigger.normal 📋Chrome3/10/2026 Edge3/12/20262
css.properties.timeline-trigger-name 📋Chrome3/10/2026 Edge3/12/20262
css.properties.timeline-trigger-name.none 📋Chrome3/10/2026 Edge3/12/20262
css.properties.timeline-trigger-source 📋Chrome3/10/2026 Edge3/12/20262
css.properties.timeline-trigger-source.auto 📋Chrome3/10/2026 Edge3/12/20262
css.properties.timeline-trigger-source.none 📋Chrome3/10/2026 Edge3/12/20262
css.properties.top 📋Chrome12/11/2008 Edge7/29/20152421
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.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.properties.top.anchor-size 📋Chrome1/14/2025 Edge1/17/20253
css.properties.top.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.touch-action 📋Chrome7/16/2014 Edge7/29/2015378
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.manipulation Chrome7/16/2014 Edge7/29/2015378
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.none Chrome7/16/2014 Edge7/29/2015378
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-down Chrome12/1/2016 Edge1/15/20201140
css.properties.touch-action.pan-left Chrome12/1/2016 Edge1/15/20201140
css.properties.touch-action.pan-right Chrome12/1/2016 Edge1/15/20201140
css.properties.touch-action.pan-up Chrome12/1/2016 Edge1/15/20201140
css.properties.touch-action.pan-x Chrome7/16/2014 Edge7/29/2015378
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-y Chrome7/16/2014 Edge7/29/2015378
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pinch-zoom Edge7/29/2015 Chrome1/25/2017546
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.Firefox for Android: Not applicable to Firefox for Android platforms that support neither pointer nor touch events.
css.properties.transform 📋Chrome7/16/2014 Edge7/29/2015378
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 Chrome6/7/2011 Edge7/29/20151513
css.properties.transform.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transform-box 📋Chrome1/23/2018 Edge1/15/2020722
css.properties.transform-box.border-box 📋Chrome10/10/2023 Edge10/13/20233
css.properties.transform-box.content-box 📋Chrome10/10/2023 Edge10/13/20233
css.properties.transform-box.fill-box 📋Chrome1/23/2018 Edge1/15/2020722
css.properties.transform-box.stroke-box 📋Chrome10/10/2023 Edge10/13/20233
css.properties.transform-box.view-box 📋Chrome1/23/2018 Edge1/15/2020722
css.properties.transform-origin 📋Chrome7/16/2014 Edge7/29/2015378
css.properties.transform-origin.bottom 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transform-origin.center 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transform-origin.left 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transform-origin.right 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transform-origin.svg_elements Chrome5/15/2012 Edge4/30/20182176
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.transform-origin.three_value_syntax Chrome6/7/2011 Edge7/29/20151513
css.properties.transform-origin.top 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transform-style 📋Chrome7/16/2014 Edge7/29/2015378
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 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.transform-style.preserve-3d 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.transition 📋Chrome3/26/2013 Edge7/29/2015855
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 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.allow-discrete 📋Chrome8/26/2014 Edge7/29/2015337
css.properties.transition.ease 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.ease-in 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.ease-in-out 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.ease-out 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.linear 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.normal 📋Chrome8/26/2014 Edge7/29/2015337
css.properties.transition.step-end 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.step-start 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition.transition-behavior Chrome9/12/2023 Edge9/15/20233
css.properties.transition-behavior 📋Chrome9/12/2023 Edge9/15/20233
css.properties.transition-behavior.allow-discrete 📋Chrome9/12/2023 Edge9/15/20233
css.properties.transition-behavior.normal 📋Chrome9/12/2023 Edge9/15/20233
css.properties.transition-behavior.transitionable_content-visibility 📋Chrome9/12/2023 Edge9/15/20233
css.properties.transition-behavior.transitionable_display 📋Chrome9/12/2023 Edge9/15/20233
css.properties.transition-delay 📋Chrome3/26/2013 Edge7/29/2015855
css.properties.transition-duration 📋Chrome3/26/2013 Edge7/29/2015855
css.properties.transition-property 📋Chrome3/26/2013 Edge7/29/2015855
css.properties.transition-property.IDENT_value Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-property.all 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-property.none 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-timing-function 📋Chrome3/26/2013 Edge7/29/2015855
css.properties.transition-timing-function.ease 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-timing-function.ease-in 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-timing-function.ease-in-out 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-timing-function.ease-out 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-timing-function.jump Chrome9/10/2019 Edge1/15/2020127
css.properties.transition-timing-function.linear 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-timing-function.step-end 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.transition-timing-function.step-start 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.translate 📋Chrome8/2/2022 Edge8/5/20223
css.properties.translate.none 📋Chrome8/2/2022 Edge8/5/20223
css.properties.trigger-scope 📋Chrome3/10/2026 Edge3/12/20262
css.properties.trigger-scope.all 📋Chrome3/10/2026 Edge3/12/20262
css.properties.trigger-scope.none 📋Chrome3/10/2026 Edge3/12/20262
css.properties.unicode-bidi 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.unicode-bidi.bidi-override 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.unicode-bidi.embed 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.unicode-bidi.isolate 📋Chrome1/20/2016 Edge1/15/20201456
Chrome: Before Chrome 47, -webkit-isolate could lock up the browser.Chrome: Since Chrome 19, the syntax from a previous version of the specification, where the isolate keyword could be used together with bidi-override, is allowed.Firefox: From Firefox 10 to Firefox 16 (inclusive), the isolate keyword could be used together with bidi-override, which was the syntax from a previous version of the specification. From Firefox 17, only one value is allowed. Use isolate-override instead the previous isolate bidi-override.Firefox for Android: From Firefox for Android 10 to Firefox for Android 16 (inclusive), the isolate keyword could be used together with bidi-override, which was the syntax from a previous version of the specification. From Firefox for Android 17, only one value is allowed. Use isolate-override instead the previous isolate bidi-override.Opera: Before Opera 34, -webkit-isolate could lock up the browser.Opera: Since Opera 15, the syntax from a previous version of the specification, where the isolate keyword could be used together with bidi-override, is allowed.Safari: Before Safari 9, -webkit-isolate could lock up the browser.Safari on iOS: Before Safari on iOS 9, -webkit-isolate could lock up the browser.WebView on iOS: Before WebView on iOS 9, -webkit-isolate could lock up the browser.
css.properties.unicode-bidi.isolate-override 📋Chrome1/20/2016 Edge1/15/20201456
css.properties.unicode-bidi.normal 📋Chrome5/21/2009 Edge7/29/20152260
css.properties.unicode-bidi.plaintext 📋Chrome1/20/2016 Edge1/15/20201456
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-modify Chrome12/11/2008 Edge7/29/20152421
Firefox: While the CSS property is parsed and accepted, it does not have any effect.Firefox for Android: While the CSS property is parsed and accepted, it does not have any effect.
css.properties.user-modify.read-write-plaintext-only Chrome12/11/2008 Edge7/29/20152421
css.properties.user-select 📋Chrome10/12/2016 Edge1/15/20201190
css.properties.user-select.all Chrome8/31/2016 Edge1/15/20201232
css.properties.user-select.auto Chrome12/11/2008 Edge7/29/20152421
css.properties.user-select.none Chrome12/11/2008 Edge7/29/20152421
css.properties.user-select.text Chrome12/11/2008 Edge7/29/20152421
css.properties.vector-effect 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.vector-effect.non-scaling-stroke 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.vector-effect.none 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.vertical-align 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.vertical-align.baseline 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.vertical-align.bottom 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.vertical-align.middle 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.vertical-align.sub 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.vertical-align.super 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.vertical-align.text-bottom 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.vertical-align.text-top 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.vertical-align.top 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.view-timeline 📋Chrome7/18/2023 Edge7/21/20233
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline.none 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-timeline-axis 📋Chrome7/18/2023 Edge7/21/20233
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline-axis.block 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-timeline-axis.inline 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-timeline-axis.x 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-timeline-axis.y 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-timeline-inset 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-timeline-inset.auto 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-timeline-name 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-timeline-name.none 📋Chrome7/18/2023 Edge7/21/20233
css.properties.view-transition-class 📋Chrome5/14/2024 Edge5/17/20243
css.properties.view-transition-class.none 📋Chrome5/14/2024 Edge5/17/20243
css.properties.view-transition-group 📋Chrome9/2/2025 Edge9/5/20253
css.properties.view-transition-group.contain Chrome9/2/2025 Edge9/5/20253
css.properties.view-transition-group.nearest Chrome9/2/2025 Edge9/5/20253
css.properties.view-transition-group.normal Chrome9/2/2025 Edge9/5/20253
css.properties.view-transition-name 📋Chrome3/7/2023 Edge3/13/20236
css.properties.view-transition-name.match-element 📋Chrome5/27/2025 Edge5/29/20252
css.properties.view-transition-name.none 📋Chrome3/7/2023 Edge3/13/20236
css.properties.visibility 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: Internet Explorer doesn't support visibility: initial.Internet Explorer: Internet Explorer doesn't support visibility: unset.Internet Explorer: Up to Internet Explorer 7, descendants of hidden elements will still be invisible even if they have visibility set to visible.
css.properties.visibility.collapse 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: Before Chrome 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome: Before Chrome 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome: Since Chrome 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Chrome Android: Before Chrome Android 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome Android: Before Chrome Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome Android: Since Chrome Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Edge: For Edge 79 through Edge 91, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Edge: Since Edge 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Firefox: Firefox doesn't hide borders when hiding <col> and <colgroup> elements if border-collapse: collapse is set.Firefox: Before Firefox 88, collapse is not supported on ruby annotations.Firefox for Android: Firefox for Android doesn't hide borders when hiding <col> and <colgroup> elements if border-collapse: collapse is set.Firefox for Android: Before Firefox for Android 88, collapse is not supported on ruby annotations.Quest Browser: Before Quest Browser 5.0, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Quest Browser: Before Quest Browser 17.0, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Quest Browser: Since Quest Browser 17.0, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Opera: Before Opera 49, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera: Before Opera 78, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera: Since Opera 78, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Opera Android: Before Opera Android 46, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera Android: Before Opera Android 65, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera Android: Since Opera Android 65, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Safari: Safari treats visibility: collapse like hidden, leaving a white gap.Safari: Safari supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.Safari on iOS: Safari on iOS treats visibility: collapse like hidden, leaving a white gap.Safari on iOS: Safari on iOS supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.Samsung Internet: Before Samsung Internet 8.0, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Samsung Internet: Before Samsung Internet 16.0, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Samsung Internet: Since Samsung Internet 16.0, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.WebView Android: Before WebView Android 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.WebView Android: Before WebView Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.WebView Android: Since WebView Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.WebView on iOS: WebView on iOS treats visibility: collapse like hidden, leaving a white gap.WebView on iOS: WebView on iOS supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.
css.properties.visibility.hidden 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.visibility.visible 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.white-space 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.white-space.break-spaces 📋Chrome7/30/2019 Edge1/15/2020169
css.properties.white-space.collapse 📋Chrome5/30/2023 Edge6/2/20233
css.properties.white-space.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.white-space.nowrap 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.white-space.pre 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.white-space.pre-line 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.white-space.pre-wrap 📋Chrome12/11/2008 Edge7/29/20152421
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.preserve 📋Chrome5/30/2023 Edge6/2/20233
css.properties.white-space.preserve-breaks 📋Chrome5/30/2023 Edge6/2/20233
css.properties.white-space.shorthand_values Chrome5/30/2023 Edge6/2/20233
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.textarea_support Chrome12/11/2008 Edge7/29/20152421
css.properties.white-space.wrap 📋Chrome5/30/2023 Edge6/2/20233
css.properties.white-space-collapse 📋Chrome5/30/2023 Edge6/2/20233
css.properties.white-space-collapse.break-spaces 📋Chrome5/30/2023 Edge6/2/20233
css.properties.white-space-collapse.collapse 📋Chrome5/30/2023 Edge6/2/20233
css.properties.white-space-collapse.preserve 📋Chrome5/30/2023 Edge6/2/20233
css.properties.white-space-collapse.preserve-breaks 📋Chrome5/30/2023 Edge6/2/20233
css.properties.widows 📋Chrome2/21/2013 Edge7/29/2015888
css.properties.width 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.width.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.properties.width.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.width.fit-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.width.is_animatable Chrome3/26/2013 Edge7/29/2015855
css.properties.width.max-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.width.min-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.width.stretch 📋Chrome6/24/2025 Edge6/26/20252
css.properties.will-change 📋Chrome7/16/2014 Edge1/15/20202009
css.properties.will-change.auto 📋Chrome7/16/2014 Edge1/15/20202009
css.properties.will-change.contents 📋Chrome7/16/2014 Edge1/15/20202009
css.properties.will-change.scroll-position 📋Chrome7/16/2014 Edge1/15/20202009
css.properties.word-break 📋Chrome12/11/2008 Edge7/29/20152421
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.auto-phrase 📋Chrome10/31/2023 Edge11/2/20232
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.properties.word-break.break-all 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.word-break.break-word 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.word-break.keep-all 📋Chrome7/21/2015 Edge7/29/20158
css.properties.word-break.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.word-spacing 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.word-spacing.normal 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.word-spacing.percentages Chrome2/10/2026 Edge2/14/20264
css.properties.word-spacing.svg_elements Chrome12/11/2008 Edge7/29/20152421
css.properties.writing-mode 📋Edge7/29/2015 Chrome1/20/2016175
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 Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.lr Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.lr-tb Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.rl Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.rl-tb Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.sideways-lr Chrome1/14/2025 Edge1/17/20253
css.properties.writing-mode.sideways-rl Chrome1/14/2025 Edge1/17/20253
css.properties.writing-mode.tb Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.tb-rl Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.vertical-lr Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.vertical-rl Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.vertical_oriented_form_controls Chrome4/16/2024 Edge4/18/20242
Chrome: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Chrome: Supported for select, button, textarea and textual input elements.Chrome: Only supported for select and button elements.Chrome Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Chrome Android: Supported for select, button, textarea and textual input elements.Chrome Android: Only supported for select and button elements.Edge: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Edge: Supported for select, button, textarea and textual input elements.Edge: Only supported for select and button elements.Opera: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Opera: Supported for select, button, textarea and textual input elements.Opera: Only supported for select and button elements.Opera Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Opera Android: Supported for select, button, textarea and textual input elements.Opera Android: Only supported for select and button elements.Safari: Support for range sliders, textual inputs, and textareas onlySafari on iOS: Support for range sliders, textual inputs, and textareas onlySamsung Internet: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Samsung Internet: Supported for select, button, textarea and textual input elements.WebView Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.WebView Android: Supported for select, button, textarea and textual input elements.WebView Android: Only supported for select and button elements.WebView on iOS: Support for range sliders, textual inputs, and textareas only
css.properties.x 📋Chrome4/14/2015 Edge1/15/20201737
css.properties.y 📋Chrome4/14/2015 Edge1/15/20201737
css.properties.z-index 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.z-index.auto 📋Chrome12/11/2008 Edge7/29/20152421
css.properties.z-index.negative_values Chrome12/11/2008 Edge7/29/20152421
css.properties.zoom 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 131, SVG elements are not zoomed properly. See bug 1905023 and bug 878346.Firefox for Android: Before Firefox for Android 131, SVG elements are not zoomed properly. See bug 1905023 and bug 878346.
css.selectors.-webkit-inner-spin-button Chrome9/2/2010 Edge1/15/20203422
css.selectors.-webkit-meter-bar Chrome6/7/2011 Edge1/15/20203144
css.selectors.-webkit-meter-even-less-good-value Chrome6/7/2011 Edge1/15/20203144
css.selectors.-webkit-meter-inner-element Chrome11/6/2012 Edge1/15/20202626
css.selectors.-webkit-meter-optimum-value Chrome6/7/2011 Edge1/15/20203144
css.selectors.-webkit-meter-suboptimum-value Chrome6/7/2011 Edge1/15/20203144
css.selectors.-webkit-progress-bar Chrome2/21/2013 Edge1/15/20202519
css.selectors.-webkit-progress-inner-element Chrome11/6/2012 Edge1/15/20202626
css.selectors.-webkit-progress-value Chrome2/21/2013 Edge1/15/20202519
css.selectors.-webkit-resizer Chrome5/21/2009 Edge1/15/20203891
css.selectors.-webkit-scrollbar Chrome5/21/2009 Edge1/15/20203891
Safari on iOS: From Safari 13, only display: none works with this pseudo-element. Other styles have no effect.WebView on iOS: From Safari 13, only display: none works with this pseudo-element. Other styles have no effect.
css.selectors.-webkit-scrollbar-button Chrome5/21/2009 Edge1/15/20203891
css.selectors.-webkit-scrollbar-corner Chrome5/21/2009 Edge1/15/20203891
css.selectors.-webkit-scrollbar-thumb Chrome5/21/2009 Edge1/15/20203891
css.selectors.-webkit-scrollbar-track Chrome5/21/2009 Edge1/15/20203891
css.selectors.-webkit-scrollbar-track-piece Chrome5/21/2009 Edge1/15/20203891
css.selectors.-webkit-search-cancel-button Chrome12/11/2008 Edge1/15/20204052
css.selectors.-webkit-search-results-button Chrome12/11/2008 Edge1/15/20204052
css.selectors.-webkit-slider-runnable-track Chrome3/26/2013 Edge1/15/20202486
css.selectors.-webkit-slider-thumb Chrome1/14/2014 Edge1/15/20202192
css.selectors.active 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.active.non_a_elements Chrome12/11/2008 Edge7/29/20152421
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.active-view-transition 📋Chrome5/14/2024 Edge5/17/20243
css.selectors.active-view-transition-type 📋Chrome5/14/2024 Edge5/17/20243
css.selectors.after 📋Chrome12/11/2008 Edge7/29/20152421
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 Chrome3/26/2013 Edge7/29/2015855
css.selectors.after.nested_marker 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.any-link 📋Chrome3/6/2018 Edge1/15/2020680
css.selectors.any-link.not_match_link Chrome3/6/2018 Edge1/15/2020680
css.selectors.attribute 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.attribute.case_insensitive_modifier Chrome3/2/2016 Edge1/15/20201414
css.selectors.autofill 📋Chrome2/7/2023 Edge2/9/20232
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.backdrop 📋Chrome8/26/2014 Edge1/15/20201968
css.selectors.backdrop.dialog Chrome1/14/2014 Edge1/15/20202192
css.selectors.backdrop.fullscreen Edge7/29/2015 Chrome9/4/20181133
css.selectors.backdrop.inherit_from_originating_element Chrome2/20/2024 Edge2/23/20243
css.selectors.backdrop.popover Chrome5/30/2023 Edge6/2/20233
css.selectors.before 📋Chrome12/11/2008 Edge7/29/20152421
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 Chrome3/26/2013 Edge7/29/2015855
css.selectors.before.nested_marker 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.checked 📋Chrome12/11/2008 Edge7/29/20152421
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.checkmark 📋Chrome2/4/2025 Edge2/6/20252
css.selectors.child 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.class 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.column 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.column.nested_scroll-marker Chrome4/1/2025 Edge4/4/20253
css.selectors.cue 📋Chrome3/26/2013 Edge1/15/20202486
Firefox: From Firefox 69, only allowed properties apply to the ::cue pseudo-element with no argument. See Permitted properties for a list of the allowed properties.
css.selectors.cue.selector_argument Chrome3/26/2013 Edge1/15/20202486
css.selectors.default 📋Chrome3/8/2011 Edge1/15/20203235
css.selectors.defined 📋Chrome10/12/2016 Edge1/15/20201190
css.selectors.descendant 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.details-content 📋Chrome11/12/2024 Edge11/14/20242
Safari: Does not support chaining pseudo-elements after ::details-content. See bug 283446.Safari on iOS: Does not support chaining pseudo-elements after ::details-content. See bug 283446.WebView on iOS: Does not support chaining pseudo-elements after ::details-content. See bug 283446.
css.selectors.dir 📋Chrome12/5/2023 Edge12/7/20232
css.selectors.disabled 📋Chrome12/11/2008 Edge7/29/20152421
Edge: Before Edge 79, Edge did not recognize :disabled on the <fieldset> element.Internet Explorer: Internet Explorer does not recognize :disabled on the <fieldset> element.
css.selectors.empty 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.enabled 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.file-selector-button 📋Chrome3/2/2021 Edge3/4/20212
css.selectors.first 📋Chrome3/28/2012 Edge7/29/20151218
css.selectors.first-child 📋Chrome1/25/2010 Edge7/29/20152011
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-child.no_parent_required Chrome3/9/2017 Edge1/15/20201042
css.selectors.first-letter 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.first-line 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: Before Chrome 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome: Before Chrome 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome Android: Before Chrome Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome Android: Before Chrome Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Quest Browser: Before Quest Browser 5.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Quest Browser: Before Quest Browser 5.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Opera: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera Android: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera Android: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Safari: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Samsung Internet: Before Samsung Internet 8.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Samsung Internet: Before Samsung Internet 8.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView Android: Before WebView Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView Android: Before WebView Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.WebView on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.
css.selectors.first-of-type 📋Chrome12/11/2008 Edge7/29/20152421
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.focus 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.focus-visible 📋Edge10/9/2020 Chrome10/20/202011
css.selectors.focus-within 📋Chrome7/25/2017 Edge1/15/2020904
css.selectors.fullscreen 📋Edge7/29/2015 Chrome12/4/20181224
Safari on iOS: Only available on iPad, not on iPhone.Safari on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.Safari on iOS: Only available on iPad, not on iPhone.WebView on iOS: Only available on iPad, not on iPhone.WebView on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.WebView on iOS: Only available on iPad, not on iPhone.
css.selectors.future 📋Chrome11/6/2012 Edge1/15/20202626
css.selectors.grammar-error 📋Chrome1/23/2024 Edge1/25/20242
css.selectors.has 📋Edge9/1/2022 Chrome9/2/20221
css.selectors.highlight 📋Edge9/1/2022 Chrome9/2/20221
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.host 📋Chrome10/12/2016 Edge1/15/20201190
css.selectors.host-context 📋Chrome10/12/2016 Edge1/15/20201190
css.selectors.hostfunction 📋Chrome10/12/2016 Edge1/15/20201190
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.hover 📋Chrome12/11/2008 Edge7/29/20152421
Safari on iOS: As of Safari for iOS 7.1.2, tapping a clickable element causes the element to enter the :hover state. The element will remain in the :hover state until a different element has entered the :hover state.WebView on iOS: As of Safari for iOS 7.1.2, tapping a clickable element causes the element to enter the :hover state. The element will remain in the :hover state until a different element has entered the :hover state.
css.selectors.hover.a_elements Chrome12/11/2008 Edge7/29/20152421
css.selectors.hover.all_elements Chrome12/11/2008 Edge7/29/20152421
Edge: In Edge, hovering over an element and then scrolling up or down without moving the pointer will leave the element in the :hover state until the pointer is moved.Internet Explorer: In Internet Explorer 8 to Internet Explorer 11, hovering over an element and then scrolling up or down without moving the pointer will leave the element in the :hover state until the pointer is moved. See bug 926665.Internet Explorer: In Internet Explorer 9 (and possibly earlier), if a <table> has a parent with a non-auto width, overflow-x: auto;, the <table> has enough content to horizontally overflow its parent, and there are :hover styles set on elements within the table, then hovering over said elements will cause the <table>'s height to increase. See a live demo that triggers the bug. One workaround for the bug is to set min-height: 0%; (the % unit must be specified, since unitless and px don't work) on the <table>'s parent element.
css.selectors.id 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.in-range 📋Chrome3/8/2011 Edge11/12/20151710
Chrome: Before Chrome 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome 52, it was changed to only match enabled read-write inputs.Chrome Android: Before Chrome Android 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome Android 52, it was changed to only match enabled read-write inputs.Firefox: Before Firefox 50, :in-range matched disabled and read-only inputs (see bug 1264157). In Firefox 50, it was changed to only match enabled read-write inputs.Quest Browser: Before Quest Browser 5.0, :in-range matched disabled and read-only inputs (see bug 41248615). In Quest Browser 5.0, it was changed to only match enabled read-write inputs.Opera: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Opera Android: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Safari: In Safari, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Safari on iOS: In Safari on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Samsung Internet: Before version 6.0, :in-range matched disabled and read-only inputs (see bug 41248615). In version 6.0, it was changed to only match enabled read-write inputs.WebView Android: Before version 52, :in-range matched disabled and read-only inputs (see bug 41248615). In version 52, it was changed to only match enabled read-write inputs.WebView on iOS: In WebView on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.
css.selectors.indeterminate 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.indeterminate.checkbox Chrome12/11/2008 Edge7/29/20152421
css.selectors.indeterminate.progress Chrome9/2/2010 Edge7/29/20151791
css.selectors.indeterminate.radio Chrome11/18/2014 Edge1/15/20201884
css.selectors.interest-source 📋Chrome10/28/2025 Edge10/31/20253
css.selectors.interest-target 📋Chrome10/28/2025 Edge10/31/20253
css.selectors.invalid 📋Chrome3/8/2011 Edge7/29/20151604
css.selectors.invalid.form Chrome1/21/2015 Edge1/15/20201820
css.selectors.is 📋Chrome1/19/2021 Edge1/21/20212
Chrome: Doesn't support combinators.Chrome Android: Doesn't support combinators.Edge: Doesn't support combinators.Firefox: Doesn't support combinators.Firefox: See bug 906353.Firefox for Android: Doesn't support combinators.Firefox for Android: See bug 906353.Quest Browser: Doesn't support combinators.Opera: Doesn't support combinators.Opera Android: Doesn't support combinators.Safari: Doesn't support combinators.Safari on iOS: Doesn't support combinators.WebView Android: Doesn't support combinators.WebView on iOS: Doesn't support combinators.
css.selectors.is.forgiving_selector_list Chrome1/19/2021 Edge1/21/20212
css.selectors.lang 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.last-child 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.last-child.no_parent_required Chrome3/9/2017 Edge1/15/20201042
css.selectors.last-of-type 📋Chrome12/11/2008 Edge7/29/20152421
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.left 📋Chrome9/2/2010 Edge7/29/20151791
css.selectors.link 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.link.not_match_link Chrome12/11/2008 Edge7/29/20152421
css.selectors.list 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.marker 📋Edge10/9/2020 Chrome10/20/202011
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 Edge10/9/2020 Chrome10/20/202011
css.selectors.modal 📋Edge9/1/2022 Chrome9/2/20221
css.selectors.namespace 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.nesting 📋Chrome12/5/2023 Edge12/7/20232
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.selectors.nesting.at-scope Chrome12/2/2025 Edge12/5/20253
css.selectors.next-sibling 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.Internet Explorer: Internet Explorer 7 doesn't update the style correctly when an element is dynamically placed before an element that matched the selector.Internet Explorer: In Internet Explorer 8, if an element is inserted dynamically by clicking on a link the first-child style isn't applied until the link loses focus.
css.selectors.not 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.not.selector_list Chrome1/19/2021 Edge1/21/20212
css.selectors.nth-child 📋Chrome12/11/2008 Edge7/29/20152421
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-child.no_parent_required Chrome3/9/2017 Edge1/15/20201042
css.selectors.nth-child.of_syntax Chrome3/7/2023 Edge3/13/20236
css.selectors.nth-last-child 📋Chrome1/25/2010 Edge7/29/20152011
css.selectors.nth-last-child.no_parent_required Chrome3/9/2017 Edge1/15/20201042
css.selectors.nth-last-child.of_syntax Chrome3/7/2023 Edge3/13/20236
css.selectors.nth-last-of-type 📋Chrome1/25/2010 Edge7/29/20152011
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.nth-of-type 📋Chrome12/11/2008 Edge7/29/20152421
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.only-child 📋Chrome5/21/2009 Edge7/29/20152260
css.selectors.only-child.no_parent_required Chrome3/9/2017 Edge1/15/20201042
css.selectors.only-of-type 📋Chrome12/11/2008 Edge7/29/20152421
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.open 📋Chrome2/4/2025 Edge2/6/20252
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.optional 📋Chrome3/8/2011 Edge7/29/20151604
css.selectors.out-of-range 📋Chrome3/8/2011 Edge11/12/20151710
css.selectors.part 📋Chrome3/12/2019 Edge1/15/2020309
css.selectors.past 📋Chrome11/6/2012 Edge1/15/20202626
css.selectors.picker 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.picker-icon 📋Chrome2/4/2025 Edge2/6/20252
css.selectors.picture-in-picture 📋Chrome2/7/2023 Edge2/9/20232
css.selectors.placeholder 📋Chrome3/9/2017 Edge1/15/20201042
css.selectors.placeholder-shown 📋Chrome12/1/2015 Edge1/15/20201506
css.selectors.placeholder-shown.non_text_types Chrome12/1/2015 Edge1/15/20201506
css.selectors.popover-open 📋Chrome5/30/2023 Edge6/2/20233
css.selectors.read-only 📋Chrome12/11/2008 Edge11/12/20152527
css.selectors.read-write 📋Chrome12/11/2008 Edge11/12/20152527
css.selectors.required 📋Chrome3/8/2011 Edge7/29/20151604
css.selectors.right 📋Chrome9/2/2010 Edge7/29/20151791
css.selectors.root 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.scope 📋Chrome5/21/2013 Edge1/15/20202430
Firefox: Firefox 55 removes support for <style scoped> but not for the :scope pseudo-class, which is still supported. <style scoped> made it possible to explicitly set up element scopes, but ongoing discussions about the design of this feature as well as lack of other implementations resulted in the decision to remove it.Firefox for Android: Firefox for Android 55 removes support for <style scoped> but not for the :scope pseudo-class, which is still supported. <style scoped> made it possible to explicitly set up element scopes, but ongoing discussions about the design of this feature as well as lack of other implementations resulted in the decision to remove it.
css.selectors.scope.dom_api Chrome5/21/2013 Edge1/15/20202430
css.selectors.scroll-button 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.block-end 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.block-start 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.down 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.inline-end 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.inline-start 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.left 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.right 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.star 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-button.up 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-marker 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.scroll-marker-group 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.search-text 📋Chrome1/13/2026 Edge1/21/20268
css.selectors.selection 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.selection.text-decoration Edge9/1/2022 Chrome9/2/20221
css.selectors.slotted 📋Chrome4/13/2016 Edge1/15/20201372
css.selectors.spelling-error 📋Chrome1/23/2024 Edge1/25/20242
css.selectors.state 📋Chrome5/14/2024 Edge5/17/20243
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.selectors.subsequent-sibling 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.target 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.target-after 📋Chrome10/28/2025 Edge10/31/20253
css.selectors.target-before 📋Chrome10/28/2025 Edge10/31/20253
css.selectors.target-current 📋Chrome4/1/2025 Edge4/4/20253
css.selectors.target-text 📋Chrome3/2/2021 Edge3/4/20212
css.selectors.type 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.type.namespaces Chrome12/11/2008 Edge7/29/20152421
css.selectors.universal 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.universal.namespaces Chrome12/11/2008 Edge7/29/20152421
css.selectors.user-invalid 📋Chrome10/31/2023 Edge11/2/20232
css.selectors.user-valid 📋Chrome10/31/2023 Edge11/2/20232
css.selectors.valid 📋Chrome3/8/2011 Edge7/29/20151604
css.selectors.valid.form Chrome1/21/2015 Edge1/15/20201820
css.selectors.view-transition 📋Chrome1/10/2023 Edge1/12/20232
css.selectors.view-transition-group 📋Chrome1/10/2023 Edge1/12/20232
css.selectors.view-transition-group-children 📋Chrome9/2/2025 Edge9/5/20253
css.selectors.view-transition-image-pair 📋Chrome1/10/2023 Edge1/12/20232
css.selectors.view-transition-new 📋Chrome1/10/2023 Edge1/12/20232
css.selectors.view-transition-old 📋Chrome1/10/2023 Edge1/12/20232
css.selectors.visited 📋Chrome12/11/2008 Edge7/29/20152421
css.selectors.visited.not_match_link Chrome12/11/2008 Edge7/29/20152421
css.selectors.visited.privacy_measures Chrome9/2/2010 Edge7/29/20151791
css.selectors.where 📋Chrome1/19/2021 Edge1/21/20212
css.selectors.where.forgiving_selector_list Chrome1/19/2021 Edge1/21/20212
css.selectors.xr-overlay 📋Chrome5/19/2020 Edge5/21/20202
css.types.abs 📋Chrome6/24/2025 Edge6/26/20252
css.types.acos 📋Chrome3/7/2023 Edge3/13/20236
css.types.anchor 📋Chrome5/14/2024 Edge5/17/20243
css.types.anchor-size 📋Chrome5/14/2024 Edge5/17/20243
css.types.anchor-size.inset_margin Chrome1/14/2025 Edge1/17/20253
css.types.angle 📋Chrome5/21/2009 Edge7/29/20152260
css.types.angle.deg Chrome5/21/2009 Edge7/29/20152260
css.types.angle.grad Chrome5/21/2009 Edge7/29/20152260
css.types.angle.rad Chrome5/21/2009 Edge7/29/20152260
css.types.angle.turn Chrome5/21/2009 Edge7/29/20152260
css.types.angle-percentage 📋Chrome5/21/2009 Edge7/29/20152260
css.types.asin 📋Chrome3/7/2023 Edge3/13/20236
css.types.atan 📋Chrome3/7/2023 Edge3/13/20236
css.types.atan2 📋Chrome3/7/2023 Edge3/13/20236
css.types.attr 📋Chrome5/21/2009 Edge7/29/20152260
css.types.attr.declaration-value 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.angle 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.color 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.custom-ident 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.ident 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.image 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.integer 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.length 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.length-percentage 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.number 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.percentage 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.resolution 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.string 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.time 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.transform-function 📋Chrome2/4/2025 Edge2/6/20252
css.types.attr.type_function.url 📋Chrome2/4/2025 Edge2/6/20252
css.types.basic-shape 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.animation Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.circle 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.ellipse 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.inset 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.path 📋Chrome7/20/2016 Edge1/15/20201274
css.types.basic-shape.path.clip-path 📋Chrome1/19/2021 Edge1/21/20212
css.types.basic-shape.path.d 📋Chrome7/20/2016 Edge1/15/20201274
css.types.basic-shape.path.offset-path 📋Chrome1/25/2017 Edge1/15/20201085
css.types.basic-shape.polygon 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.rect 📋Chrome10/31/2023 Edge11/2/20232
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.shape 📋Chrome4/1/2025 Edge4/4/20253
css.types.basic-shape.xywh 📋Chrome10/31/2023 Edge11/2/20232
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.blend-mode 📋Chrome5/20/2014 Edge1/15/20202066
css.types.calc 📋Chrome3/26/2013 Edge7/29/2015855
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.color_component Chrome10/31/2023 Edge11/2/20232
css.types.calc.gradient_color_stops Chrome5/15/2012 Edge7/29/20151170
css.types.calc.nested Chrome5/25/2016 Edge10/17/2017510
css.types.calc.number_values Chrome11/12/2013 Edge7/29/2015624
css.types.calc.typed_division_produces_unitless_number 📋Chrome9/2/2025 Edge9/5/20253
css.types.calc-keyword 📋Chrome3/1/2022 Edge3/3/20222
css.types.calc-keyword.NaN Chrome3/1/2022 Edge3/3/20222
css.types.calc-keyword.e Chrome2/7/2023 Edge2/9/20232
css.types.calc-keyword.infinity Chrome3/1/2022 Edge3/3/20222
css.types.calc-keyword.pi Chrome1/10/2023 Edge1/12/20232
css.types.calc-size 📋Chrome9/17/2024 Edge9/19/20242
css.types.clamp 📋Chrome12/10/2019 Edge1/15/202036
css.types.color 📋Chrome12/11/2008 Edge7/29/20152421
css.types.color.color 📋Chrome3/7/2023 Edge3/13/20236
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.colorSpace_parameter_accepts_display-p3-linear_value 📋Chrome1/13/2026 Edge1/21/20268
css.types.color.color.mixed_type_parameters Chrome3/7/2023 Edge3/13/20236
css.types.color.color.relative_syntax 📋Chrome10/31/2023 Edge11/2/20232
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.color-mix 📋Chrome3/7/2023 Edge3/13/20236
css.types.color.currentcolor 📋Chrome12/11/2008 Edge7/29/20152421
css.types.color.hsl 📋Chrome12/11/2008 Edge7/29/20152421
css.types.color.hsl.alpha_parameter Chrome3/6/2018 Edge1/15/2020680
css.types.color.hsl.mixed_type_parameters Chrome1/23/2024 Edge1/25/20242
css.types.color.hsl.relative_syntax 📋Chrome5/14/2024 Edge5/17/20243
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.hsl.space_separated_parameters Chrome3/6/2018 Edge1/15/2020680
css.types.color.hwb 📋Chrome4/26/2022 Edge4/28/20222
css.types.color.hwb.mixed_type_parameters Chrome1/23/2024 Edge1/25/20242
css.types.color.hwb.relative_syntax 📋Chrome5/14/2024 Edge5/17/20243
Chrome: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Chrome Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Edge: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).Samsung Internet: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).
css.types.color.lab 📋Chrome3/7/2023 Edge3/13/20236
css.types.color.lab.mixed_type_parameters Chrome8/15/2023 Edge8/21/20236
css.types.color.lab.relative_syntax 📋Chrome10/31/2023 Edge11/2/20232
css.types.color.lch 📋Chrome3/7/2023 Edge3/13/20236
css.types.color.lch.mixed_type_parameters Chrome8/15/2023 Edge8/21/20236
css.types.color.lch.relative_syntax 📋Chrome10/31/2023 Edge11/2/20232
Safari: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Safari on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).WebView on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).
css.types.color.light-dark 📋Chrome3/19/2024 Edge3/22/20243
css.types.color.named-color 📋Chrome12/11/2008 Edge7/29/20152421
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 Chrome10/7/2014 Edge7/29/2015295
css.types.color.named-color.transparent 📋Chrome12/11/2008 Edge7/29/20152421
css.types.color.oklab 📋Chrome3/7/2023 Edge3/13/20236
css.types.color.oklab.mixed_type_parameters Chrome8/15/2023 Edge8/21/20236
css.types.color.oklab.relative_syntax 📋Chrome2/20/2024 Edge2/23/20243
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 📋Chrome3/7/2023 Edge3/13/20236
css.types.color.oklch.mixed_type_parameters Chrome8/15/2023 Edge8/21/20236
css.types.color.oklch.relative_syntax 📋Chrome2/20/2024 Edge2/23/20243
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 📋Chrome12/11/2008 Edge7/29/20152421
css.types.color.rgb.alpha_parameter Chrome3/6/2018 Edge1/15/2020680
css.types.color.rgb.float_values Chrome4/17/2018 Edge1/15/2020638
css.types.color.rgb.mixed_type_parameters Chrome2/20/2024 Edge2/23/20243
css.types.color.rgb.relative_syntax 📋Chrome2/20/2024 Edge2/23/20243
Chrome: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Chrome Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Edge: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Opera: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Opera Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Safari: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.Safari on iOS: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.Samsung Internet: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.WebView Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.WebView on iOS: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.
css.types.color.rgb.space_separated_parameters Chrome3/6/2018 Edge1/15/2020680
css.types.color.rgb_hexadecimal_notation 📋Chrome12/11/2008 Edge7/29/20152421
css.types.color.rgb_hexadecimal_notation.alpha_hexadecimal_notation Chrome10/17/2017 Edge1/15/2020820
css.types.color.system-color 📋Chrome12/11/2008 Edge7/29/20152421
css.types.color.system-color.accentcolor_accentcolortext 📋Chrome7/18/2023 Edge7/21/20233
Safari: Only supports a fallback: The native color when accent colour (in macOS' appearance panel) is set to 'multicolour'. On iOS falls back to the blue accent colourSafari on iOS: Only supports a fallback: The native color when accent colour (in macOS' appearance panel) is set to 'multicolour'. On iOS falls back to the blue accent colourWebView on iOS: Only supports a fallback: The native color when accent colour (in macOS' appearance panel) is set to 'multicolour'. On iOS falls back to the blue accent colour
css.types.color.system-color.buttonborder 📋Chrome4/26/2022 Edge4/28/20222
css.types.color.system-color.mark 📋Chrome5/24/2022 Edge5/31/20227
css.types.color.system-color.marktext 📋Chrome5/24/2022 Edge5/31/20227
css.types.color.transparent Chrome12/11/2008 Edge7/29/20152421
css.types.corner-shape-value 📋Chrome8/5/2025 Edge8/7/20252
css.types.corner-shape-value.bevel 📋Chrome8/5/2025 Edge8/7/20252
css.types.corner-shape-value.notch 📋Chrome8/5/2025 Edge8/7/20252
css.types.corner-shape-value.round 📋Chrome8/5/2025 Edge8/7/20252
css.types.corner-shape-value.scoop 📋Chrome8/5/2025 Edge8/7/20252
css.types.corner-shape-value.square 📋Chrome8/5/2025 Edge8/7/20252
css.types.corner-shape-value.squircle 📋Chrome8/5/2025 Edge8/7/20252
css.types.corner-shape-value.superellipse 📋Chrome8/5/2025 Edge8/7/20252
css.types.cos 📋Chrome3/7/2023 Edge3/13/20236
css.types.counter 📋Chrome12/11/2008 Edge7/29/20152421
css.types.counters 📋Chrome12/11/2008 Edge7/29/20152421
css.types.dashed-function 📋Chrome8/5/2025 Edge8/7/20252
css.types.dimension 📋Chrome12/11/2008 Edge7/29/20152421
css.types.dynamic-range-limit-mix 📋Chrome4/29/2025 Edge5/1/20252
css.types.easing-function 📋Chrome1/25/2010 Edge7/29/20152011
css.types.easing-function.cubic-bezier 📋Chrome12/13/2011 Edge7/29/20151324
css.types.easing-function.linear-function 📋Chrome5/2/2023 Edge5/5/20233
css.types.easing-function.steps 📋Chrome12/2/2010 Edge7/29/20151700
css.types.easing-function.steps.jump Chrome9/10/2019 Edge1/15/2020127
css.types.env 📋Chrome9/4/2018 Edge1/15/2020498
css.types.env.keyboard-inset-bottom 📋Chrome9/21/2021 Edge9/24/20213
css.types.env.keyboard-inset-height 📋Chrome9/21/2021 Edge9/24/20213
css.types.env.keyboard-inset-left 📋Chrome9/21/2021 Edge9/24/20213
css.types.env.keyboard-inset-right 📋Chrome9/21/2021 Edge9/24/20213
css.types.env.keyboard-inset-top 📋Chrome9/21/2021 Edge9/24/20213
css.types.env.keyboard-inset-width 📋Chrome9/21/2021 Edge9/24/20213
css.types.env.safe-area-inset-bottom 📋Chrome9/4/2018 Edge1/15/2020498
css.types.env.safe-area-inset-left 📋Chrome9/4/2018 Edge1/15/2020498
css.types.env.safe-area-inset-right 📋Chrome9/4/2018 Edge1/15/2020498
css.types.env.safe-area-inset-top 📋Chrome9/4/2018 Edge1/15/2020498
css.types.env.titlebar-area-height 📋Chrome8/31/2021 Edge9/2/20212
Chrome: Before version 93, Linux is unsupported.Chrome Android: Before version 93, Linux is unsupported.Edge: Before version 93, Linux is unsupported.
css.types.env.titlebar-area-width 📋Chrome8/31/2021 Edge9/2/20212
Chrome: Before version 93, Linux is unsupported.Chrome Android: Before version 93, Linux is unsupported.Edge: Before version 93, Linux is unsupported.
css.types.env.titlebar-area-x 📋Chrome8/31/2021 Edge9/2/20212
Chrome: Before version 93, Linux is unsupported.Chrome Android: Before version 93, Linux is unsupported.Edge: Before version 93, Linux is unsupported.
css.types.env.titlebar-area-y 📋Chrome8/31/2021 Edge9/2/20212
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.viewport-segment-bottom 📋Chrome6/24/2025 Edge6/26/20252
css.types.env.viewport-segment-height 📋Chrome6/24/2025 Edge6/26/20252
css.types.env.viewport-segment-left 📋Chrome6/24/2025 Edge6/26/20252
css.types.env.viewport-segment-right 📋Chrome6/24/2025 Edge6/26/20252
css.types.env.viewport-segment-top 📋Chrome6/24/2025 Edge6/26/20252
css.types.env.viewport-segment-width 📋Chrome6/24/2025 Edge6/26/20252
css.types.exp 📋Chrome12/5/2023 Edge12/7/20232
css.types.filter-function 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.blur 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.brightness 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.contrast 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.drop-shadow 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.grayscale 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.hue-rotate 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.invert 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.opacity 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.saturate 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.sepia 📋Chrome3/28/2012 Edge7/29/20151218
css.types.flex 📋Chrome8/20/2013 Edge7/29/2015708
css.types.global_keywords Chrome12/11/2008 Edge7/29/20152421
css.types.global_keywords.inherit 📋Chrome12/11/2008 Edge7/29/20152421
css.types.global_keywords.initial 📋Chrome12/11/2008 Edge11/12/20152527
css.types.global_keywords.revert 📋Edge7/16/2020 Chrome7/27/202011
css.types.global_keywords.revert-layer 📋Chrome3/1/2022 Edge3/3/20222
css.types.global_keywords.unset 📋Chrome3/3/2015 Edge11/12/2015254
css.types.gradient 📋Chrome3/26/2013 Edge7/29/2015855
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.conic-gradient 📋Chrome9/4/2018 Edge1/15/2020498
css.types.gradient.conic-gradient.doubleposition Chrome1/29/2019 Edge1/15/2020351
css.types.gradient.conic-gradient.hue_interpolation_method Chrome3/7/2023 Edge3/13/20236
css.types.gradient.conic-gradient.interpolation_color_space Chrome3/7/2023 Edge3/13/20236
css.types.gradient.conic-gradient.single_color_stop 📋Chrome4/1/2025 Edge4/4/20253
css.types.gradient.linear-gradient 📋Chrome3/26/2013 Edge7/29/2015855
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.doubleposition Chrome12/4/2018 Edge1/15/2020407
css.types.gradient.linear-gradient.hue_interpolation_method Chrome3/7/2023 Edge3/13/20236
css.types.gradient.linear-gradient.interpolation_color_space Chrome3/7/2023 Edge3/13/20236
css.types.gradient.linear-gradient.interpolation_hints Chrome1/21/2015 Edge1/15/20201820
css.types.gradient.linear-gradient.premultiplied_gradients Chrome8/20/2013 Edge1/15/20202339
css.types.gradient.linear-gradient.single_color_stop 📋Chrome4/1/2025 Edge4/4/20253
css.types.gradient.linear-gradient.to Chrome3/26/2013 Edge7/29/2015855
css.types.gradient.linear-gradient.unitless_0_angle Chrome3/26/2013 Edge7/29/2015855
Firefox: Accepted only in -webkit-linear-gradient() and -moz-linear-gradient(), not linear-gradient().Firefox for Android: Accepted only in -webkit-linear-gradient() and -moz-linear-gradient(), not linear-gradient().
css.types.gradient.radial-gradient 📋Chrome3/26/2013 Edge7/29/2015855
Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Internet Explorer: Internet Explorer 5.5 through 9.0 supported gradients via a proprietary filter: -ms-filter: progid:DXImageTransform.Microsoft.Gradient().Safari: Safari 4 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.Safari on iOS: Safari on iOS 3.2 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.WebView on iOS: WebView on iOS 3.2 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.
css.types.gradient.radial-gradient.at Chrome3/26/2013 Edge7/29/2015855
css.types.gradient.radial-gradient.doubleposition Chrome12/4/2018 Edge1/15/2020407
css.types.gradient.radial-gradient.hue_interpolation_method Chrome3/7/2023 Edge3/13/20236
css.types.gradient.radial-gradient.interpolation_color_space Chrome3/7/2023 Edge3/13/20236
css.types.gradient.radial-gradient.interpolation_hints Chrome1/21/2015 Edge1/15/20201820
css.types.gradient.radial-gradient.premultiplied_gradients Chrome8/20/2013 Edge1/15/20202339
css.types.gradient.radial-gradient.single_color_stop 📋Chrome4/1/2025 Edge4/4/20253
css.types.gradient.repeating-conic-gradient 📋Chrome9/4/2018 Edge1/15/2020498
css.types.gradient.repeating-conic-gradient.hue_interpolation_method Chrome3/7/2023 Edge3/13/20236
css.types.gradient.repeating-conic-gradient.interpolation_color_space Chrome3/7/2023 Edge3/13/20236
css.types.gradient.repeating-conic-gradient.single_color_stop 📋Chrome4/1/2025 Edge4/4/20253
css.types.gradient.repeating-linear-gradient 📋Chrome3/26/2013 Edge7/29/2015855
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.doubleposition Chrome12/4/2018 Edge1/15/2020407
css.types.gradient.repeating-linear-gradient.hue_interpolation_method Chrome3/7/2023 Edge3/13/20236
css.types.gradient.repeating-linear-gradient.interpolation_color_space Chrome3/7/2023 Edge3/13/20236
css.types.gradient.repeating-linear-gradient.interpolation_hints Chrome1/21/2015 Edge1/15/20201820
css.types.gradient.repeating-linear-gradient.single_color_stop 📋Chrome4/1/2025 Edge4/4/20253
css.types.gradient.repeating-linear-gradient.to Chrome3/26/2013 Edge7/29/2015855
css.types.gradient.repeating-linear-gradient.unitless_0_angle Chrome3/26/2013 Edge7/29/2015855
Firefox: Accepted only in -webkit-repeating-linear-gradient() and -moz-repeating-linear-gradient(), not repeating-linear-gradient().Firefox for Android: Accepted only in -webkit-repeating-linear-gradient() and -moz-repeating-linear-gradient(), not repeating-linear-gradient().
css.types.gradient.repeating-radial-gradient 📋Chrome3/26/2013 Edge7/29/2015855
Firefox: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox for Android: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Safari: Safari 4 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.Safari on iOS: Safari on iOS 3.2 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.WebView on iOS: WebView on iOS 3.2 was supporting an experimental -webkit-gradient(radial,…) function. This old outdated syntax is still supported for compatibility purposes.
css.types.gradient.repeating-radial-gradient.at Chrome3/26/2013 Edge7/29/2015855
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.gradient.repeating-radial-gradient.doubleposition Chrome12/4/2018 Edge1/15/2020407
css.types.gradient.repeating-radial-gradient.hue_interpolation_method Chrome3/7/2023 Edge3/13/20236
css.types.gradient.repeating-radial-gradient.interpolation_color_space Chrome3/7/2023 Edge3/13/20236
css.types.gradient.repeating-radial-gradient.interpolation_hints Chrome1/21/2015 Edge1/15/20201820
css.types.gradient.repeating-radial-gradient.single_color_stop 📋Chrome4/1/2025 Edge4/4/20253
css.types.hypot 📋Chrome12/5/2023 Edge12/7/20232
css.types.if 📋Chrome5/27/2025 Edge5/29/20252
css.types.if.style Chrome5/27/2025 Edge5/29/20252
css.types.if.style.range_syntax 📋Chrome10/28/2025 Edge10/31/20253
css.types.image 📋Chrome12/11/2008 Edge7/29/20152421
css.types.image.cross-fade 📋Chrome2/8/2012 Edge1/15/20202898
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.image-set 📋Chrome5/2/2023 Edge5/5/20233
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.image.paint 📋Chrome3/6/2018 Edge1/15/2020680
css.types.integer 📋Chrome12/11/2008 Edge7/29/20152421
css.types.length 📋Chrome12/11/2008 Edge7/29/20152421
css.types.length.Q Chrome12/6/2017 Edge1/15/2020770
css.types.length.cap Chrome10/10/2023 Edge10/13/20233
css.types.length.ch Chrome5/21/2013 Edge7/29/2015799
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.container_query_length_units Edge9/1/2022 Chrome9/2/20221
css.types.length.em Chrome12/11/2008 Edge7/29/20152421
css.types.length.ex Chrome12/11/2008 Edge7/29/20152421
css.types.length.ic Chrome9/27/2022 Edge10/3/20226
css.types.length.lh 📋Chrome1/10/2023 Edge1/12/20232
css.types.length.rcap 📋Chrome10/10/2023 Edge10/13/20233
css.types.length.rch 📋Chrome3/7/2023 Edge3/13/20236
css.types.length.rem Chrome1/25/2010 Edge7/29/20152011
css.types.length.rex 📋Chrome3/7/2023 Edge3/13/20236
css.types.length.ric 📋Chrome3/7/2023 Edge3/13/20236
css.types.length.rlh 📋Chrome3/7/2023 Edge3/13/20236
css.types.length.vb Chrome11/29/2022 Edge12/5/20226
css.types.length.vh Chrome6/26/2012 Edge7/29/20151128
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.vi Chrome11/29/2022 Edge12/5/20226
css.types.length.viewport_percentage_units_dynamic Chrome11/29/2022 Edge12/5/20226
css.types.length.viewport_percentage_units_large Chrome11/29/2022 Edge12/5/20226
css.types.length.viewport_percentage_units_small Chrome11/29/2022 Edge12/5/20226
css.types.length.vmax Chrome3/26/2013 Edge10/17/20171666
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length.vmin Chrome3/26/2013 Edge7/29/2015855
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length.vw Chrome6/26/2012 Edge7/29/20151128
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 📋Chrome12/11/2008 Edge7/29/20152421
css.types.line-style 📋Chrome12/11/2008 Edge7/29/20152421
css.types.log 📋Chrome12/5/2023 Edge12/7/20232
css.types.max 📋Chrome12/10/2019 Edge1/15/202036
css.types.min 📋Chrome12/10/2019 Edge1/15/202036
css.types.mod 📋Chrome5/14/2024 Edge5/17/20243
css.types.mod.mixed_type_parameters 📋Chrome5/14/2024 Edge5/17/20243
css.types.number 📋Chrome12/11/2008 Edge7/29/20152421
css.types.number.scientific_notation Chrome5/19/2015 Edge7/29/201571
css.types.overflow 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: From version 4 to 6, Internet Explorer enlarges an element with visible (default value) to fit the content inside it.
css.types.overflow.clip Chrome4/13/2021 Edge4/15/20212
css.types.overflow.overlay Chrome5/30/2023 Edge6/2/20233
Chrome: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Chrome Android: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Edge: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Quest Browser: Before version false, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version false, the keyword aliases to the standard auto keyword. See bug 40444262.Opera: Before version 100, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 100, the keyword aliases to the standard auto keyword. See bug 40444262.Safari: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.Safari on iOS: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.WebView Android: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.WebView on iOS: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.
css.types.percentage 📋Chrome12/11/2008 Edge7/29/20152421
css.types.position 📋Chrome12/11/2008 Edge7/29/20152421
css.types.position.four_value_syntax Chrome2/21/2013 Edge7/29/2015888
css.types.position.keyword_value_syntax Chrome12/11/2008 Edge7/29/20152421
css.types.pow 📋Chrome12/5/2023 Edge12/7/20232
css.types.progress 📋Chrome6/24/2025 Edge6/26/20252
css.types.ratio 📋Chrome9/15/2009 Edge7/29/20152143
css.types.ray 📋Chrome8/15/2023 Edge8/21/20236
css.types.ray.position Chrome8/15/2023 Edge8/21/20236
css.types.ray.size Chrome8/15/2023 Edge8/21/20236
css.types.rem 📋Chrome5/14/2024 Edge5/17/20243
css.types.rem.mixed_type_parameters 📋Chrome5/14/2024 Edge5/17/20243
css.types.resolution 📋Chrome8/20/2013 Edge7/29/2015708
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.types.resolution.dpcm Chrome8/20/2013 Edge7/29/2015708
css.types.resolution.dpi Chrome8/20/2013 Edge7/29/2015708
css.types.resolution.dppx Chrome8/20/2013 Edge7/29/2015708
css.types.resolution.x Chrome7/24/2018 Edge1/15/2020540
css.types.round 📋Chrome5/14/2024 Edge5/17/20243
css.types.round.mixed_type_parameters 📋Chrome5/14/2024 Edge5/17/20243
css.types.shape 📋Chrome12/11/2008 Edge7/29/20152421
css.types.shape.rect Chrome12/11/2008 Edge7/29/20152421
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.sibling-count 📋Chrome6/24/2025 Edge6/26/20252
css.types.sibling-index 📋Chrome6/24/2025 Edge6/26/20252
css.types.sign 📋Chrome6/24/2025 Edge6/26/20252
css.types.sign.typed_division_produces_unitless_number 📋Chrome9/2/2025 Edge9/5/20253
css.types.sin 📋Chrome3/7/2023 Edge3/13/20236
css.types.sqrt 📋Chrome12/5/2023 Edge12/7/20232
css.types.string 📋Chrome12/11/2008 Edge7/29/20152421
css.types.string.unicode_escaped_characters Chrome12/11/2008 Edge7/29/20152421
css.types.superellipse 📋Chrome8/5/2025 Edge8/7/20252
css.types.tan 📋Chrome3/7/2023 Edge3/13/20236
css.types.text-edge 📋Chrome2/4/2025 Edge2/6/20252
css.types.text-edge.alphabetic 📋Chrome2/4/2025 Edge2/6/20252
css.types.text-edge.cap 📋Chrome2/4/2025 Edge2/6/20252
css.types.text-edge.ex 📋Chrome2/4/2025 Edge2/6/20252
css.types.text-edge.text 📋Chrome2/4/2025 Edge2/6/20252
css.types.time 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function 📋Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: Internet Explorer 9 supports 2D but not 3D transforms. In version 9, mixing 2D and 3D transform functions invalidates the entire property.
css.types.transform-function.matrix 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 16, the translation values of matrix() could be <length>s, in addition to the standard <number>.
css.types.transform-function.matrix3d 📋Chrome6/7/2011 Edge7/29/20151513
Firefox: Before Firefox 16, the translation values of matrix3d() could be <length>s, in addition to the standard <number>.
css.types.transform-function.perspective 📋Chrome6/7/2011 Edge7/29/20151513
css.types.transform-function.perspective.none 📋Chrome1/4/2022 Edge1/6/20222
css.types.transform-function.rotate 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.rotate3d 📋Chrome6/7/2011 Edge7/29/20151513
css.types.transform-function.rotateX 📋Chrome6/7/2011 Edge7/29/20151513
css.types.transform-function.rotateY 📋Chrome6/7/2011 Edge7/29/20151513
css.types.transform-function.rotateZ 📋Chrome6/7/2011 Edge7/29/20151513
css.types.transform-function.scale 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.scale3d 📋Chrome6/7/2011 Edge7/29/20151513
css.types.transform-function.scaleX 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.scaleY 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.scaleZ 📋Chrome6/7/2011 Edge7/29/20151513
css.types.transform-function.skew 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Firefox 14 removed experimental support for skew(), but it was reintroduced in Firefox 15.
css.types.transform-function.skewX 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.skewY 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.translate 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.translate3d 📋Chrome6/7/2011 Edge7/29/20151513
css.types.transform-function.translateX 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.translateY 📋Chrome12/11/2008 Edge7/29/20152421
css.types.transform-function.translateZ 📋Chrome6/7/2011 Edge7/29/20151513
css.types.type 📋Chrome8/5/2025 Edge8/7/20252
css.types.url 📋Chrome12/11/2008 Edge7/29/20152421
css.types.var 📋Chrome3/2/2016 Edge4/5/2017399