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 EdgeLast in Safari
First in Edge 882
First in Safari 2137

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

3019 APIs took an average of 1758.95 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 Edge and Safari). TTA (time to available).
CSS APIsCSS TTA
2003 4254472.12
2004 654231.20
2005 393794.15
2007 1502986.67
2008 672814.01
2009 1692903.78
2010 1013090.47
2011 642776.30
2012 561331.63
2013 1241882.76
2014 461686.43
2015 169961.63
2016 1421293.92
2017 166692.54
2018 25901.20
2019 218322.21
2020 279666.95
2021 76534.21
2022 163324.86
2023 127443.03
2024 241338.56
2025 107116.37

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 Edge and Safari. TTA (time to available).
Year CSSCSS TTA
2003
  Safari 4254472.12
2004
  Safari 654231.20
2005
  Safari 393794.15
2007
  Safari 1502986.67
2008
  Safari 672814.01
2009
  Safari 1692903.78
2010
  Safari 1013090.47
2011
  Safari 642776.30
2012
  Safari 561331.63
2013
  Safari 1241882.76
2014
  Safari 461686.43
2015
  Edge 127665.77
  Safari 421856.26
2016
  Safari 1391315.55
  Edge 3291.67
2017
  Safari 158699.90
  Edge 8547.13
2018
  Safari 15690.73
  Edge 101216.90
2019
  Safari 218322.21
2020
  Safari 17625.53
  Edge 262669.64
2021
  Edge 51498.37
  Safari 25607.32
2022
  Edge 45222.47
  Safari 118363.91
2023
  Edge 111471.65
  Safari 16244.50
2024
  Edge 206380.44
  Safari 3592.06
2025
  Edge 59146.63
  Safari 4879.19

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 Edge and Safari. TTA (time to available).
Year CSS countCSS TTA
2003
  Edge 4254472.12
2004
  Edge 654231.20
2005
  Edge 393794.15
2007
  Edge 1502986.67
2008
  Edge 672814.01
2009
  Edge 1692903.78
2010
  Edge 1013090.47
2011
  Edge 642776.30
2012
  Edge 561331.63
2013
  Edge 1241882.76
2014
  Edge 461686.43
2015
  Safari 127665.77
  Edge 421856.26
2016
  Edge 1391315.55
  Safari 3291.67
2017
  Edge 158699.90
  Safari 8547.13
2018
  Edge 15690.73
  Safari 101216.90
2019
  Edge 218322.21
2020
  Edge 17625.53
  Safari 262669.64
2021
  Safari 51498.37
  Edge 25607.32
2022
  Safari 45222.47
  Edge 118363.91
2023
  Safari 111471.65
  Edge 16244.50
2024
  Safari 206380.44
  Edge 3592.06
2025
  Safari 59146.63
  Edge 4879.19

Stable APIs

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

Raw Data

Quick Links:

CSS Data

API First Browser Date Last Browser Date Days Notes
css.at-rules.charset 📋Safari6/8/2009 Edge7/29/20152242
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 Safari9/12/202211
css.at-rules.container.style_queries_for_custom_properties 📋Edge3/13/2023 Safari9/16/2024553
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.counter-style 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.counter-style.additive-symbols 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.counter-style.fallback 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.counter-style.negative 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.counter-style.pad 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.counter-style.prefix 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.counter-style.range 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.counter-style.suffix 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.counter-style.symbols 📋Edge5/27/2021 Safari9/18/2023844
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 📋Edge5/27/2021 Safari9/18/2023844
css.at-rules.font-face 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.OpenType_COLRv0 Safari4/12/2018 Edge1/15/2020643
css.at-rules.font-face.OpenType_SBIX Safari3/21/2016 Edge1/15/20201395
css.at-rules.font-face.WOFF 📋Safari7/20/2011 Edge7/29/20151470
css.at-rules.font-face.WOFF_2 📋Edge8/2/2016 Safari9/20/201649
Safari: Supported only on macOS 10.12 (Sierra) and later.
css.at-rules.font-face.font-display 📋Safari4/12/2018 Edge1/15/2020643
css.at-rules.font-face.font-family 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.font-feature-settings 📋Safari9/20/2016 Edge9/5/20253272
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 📋Safari3/27/2017 Edge4/30/2018399
css.at-rules.font-face.font-style 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.font-variant Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.font-weight 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.size-adjust 📋Edge7/22/2021 Safari9/18/2023788
css.at-rules.font-face.src 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.src.format_keyword Safari6/8/2009 Edge12/5/20224928
css.at-rules.font-face.src.format_variations Safari9/19/2017 Edge4/30/2018223
css.at-rules.font-face.src.tech_keyword Edge12/5/2022 Safari9/18/2023287
css.at-rules.font-face.unicode-range 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-feature-values 📋Safari3/21/2016 Edge3/13/20232548
css.at-rules.font-feature-values.annotation Safari3/21/2016 Edge3/13/20232548
css.at-rules.font-feature-values.character-variant Safari3/21/2016 Edge3/13/20232548
css.at-rules.font-feature-values.historical-forms Safari3/21/2016 Edge3/13/20232548
css.at-rules.font-feature-values.ornaments Safari3/21/2016 Edge3/13/20232548
css.at-rules.font-feature-values.styleset Safari3/21/2016 Edge3/13/20232548
css.at-rules.font-feature-values.stylistic Safari3/21/2016 Edge3/13/20232548
css.at-rules.font-feature-values.swash Safari3/21/2016 Edge3/13/20232548
css.at-rules.font-palette-values 📋Safari3/14/2022 Edge4/28/202245
css.at-rules.font-palette-values.base-palette 📋Safari3/14/2022 Edge4/28/202245
css.at-rules.font-palette-values.font-family 📋Safari3/14/2022 Edge4/28/202245
css.at-rules.font-palette-values.override-colors 📋Safari3/14/2022 Edge4/28/202245
css.at-rules.import 📋Safari6/23/2003 Edge7/29/20154419
css.at-rules.import.layer 📋Edge3/3/2022 Safari3/14/202211
css.at-rules.import.supports 📋Edge2/23/2024 Safari5/13/202480
css.at-rules.keyframes 📋Edge7/29/2015 Safari9/30/201563
css.at-rules.keyframes.ignore_important_declarations Safari3/27/2017 Edge1/15/20201024
css.at-rules.keyframes.named_range_keyframes 📋Edge7/21/2023 Safari9/15/2025787
css.at-rules.layer 📋Edge3/3/2022 Safari3/14/202211
css.at-rules.media 📋Safari10/26/2007 Edge7/29/20152833
css.at-rules.media.-webkit-device-pixel-ratio 📋Safari10/26/2007 Edge7/29/20152833
Firefox: Implemented as an alias for -moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for -moz-device-pixel-ratio.
css.at-rules.media.-webkit-max-device-pixel-ratio 📋Safari10/26/2007 Edge7/29/20152833
Firefox: Implemented as an alias for max--moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for max--moz-device-pixel-ratio.
css.at-rules.media.-webkit-min-device-pixel-ratio 📋Safari10/26/2007 Edge7/29/20152833
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 📋Safari6/8/2009 Edge7/29/20152242
css.at-rules.media.any-hover 📋Safari9/30/2015 Edge10/17/2017748
css.at-rules.media.any-pointer 📋Edge7/29/2015 Safari9/30/201563
css.at-rules.media.aspect-ratio 📋Safari6/7/2010 Edge7/29/20151878
css.at-rules.media.calc 📋Safari9/17/2018 Edge1/15/2020485
css.at-rules.media.color 📋Safari10/26/2007 Edge7/29/20152833
css.at-rules.media.color-gamut 📋Safari9/20/2016 Edge1/15/20201212
css.at-rules.media.color-gamut.p3 📋Safari9/20/2016 Edge1/15/20201212
Firefox: color-gamut: p3 is always false because Firefox does not support wide-gamut color. See bug 1626624.Firefox for Android: color-gamut: p3 is always false because Firefox for Android does not support wide-gamut color. See bug 1626624.
css.at-rules.media.color-gamut.rec2020 📋Safari9/20/2016 Edge1/15/20201212
Firefox: color-gamut: rec2020 is always false because Firefox does not support wide-gamut color. See bug 1626624.Firefox for Android: color-gamut: rec2020 is always false because Firefox for Android does not support wide-gamut color. See bug 1626624.
css.at-rules.media.color-gamut.srgb 📋Safari9/20/2016 Edge1/15/20201212
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 📋Safari10/16/2014 Edge1/15/20201917
css.at-rules.media.device-aspect-ratio 📋Safari10/26/2007 Edge7/29/20152833
css.at-rules.media.device-height 📋Safari10/26/2007 Edge7/29/20152833
css.at-rules.media.device-width 📋Safari10/26/2007 Edge7/29/20152833
css.at-rules.media.display-mode 📋Safari9/19/2019 Edge1/15/2020118
css.at-rules.media.display-mode.browser 📋Safari9/19/2019 Edge1/15/2020118
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 📋Safari9/19/2019 Edge1/15/2020118
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 📋Safari9/19/2019 Edge1/15/2020118
Firefox: display-mode: minimal-ui is never true.Safari: display-mode: minimal-ui is never true.Safari on iOS: display-mode: minimal-ui is never true.WebView on iOS: display-mode: minimal-ui is never true.
css.at-rules.media.display-mode.standalone 📋Safari9/19/2019 Edge1/15/2020118
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.dynamic-range 📋Safari3/24/2020 Edge2/3/2022681
css.at-rules.media.forced-colors 📋Edge1/15/2020 Safari9/12/2022971
css.at-rules.media.grid 📋Safari10/26/2007 Edge7/29/20152833
css.at-rules.media.height 📋Safari10/26/2007 Edge7/29/20152833
css.at-rules.media.hover 📋Edge7/29/2015 Safari9/30/201563
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 Safari10/26/2007 Edge7/29/20152833
css.at-rules.media.monochrome 📋Safari10/26/2007 Edge1/15/20204464
css.at-rules.media.nested-queries Safari10/22/2013 Edge7/29/2015645
css.at-rules.media.or_syntax Edge8/5/2022 Safari3/27/2023234
css.at-rules.media.orientation 📋Safari6/7/2010 Edge7/29/20151878
css.at-rules.media.overflow-block 📋Edge5/5/2023 Safari9/18/2023136
css.at-rules.media.overflow-inline 📋Edge5/5/2023 Safari9/18/2023136
css.at-rules.media.pointer 📋Edge7/29/2015 Safari9/30/201563
css.at-rules.media.prefers-color-scheme 📋Safari3/25/2019 Edge1/15/2020296
css.at-rules.media.prefers-contrast 📋Safari4/26/2021 Edge11/19/2021207
css.at-rules.media.prefers-reduced-motion 📋Safari3/27/2017 Edge1/15/20201024
css.at-rules.media.range_syntax Edge8/5/2022 Safari3/27/2023234
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 📋Edge7/29/2015 Safari9/12/20222602
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.at-rules.media.scan 📋Edge8/5/2022 Safari3/27/2023234
css.at-rules.media.scripting 📋Safari9/18/2023 Edge12/7/202380
css.at-rules.media.update 📋Edge5/5/2023 Safari9/18/2023136
css.at-rules.media.width 📋Safari10/26/2007 Edge7/29/20152833
css.at-rules.namespace 📋Safari6/23/2003 Edge7/29/20154419
css.at-rules.page 📋Edge7/29/2015 Safari12/11/20243423
css.at-rules.page.size 📋Edge1/15/2020 Safari12/11/20241792
css.at-rules.page.size.jis-b4 📋Edge5/21/2020 Safari12/11/20241665
css.at-rules.page.size.jis-b5 📋Edge5/21/2020 Safari12/11/20241665
css.at-rules.position-try 📋Edge5/17/2024 Safari9/15/2025486
css.at-rules.property 📋Edge8/27/2020 Safari3/27/2023942
css.at-rules.property.inherits 📋Edge8/27/2020 Safari3/27/2023942
css.at-rules.property.initial-value 📋Edge8/27/2020 Safari3/27/2023942
css.at-rules.property.syntax 📋Edge8/27/2020 Safari3/27/2023942
css.at-rules.scope 📋Edge10/13/2023 Safari3/5/2024144
css.at-rules.starting-style 📋Edge9/15/2023 Safari5/13/2024241
css.at-rules.supports 📋Edge7/29/2015 Safari9/30/201563
css.at-rules.supports.font-format Edge12/5/2022 Safari9/18/2023287
css.at-rules.supports.font-tech Edge12/5/2022 Safari9/18/2023287
css.at-rules.supports.selector Edge5/21/2020 Safari4/26/2021340
css.at-rules.view-transition 📋Edge6/13/2024 Safari12/11/2024181
css.properties.-webkit-border-before Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-border-horizontal-spacing Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-border-vertical-spacing Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-box-reflect Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-column-break-after Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-column-break-before Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-column-break-inside Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-locale Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-logical-height Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-logical-width Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-margin-after Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-margin-before Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-mask-box-image Safari3/18/2008 Edge1/15/20204320
css.properties.-webkit-mask-composite Safari3/18/2008 Edge10/2/20183850
css.properties.-webkit-mask-position-x Safari3/18/2008 Edge10/2/20183850
css.properties.-webkit-mask-position-y Safari3/18/2008 Edge10/2/20183850
css.properties.-webkit-max-logical-height Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-max-logical-width Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-min-logical-height Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-min-logical-width Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-perspective-origin-x Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-perspective-origin-y Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-rtl-ordering Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-text-combine Safari7/20/2011 Edge1/15/20203101
css.properties.-webkit-text-fill-color 📋Safari10/26/2007 Edge7/29/20152833
css.properties.-webkit-text-security Safari10/26/2007 Edge1/15/20204464
css.properties.-webkit-text-stroke 📋Safari10/26/2007 Edge4/5/20173449
css.properties.-webkit-text-stroke-color 📋Safari10/26/2007 Edge4/5/20173449
css.properties.-webkit-text-stroke-width 📋Safari10/26/2007 Edge4/5/20173449
css.properties.-webkit-transform-origin-x Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-transform-origin-y Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-transform-origin-z Safari6/8/2009 Edge1/15/20203873
css.properties.-webkit-user-drag Safari6/8/2009 Edge1/15/20203873
css.properties.accent-color 📋Edge9/2/2021 Safari3/14/2022193
Chrome Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Quest Browser: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Opera Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Safari: Safari does not maintain minimum contrast for legibility of the control. See bug 244233.Safari on iOS: Safari on iOS does not maintain minimum contrast for legibility of the control. See bug 244233.Samsung Internet: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.WebView Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.WebView on iOS: WebView on iOS does not maintain minimum contrast for legibility of the control. See bug 244233.
css.properties.accent-color.auto Edge9/2/2021 Safari3/14/2022193
css.properties.align-content 📋Edge7/29/2015 Safari9/30/201563
css.properties.align-content.block_context 📋Safari3/5/2024 Edge3/22/202417
css.properties.align-content.flex_context 📋Edge7/29/2015 Safari9/30/201563
css.properties.align-content.flex_context.baseline Safari9/30/2015 Edge1/15/20201568
css.properties.align-content.flex_context.first_baseline Safari9/19/2017 Edge1/15/2020848
css.properties.align-content.flex_context.safe_unsafe Edge7/21/2023 Safari7/29/2024374
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 Safari9/19/2017 Edge1/15/2020848
css.properties.align-content.flex_context.start_end Edge9/2/2021 Safari7/20/2022321
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 Safari9/30/2015 Edge1/15/20201568
css.properties.align-content.grid_context 📋Safari3/27/2017 Edge10/17/2017204
css.properties.align-content.multicol_context 📋Safari3/5/2024 Edge3/22/202417
css.properties.align-content.normal 📋Edge7/29/2015 Safari9/30/201563
css.properties.align-items 📋Edge7/29/2015 Safari9/30/201563
css.properties.align-items.anchor-center 📋Edge5/17/2024 Safari9/15/2025486
css.properties.align-items.flex_context 📋Safari10/22/2013 Edge7/29/2015645
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 Safari10/22/2013 Edge1/15/20202276
css.properties.align-items.flex_context.first_baseline Safari9/19/2017 Edge1/15/2020848
css.properties.align-items.flex_context.last_baseline Edge12/5/2022 Safari12/13/20228
css.properties.align-items.flex_context.safe_unsafe Edge7/21/2023 Safari7/29/2024374
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 Edge9/2/2021 Safari3/14/2022193
css.properties.align-items.grid_context 📋Safari3/27/2017 Edge10/17/2017204
css.properties.align-items.grid_context.start_end Safari9/19/2017 Edge1/15/2020848
css.properties.align-self 📋Edge7/29/2015 Safari9/30/201563
css.properties.align-self.anchor-center 📋Edge5/17/2024 Safari9/15/2025486
css.properties.align-self.auto 📋Safari10/22/2013 Edge1/15/20202276
css.properties.align-self.flex_context 📋Safari10/22/2013 Edge7/29/2015645
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 📋Safari10/22/2013 Edge1/15/20202276
css.properties.align-self.flex_context.first_baseline Safari9/19/2017 Edge1/15/2020848
css.properties.align-self.flex_context.last_baseline Edge12/5/2022 Safari12/13/20228
css.properties.align-self.flex_context.safe_unsafe Edge7/21/2023 Safari7/29/2024374
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 Edge9/2/2021 Safari3/14/2022193
Opera: Before version 79, this value is recognized, but has no effect.
css.properties.align-self.flex_context.stretch 📋Safari9/30/2015 Edge1/15/20201568
css.properties.align-self.grid_context 📋Safari3/27/2017 Edge10/17/2017204
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 📋Safari10/22/2013 Edge1/15/20202276
css.properties.align-self.stretch 📋Safari10/22/2013 Edge1/15/20202276
css.properties.alignment-baseline 📋Safari7/20/2011 Edge1/15/20203101
css.properties.alignment-baseline.alphabetic Safari7/20/2011 Edge1/15/20203101
css.properties.alignment-baseline.baseline Safari7/20/2011 Edge1/15/20203101
css.properties.alignment-baseline.central Safari7/20/2011 Edge1/15/20203101
css.properties.alignment-baseline.ideographic Safari7/20/2011 Edge1/15/20203101
css.properties.alignment-baseline.mathematical Safari7/20/2011 Edge1/15/20203101
css.properties.alignment-baseline.middle Safari7/20/2011 Edge1/15/20203101
css.properties.alignment-baseline.text-after-edge Safari7/20/2011 Edge1/15/20203101
css.properties.alignment-baseline.text-before-edge Safari7/20/2011 Edge1/15/20203101
css.properties.all 📋Safari3/21/2016 Edge1/15/20201395
css.properties.anchor-name 📋Edge5/17/2024 Safari9/15/2025486
css.properties.anchor-name.none 📋Edge5/17/2024 Safari9/15/2025486
css.properties.anchor-scope 📋Edge11/14/2024 Safari9/15/2025305
css.properties.anchor-scope.all 📋Edge11/14/2024 Safari9/15/2025305
css.properties.anchor-scope.none 📋Edge11/14/2024 Safari9/15/2025305
css.properties.animation 📋Edge7/29/2015 Safari9/30/201563
WebView Android: The animation-fill-mode property is not supported in Android browsers below 2.3.
css.properties.animation.alternate 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.alternate-reverse 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.auto 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.backwards 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.both 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.ease 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.ease-in 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.ease-in-out 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.ease-out 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.forwards 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.infinite 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.linear 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.none 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.normal 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.paused 📋Safari6/8/2009 Edge1/15/20203873
css.properties.animation.reverse 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.running 📋Safari6/8/2009 Edge1/15/20203873
css.properties.animation.step-end 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation.step-start 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-composition 📋Safari9/12/2022 Edge4/6/2023206
css.properties.animation-composition.accumulate 📋Safari9/12/2022 Edge4/6/2023206
css.properties.animation-composition.add 📋Safari9/12/2022 Edge4/6/2023206
css.properties.animation-composition.replace 📋Safari9/12/2022 Edge4/6/2023206
css.properties.animation-delay 📋Edge7/29/2015 Safari9/30/201563
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 📋Edge7/29/2015 Safari9/30/201563
css.properties.animation-direction.alternate 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-direction.alternate-reverse 📋Safari7/25/2012 Edge7/29/20151099
css.properties.animation-direction.normal 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-direction.reverse 📋Safari7/25/2012 Edge7/29/20151099
css.properties.animation-duration 📋Edge7/29/2015 Safari9/30/201563
Internet Explorer: Once the element has loaded, changing the value of this property has no effect.
css.properties.animation-duration.auto 📋Edge7/21/2023 Safari3/31/2025619
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 📋Edge7/29/2015 Safari9/30/201563
css.properties.animation-fill-mode.backwards 📋Safari6/7/2010 Edge7/29/20151878
css.properties.animation-fill-mode.both 📋Safari6/7/2010 Edge7/29/20151878
css.properties.animation-fill-mode.forwards 📋Safari6/7/2010 Edge7/29/20151878
css.properties.animation-fill-mode.none 📋Safari6/7/2010 Edge7/29/20151878
css.properties.animation-iteration-count 📋Edge7/29/2015 Safari9/30/201563
css.properties.animation-iteration-count.infinite 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-name 📋Edge7/29/2015 Safari9/30/201563
css.properties.animation-name.none 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-play-state 📋Edge7/29/2015 Safari9/30/201563
css.properties.animation-play-state.paused 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-play-state.running 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-range 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-range.normal 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-range-end 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-range-end.normal 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-range-start 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-range-start.normal 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-timeline 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-timeline.auto 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-timeline.none 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-timeline.scroll 📋Edge7/21/2023 Safari9/15/2025787
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 📋Edge7/21/2023 Safari9/15/2025787
css.properties.animation-timing-function 📋Edge7/29/2015 Safari9/30/201563
css.properties.animation-timing-function.ease 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.ease-in 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.ease-in-out 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.ease-out 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.jump Edge1/15/2020 Safari9/16/2020245
css.properties.animation-timing-function.linear 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.step-end 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-timing-function.step-start 📋Safari6/8/2009 Edge7/29/20152242
css.properties.appearance 📋Edge7/16/2020 Safari3/14/2022606
css.properties.appearance.auto 📋Edge5/21/2020 Safari3/14/2022662
css.properties.appearance.button 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.checkbox 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.listbox 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.menulist 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.menulist-button 📋Safari10/26/2007 Edge7/29/20152833
Firefox: See bug 1481615.Firefox for Android: See bug 1481615.
css.properties.appearance.meter 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.none 📋Safari10/26/2007 Edge7/29/20152833
Firefox: Doesn't work with <input type="checkbox"> and <input type="radio">.Firefox for Android: Doesn't work with <input type="checkbox"> and <input type="radio">.
css.properties.appearance.progress-bar 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.radio 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.searchfield 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.textarea 📋Safari10/26/2007 Edge7/29/20152833
css.properties.appearance.textfield 📋Safari10/26/2007 Edge7/29/20152833
css.properties.aspect-ratio 📋Edge1/21/2021 Safari9/20/2021242
css.properties.aspect-ratio.auto 📋Edge1/21/2021 Safari9/20/2021242
css.properties.backdrop-filter 📋Edge1/15/2020 Safari9/16/20241706
Firefox: Before Firefox 123, the property was not supported on systems with unknown GPU vendor (see bug 1868737).Firefox for Android: Before Firefox for Android 123, the property was not supported on systems with unknown GPU vendor (see bug 1868737).
css.properties.backdrop-filter.none 📋Safari9/30/2015 Edge1/15/20201568
css.properties.backface-visibility 📋Edge7/29/2015 Safari3/14/20222420
css.properties.backface-visibility.hidden 📋Safari7/20/2011 Edge7/29/20151470
css.properties.backface-visibility.visible 📋Safari7/20/2011 Edge7/29/20151470
css.properties.background 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.SVG_image_as_background Safari3/18/2008 Edge7/29/20152689
css.properties.background.background-clip Safari7/20/2011 Edge7/29/20151470
css.properties.background.background-origin Safari7/20/2011 Edge7/29/20151470
css.properties.background.background-size Safari7/20/2011 Edge7/29/20151470
css.properties.background.border-box 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.bottom 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.center 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.content-box 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.fixed 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.left 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.local 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.multiple_backgrounds Safari4/15/2005 Edge7/29/20153757
css.properties.background.no-repeat 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.padding-box 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.repeat 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.repeat-x 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.repeat-y 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.right 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.round 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.scroll 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.space 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background.top 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-attachment 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-attachment.fixed 📋Edge7/29/2015 Safari3/14/20222420
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 📋Edge7/29/2015 Safari3/14/20222420
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 Safari4/15/2005 Edge7/29/20153757
css.properties.background-attachment.scroll 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-blend-mode 📋Safari10/16/2014 Edge1/15/20201917
css.properties.background-clip 📋Safari6/7/2010 Edge7/29/20151878
Chrome: Chrome accepts alternate synonyms to its values: padding, border, and content.Chrome Android: Chrome Android accepts alternate synonyms to its values: padding, border, and content.Edge: Since Edge 79, accepts alternate synonyms to its values: padding, border, and content.Firefox: Used the -moz-background-clip: padding | border syntax.Internet Explorer: In IE 7 and IE 8 of Internet Explorer, this property always behaved like background-clip: padding-box when overflow was hidden, auto, or scroll.Quest Browser: Quest Browser accepts alternate synonyms to its values: padding, border, and content.Opera: Opera accepts alternate synonyms to its values: padding, border, and content.Opera Android: Opera accepts alternate synonyms to its values: padding, border, and content.Safari: Safari accepts alternate synonyms to its values: padding, border, and content.Safari on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.Samsung Internet: Samsung Internet accepts alternate synonyms to its values: padding, border, and content.WebView Android: WebView Android accepts alternate synonyms to its values: padding, border, and content.WebView on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.
css.properties.background-clip.border-box 📋Safari10/26/2007 Edge7/29/20152833
css.properties.background-clip.content-box 📋Safari10/26/2007 Edge7/29/20152833
Internet Explorer: In IE 7 and IE 9 of Internet Explorer, it always behaved like background-clip: padding-box if overflow: hidden | auto | scroll
css.properties.background-clip.padding-box 📋Safari10/26/2007 Edge7/29/20152833
css.properties.background-clip.text 📋Safari9/16/2020 Edge12/7/20231177
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 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: In Internet Explorer 8 and 9, there is a bug where a computed background-color of transparent causes click events to not get fired on overlaid elements.
css.properties.background-color.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.background-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-image 📋Safari6/23/2003 Edge7/29/20154419
Firefox: If the browser.display.use_document_colors user preference in about:config is set to false, background images will not be displayed.Firefox for Android: If the browser.display.use_document_colors user preference in about:config is set to false, background images will not be displayed.
css.properties.background-image.gradients 📋Safari6/8/2009 Edge7/29/20152242
Chrome: Some versions support only experimental gradients prefixed with -webkit.Chrome Android: Some versions support only experimental gradients prefixed with -webkit.Firefox: Some versions support only experimental gradients prefixed with -moz.Firefox for Android: Some versions support only experimental gradients prefixed with -moz.Quest Browser: Some versions support only experimental gradients prefixed with -webkit.Opera: Some versions support only experimental gradients prefixed with -o.Opera Android: Some versions support only experimental gradients prefixed with -webkit.Safari: Some versions support only experimental gradients prefixed with -webkit.Safari on iOS: Some versions support only experimental gradients prefixed with -webkit.Samsung Internet: Some versions support only experimental gradients prefixed with -webkit.WebView Android: Some versions support only experimental gradients prefixed with -webkit.WebView on iOS: Some versions support only experimental gradients prefixed with -webkit.
css.properties.background-image.image-set 📋Edge5/5/2023 Safari9/18/2023136
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 Safari4/15/2005 Edge7/29/20153757
css.properties.background-image.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-image.svg_images Safari6/7/2010 Edge7/29/20151878
Safari: Support of SVG in CSS background is incomplete.Safari on iOS: Support of SVG in CSS background is incomplete.WebView on iOS: Support of SVG in CSS background is incomplete.
css.properties.background-origin 📋Safari10/26/2007 Edge7/29/20152833
Chrome: Chrome accepts alternate synonyms to its values: padding, border, and content.Chrome Android: Chrome Android accepts alternate synonyms to its values: padding, border, and content.Edge: Since Edge 79, accepts alternate synonyms to its values: padding, border, and content.Firefox: Used the -moz-background-clip: padding | border syntax.Internet Explorer: In IE 7 and before, Internet explorer was behaving as if background-origin: border-box was set. In Internet Explorer 8, as if background-origin: padding-box, the regular default value, was set.Quest Browser: Quest Browser accepts alternate synonyms to its values: padding, border, and content.Opera: Opera accepts alternate synonyms to its values: padding, border, and content.Opera Android: Opera accepts alternate synonyms to its values: padding, border, and content.Safari: Webkit accepts alternate synonyms to its values: padding, border, and content.Safari on iOS: Webkit accepts alternate synonyms to its values: padding, border, and content.Samsung Internet: Samsung Internet accepts alternate synonyms to its values: padding, border, and content.WebView Android: WebView accepts alternate synonyms to its values: padding, border, and content.WebView on iOS: Webkit accepts alternate synonyms to its values: padding, border, and content.
css.properties.background-origin.border-box 📋Safari10/26/2007 Edge7/29/20152833
css.properties.background-origin.content-box 📋Safari10/26/2007 Edge7/29/20152833
Internet Explorer: In IE 7 and IE 9 of Internet Explorer, it always behaved like background-clip: padding if overflow: hidden | auto | scroll.
css.properties.background-origin.padding-box 📋Safari10/26/2007 Edge7/29/20152833
css.properties.background-position 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-position.bottom 📋Safari6/23/2003 Edge1/15/20206050
css.properties.background-position.center 📋Safari6/23/2003 Edge1/15/20206050
css.properties.background-position.left 📋Safari6/23/2003 Edge1/15/20206050
css.properties.background-position.multiple_backgrounds Safari4/15/2005 Edge7/29/20153757
css.properties.background-position.right 📋Safari6/23/2003 Edge1/15/20206050
css.properties.background-position.side-relative_values Safari10/22/2013 Edge7/29/2015645
css.properties.background-position.top 📋Safari6/23/2003 Edge1/15/20206050
css.properties.background-position-x 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-position-x.side-relative_values Safari3/14/2022 Edge1/21/20261409
css.properties.background-position-y 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-position-y.side-relative_values Safari3/14/2022 Edge1/21/20261409
css.properties.background-repeat 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.2-value Safari6/7/2010 Edge7/29/20151878
css.properties.background-repeat.multiple_backgrounds Safari4/15/2005 Edge7/29/20153757
css.properties.background-repeat.no-repeat 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.repeat 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.repeat-x 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.repeat-y 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.round 📋Safari10/16/2014 Edge7/29/2015286
css.properties.background-repeat.space 📋Safari10/16/2014 Edge7/29/2015286
css.properties.background-size 📋Safari6/7/2010 Edge7/29/20151878
Chrome: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Chrome Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Quest Browser: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Opera Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera Android: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Safari: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Safari on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Samsung Internet: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.
css.properties.background-size.auto 📋Safari10/26/2007 Edge7/29/20152833
css.properties.background-size.contain 📋Safari6/7/2010 Edge7/29/20151878
css.properties.background-size.cover 📋Safari6/7/2010 Edge7/29/20151878
css.properties.baseline-shift 📋Safari6/8/2009 Edge1/15/20203873
css.properties.baseline-shift.baseline 📋Safari6/8/2009 Edge1/15/20203873
css.properties.baseline-shift.sub 📋Safari6/8/2009 Edge1/15/20203873
css.properties.baseline-shift.super 📋Safari6/8/2009 Edge1/15/20203873
css.properties.block-size 📋Safari3/25/2019 Edge1/15/2020296
css.properties.block-size.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.block-size.auto 📋Safari7/20/2011 Edge1/15/20203101
css.properties.block-size.fit-content 📋Safari3/25/2019 Edge1/15/2020296
css.properties.block-size.max-content Safari3/25/2019 Edge1/15/2020296
css.properties.block-size.min-content Safari3/25/2019 Edge1/15/2020296
css.properties.border 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-block 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.currentColor 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.dashed 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.dotted 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.double 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.groove 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.hidden 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.inset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.medium 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.none 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.outset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.ridge 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.solid 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.thick 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.thin 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block.transparent 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-color 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-color.currentColor 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-color.transparent 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-end 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.currentColor 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.dashed 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.dotted 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.double 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.groove 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.hidden 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.inset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.medium 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.outset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.ridge 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.solid 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.thick 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.thin 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end.transparent 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-color 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-color.currentColor 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-color.transparent 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.dashed 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.dotted 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.double 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.groove 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.hidden 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.inset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.outset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.ridge 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-style.solid 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-width 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-width.medium 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-width.thick 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-end-width.thin 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.currentColor 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.dashed 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.dotted 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.double 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.groove 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.hidden 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.inset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.medium 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.outset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.ridge 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.solid 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.thick 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.thin 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start.transparent 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-color 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-color.currentColor 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-color.transparent 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.dashed 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.dotted 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.double 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.groove 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.hidden 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.inset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.outset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.ridge 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-style.solid 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-width 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-width.medium 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-width.thick 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-start-width.thin 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-block-style 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.dashed 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.dotted 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.double 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.groove 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.hidden 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.inset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.none 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.outset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.ridge 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-style.solid 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-width 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-width.medium 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-width.thick 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-block-width.thin 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-bottom 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-bottom.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-color 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-color.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-bottom-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-left-radius 📋Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-left-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-bottom-left-radius.percentages Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-right-radius 📋Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-right-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-bottom-right-radius.percentages Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-style 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-style.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-style.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-width 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-width.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-width.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-width.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-collapse 📋Safari10/24/2003 Edge7/29/20154296
css.properties.border-collapse.collapse Safari10/24/2003 Edge1/15/20205927
css.properties.border-collapse.separate Safari10/24/2003 Edge1/15/20205927
css.properties.border-color 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-color.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-end-end-radius 📋Edge3/4/2021 Safari9/20/2021200
css.properties.border-end-start-radius 📋Edge3/4/2021 Safari9/20/2021200
css.properties.border-image 📋Safari7/25/2012 Edge7/29/20151099
Chrome: Before Chrome 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Chrome Android: Before Chrome Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Edge: Before Edge 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Firefox: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox: Until Firefox 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox: From Firefox 48 until Firefox 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox: Until Firefox 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox: Before Firefox 15, an earlier version of the specification was implemented, prefixed.Firefox for Android: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox for Android: Until Firefox for Android 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox for Android: From Firefox for Android 48 until Firefox for Android 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox for Android: Until Firefox for Android 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox for Android: Before Firefox for Android 15, an earlier version of the specification was implemented, prefixed.Quest Browser: Before Quest Browser false, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera: Before Opera 98, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera Android: A border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Samsung Internet: Before Samsung Internet 23.0, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).WebView Android: Before WebView 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).
css.properties.border-image.fill Safari7/25/2012 Edge7/29/20151099
css.properties.border-image.gradient Safari6/8/2009 Edge7/29/20152242
css.properties.border-image.none 📋Safari10/26/2007 Edge7/29/20152833
css.properties.border-image.optional_border_image_slice Safari7/25/2012 Edge7/29/20151099
css.properties.border-image.repeat 📋Safari10/26/2007 Edge7/29/20152833
css.properties.border-image.round 📋Safari10/26/2007 Edge7/29/20152833
css.properties.border-image.space 📋Safari10/26/2007 Edge7/29/20152833
css.properties.border-image.stretch 📋Safari10/26/2007 Edge7/29/20152833
css.properties.border-image-outset 📋Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-repeat 📋Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-repeat.repeat 📋Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-repeat.round 📋Edge7/29/2015 Safari3/21/2016236
css.properties.border-image-repeat.space 📋Edge7/29/2015 Safari3/21/2016236
css.properties.border-image-repeat.stretch 📋Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-slice 📋Safari7/25/2012 Edge7/29/20151099
Firefox: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox: Until Firefox 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox: From Firefox 48 until Firefox 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox: Until Firefox 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox for Android: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox for Android: Until Firefox for Android 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox for Android: From Firefox for Android 48 until Firefox for Android 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox for Android: Until Firefox for Android 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).
css.properties.border-image-source 📋Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-source.none 📋Safari7/25/2012 Edge7/29/20151099
css.properties.border-image-width 📋Safari7/25/2012 Edge7/29/20151099
Chrome: Before Chrome 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Chrome Android: Before Chrome Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Edge: Before Edge 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Quest Browser: Before Quest Browser false, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera: Before Opera 98, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera Android: Before Opera Android 75, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Samsung Internet: Before Samsung Internet 23.0, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).WebView Android: Before WebView Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).
css.properties.border-image-width.auto 📋Safari7/25/2012 Edge7/29/20151099
css.properties.border-inline 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.currentColor 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.dashed 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.dotted 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.double 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.groove 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.hidden 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.inset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.medium 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.none 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.outset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.ridge 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.solid 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.thick 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.thin 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline.transparent 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-color 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-color.currentColor 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-color.transparent 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-end 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.currentColor 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.dashed 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.dotted 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.double 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.groove 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.hidden 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.inset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.medium 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.outset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.ridge 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.solid 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.thick 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.thin 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end.transparent 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-color 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-color.currentColor 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-color.transparent 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.dashed 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.dotted 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.double 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.groove 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.hidden 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.inset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.outset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.ridge 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-style.solid 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-width 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-width.medium 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-width.thick 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-end-width.thin 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.currentColor 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.dashed 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.dotted 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.double 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.groove 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.hidden 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.inset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.medium 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.outset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.ridge 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.solid 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.thick 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.thin 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start.transparent 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-color 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-color.currentColor 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-color.transparent 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.dashed 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.dotted 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.double 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.groove 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.hidden 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.inset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.outset 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.ridge 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-style.solid 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-width 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-width.medium 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-width.thick 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-start-width.thin 📋Safari3/25/2019 Edge1/15/2020296
css.properties.border-inline-style 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.dashed 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.dotted 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.double 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.groove 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.hidden 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.inset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.none 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.outset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.ridge 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-style.solid 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-width 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-width.medium 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-width.thick 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-inline-width.thin 📋Edge11/19/2020 Safari4/26/2021158
css.properties.border-left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-left.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-color 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-color.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-left-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.
css.properties.border-left-style.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-style.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-width 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-width.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-width.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left-width.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-radius 📋Safari6/7/2010 Edge7/29/20151878
Chrome: Chrome ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox: To conform to the CSS3 standard, Firefox 4 changes the handling of <percentage> values to match the specification. You can specify an ellipse as a border on an arbitrary sized element with border-radius: 50%;. Firefox 4 also makes rounded corners clip content and images if overflow: visible is not set.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-style was solid. This has been fixed in Firefox 50.Opera: Before Opera 11.60, replaced elements with border-radius do not have rounded corners.Safari: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.Safari on iOS: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.WebView on iOS: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.
css.properties.border-radius.4_values_for_4_corners Safari6/7/2010 Edge7/29/20151878
css.properties.border-radius.elliptical_borders Safari10/26/2007 Edge7/29/20152833
Chrome: Before Chrome 4, the slash / notation is unsupported. If two values are specified, then an elliptical border is drawn on all four corners. -webkit-border-radius: 40px 10px; is equivalent to border-radius: 40px / 10px;.Safari: Before Safari 5, the slash / notation is unsupported. If two values are specified, then an elliptical border is drawn on all four corners. -webkit-border-radius: 40px 10px; is equivalent to border-radius: 40px / 10px;.
css.properties.border-radius.percentages Safari7/20/2011 Edge7/29/20151470
Firefox: Before Firefox 4, <percentage> values are implemented in a non-standard way. Both horizontal and vertical radii were relative to the width of the border box.Opera: Before Opera 11.5, the implementation of <percentage> values was buggy.
css.properties.border-right 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-right.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-color 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-color.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-right-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-bottom-style was solid. This has been fixed in Firefox 50.
css.properties.border-right-style.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-style.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-width 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-width.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-width.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right-width.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-spacing 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-start-end-radius 📋Edge3/4/2021 Safari9/20/2021200
css.properties.border-start-start-radius 📋Edge3/4/2021 Safari9/20/2021200
css.properties.border-style 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-style.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-style.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-top.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-color 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-color.currentColor 📋Safari3/21/2016 Edge4/5/2017380
css.properties.border-top-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-left-radius 📋Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-left-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-top-left-radius.percentages Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-right-radius 📋Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-right-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-top-right-radius.percentages Safari6/7/2010 Edge7/29/20151878
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-style 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-top-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners (with border-radius) were always rendered as if border-top-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-style.dashed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.dotted 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.double 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.groove 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.inset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.outset 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.ridge 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-style.solid 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-width 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-width.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-width.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-width.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-width 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-width.medium 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-width.thick 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-width.thin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.bottom 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: In Internet Explorer versions before 7, when both top and bottom are specified, the element position is overconstrained and the top property has precedence; the computed value of bottom is set to -top, while its specified value is ignored.
css.properties.bottom.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.bottom.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.bottom.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.box-align Safari10/26/2007 Edge7/29/20152833
css.properties.box-decoration-break 📋Safari10/22/2013 Edge10/17/20244013
Chrome: This property is only supported for inline elements.Chrome Android: This property is only supported for inline elements.Edge: This property is only supported for inline elements.Quest Browser: This property is only supported for inline elements.Safari: This property is only supported for inline elements.Safari on iOS: This property is only supported for inline elements.Samsung Internet: This property is only supported for inline elements.WebView Android: This property is only supported for inline elements.WebView on iOS: This property is only supported for inline elements.
css.properties.box-decoration-break.clone 📋Safari10/22/2013 Edge10/17/20244013
Chrome: This value was only supported with the -webkit- prefix.Chrome Android: This value was only supported with the -webkit- prefix.Edge: This value was only supported with the -webkit- prefix.Quest Browser: This value was only supported with the -webkit- prefix.Opera: This value was only supported with the -webkit- prefix.Opera Android: This value was only supported with the -webkit- prefix.Samsung Internet: This value was only supported with the -webkit- prefix.WebView Android: This value was only supported with the -webkit- prefix.
css.properties.box-decoration-break.slice 📋Safari10/22/2013 Edge10/17/20244013
Chrome: This value was only supported with the -webkit- prefix.Chrome Android: This value was only supported with the -webkit- prefix.Edge: This value was only supported with the -webkit- prefix.Quest Browser: This value was only supported with the -webkit- prefix.Opera: This value was only supported with the -webkit- prefix.Opera Android: This value was only supported with the -webkit- prefix.Samsung Internet: This value was only supported with the -webkit- prefix.WebView Android: This value was only supported with the -webkit- prefix.
css.properties.box-direction Safari10/26/2007 Edge7/29/20152833
css.properties.box-flex Safari10/26/2007 Edge7/29/20152833
css.properties.box-ordinal-group Safari10/26/2007 Edge7/29/20152833
css.properties.box-orient Safari10/26/2007 Edge7/29/20152833
css.properties.box-pack Safari10/26/2007 Edge7/29/20152833
css.properties.box-shadow 📋Safari7/20/2011 Edge7/29/20151470
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 Safari6/7/2010 Edge7/29/20151878
Internet Explorer: inset must be the last keyword in the declaration.
css.properties.box-shadow.multiple_shadows Safari10/26/2007 Edge7/29/20152833
css.properties.box-shadow.none 📋Safari10/26/2007 Edge7/29/20152833
css.properties.box-shadow.spread_radius Safari6/7/2010 Edge7/29/20151878
css.properties.box-sizing 📋Safari7/20/2011 Edge7/29/20151470
Chrome: box-sizing is not respected when the height is calculated from window.getComputedStyle().Chrome Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox: Before Firefox 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox for Android: Before Firefox for Android 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Internet Explorer: box-sizing is not respected when the height is calculated from window.getComputedStyle().Quest Browser: box-sizing is not respected when the height is calculated from window.getComputedStyle().Opera Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Samsung Internet: box-sizing is not respected when the height is calculated from window.getComputedStyle().WebView Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().
css.properties.box-sizing.border-box 📋Safari10/26/2007 Edge7/29/20152833
css.properties.box-sizing.content-box 📋Safari10/26/2007 Edge7/29/20152833
css.properties.break-after 📋Edge7/29/2015 Safari9/20/2016419
css.properties.break-after.auto Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.avoid-column Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.avoid-page Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.column Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.left Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.page Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.paged_context 📋Edge7/29/2015 Safari9/20/2016419
css.properties.break-after.paged_context.avoid-page Edge7/29/2015 Safari9/20/2016419
css.properties.break-after.paged_context.page Edge7/29/2015 Safari9/20/2016419
css.properties.break-after.recto Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.right Safari9/20/2016 Edge1/15/20201212
css.properties.break-after.verso Safari9/20/2016 Edge1/15/20201212
css.properties.break-before 📋Edge7/29/2015 Safari9/20/2016419
css.properties.break-before.auto Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.avoid-column Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.avoid-page Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.column Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.left Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.page Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.paged_context 📋Edge7/29/2015 Safari9/20/2016419
css.properties.break-before.paged_context.page Edge7/29/2015 Safari9/20/2016419
css.properties.break-before.recto Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.right Safari9/20/2016 Edge1/15/20201212
css.properties.break-before.verso Safari9/20/2016 Edge1/15/20201212
css.properties.break-inside 📋Edge7/29/2015 Safari9/20/2016419
css.properties.break-inside.auto Safari9/20/2016 Edge1/15/20201212
css.properties.break-inside.avoid Safari9/20/2016 Edge1/15/20201212
css.properties.break-inside.avoid-column Safari9/20/2016 Edge1/15/20201212
css.properties.break-inside.avoid-page Safari9/20/2016 Edge1/15/20201212
css.properties.break-inside.multicol_context 📋Edge7/29/2015 Safari9/20/2016419
css.properties.break-inside.multicol_context.avoid-column Edge7/29/2015 Safari9/20/2016419
css.properties.break-inside.paged_context 📋Edge7/29/2015 Safari9/20/2016419
css.properties.buffered-rendering Safari10/22/2013 Edge1/15/20202276
css.properties.buffered-rendering.auto Safari10/22/2013 Edge1/15/20202276
css.properties.buffered-rendering.dynamic Safari10/22/2013 Edge1/15/20202276
css.properties.buffered-rendering.static Safari10/22/2013 Edge1/15/20202276
css.properties.caption-side 📋Safari6/23/2003 Edge7/29/20154419
css.properties.caption-side.bottom Safari6/23/2003 Edge1/15/20206050
css.properties.caption-side.top Safari6/23/2003 Edge1/15/20206050
css.properties.caret-color 📋Safari4/12/2018 Edge1/15/2020643
css.properties.caret-color.auto 📋Safari4/12/2018 Edge1/15/2020643
css.properties.caret-color.currentColor 📋Safari4/12/2018 Edge1/15/2020643
css.properties.caret-color.transparent 📋Safari4/12/2018 Edge1/15/2020643
css.properties.clear 📋Safari6/23/2003 Edge7/29/20154419
css.properties.clear.both 📋Safari6/23/2003 Edge7/29/20154419
css.properties.clear.inline-end 📋Safari9/20/2021 Edge10/13/2023753
css.properties.clear.inline-start 📋Safari9/20/2021 Edge10/13/2023753
css.properties.clear.left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.clear.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.clear.right 📋Safari6/23/2003 Edge7/29/20154419
css.properties.clip 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Before Internet Explorer 7, Internet Explorer incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).Safari: Safari incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).Safari on iOS: Safari on iOS incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).WebView on iOS: WebView on iOS incorrectly interprets clip: auto as clip: rect(auto, auto, auto, auto).
css.properties.clip.auto Safari6/23/2003 Edge1/15/20206050
css.properties.clip-path 📋Safari3/21/2016 Edge1/15/20201395
Edge: Only supports clip paths defined by url().Internet Explorer: Only supports clip paths defined by url().
css.properties.clip-path.basic_shape 📋Safari10/22/2013 Edge1/15/20202276
css.properties.clip-path.border-box 📋Safari9/19/2019 Edge11/2/20231505
css.properties.clip-path.content-box 📋Safari9/19/2019 Edge11/2/20231505
css.properties.clip-path.fill-box 📋Safari3/24/2020 Edge11/2/20231318
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 Safari10/22/2013 Edge1/15/20202276
css.properties.clip-path.is_animatable Safari3/25/2019 Edge1/15/2020296
css.properties.clip-path.margin-box 📋Safari9/19/2019 Edge11/2/20231505
css.properties.clip-path.padding-box 📋Safari9/19/2019 Edge11/2/20231505
css.properties.clip-path.path Safari3/24/2020 Edge1/21/2021303
css.properties.clip-path.stroke-box 📋Safari3/24/2020 Edge11/2/20231318
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 Safari10/22/2013 Edge7/29/2015645
css.properties.clip-path.view-box 📋Safari3/24/2020 Edge11/2/20231318
css.properties.clip-rule 📋Safari6/7/2010 Edge1/15/20203509
css.properties.clip-rule.evenodd 📋Safari6/7/2010 Edge1/15/20203509
css.properties.clip-rule.nonzero 📋Safari6/7/2010 Edge1/15/20203509
css.properties.color 📋Safari6/23/2003 Edge7/29/20154419
css.properties.color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.color-interpolation 📋Safari6/8/2009 Edge1/15/20203873
css.properties.color-interpolation.auto 📋Safari6/8/2009 Edge1/15/20203873
css.properties.color-interpolation.linearRGB 📋Safari6/8/2009 Edge1/15/20203873
css.properties.color-interpolation.sRGB 📋Safari6/8/2009 Edge1/15/20203873
css.properties.color-interpolation-filters 📋Safari10/26/2007 Edge1/15/20204464
css.properties.color-interpolation-filters.auto 📋Safari10/26/2007 Edge1/15/20204464
css.properties.color-interpolation-filters.linearRGB 📋Safari9/30/2015 Edge1/15/20201568
css.properties.color-interpolation-filters.sRGB 📋Safari9/30/2015 Edge1/15/20201568
css.properties.color-scheme 📋Safari9/19/2019 Edge4/13/2020207
css.properties.color-scheme.dark Safari9/19/2019 Edge4/13/2020207
css.properties.color-scheme.light Safari9/19/2019 Edge4/13/2020207
css.properties.color-scheme.normal Safari9/19/2019 Edge4/13/2020207
css.properties.color-scheme.only Safari9/19/2019 Edge2/3/2022868
css.properties.column-count 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-fill 📋Edge7/29/2015 Safari9/30/201563
css.properties.column-fill.auto 📋Safari10/16/2014 Edge7/29/2015286
css.properties.column-fill.balance 📋Safari10/16/2014 Edge7/29/2015286
css.properties.column-gap 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-gap.flex_context 📋Edge7/16/2020 Safari4/26/2021284
css.properties.column-gap.grid_context 📋Edge10/17/2017 Safari9/17/2018335
css.properties.column-gap.multicol_context 📋Edge7/29/2015 Safari9/20/2016419
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 Safari3/25/2019524
css.properties.column-gap.multicol_context.percentage_values Edge10/17/2017 Safari9/17/2018335
css.properties.column-gap.normal 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule 📋Edge7/29/2015 Safari9/30/201563
Firefox: Before Firefox 3, the default value for the normal keyword was 0 and not 1em.
css.properties.column-rule.dashed 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.dotted 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.double 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.groove 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.hidden 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.inset 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.medium 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.none 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.outset 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.ridge 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.solid 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.thick 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.thin 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule.transparent 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-color 📋Edge7/29/2015 Safari9/30/201563
css.properties.column-rule-color.transparent 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style 📋Edge7/29/2015 Safari9/30/201563
css.properties.column-rule-style.dashed 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.dotted 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.double 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.groove 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.hidden 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.inset 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.none 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.outset 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.ridge 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style.solid 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-width 📋Edge7/29/2015 Safari9/30/201563
css.properties.column-rule-width.medium 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-width.thick 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-width.thin 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-span 📋Edge7/29/2015 Safari9/30/201563
css.properties.column-span.all 📋Safari7/20/2011 Edge7/29/20151470
css.properties.column-span.none 📋Safari7/20/2011 Edge7/29/20151470
css.properties.column-width 📋Edge7/29/2015 Safari9/30/201563
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 Safari10/26/2007 Edge7/29/20152833
css.properties.columns 📋Edge7/29/2015 Safari9/30/201563
Firefox: Before version 37, multiple columns didn't work with display: table-caption elements.Firefox for Android: Before version 37, multiple columns didn't work with display: table-caption elements.
css.properties.columns.auto 📋Safari10/26/2007 Edge7/29/20152833
css.properties.contain 📋Edge1/15/2020 Safari3/14/2022789
css.properties.contain.content 📋Edge1/15/2020 Safari3/14/2022789
css.properties.contain.inline-size 📋Edge9/1/2022 Safari9/12/202211
css.properties.contain.layout 📋Edge1/15/2020 Safari3/14/2022789
css.properties.contain.none 📋Edge1/15/2020 Safari3/14/2022789
css.properties.contain.paint 📋Edge1/15/2020 Safari3/14/2022789
css.properties.contain.size 📋Edge1/15/2020 Safari3/14/2022789
css.properties.contain.strict 📋Edge1/15/2020 Safari3/14/2022789
css.properties.contain.style 📋Edge1/15/2020 Safari3/14/2022789
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 📋Edge10/21/2021 Safari9/18/2023697
css.properties.contain-intrinsic-block-size.none 📋Edge2/3/2022 Safari9/18/2023592
css.properties.contain-intrinsic-height 📋Edge10/21/2021 Safari9/18/2023697
css.properties.contain-intrinsic-height.none 📋Edge2/3/2022 Safari9/18/2023592
css.properties.contain-intrinsic-inline-size 📋Edge10/21/2021 Safari9/18/2023697
css.properties.contain-intrinsic-inline-size.none 📋Edge2/3/2022 Safari9/18/2023592
css.properties.contain-intrinsic-size 📋Edge5/21/2020 Safari9/18/20231215
css.properties.contain-intrinsic-size.auto_none Edge9/15/2023 Safari9/18/20233
css.properties.contain-intrinsic-size.none 📋Edge2/3/2022 Safari9/18/2023592
css.properties.contain-intrinsic-width 📋Edge10/21/2021 Safari9/18/2023697
css.properties.contain-intrinsic-width.none 📋Edge2/3/2022 Safari9/18/2023592
css.properties.container 📋Edge9/1/2022 Safari9/12/202211
css.properties.container.inline-size 📋Edge9/1/2022 Safari9/12/202211
css.properties.container.none 📋Edge9/1/2022 Safari9/12/202211
css.properties.container.normal 📋Safari9/12/2022 Edge1/12/2023122
css.properties.container.scroll-state 📋Edge9/1/2022 Safari9/12/202211
css.properties.container.size 📋Edge9/1/2022 Safari9/12/202211
css.properties.container-name 📋Edge9/1/2022 Safari9/12/202211
css.properties.container-name.none 📋Edge9/1/2022 Safari9/12/202211
css.properties.container-type 📋Edge9/1/2022 Safari9/12/202211
css.properties.container-type.inline-size 📋Edge9/1/2022 Safari9/12/202211
css.properties.container-type.normal 📋Edge9/1/2022 Safari9/12/202211
css.properties.container-type.size 📋Edge9/1/2022 Safari9/12/202211
css.properties.container-type.weak_containment 📋Edge9/19/2024 Safari3/31/2025193
css.properties.content 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.alt_text Edge1/15/2020 Safari3/5/20241511
css.properties.content.close-quote 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.element_replacement Safari9/30/2015 Edge1/15/20201568
css.properties.content.gradient 📋Safari10/22/2013 Edge7/29/2015645
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 📋Edge5/5/2023 Safari9/18/2023136
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 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.no-open-quote 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.open-quote 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.url 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content-visibility 📋Edge8/27/2020 Safari9/16/20241481
css.properties.content-visibility.auto 📋Edge8/27/2020 Safari9/15/20251845
Safari: Skipped content is not findable via find-in-page.Safari on iOS: Skipped content is not findable via find-in-page.WebView on iOS: Skipped content is not findable via find-in-page.
css.properties.content-visibility.hidden 📋Edge8/27/2020 Safari9/16/20241481
css.properties.content-visibility.is_transitionable 📋Edge9/15/2023 Safari9/16/2024367
css.properties.content-visibility.keyframe_animatable 📋Edge8/21/2023 Safari9/16/2024392
css.properties.content-visibility.visible 📋Edge8/27/2020 Safari9/16/20241481
css.properties.counter-increment 📋Safari10/26/2007 Edge7/29/20152833
css.properties.counter-increment.list-item 📋Edge7/29/2015 Safari9/30/201563
css.properties.counter-increment.none 📋Safari10/26/2007 Edge7/29/20152833
css.properties.counter-reset 📋Safari10/26/2007 Edge7/29/20152833
css.properties.counter-reset.list-item 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari10/26/2007 Edge7/29/20152833
css.properties.counter-set 📋Edge8/27/2020 Safari12/11/20231201
css.properties.counter-set.list-item 📋Edge8/27/2020 Safari12/11/20231201
css.properties.counter-set.none 📋Edge8/27/2020 Safari12/11/20231201
css.properties.cursor 📋Safari2/2/2004 Edge7/29/20154195
Firefox: Starting in Firefox 67, the maximum size allowed for custom cursors is 32x32 pixels due to cursors being misused by certain malicious sites.Internet Explorer: In Internet Explorer 11, when cursor is applied to an element and this element is underneath an open <select> menu and the user hovers over a <select> menu item that's on top of said element, the cursor for said element will be displayed rather than the <select>'s normal cursor. See bug 817822.Safari on iOS: This property is only supported on iPads with an external pointing device.Safari on iOS: Unsupported values use the default pointer as a fallback.WebView on iOS: This property is only supported on iPads with an external pointing device.WebView on iOS: Unsupported values use the default pointer as a fallback.
css.properties.cursor.alias 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.all-scroll 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.auto 📋Safari2/2/2004 Edge7/29/20154195
css.properties.cursor.cell 📋Safari10/26/2007 Edge7/29/20152833
css.properties.cursor.col-resize 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.context-menu 📋Safari10/26/2007 Edge7/29/20152833
Chrome: This cursor is only supported on macOS and Linux.Chrome Android: This cursor is only supported on macOS and Linux.Firefox: This cursor is only supported on macOS and Linux.Quest Browser: This cursor is only supported on macOS and Linux.Opera Android: This cursor is only supported on macOS and Linux.Safari on iOS: If this value is used, the iPad will display the default pointer instead.Samsung Internet: This cursor is only supported on macOS and Linux.WebView Android: This cursor is only supported on macOS and Linux.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.copy 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.crosshair 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.default 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.e-resize 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ew-resize 📋Safari10/26/2007 Edge7/29/20152833
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 Safari9/19/2017413
Chrome: Chrome also continues to support the prefixed versions.Chrome: Chrome 22 added Windows support.Chrome Android: Chrome Android also continues to support the prefixed versions.Chrome Android: Chrome Android 25 added Windows support.Quest Browser: Quest Browser also continues to support the prefixed versions.Quest Browser: Quest Browser 5.0 added Windows support.Opera: Opera also continues to support the prefixed versions.Opera: Opera 22 added Windows support.Opera Android: Opera also continues to support the prefixed versions.Opera Android: Opera 22 added Windows support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView Android: WebView Android also continues to support the prefixed versions.WebView Android: WebView Android 4.4 added Windows support.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.grabbing 📋Safari9/19/2017 Edge1/15/2020848
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 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.move 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.n-resize 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ne-resize 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nesw-resize 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.no-drop 📋Safari10/26/2007 Edge7/29/20152833
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 📋Safari6/7/2010 Edge7/29/20151878
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.not-allowed 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.ns-resize 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nw-resize 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.nwse-resize 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.pointer 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.progress 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.row-resize 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.s-resize 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.se-resize 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.sw-resize 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.text 📋Safari2/2/2004 Edge7/29/20154195
css.properties.cursor.url Safari10/26/2007 Edge7/29/20152833
Firefox: Firefox 4 added macOS support.
css.properties.cursor.url_positioning_syntax Safari10/26/2007 Edge1/15/20204464
Firefox: Firefox 4 added macOS support.Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.vertical-text 📋Safari10/26/2007 Edge7/29/20152833
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.w-resize 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.wait 📋Safari2/2/2004 Edge7/29/20154195
Safari on iOS: If this value is used, the iPad will display the default pointer instead.WebView on iOS: If this value is used, the iPad will display the default pointer instead.
css.properties.cursor.zoom-in 📋Edge7/29/2015 Safari9/30/201563
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 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari3/21/2016 Edge4/5/2017380
css.properties.cx 📋Safari9/30/2015 Edge1/15/20201568
css.properties.cy 📋Safari9/30/2015 Edge1/15/20201568
css.properties.direction 📋Safari6/23/2003 Edge7/29/20154419
css.properties.direction.ltr 📋Safari6/23/2003 Edge7/29/20154419
css.properties.direction.rtl 📋Safari6/23/2003 Edge7/29/20154419
css.properties.direction.vertical_slider_direction Safari5/18/2023 Edge4/18/2024336
Firefox: Only supported for vertical range sliders.Firefox for Android: Only supported for vertical range sliders.Safari: Only supported for vertical range sliders.Safari on iOS: Only supported for vertical range sliders.WebView on iOS: Only supported for vertical range sliders.
css.properties.display 📋Safari6/23/2003 Edge7/29/20154419
css.properties.display.block 📋Safari6/23/2003 Edge7/29/20154419
css.properties.display.contents 📋Safari4/12/2018 Edge1/15/2020643
css.properties.display.flex Edge7/29/2015 Safari9/30/201563
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 Safari9/19/2019 Edge1/15/2020118
css.properties.display.grid Safari3/27/2017 Edge10/17/2017204
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 📋Safari6/23/2003 Edge7/29/20154419
css.properties.display.inline-block Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Until Internet Explorer 8, inline-block is only for natural inline elements.
css.properties.display.inline-flex Edge7/29/2015 Safari9/30/201563
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 Safari3/27/2017 Edge10/17/2017204
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 Safari6/23/2003 Edge7/29/20154419
css.properties.display.is_transitionable 📋Edge9/15/2023 Safari9/16/2024367
css.properties.display.keyframe_animatable 📋Edge8/21/2023 Safari9/16/2024392
css.properties.display.list-item 📋Safari6/23/2003 Edge7/29/20154419
css.properties.display.multi-keyword_values Safari9/20/2021 Edge7/21/2023669
css.properties.display.none 📋Safari6/23/2003 Edge7/29/20154419
Chrome: Chrome 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.Chrome Android: Chrome Android 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.Quest Browser: Quest Browser 5.0 stopped creating layout objects for elements inside an <iframe> with display:none applied.Opera: Opera 52 stopped creating layout objects for elements inside an <iframe> with display:none applied.Opera Android: Opera Android 47 stopped creating layout objects for elements inside an <iframe> with display:none applied.Samsung Internet: Chrome 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.WebView Android: WebView Android 65 stopped creating layout objects for elements inside an <iframe> with display:none applied.
css.properties.display.table Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-caption Safari6/8/2009 Edge4/5/20172858
css.properties.display.table-cell Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-column Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-column-group Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-footer-group Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-header-group Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-row Safari6/23/2003 Edge7/29/20154419
css.properties.display.table-row-group Safari6/23/2003 Edge7/29/20154419
css.properties.dominant-baseline 📋Safari6/8/2009 Edge1/15/20203873
css.properties.dominant-baseline.alphabetic 📋Safari6/8/2009 Edge1/15/20203873
css.properties.dominant-baseline.auto 📋Safari6/8/2009 Edge1/15/20203873
css.properties.dominant-baseline.central 📋Safari6/8/2009 Edge1/15/20203873
css.properties.dominant-baseline.hanging 📋Safari6/8/2009 Edge1/15/20203873
css.properties.dominant-baseline.ideographic 📋Safari6/8/2009 Edge1/15/20203873
css.properties.dominant-baseline.mathematical 📋Safari6/8/2009 Edge1/15/20203873
css.properties.dominant-baseline.middle 📋Safari6/8/2009 Edge1/15/20203873
css.properties.dynamic-range-limit 📋Edge5/1/2025 Safari9/15/2025137
css.properties.dynamic-range-limit.no-limit 📋Edge5/1/2025 Safari9/15/2025137
css.properties.dynamic-range-limit.standard 📋Edge5/1/2025 Safari9/15/2025137
css.properties.empty-cells 📋Safari2/2/2004 Edge7/29/20154195
css.properties.empty-cells.hide 📋Safari2/2/2004 Edge7/29/20154195
css.properties.empty-cells.show 📋Safari2/2/2004 Edge7/29/20154195
css.properties.field-sizing 📋Edge3/22/2024 Safari12/12/2025630
css.properties.field-sizing.content 📋Edge3/22/2024 Safari12/12/2025630
css.properties.field-sizing.fixed 📋Edge3/22/2024 Safari12/12/2025630
css.properties.fill 📋Safari6/8/2009 Edge4/5/20172858
css.properties.fill.none 📋Safari6/8/2009 Edge4/5/20172858
css.properties.fill-opacity 📋Safari6/8/2009 Edge4/5/20172858
css.properties.fill-rule 📋Safari6/8/2009 Edge4/5/20172858
css.properties.fill-rule.evenodd 📋Safari6/8/2009 Edge4/5/20172858
css.properties.fill-rule.nonzero 📋Safari6/8/2009 Edge4/5/20172858
css.properties.filter 📋Edge7/29/2015 Safari3/21/2016236
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 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.brightness 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.contrast 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.drop-shadow 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.grayscale 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.hue-rotate 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.invert 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.none 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.opacity 📋Safari7/25/2012 Edge7/29/20151099
css.properties.filter.saturate 📋Safari7/25/2012 Edge7/29/20151099
Chrome: In Chrome 18 to 19, the saturate() function only takes integers instead of decimal or percentage values. From Chrome 20, this bug is fixed.
css.properties.filter.sepia 📋Safari7/25/2012 Edge7/29/20151099
css.properties.flex 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex.content 📋Safari9/20/2021 Edge9/24/20214
css.properties.flex.fit-content 📋Edge9/24/2021 Safari9/12/2022353
css.properties.flex.max-content 📋Edge9/24/2021 Safari9/12/2022353
css.properties.flex.min-content 📋Edge9/24/2021 Safari9/12/2022353
css.properties.flex.none 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-basis 📋Edge7/29/2015 Safari9/30/201563
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 Edge7/29/2015 Safari9/30/201563
css.properties.flex-basis.content Edge9/24/2021 Safari3/14/2022171
css.properties.flex-basis.fit-content Edge9/24/2021 Safari9/12/2022353
css.properties.flex-basis.max-content Edge9/24/2021 Safari9/12/2022353
css.properties.flex-basis.min-content Edge9/24/2021 Safari9/12/2022353
css.properties.flex-direction 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-direction.column-reverse 📋Safari10/22/2013 Edge7/29/2015645
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 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-direction.row-reverse 📋Safari10/22/2013 Edge7/29/2015645
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 📋Edge7/29/2015 Safari9/30/201563
css.properties.flex-flow.column 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.column-reverse 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.nowrap 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.row 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.row-reverse 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.wrap 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-flow.wrap-reverse 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-grow 📋Edge7/29/2015 Safari9/30/201563
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.
css.properties.flex-shrink 📋Edge7/29/2015 Safari9/30/201563
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 📋Edge7/29/2015 Safari9/30/201563
Internet Explorer: Partial support due to large number of bugs present. See Flexbugs.
css.properties.flex-wrap.nowrap 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-wrap.wrap 📋Safari10/22/2013 Edge7/29/2015645
css.properties.flex-wrap.wrap-reverse 📋Safari10/22/2013 Edge7/29/2015645
css.properties.float 📋Safari6/23/2003 Edge7/29/20154419
css.properties.float.inline-end 📋Safari9/20/2021 Edge10/13/2023753
css.properties.float.inline-start 📋Safari9/20/2021 Edge10/13/2023753
css.properties.float.left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.float.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.float.right 📋Safari6/23/2003 Edge7/29/20154419
css.properties.flood-color 📋Safari7/25/2012 Edge7/29/20151099
css.properties.flood-color.currentColor 📋Safari7/25/2012 Edge7/29/20151099
css.properties.flood-color.transparent 📋Safari7/25/2012 Edge7/29/20151099
css.properties.flood-opacity 📋Safari7/25/2012 Edge7/29/20151099
css.properties.font 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font.caption Safari6/23/2003 Edge7/29/20154419
css.properties.font.font-width_keyword_values Safari9/19/2017 Edge1/15/2020848
css.properties.font.icon Safari6/23/2003 Edge7/29/20154419
css.properties.font.menu Safari6/23/2003 Edge7/29/20154419
css.properties.font.message-box Safari6/23/2003 Edge7/29/20154419
css.properties.font.small-caption Safari6/23/2003 Edge7/29/20154419
css.properties.font.status-bar Safari6/23/2003 Edge7/29/20154419
css.properties.font-family 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Not supported on option elements. See bug 1536148.Safari: Setting font-family: initial behaves like font-family: inherit. See bug 200709.Safari on iOS: Setting font-family: initial behaves like font-family: inherit. See bug 200709.WebView on iOS: Setting font-family: initial behaves like font-family: inherit. See bug 200709.
css.properties.font-family.cursive 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.fangsong 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.fantasy 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.kai 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.khmer-mul 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.math Edge1/12/2023 Safari12/12/20251065
css.properties.font-family.monospace 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.nastaliq 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.sans-serif 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.serif 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-family.system-ui Safari9/19/2017 Edge1/15/2020848
Firefox: Supported on macOS only.
css.properties.font-feature-settings 📋Safari3/21/2016 Edge4/5/2017380
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 📋Safari3/21/2016 Edge4/5/2017380
css.properties.font-kerning 📋Safari9/30/2015 Edge1/15/20201568
css.properties.font-kerning.auto 📋Safari9/30/2015 Edge1/15/20201568
css.properties.font-kerning.none 📋Safari9/30/2015 Edge1/15/20201568
css.properties.font-kerning.normal 📋Safari9/30/2015 Edge1/15/20201568
css.properties.font-optical-sizing 📋Edge4/30/2018 Safari3/24/2020694
css.properties.font-optical-sizing.auto 📋Edge4/30/2018 Safari3/24/2020694
css.properties.font-optical-sizing.none 📋Edge4/30/2018 Safari3/24/2020694
css.properties.font-palette 📋Safari3/14/2022 Edge4/28/202245
css.properties.font-palette.dark 📋Safari3/14/2022 Edge4/28/202245
css.properties.font-palette.light 📋Safari3/14/2022 Edge4/28/202245
css.properties.font-palette.normal 📋Safari3/14/2022 Edge4/28/202245
css.properties.font-size 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-size.rem_values Safari10/22/2013 Edge7/29/2015645
Firefox: Before Firefox 57, animations using em units are not affected by changes to the font-size of the animated element's parent (bug 1254424).Firefox: Before Firefox 57, some language settings' inherited font-size is smaller than expected (bug 1391341).
css.properties.font-size.xxx-large Edge1/15/2020 Safari3/27/20231167
css.properties.font-size-adjust 📋Safari3/27/2023 Edge7/25/2024486
Firefox: Before Firefox 40, font-size-adjust: 0 was incorrectly interpreted as font-size-adjust: none (bug 1144885).Firefox: Only supported on Windows.Firefox for Android: Before Firefox for Android 40, font-size-adjust: 0 was incorrectly interpreted as font-size-adjust: none (bug 1144885).
css.properties.font-size-adjust.from-font 📋Safari9/18/2023 Edge7/25/2024311
css.properties.font-size-adjust.none 📋Safari3/27/2023 Edge7/25/2024486
css.properties.font-size-adjust.two-values Safari9/18/2023 Edge7/25/2024311
css.properties.font-smooth Safari6/8/2009 Edge1/15/20203873
Firefox: Only works on macOS.
css.properties.font-stretch 📋Edge7/29/2015 Safari9/19/2017783
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 Safari9/19/2017783
css.properties.font-stretch.expanded 📋Edge7/29/2015 Safari9/19/2017783
css.properties.font-stretch.extra-condensed 📋Edge7/29/2015 Safari9/19/2017783
css.properties.font-stretch.extra-expanded 📋Edge7/29/2015 Safari9/19/2017783
css.properties.font-stretch.normal 📋Edge7/29/2015 Safari9/19/2017783
css.properties.font-stretch.percentage Safari4/12/2018 Edge10/2/2018173
css.properties.font-stretch.semi-condensed 📋Edge7/29/2015 Safari9/19/2017783
css.properties.font-stretch.semi-expanded 📋Edge7/29/2015 Safari9/19/2017783
css.properties.font-stretch.ultra-condensed 📋Edge7/29/2015 Safari9/19/2017783
css.properties.font-stretch.ultra-expanded 📋Edge7/29/2015 Safari9/19/2017783
css.properties.font-style 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 44, oblique was not distinguished from italic.Firefox for Android: Before Firefox for Android 44, oblique was not distinguished from italic.
css.properties.font-style.italic 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-style.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-style.oblique 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-style.oblique-angle 📋Safari4/12/2018 Edge1/15/2020643
Chrome: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Chrome Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Edge: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Quest Browser: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Samsung Internet: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.
css.properties.font-synthesis 📋Safari9/30/2015 Edge1/6/20222290
css.properties.font-synthesis.none 📋Safari9/30/2015 Edge1/6/20222290
css.properties.font-synthesis.small-caps Safari3/27/2017 Edge1/6/20221746
css.properties.font-synthesis.style Safari3/27/2017 Edge1/6/20221746
css.properties.font-synthesis.weight Safari3/27/2017 Edge1/6/20221746
css.properties.font-synthesis-small-caps 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-small-caps.auto 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-small-caps.none 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-style 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-style.auto 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-style.none 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-weight 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-weight.auto 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-synthesis-weight.none 📋Edge1/6/2022 Safari3/27/2023445
css.properties.font-variant 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Only supports the small-caps and normal keywords.
css.properties.font-variant.css_fonts_shorthand Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant.historical-forms 📋Safari3/21/2016 Edge3/13/20232548
css.properties.font-variant.none 📋Safari9/30/2015 Edge1/15/20201568
css.properties.font-variant.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-variant.sub 📋Safari3/21/2016 Edge2/9/20232516
css.properties.font-variant.super 📋Safari3/21/2016 Edge2/9/20232516
css.properties.font-variant.turkic_is Safari10/16/2014 Edge7/29/2015286
css.properties.font-variant-alternates 📋Safari3/21/2016 Edge3/13/20232548
css.properties.font-variant-alternates.annotation 📋Safari12/13/2022 Edge3/13/202390
css.properties.font-variant-alternates.character_variant 📋Safari12/13/2022 Edge3/13/202390
css.properties.font-variant-alternates.historical-forms 📋Safari3/21/2016 Edge3/13/20232548
css.properties.font-variant-alternates.normal 📋Safari3/21/2016 Edge3/13/20232548
css.properties.font-variant-alternates.ornaments 📋Safari12/13/2022 Edge3/13/202390
css.properties.font-variant-alternates.styleset 📋Safari12/13/2022 Edge3/13/202390
css.properties.font-variant-alternates.stylistic 📋Safari12/13/2022 Edge3/13/202390
css.properties.font-variant-alternates.swash 📋Safari12/13/2022 Edge3/13/202390
css.properties.font-variant-caps 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-caps.all-petite-caps 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-caps.all-small-caps 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-caps.normal 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-caps.petite-caps 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-caps.small-caps 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-caps.titling-caps 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-caps.unicase 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.full-width 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.jis04 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.jis78 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.jis83 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.jis90 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.normal 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.proportional-width 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.ruby 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.simplified 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-east-asian.traditional 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-emoji 📋Safari5/13/2024 Edge11/14/2024185
css.properties.font-variant-ligatures 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-ligatures.common-ligatures 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.contextual 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.discretionary-ligatures 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.historical-ligatures 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.no-common-ligatures 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.no-contextual 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.no-discretionary-ligatures 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.no-historical-ligatures 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.none 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-ligatures.normal 📋Safari10/22/2013 Edge1/15/20202276
css.properties.font-variant-numeric 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.diagonal-fractions 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.lining-nums 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.normal 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.oldstyle-nums 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.ordinal 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.proportional-nums 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.slashed-zero 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.stacked-fractions 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-numeric.tabular-nums 📋Safari3/21/2016 Edge1/15/20201395
css.properties.font-variant-position 📋Safari3/21/2016 Edge9/15/20232734
css.properties.font-variant-position.normal 📋Safari3/21/2016 Edge9/15/20232734
css.properties.font-variant-position.sub 📋Safari3/21/2016 Edge9/15/20232734
Chrome: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Chrome Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Edge: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Opera: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Opera Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).Safari: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).Safari on iOS: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).Samsung Internet: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).WebView Android: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 352218916).WebView on iOS: If the font does not have subscript glyphs, then substitute characters are not synthesized (see bug 151471).
css.properties.font-variant-position.super 📋Safari3/21/2016 Edge9/15/20232734
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 📋Safari9/19/2017 Edge4/30/2018223
Safari: Requires macOS 10.13 High Sierra or later.Safari on iOS: Requires iOS 11 or later.WebView on iOS: Requires iOS 11 or later.
css.properties.font-variation-settings.normal 📋Safari9/19/2017 Edge4/30/2018223
css.properties.font-weight 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.bold 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.bolder 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.lighter 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-weight.number Safari9/19/2017 Edge4/30/2018223
css.properties.gap 📋Safari3/27/2017 Edge10/17/2017204
css.properties.gap.flex_context 📋Edge7/16/2020 Safari4/26/2021284
css.properties.gap.grid_context 📋Edge10/17/2017 Safari9/17/2018335
css.properties.gap.grid_context.calc_values Edge10/17/2017 Safari3/25/2019524
css.properties.gap.grid_context.percentage_values Safari9/19/2017 Edge10/17/201728
css.properties.gap.multicol_context 📋Edge10/17/2017 Safari4/26/20211287
css.properties.gap.normal 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid 📋Safari3/27/2017 Edge10/17/2017204
Samsung Internet: This was added early so is out of sync with the equivalent Chromium version.
css.properties.grid.none 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-area 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-area.auto 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-auto-columns 📋Safari3/27/2017 Edge10/17/2017204
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 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-auto-columns.max-content 📋Safari9/19/2017 Edge10/17/201728
css.properties.grid-auto-columns.min-content 📋Safari9/19/2017 Edge10/17/201728
css.properties.grid-auto-flow 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-auto-flow.column 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-auto-flow.dense 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-auto-flow.row 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-auto-rows 📋Safari3/27/2017 Edge10/17/2017204
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 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-auto-rows.max-content 📋Safari9/19/2017 Edge10/17/201728
css.properties.grid-auto-rows.min-content 📋Safari9/19/2017 Edge10/17/201728
css.properties.grid-column 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-column.auto 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-column-end 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-column-end.auto 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-column-start 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-column-start.auto 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-row 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-row.auto 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-row-end 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-row-end.auto 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-row-start 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-row-start.auto 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template.none 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-areas 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template-areas.none 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-columns 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template-columns.animation Safari9/12/2022 Edge10/27/202245
css.properties.grid-template-columns.auto 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-columns.fit-content 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template-columns.max-content 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-columns.min-content 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-columns.minmax 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template-columns.none 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-columns.repeat 📋Safari3/27/2017 Edge10/17/2017204
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 📋Safari9/12/2022 Edge9/15/2023368
css.properties.grid-template-rows 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template-rows.animation Safari9/12/2022 Edge10/27/202245
css.properties.grid-template-rows.auto 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-rows.fit-content 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template-rows.max-content 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-rows.min-content 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-rows.minmax 📋Safari3/27/2017 Edge10/17/2017204
css.properties.grid-template-rows.none 📋Safari3/27/2017 Edge1/15/20201024
css.properties.grid-template-rows.repeat 📋Safari3/27/2017 Edge10/17/2017204
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 📋Safari9/12/2022 Edge9/15/2023368
css.properties.height 📋Safari6/23/2003 Edge7/29/20154419
css.properties.height.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.height.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.height.fit-content 📋Safari9/19/2017 Edge1/15/2020848
css.properties.height.max-content 📋Safari9/19/2017 Edge1/15/2020848
css.properties.height.min-content 📋Safari9/19/2017 Edge1/15/2020848
css.properties.height.stretch 📋Safari9/30/2015 Edge6/26/20253557
css.properties.hyphenate-character 📋Edge10/3/2022 Safari9/18/2023350
css.properties.hyphenate-character.auto 📋Safari7/20/2011 Edge1/15/20203101
css.properties.hyphens 📋Edge1/15/2020 Safari9/18/20231342
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 Safari7/20/2011 Edge1/21/20213473
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.language_croatian Safari3/21/2016 Edge11/19/20201704
css.properties.hyphens.language_czech Safari3/21/2016 Edge4/6/20232572
css.properties.hyphens.language_danish Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_dutch Safari7/20/2011 Edge4/6/20234278
css.properties.hyphens.language_english Safari7/20/2011 Edge7/29/20151470
Firefox: For English, Firefox uses an en-US dictionaryFirefox for Android: For English, Firefox for Android uses an en-US dictionarySafari: For English, Safari uses different en-GB and en-US dictionaries.Safari on iOS: For English, Safari on iOS uses different en-GB and en-US dictionaries.WebView on iOS: For English, WebView on iOS uses different en-GB and en-US dictionaries.
css.properties.hyphens.language_french Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_german_reformed_orthography Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_hungarian Safari3/21/2016 Edge11/19/20201704
css.properties.hyphens.language_italian Safari7/20/2011 Edge4/6/20234278
css.properties.hyphens.language_norwegian_no Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_portuguese Safari3/21/2016 Edge11/19/20201704
css.properties.hyphens.language_russian Safari7/20/2011 Edge4/6/20234278
css.properties.hyphens.language_spanish Safari7/20/2011 Edge11/19/20203410
css.properties.hyphens.language_swedish Safari7/20/2011 Edge4/6/20234278
css.properties.hyphens.language_ukrainian Safari3/21/2016 Edge4/6/20232572
css.properties.hyphens.manual Safari7/20/2011 Edge1/21/20213473
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.hyphens.none Safari7/20/2011 Edge1/21/20213473
Chrome: Only supported on macOS.Edge: Only supported on macOS.Opera: Only supported on macOS.
css.properties.image-orientation 📋Safari3/24/2020 Edge4/13/202020
css.properties.image-orientation.from-image 📋Safari3/24/2020 Edge4/13/202020
css.properties.image-orientation.none 📋Safari3/24/2020 Edge4/13/202020
css.properties.image-rendering 📋Safari7/25/2012 Edge1/15/20202730
css.properties.image-rendering.auto 📋Safari7/25/2012 Edge1/15/20202730
css.properties.image-rendering.crisp-edges 📋Safari10/22/2013 Edge1/15/20202276
css.properties.image-rendering.pixelated 📋Safari9/20/2016 Edge1/15/20201212
css.properties.initial-letter 📋Safari9/30/2015 Edge2/9/20232689
Safari: See bug 229090 for the unprefixed property.Safari on iOS: See bug 229090 for the unprefixed property.Safari on iOS: Does not support decimal values. See bug 296785.WebView on iOS: See bug 229090 for the unprefixed property.WebView on iOS: Does not support decimal values. See bug 296785.
css.properties.initial-letter.normal 📋Safari9/30/2015 Edge2/9/20232689
css.properties.inline-size 📋Safari3/25/2019 Edge1/15/2020296
css.properties.inline-size.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.inline-size.auto 📋Safari7/20/2011 Edge1/15/20203101
css.properties.inline-size.fit-content 📋Safari3/25/2019 Edge1/15/2020296
css.properties.inline-size.max-content Safari3/25/2019 Edge1/15/2020296
css.properties.inline-size.min-content Safari3/25/2019 Edge1/15/2020296
css.properties.inset 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.inset.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.inset.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-block 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-block.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.inset-block.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.inset-block.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-block-end 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-block-end.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.inset-block-end.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.inset-block-end.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-block-start 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-block-start.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.inset-block-start.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.inset-block-start.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-inline 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-inline.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.inset-inline.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.inset-inline.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-inline-end 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-inline-end.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.inset-inline-end.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.inset-inline-end.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-inline-start 📋Edge11/19/2020 Safari4/26/2021158
css.properties.inset-inline-start.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.inset-inline-start.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.inset-inline-start.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.isolation 📋Safari10/16/2014 Edge1/15/20201917
css.properties.isolation.auto 📋Safari10/16/2014 Edge1/15/20201917
css.properties.isolation.isolate 📋Safari10/16/2014 Edge1/15/20201917
css.properties.justify-content 📋Edge7/29/2015 Safari9/30/201563
css.properties.justify-content.flex_context 📋Safari10/22/2013 Edge7/29/2015645
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 Safari9/30/2015 Edge9/2/20212164
Internet Explorer: This value is recognized, but has no effect.Opera Android: This value is recognized, but has no effect.
css.properties.justify-content.flex_context.safe_unsafe Edge7/21/2023 Safari7/29/2024374
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 Safari9/19/2017 Edge1/15/2020848
css.properties.justify-content.flex_context.start_end Edge9/2/2021 Safari3/14/2022193
css.properties.justify-content.flex_context.stretch Safari9/30/2015 Edge1/15/20201568
css.properties.justify-content.grid_context 📋Safari3/27/2017 Edge10/17/2017204
css.properties.justify-content.left Safari10/22/2013 Edge1/15/20202276
css.properties.justify-content.normal Safari10/22/2013 Edge1/15/20202276
css.properties.justify-content.right Safari10/22/2013 Edge1/15/20202276
css.properties.justify-items 📋Edge7/29/2015 Safari9/30/201563
css.properties.justify-items.anchor-center 📋Edge5/17/2024 Safari9/15/2025486
css.properties.justify-items.center Safari9/30/2015 Edge1/15/20201568
css.properties.justify-items.flex_context 📋Edge7/29/2015 Safari9/30/201563
css.properties.justify-items.grid_context 📋Safari3/27/2017 Edge10/17/2017204
css.properties.justify-items.left Safari9/30/2015 Edge1/15/20201568
css.properties.justify-items.legacy 📋Safari9/30/2015 Edge1/15/20201568
css.properties.justify-items.right Safari9/30/2015 Edge1/15/20201568
css.properties.justify-self 📋Safari3/27/2017 Edge10/17/2017204
css.properties.justify-self.anchor-center 📋Edge5/17/2024 Safari9/15/2025486
css.properties.justify-self.auto Safari3/27/2017 Edge1/15/20201024
css.properties.justify-self.grid_context 📋Safari3/27/2017 Edge10/17/2017204
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 Safari3/27/2017 Edge1/15/20201024
css.properties.justify-self.normal Safari3/27/2017 Edge1/15/20201024
css.properties.justify-self.right Safari3/27/2017 Edge1/15/20201024
css.properties.justify-self.stretch Safari3/27/2017 Edge1/15/20201024
css.properties.left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.left.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.left.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.left.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.letter-spacing 📋Safari6/23/2003 Edge7/29/20154419
css.properties.letter-spacing.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.letter-spacing.svg_elements Safari7/20/2011 Edge7/29/20151470
css.properties.lighting-color 📋Safari7/25/2012 Edge7/29/20151099
css.properties.lighting-color.currentColor 📋Safari7/25/2012 Edge7/29/20151099
css.properties.lighting-color.transparent 📋Safari7/25/2012 Edge7/29/20151099
css.properties.line-break 📋Edge8/2/2016 Safari9/19/2017413
css.properties.line-break.anywhere 📋Safari9/19/2019 Edge5/21/2020245
css.properties.line-break.auto 📋Safari10/22/2013 Edge1/15/20202276
css.properties.line-break.loose 📋Safari10/16/2014 Edge1/15/20201917
css.properties.line-break.normal 📋Safari4/29/2005 Edge1/15/20205374
css.properties.line-break.strict 📋Safari10/16/2014 Edge1/15/20201917
css.properties.line-clamp 📋Safari6/7/2010 Edge4/30/20182884
Safari: Accidental exposure.Safari on iOS: Accidental exposure.WebView on iOS: Accidental exposure.
css.properties.line-height 📋Safari6/23/2003 Edge7/29/20154419
css.properties.line-height.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style.inside 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style.outside 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-image 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 86, this property did not accept an <image> type, and required the URL of an image.Firefox for Android: Before Firefox for Android 86, this property did not accept an <image> type, and required the URL of an image.
css.properties.list-style-image.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-position 📋Safari6/23/2003 Edge7/29/20154419
Safari: In Safari, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.Safari on iOS: In Safari on iOS, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.WebView on iOS: In WebView on iOS, if a block element is the first child of a list element declared as list-style-position: inside, then the marker box is placed on the same line as the block element.
css.properties.list-style-position.inside 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-position.outside 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.afar Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.amharic Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.amharic-abegede Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.arabic-indic 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.armenian 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.asterisks Safari7/20/2011 Edge5/27/20213599
css.properties.list-style-type.bengali 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.binary Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.cambodian 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.circle 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.cjk-decimal 📋Edge5/27/2021 Safari9/20/2021116
css.properties.list-style-type.cjk-earthly-branch 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.cjk-heavenly-stem 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.cjk-ideographic 📋Safari6/7/2010 Edge1/15/20203509
Opera: Until version 15, only decimal numbers display.Opera Android: Until version 15, only decimal numbers display.
css.properties.list-style-type.decimal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.decimal-leading-zero 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.devanagari 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.disc 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.disclosure-closed 📋Edge3/4/2021 Safari9/20/2021200
css.properties.list-style-type.disclosure-open 📋Edge3/4/2021 Safari9/20/2021200
css.properties.list-style-type.ethiopic Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-abegede Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-abegede-am-et Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-abegede-gez Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-abegede-ti-er Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-abegede-ti-et Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-halehame Edge1/15/2020 Safari9/18/20231342
css.properties.list-style-type.ethiopic-halehame-aa-er Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-halehame-aa-et Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-halehame-am Edge1/15/2020 Safari9/18/20231342
css.properties.list-style-type.ethiopic-halehame-am-et Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-halehame-gez Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-halehame-om-et Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-halehame-sid-et Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-halehame-so-et Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-halehame-ti-er Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.ethiopic-halehame-ti-et Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.ethiopic-halehame-tig Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.ethiopic-numeric 📋Edge5/27/2021 Safari9/20/2021116
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 Safari7/20/2011 Edge5/27/20213599
css.properties.list-style-type.georgian 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.gujarati 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.gurmukhi 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.hangul Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.hangul-consonant Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.hebrew 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.hiragana 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.hiragana-iroha 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.japanese-formal 📋Edge5/27/2021 Safari9/20/2021116
css.properties.list-style-type.japanese-informal 📋Edge5/27/2021 Safari9/20/2021116
css.properties.list-style-type.kannada 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.katakana 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.katakana-iroha 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.khmer 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.korean-hangul-formal 📋Edge1/15/2020 Safari9/20/2021614
css.properties.list-style-type.korean-hanja-formal 📋Edge1/15/2020 Safari9/20/2021614
css.properties.list-style-type.korean-hanja-informal 📋Edge1/15/2020 Safari9/20/2021614
css.properties.list-style-type.lao 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.lower-alpha 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.lower-armenian 📋Safari7/20/2011 Edge1/15/20203101
css.properties.list-style-type.lower-greek 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.lower-hexadecimal Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.lower-latin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.lower-norwegian Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.lower-roman 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.malayalam 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.mongolian 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.myanmar 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.octal Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.oriya 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.oromo Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.persian 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.sidama Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.simp-chinese-formal 📋Edge1/15/2020 Safari9/20/2021614
css.properties.list-style-type.simp-chinese-informal 📋Edge1/15/2020 Safari9/20/2021614
css.properties.list-style-type.somali Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.square 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.string Edge1/15/2020 Safari4/26/2021467
css.properties.list-style-type.tamil 📋Edge5/27/2021 Safari9/20/2021116
css.properties.list-style-type.telugu 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.thai 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.tibetan 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.tigre Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.tigrinya-er Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.tigrinya-er-abegede Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.tigrinya-et Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.tigrinya-et-abegede Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.trad-chinese-formal 📋Edge1/15/2020 Safari9/20/2021614
css.properties.list-style-type.trad-chinese-informal 📋Edge1/15/2020 Safari9/20/2021614
css.properties.list-style-type.upper-alpha 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.upper-armenian 📋Safari7/20/2011 Edge1/15/20203101
css.properties.list-style-type.upper-greek Safari6/23/2003 Edge5/27/20216548
css.properties.list-style-type.upper-hexadecimal Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.upper-latin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.upper-norwegian Safari6/7/2010 Edge5/27/20214007
css.properties.list-style-type.upper-roman 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.urdu Safari6/7/2010 Edge1/15/20203509
css.properties.margin 📋Safari6/23/2003 Edge7/29/20154419
css.properties.margin.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin.auto Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-block 📋Edge11/19/2020 Safari4/26/2021158
css.properties.margin-block.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-block.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.margin-block-end 📋Safari3/25/2019 Edge1/15/2020296
css.properties.margin-block-end.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-block-end.auto 📋Safari3/25/2019 Edge1/15/2020296
css.properties.margin-block-start 📋Safari3/25/2019 Edge1/15/2020296
css.properties.margin-block-start.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-block-start.auto 📋Safari3/25/2019 Edge1/15/2020296
css.properties.margin-bottom 📋Safari6/23/2003 Edge7/29/20154419
css.properties.margin-bottom.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-bottom.auto 📋Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-inline 📋Edge11/19/2020 Safari4/26/2021158
css.properties.margin-inline.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-inline.auto 📋Edge11/19/2020 Safari4/26/2021158
css.properties.margin-inline-end 📋Safari3/25/2019 Edge1/15/2020296
css.properties.margin-inline-end.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-inline-end.auto 📋Safari3/25/2019 Edge1/15/2020296
css.properties.margin-inline-start 📋Safari3/25/2019 Edge1/15/2020296
css.properties.margin-inline-start.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-inline-start.auto 📋Safari3/25/2019 Edge1/15/2020296
css.properties.margin-left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.margin-left.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-left.auto Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-right 📋Safari6/23/2003 Edge7/29/20154419
css.properties.margin-right.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-right.auto Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.margin-top 📋Safari6/23/2003 Edge7/29/20154419
css.properties.margin-top.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.margin-top.auto Safari6/23/2003 Edge7/29/20154419
Edge: The auto value is not supported in quirks mode.Internet Explorer: The auto value is not supported in quirks mode.
css.properties.marker 📋Safari6/8/2009 Edge4/5/20172858
css.properties.marker.none 📋Safari6/8/2009 Edge4/5/20172858
css.properties.marker-end 📋Safari6/8/2009 Edge4/5/20172858
css.properties.marker-end.none 📋Safari6/8/2009 Edge4/5/20172858
css.properties.marker-mid 📋Safari6/8/2009 Edge4/5/20172858
css.properties.marker-mid.none 📋Safari6/8/2009 Edge4/5/20172858
css.properties.marker-start 📋Safari6/8/2009 Edge4/5/20172858
css.properties.marker-start.none 📋Safari6/8/2009 Edge4/5/20172858
css.properties.mask 📋Safari3/14/2022 Edge12/7/2023633
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 📋Edge1/15/2020 Safari12/11/20231426
css.properties.mask-border-outset 📋Edge1/15/2020 Safari12/11/20231426
css.properties.mask-border-repeat 📋Edge1/15/2020 Safari12/11/20231426
css.properties.mask-border-slice 📋Edge1/15/2020 Safari12/11/20231426
css.properties.mask-border-source 📋Edge1/15/2020 Safari12/11/20231426
css.properties.mask-border-width 📋Edge1/15/2020 Safari12/11/20231426
css.properties.mask-clip 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-clip.border Safari6/8/2009 Edge1/15/20203873
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 Safari6/8/2009 Edge1/15/20203873
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 Safari6/8/2009 Edge1/15/20203873
Chrome: Only works when using -webkit-mask-clip.Chrome Android: Only works when using -webkit-mask-clip.Edge: Only works when using -webkit-mask-clip.Quest Browser: Only works when using -webkit-mask-clip.Opera: Only works when using -webkit-mask-clip.Opera Android: Only works when using -webkit-mask-clip.Samsung Internet: Only works when using -webkit-mask-clip.
css.properties.mask-clip.text Safari6/8/2009 Edge1/15/20203873
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-composite 📋Safari3/14/2022 Edge12/7/2023633
Chrome: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Chrome Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Edge: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Opera: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Opera Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Safari: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Safari on iOS: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.Samsung Internet: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.WebView Android: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.WebView on iOS: See also -webkit-mask-composite for a similar non-standard property that uses different keywords.
css.properties.mask-composite.add 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-composite.exclude 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-composite.intersect 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-composite.subtract 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-image 📋Safari3/14/2022 Edge12/7/2023633
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 Safari6/8/2009 Edge10/2/20183403
css.properties.mask-image.svg_masks Safari6/8/2009 Edge10/2/20183403
css.properties.mask-mode 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-mode.alpha 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-mode.luminance 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-mode.match-source 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-origin 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-origin.border Edge1/15/2020 Safari3/14/2022789
css.properties.mask-origin.content Edge1/15/2020 Safari3/14/2022789
css.properties.mask-origin.padding Edge1/15/2020 Safari3/14/2022789
css.properties.mask-position 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-repeat 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-size 📋Safari3/14/2022 Edge12/7/2023633
css.properties.mask-type 📋Safari10/22/2013 Edge1/15/20202276
css.properties.mask-type.alpha 📋Safari10/22/2013 Edge1/15/20202276
css.properties.mask-type.luminance 📋Safari10/22/2013 Edge1/15/20202276
css.properties.math-shift 📋Edge1/12/2023 Safari12/12/20251065
css.properties.math-shift.compact 📋Edge1/12/2023 Safari12/12/20251065
css.properties.math-shift.normal 📋Edge1/12/2023 Safari12/12/20251065
css.properties.math-style 📋Safari4/26/2021 Edge1/12/2023626
css.properties.math-style.compact 📋Safari4/26/2021 Edge1/12/2023626
css.properties.math-style.normal 📋Safari4/26/2021 Edge1/12/2023626
css.properties.max-block-size 📋Safari3/25/2019 Edge1/15/2020296
css.properties.max-block-size.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.max-block-size.fit-content Safari3/25/2019 Edge1/15/2020296
css.properties.max-block-size.max-content Safari3/25/2019 Edge1/15/2020296
css.properties.max-block-size.min-content Safari3/25/2019 Edge1/15/2020296
css.properties.max-block-size.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.max-height 📋Safari4/15/2005 Edge7/29/20153757
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 📋Edge5/17/2024 Safari9/15/2025486
css.properties.max-height.fit-content 📋Safari9/19/2017 Edge1/15/2020848
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 📋Safari9/19/2017 Edge1/15/2020848
css.properties.max-height.min-content 📋Safari9/19/2017 Edge1/15/2020848
css.properties.max-height.none 📋Safari4/15/2005 Edge7/29/20153757
css.properties.max-height.stretch 📋Safari9/30/2015 Edge6/26/20253557
css.properties.max-inline-size 📋Safari3/25/2019 Edge1/15/2020296
css.properties.max-inline-size.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.max-inline-size.fit-content Safari3/25/2019 Edge1/15/2020296
css.properties.max-inline-size.max-content Safari3/25/2019 Edge1/15/2020296
css.properties.max-inline-size.min-content Safari3/25/2019 Edge1/15/2020296
css.properties.max-inline-size.none 📋Safari3/25/2019 Edge1/15/2020296
css.properties.max-width 📋Safari6/23/2003 Edge7/29/20154419
Firefox: CSS 2.1 leaves the behavior of max-width with table undefined. Firefox supports applying max-width to table elements.Firefox for Android: CSS 2.1 leaves the behavior of max-width with table undefined. Firefox for Android supports applying max-width to table elements.Opera: CSS 2.1 leaves the behavior of max-width with table undefined. Opera supports applying max-width to table elements.
css.properties.max-width.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.max-width.fit-content 📋Safari9/19/2017 Edge1/15/2020848
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 📋Safari9/19/2017 Edge1/15/2020848
css.properties.max-width.min-content 📋Safari9/19/2017 Edge1/15/2020848
css.properties.max-width.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.max-width.stretch 📋Safari10/22/2013 Edge6/26/20254265
css.properties.min-block-size 📋Safari3/25/2019 Edge1/15/2020296
css.properties.min-block-size.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.min-block-size.auto 📋Safari3/25/2019 Edge1/15/2020296
css.properties.min-block-size.fit-content Safari3/25/2019 Edge1/15/2020296
css.properties.min-block-size.max-content Safari3/25/2019 Edge1/15/2020296
css.properties.min-block-size.min-content Safari3/25/2019 Edge1/15/2020296
css.properties.min-height 📋Safari4/15/2005 Edge7/29/20153757
Firefox: CSS 2.1 leaves the behavior of min-height with table undefined. Firefox supports applying min-height to table elements.Firefox for Android: CSS 2.1 leaves the behavior of min-height with table undefined. Firefox for Android supports applying min-height to table elements.Internet Explorer: In Internet Explorer 10 and 11, a min-height declaration on a column-direction flex container doesn't apply to the container's flex items. See Flexbug #3 for more info.Opera: CSS 2.1 leaves the behavior of min-height with table undefined. Opera supports applying min-height to table elements.
css.properties.min-height.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.min-height.auto Safari10/22/2013 Edge7/29/2015645
Firefox: Firefox 18 and later used auto as the initial value for min-height.Firefox for Android: Firefox for Android 18 and later used auto as the initial value for min-height.
css.properties.min-height.fit-content Safari9/19/2017 Edge1/15/2020848
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 Safari9/19/2017 Edge1/15/2020848
css.properties.min-height.min-content Safari9/19/2017 Edge1/15/2020848
css.properties.min-height.stretch Safari9/30/2015 Edge6/26/20253557
css.properties.min-inline-size 📋Safari3/25/2019 Edge1/15/2020296
css.properties.min-inline-size.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.min-inline-size.auto 📋Safari3/25/2019 Edge1/15/2020296
css.properties.min-inline-size.fit-content Safari3/25/2019 Edge1/15/2020296
css.properties.min-inline-size.max-content Safari3/25/2019 Edge1/15/2020296
css.properties.min-inline-size.min-content Safari3/25/2019 Edge1/15/2020296
css.properties.min-width 📋Safari6/23/2003 Edge7/29/20154419
Firefox: CSS 2.1 leaves the behavior of min-width with table undefined. Firefox supports applying min-width to table elements.Firefox for Android: CSS 2.1 leaves the behavior of min-width with table undefined. Firefox for Android supports applying min-width to table elements.Opera: CSS 2.1 leaves the behavior of min-width with table undefined. Opera supports applying min-width to table elements.
css.properties.min-width.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.min-width.auto Safari10/22/2013 Edge7/29/2015645
Chrome: Chrome uses auto as the initial value for min-width.Chrome Android: Chrome Android uses auto as the initial value for min-width.Edge: Edge uses auto as the initial value for min-width.Firefox: Firefox 18 and later (until the value was removed), used auto as the initial value for min-width.Firefox for Android: Firefox for Android 18 and later (until the value was removed), used auto as the initial value for min-width.Quest Browser: Quest Browser uses auto as the initial value for min-width.Opera: Opera uses auto as the initial value for min-width.Opera Android: Opera Android uses auto as the initial value for min-width.Samsung Internet: Samsung Internet uses auto as the initial value for min-width.WebView Android: WebView Android uses auto as the initial value for min-width.
css.properties.min-width.fit-content Safari9/19/2017 Edge1/15/2020848
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 Safari9/19/2017 Edge1/15/2020848
css.properties.min-width.min-content Safari9/19/2017 Edge1/15/2020848
css.properties.min-width.stretch Safari10/22/2013 Edge6/26/20254265
css.properties.mix-blend-mode 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.color 📋Safari9/20/2016 Edge1/15/20201212
css.properties.mix-blend-mode.color-burn 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.color-dodge 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.darken 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.difference 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.exclusion 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.hard-light 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.hue 📋Safari9/20/2016 Edge1/15/20201212
css.properties.mix-blend-mode.lighten 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.luminosity 📋Safari9/20/2016 Edge1/15/20201212
css.properties.mix-blend-mode.multiply 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.normal 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.overlay 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.plus-lighter 📋Safari3/21/2016 Edge4/1/20222202
css.properties.mix-blend-mode.saturation 📋Safari9/20/2016 Edge1/15/20201212
css.properties.mix-blend-mode.screen 📋Safari10/16/2014 Edge1/15/20201917
css.properties.mix-blend-mode.soft-light 📋Safari10/16/2014 Edge1/15/20201917
css.properties.object-fit 📋Safari9/20/2016 Edge1/15/20201212
Edge: Only supported for <img> elements.
css.properties.object-fit.contain 📋Safari9/20/2016 Edge1/15/20201212
css.properties.object-fit.cover 📋Safari9/20/2016 Edge1/15/20201212
css.properties.object-fit.fill 📋Safari9/20/2016 Edge1/15/20201212
css.properties.object-fit.none 📋Safari9/20/2016 Edge1/15/20201212
css.properties.object-fit.scale-down 📋Safari9/20/2016 Edge1/15/20201212
css.properties.object-position 📋Safari9/20/2016 Edge1/15/20201212
Edge: Only supported for <img> elements.
css.properties.object-position.bottom 📋Safari9/20/2016 Edge10/17/2017392
css.properties.object-position.center 📋Safari9/20/2016 Edge10/17/2017392
css.properties.object-position.left 📋Safari9/20/2016 Edge10/17/2017392
css.properties.object-position.right 📋Safari9/20/2016 Edge10/17/2017392
css.properties.object-position.top 📋Safari9/20/2016 Edge10/17/2017392
css.properties.offset 📋Edge1/15/2020 Safari9/12/2022971
css.properties.offset.auto 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.border-box 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.bottom 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.center 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.content-box 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.fill-box 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.left 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.none 📋Edge1/15/2020 Safari9/12/2022971
css.properties.offset.normal 📋Edge8/21/2023 Safari9/18/202328
css.properties.offset.padding-box 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.right 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.stroke-box 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.top 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset.view-box 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-anchor 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-anchor.auto 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-anchor.bottom 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-anchor.center 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-anchor.left 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-anchor.right 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-anchor.top 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-distance 📋Edge1/15/2020 Safari9/12/2022971
css.properties.offset-path 📋Edge1/15/2020 Safari3/14/2022789
Samsung Internet: path() is the only value type supported.
css.properties.offset-path.basic_shape 📋Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.border-box 📋Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.content-box 📋Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.fill-box 📋Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.none 📋Edge2/7/2020 Safari9/16/20241683
css.properties.offset-path.padding-box 📋Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.path Edge1/15/2020 Safari9/12/2022971
css.properties.offset-path.ray 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-path.stroke-box 📋Edge8/21/2023 Safari9/16/2024392
css.properties.offset-path.url 📋Edge8/21/2023 Safari9/18/202328
css.properties.offset-path.view-box 📋Edge8/21/2023 Safari9/16/2024392
css.properties.offset-position 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-position.auto 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-position.bottom 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-position.center 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-position.left 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-position.normal 📋Edge8/21/2023 Safari12/11/2023112
css.properties.offset-position.right 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-position.top 📋Safari9/12/2022 Edge8/21/2023343
css.properties.offset-rotate 📋Edge1/15/2020 Safari9/12/2022971
css.properties.offset-rotate.auto 📋Edge1/15/2020 Safari9/12/2022971
css.properties.offset-rotate.reverse 📋Edge1/15/2020 Safari9/12/2022971
css.properties.opacity 📋Safari4/29/2005 Edge7/29/20153743
css.properties.opacity.percentages Edge1/15/2020 Safari3/24/202069
css.properties.order 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari4/15/2005 Edge7/29/20153757
css.properties.outline 📋Edge9/24/2021 Safari3/27/2023549
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 📋Safari2/2/2004 Edge1/15/20205826
css.properties.outline.currentColor 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.dashed 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.dotted 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.double 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.groove 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.inset 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.medium 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.none 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.outset 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.ridge 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.solid 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.thick 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.thin 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline.transparent 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-color 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-color.transparent 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-offset 📋Safari2/2/2004 Edge4/5/20174811
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.outline-style 📋Safari2/2/2004 Edge7/29/20154195
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.outline-style.auto 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.dashed 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.dotted 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.double 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.groove 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.inset 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.none 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.outset 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.ridge 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-style.solid 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-width 📋Safari2/2/2004 Edge7/29/20154195
Firefox: Before Firefox 88, an outline does not follow the shape of border-radius.Firefox for Android: Before Firefox for Android 88, an outline does not follow the shape of border-radius.
css.properties.outline-width.medium 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-width.thick 📋Safari2/2/2004 Edge7/29/20154195
css.properties.outline-width.thin 📋Safari2/2/2004 Edge7/29/20154195
css.properties.overflow 📋Safari6/23/2003 Edge7/29/20154419
Firefox: After Firefox 3.6, the overflow property is correctly applied to table group elements (<thead>, <tbody>, <tfoot>).Internet Explorer: From version 4 to 6, Internet Explorer enlarges an element with overflow: visible (default value) to fit the content inside it. height and width behave like min-height and min-width, respectively.
css.properties.overflow.auto 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow.clip 📋Edge4/15/2021 Safari9/12/2022515
css.properties.overflow.hidden 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow.multiple_keywords Edge1/15/2020 Safari3/24/202069
css.properties.overflow.scroll 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow.visible 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-block 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-block.auto 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-block.clip 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-block.hidden 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-block.scroll 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-block.visible 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-inline 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-inline.auto 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-inline.clip 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-inline.hidden 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-inline.scroll 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-inline.visible 📋Edge4/4/2025 Safari9/15/2025164
css.properties.overflow-wrap 📋Safari10/22/2013 Edge10/2/20181806
css.properties.overflow-wrap.anywhere 📋Edge2/7/2020 Safari3/14/2022766
css.properties.overflow-wrap.break-word 📋Safari6/23/2003 Edge7/29/20154419
css.properties.overflow-wrap.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.overflow-x 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-x.auto 📋Safari10/26/2007 Edge7/29/20152833
Safari: Before Safari 12.1, overlay only had an effect on legacy scrollbars on macOS. Since Safari 12.1, it is parsed as auto.Safari on iOS: Before Safari on iOS 12.1, overlay only had an effect on legacy scrollbars on macOS. Since Safari on iOS 12.1, it is parsed as auto.WebView on iOS: Before WebView on iOS 12.1, overlay only had an effect on legacy scrollbars on macOS. Since WebView on iOS 12.1, it is parsed as auto.
css.properties.overflow-x.clip 📋Edge4/15/2021 Safari9/12/2022515
css.properties.overflow-x.hidden 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-x.scroll 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-x.visible 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-y 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-y.auto 📋Safari10/26/2007 Edge7/29/20152833
Safari: Before Safari 12.1, overlay only had an effect on legacy scrollbars on macOS. Since Safari 12.1, it is parsed as auto.Safari on iOS: Before Safari on iOS 12.1, overlay only had an effect on legacy scrollbars on macOS. Since Safari on iOS 12.1, it is parsed as auto.WebView on iOS: Before WebView on iOS 12.1, overlay only had an effect on legacy scrollbars on macOS. Since WebView on iOS 12.1, it is parsed as auto.
css.properties.overflow-y.clip 📋Edge4/15/2021 Safari9/12/2022515
css.properties.overflow-y.hidden 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-y.scroll 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overflow-y.visible 📋Safari10/26/2007 Edge7/29/20152833
css.properties.overscroll-behavior 📋Edge10/2/2018 Safari9/12/20221441
css.properties.overscroll-behavior.auto 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior.contain 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior.none 📋Edge1/15/2020 Safari9/12/2022971
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-block 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-block.auto 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-block.contain 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-block.none 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-inline 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-inline.auto 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-inline.contain 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-inline.none 📋Edge1/15/2020 Safari9/12/2022971
css.properties.overscroll-behavior-x 📋Edge10/2/2018 Safari9/12/20221441
css.properties.overscroll-behavior-x.auto 📋Edge10/2/2018 Safari9/12/20221441
css.properties.overscroll-behavior-x.contain 📋Edge10/2/2018 Safari9/12/20221441
css.properties.overscroll-behavior-x.none 📋Edge1/15/2020 Safari9/12/2022971
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-y 📋Edge10/2/2018 Safari9/12/20221441
css.properties.overscroll-behavior-y.auto 📋Edge10/2/2018 Safari9/12/20221441
css.properties.overscroll-behavior-y.contain 📋Edge10/2/2018 Safari9/12/20221441
css.properties.overscroll-behavior-y.none 📋Edge1/15/2020 Safari9/12/2022971
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.padding 📋Safari6/23/2003 Edge7/29/20154419
css.properties.padding-block 📋Edge11/19/2020 Safari4/26/2021158
css.properties.padding-block-end 📋Safari3/25/2019 Edge1/15/2020296
css.properties.padding-block-start 📋Safari3/25/2019 Edge1/15/2020296
css.properties.padding-bottom 📋Safari6/23/2003 Edge7/29/20154419
css.properties.padding-inline 📋Edge11/19/2020 Safari4/26/2021158
css.properties.padding-inline-end 📋Safari3/25/2019 Edge1/15/2020296
css.properties.padding-inline-start 📋Safari3/25/2019 Edge1/15/2020296
css.properties.padding-left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.padding-right 📋Safari6/23/2003 Edge7/29/20154419
css.properties.padding-top 📋Safari6/23/2003 Edge7/29/20154419
css.properties.page 📋Safari6/23/2003 Edge8/27/20206275
css.properties.page.auto 📋Safari6/23/2003 Edge8/27/20206275
css.properties.page-break-after 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-after.always 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-after.auto 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-after.left 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-after.right 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before.always 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before.auto 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before.left 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-before.right 📋Safari2/2/2004 Edge7/29/20154195
css.properties.page-break-inside 📋Safari4/15/2005 Edge7/29/20153757
css.properties.page-break-inside.auto 📋Safari4/15/2005 Edge7/29/20153757
css.properties.page-break-inside.avoid 📋Safari4/15/2005 Edge7/29/20153757
Firefox: Until Firefox 25, page-break-inside: avoid did not work with the height of a block.Firefox for Android: Until Firefox for Android 25, page-break-inside: avoid did not work with the height of a block.
css.properties.paint-order 📋Safari9/19/2017 Edge3/22/20242376
Chrome: Does not affect stroked HTML text, see bug 41372165Chrome Android: Does not affect stroked HTML text, see bug 41372165Edge: Does not affect stroked HTML text, see bug 41372165Quest Browser: Does not affect stroked HTML text, see bug 41372165Opera: Does not affect stroked HTML text, see bug 41372165Opera Android: Does not affect stroked HTML text, see bug 41372165Safari: Does not affect stroked HTML text, see bug 168601Safari on iOS: Does not affect stroked HTML text, see bug 168601Samsung Internet: Does not affect stroked HTML text, see bug 41372165WebView Android: Does not affect stroked HTML text, see bug 41372165WebView on iOS: Does not affect stroked HTML text, see bug 168601
css.properties.paint-order.fill 📋Safari10/16/2014 Edge1/15/20201917
css.properties.paint-order.markers 📋Safari10/16/2014 Edge1/15/20201917
css.properties.paint-order.normal 📋Safari10/16/2014 Edge1/15/20201917
css.properties.paint-order.stroke 📋Safari10/16/2014 Edge1/15/20201917
css.properties.perspective 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin 📋Edge7/29/2015 Safari9/30/201563
css.properties.perspective-origin.bottom 📋Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.center 📋Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.left 📋Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.right 📋Safari6/8/2009 Edge7/29/20152242
css.properties.perspective-origin.top 📋Safari6/8/2009 Edge7/29/20152242
css.properties.place-content 📋Safari9/30/2015 Edge1/15/20201568
css.properties.place-content.flex_context Safari9/30/2015 Edge1/15/20201568
Firefox: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.Firefox for Android: Starting with version 60, you can only specify a single value if it is valid for both align-content and justify-content.
css.properties.place-content.grid_context Safari9/19/2017 Edge1/15/2020848
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 📋Safari9/19/2017 Edge1/15/2020848
css.properties.place-items.anchor-center 📋Edge5/17/2024 Safari9/15/2025486
css.properties.place-items.flex_context Safari9/19/2017 Edge1/15/2020848
css.properties.place-items.grid_context Safari9/19/2017 Edge1/15/2020848
css.properties.place-self 📋Safari9/19/2017 Edge1/15/2020848
css.properties.place-self.anchor-center 📋Edge5/17/2024 Safari9/15/2025486
css.properties.place-self.flex_context Safari9/19/2017 Edge1/15/2020848
css.properties.place-self.grid_context Safari9/19/2017 Edge1/15/2020848
css.properties.pointer-events 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.all 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.auto 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.bounding-box 📋Safari9/19/2019 Edge1/15/2020118
css.properties.pointer-events.fill 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.html_elements Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.none 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.painted 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.stroke 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.visible 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.visibleFill 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.visiblePainted 📋Safari6/8/2009 Edge7/29/20152242
css.properties.pointer-events.visibleStroke 📋Safari6/8/2009 Edge7/29/20152242
css.properties.position 📋Safari6/23/2003 Edge7/29/20154419
css.properties.position.absolute 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 57, absolute positioning did not work correctly when applied to elements inside tables that have border-collapse applied to them (bug 1379306).Firefox: Before Firefox 30, absolute positioning of table rows and row groups was not supported (bug 63895).Firefox for Android: Before Firefox for Android 57, absolute positioning did not work correctly when applied to elements inside tables that have border-collapse applied to them (bug 1379306).Firefox for Android: Before Firefox for Android 30, absolute positioning of table rows and row groups was not supported (bug 63895).
css.properties.position.absolutely_positioned_flex_children Edge7/29/2015 Safari9/19/2017783
css.properties.position.fixed 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 44, position: fixed didn't create a stacking context in most cases. Firefox and the specification have been modified to mimic Chrome and Safari's long-time behavior.Firefox for Android: Before Firefox for Android 44, position: fixed didn't create a stacking context in most cases. Firefox for Android and the specification have been modified to mimic Chrome and Safari's long-time behavior.Internet Explorer: In Internet Explorer, fixed positioning doesn't work if the document is in quirks mode.
css.properties.position.position_sticky_table_elements Safari10/16/2014 Edge10/17/20171097
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 📋Safari6/23/2003 Edge7/29/20154419
css.properties.position.static 📋Safari6/23/2003 Edge7/29/20154419
css.properties.position.sticky 📋Edge10/17/2017 Safari9/19/2019702
css.properties.position-anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-anchor.auto 📋Edge5/17/2024 Safari9/15/2025486
Chrome: The generic auto value exists, but it does not yet have the effect described in the spec.Chrome Android: The generic auto value exists, but it does not yet have the effect described in the spec.Edge: The generic auto value exists, but it does not yet have the effect described in the spec.Opera: The generic auto value exists, but it does not yet have the effect described in the spec.Opera Android: The generic auto value exists, but it does not yet have the effect described in the spec.Samsung Internet: The generic auto value exists, but it does not yet have the effect described in the spec.WebView Android: The generic auto value exists, but it does not yet have the effect described in the spec.
css.properties.position-area 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.block-end 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.block-start 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.bottom 📋Safari9/15/2025 Edge1/21/2026128
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 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.end 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.inline-end 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.inline-start 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.left 📋Safari9/15/2025 Edge1/21/2026128
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 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.right 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When right is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-block-end 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-block-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-block-start 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-block-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-end 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-inline-end 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-inline-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-inline-start 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-inline-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-start 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-x-end 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-x-start 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-y-end 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.self-y-start 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.span-all 📋Safari9/15/2025 Edge1/21/2026128
Chrome: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: Using span-all unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.span-block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-bottom 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-left 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-right 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-self-block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-self-block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-self-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-self-inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-self-inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-self-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-self-x-end 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-area.span-self-x-start 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-area.span-self-y-end 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-area.span-self-y-start 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-area.span-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-top 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-x-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-x-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-y-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.span-y-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-area.top 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When top is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.x-end 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.x-start 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.y-end 📋Safari9/15/2025 Edge1/21/2026128
Chrome: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.y-start 📋Safari9/15/2025 Edge1/21/2026128
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 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try.block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.bottom 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.center 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.flip-block 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try.flip-inline 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try.flip-start 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try.flip-x 📋Safari12/12/2025 Edge1/21/202640
css.properties.position-try.flip-y 📋Safari12/12/2025 Edge1/21/202640
css.properties.position-try.inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.left 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.none 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try.right 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.self-block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.self-block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.self-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.self-inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.self-inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.self-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.self-x-end 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-x-start 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-y-end 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.self-y-start 📋Safari12/12/2025 Edge1/21/202640
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 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-bottom 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-left 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-right 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-self-block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-self-block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-self-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-self-inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-self-inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-self-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-self-x-end 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-try.span-self-x-start 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-try.span-self-y-end 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-try.span-self-y-start 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-try.span-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-top 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-x-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-x-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-y-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.span-y-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.top 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.x-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.x-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.y-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try.y-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks 📋Edge8/22/2024 Safari9/15/2025389
css.properties.position-try-fallbacks.block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.bottom 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.center 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.flip-block 📋Edge8/22/2024 Safari9/15/2025389
css.properties.position-try-fallbacks.flip-inline 📋Edge8/22/2024 Safari9/15/2025389
css.properties.position-try-fallbacks.flip-start 📋Edge8/22/2024 Safari9/15/2025389
css.properties.position-try-fallbacks.flip-x 📋Safari12/12/2025 Edge1/21/202640
css.properties.position-try-fallbacks.flip-y 📋Safari12/12/2025 Edge1/21/202640
css.properties.position-try-fallbacks.inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.left 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.none 📋Edge8/22/2024 Safari9/15/2025389
css.properties.position-try-fallbacks.position-area 📋Edge8/22/2024 Safari9/15/2025389
Chrome: inset-area values had to be wrapped inside an inset-area() function.Chrome Android: inset-area values had to be wrapped inside an inset-area() function.Edge: inset-area values had to be wrapped inside an inset-area() function.Opera: inset-area values had to be wrapped inside an inset-area() function.Opera Android: inset-area values had to be wrapped inside an inset-area() function.Samsung Internet: inset-area values had to be wrapped inside an inset-area() function.WebView Android: inset-area values had to be wrapped inside an inset-area() function.
css.properties.position-try-fallbacks.right 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.self-block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.self-block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.self-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.self-inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.self-inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.self-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.self-x-end 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-x-start 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-x-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When x-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-y-end 📋Safari12/12/2025 Edge1/21/202640
Chrome: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-end is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.self-y-start 📋Safari12/12/2025 Edge1/21/202640
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 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-bottom 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-left 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-right 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-self-block-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-self-block-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-self-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-self-inline-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-self-inline-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-self-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-self-x-end 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-try-fallbacks.span-self-x-start 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-try-fallbacks.span-self-y-end 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-try-fallbacks.span-self-y-start 📋Edge12/5/2025 Safari12/12/20257
css.properties.position-try-fallbacks.span-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-top 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-x-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-x-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-y-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.span-y-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.top 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.x-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.x-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.y-end 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-fallbacks.y-start 📋Edge9/19/2024 Safari9/15/2025361
css.properties.position-try-order 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try-order.most-block-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try-order.most-height 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try-order.most-inline-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try-order.most-width 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-try-order.normal 📋Edge5/17/2024 Safari9/15/2025486
css.properties.position-visibility 📋Edge5/17/2024 Safari12/12/2025574
css.properties.position-visibility.always 📋Edge5/17/2024 Safari12/12/2025574
css.properties.position-visibility.anchors-visible 📋Edge5/17/2024 Safari12/12/2025574
css.properties.position-visibility.no-overflow 📋Edge5/17/2024 Safari12/12/2025574
css.properties.print-color-adjust 📋Safari3/14/2022 Edge5/1/20251144
Chrome: Chrome does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Chrome: Before version 26, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Chrome Android: Chrome Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Chrome Android: Before version 26, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Edge: Edge does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Edge: Before version 79, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Quest Browser: Quest Browser does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Quest Browser: Before version 5.0, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Opera: Opera does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Opera: Before version 15, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Opera Android: Opera Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Opera Android: Before version 14, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.Safari: Safari does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Safari on iOS: Safari on iOS does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Samsung Internet: Samsung Internet does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.Samsung Internet: Before version 1.5, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.WebView Android: WebView Android does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.WebView Android: Before version 4.4, if background images are clipped (for example, when using background-image sprites) and -webkit-print-color-adjust is set to exact, then backgrounds will appear distorted when printed. Solid backgrounds and background images that are not clipped (i.e., backgrounds that have narrower and shorter than the element to which they are applied) are printed correctly. See bug 40219905.WebView on iOS: WebView on iOS does not print backgrounds of the <body> element. If this property is set to exact for the <body> element, it will apply only to its descendants.
css.properties.print-color-adjust.economy 📋Safari7/25/2012 Edge5/1/20254663
css.properties.print-color-adjust.exact 📋Safari7/25/2012 Edge5/1/20254663
css.properties.quotes 📋Edge7/29/2015 Safari9/30/201563
css.properties.quotes.auto 📋Edge11/19/2020 Safari4/26/2021158
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 📋Edge7/29/2015 Safari9/30/201563
css.properties.r 📋Safari9/30/2015 Edge1/15/20201568
css.properties.resize 📋Safari10/26/2007 Edge1/15/20204464
Firefox for Android: The property is recognized, but has no effect. See bug 1776834.Safari on iOS: The property is recognized, but has no effect. See bug 211994.WebView on iOS: The property is recognized, but has no effect. See bug 211994.
css.properties.resize.block Safari9/12/2022 Edge10/13/2023396
css.properties.resize.block_level_support Safari6/8/2009 Edge1/15/20203873
Firefox: resize doesn't have any effect on <iframe>. See bug 680823)
css.properties.resize.both 📋Safari10/26/2007 Edge1/15/20204464
css.properties.resize.horizontal 📋Safari10/26/2007 Edge1/15/20204464
css.properties.resize.inline Safari9/12/2022 Edge10/13/2023396
css.properties.resize.none 📋Safari10/26/2007 Edge1/15/20204464
css.properties.resize.vertical 📋Safari10/26/2007 Edge1/15/20204464
css.properties.right 📋Safari6/23/2003 Edge7/29/20154419
css.properties.right.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.right.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.right.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.rotate 📋Safari4/26/2021 Edge8/5/2022466
css.properties.rotate.none 📋Safari4/26/2021 Edge8/5/2022466
css.properties.rotate.x_y_z_angle Safari4/26/2021 Edge8/5/2022466
css.properties.row-gap 📋Safari3/27/2017 Edge10/17/2017204
css.properties.row-gap.flex_context 📋Edge7/16/2020 Safari4/26/2021284
css.properties.row-gap.grid_context 📋Edge10/17/2017 Safari9/17/2018335
css.properties.row-gap.normal 📋Safari3/27/2017 Edge10/17/2017204
css.properties.ruby-align 📋Edge8/22/2024 Safari12/11/2024111
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 📋Edge8/22/2024 Safari12/11/2024111
css.properties.ruby-align.space-around 📋Edge8/22/2024 Safari12/11/2024111
css.properties.ruby-align.space-between 📋Edge8/22/2024 Safari12/11/2024111
css.properties.ruby-align.start 📋Edge8/22/2024 Safari12/11/2024111
css.properties.ruby-position 📋Edge7/16/2020 Safari12/11/20241609
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 Safari12/11/20241609
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 Safari12/11/20241609
css.properties.ruby-position.under Edge7/16/2020 Safari12/11/20241609
css.properties.rx 📋Edge1/15/2020 Safari3/5/20241511
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 📋Edge1/15/2020 Safari3/5/20241511
css.properties.ry 📋Edge1/15/2020 Safari3/5/20241511
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 📋Edge1/15/2020 Safari3/5/20241511
css.properties.scale 📋Safari4/26/2021 Edge8/5/2022466
css.properties.scale.none 📋Safari4/26/2021 Edge8/5/2022466
css.properties.scroll-behavior 📋Edge1/15/2020 Safari3/14/2022789
css.properties.scroll-behavior.auto 📋Edge1/15/2020 Safari3/14/2022789
css.properties.scroll-behavior.smooth 📋Edge1/15/2020 Safari3/14/2022789
css.properties.scroll-margin 📋Edge1/15/2020 Safari4/26/2021467
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 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-margin-block-end 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-margin-block-start 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-margin-bottom 📋Edge1/15/2020 Safari4/26/2021467
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 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-margin-inline-end 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-margin-inline-start 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-margin-left 📋Edge1/15/2020 Safari4/26/2021467
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 📋Edge1/15/2020 Safari4/26/2021467
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 📋Edge1/15/2020 Safari4/26/2021467
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-padding 📋Edge1/15/2020 Safari4/26/2021467
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 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-padding-block 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-block.auto 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-block-end 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-block-end.auto 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-block-start 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-block-start.auto 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-bottom 📋Edge1/15/2020 Safari4/26/2021467
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 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-inline 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-inline.auto 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-inline-end 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-inline-end.auto 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-inline-start 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-inline-start.auto 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-left 📋Edge1/15/2020 Safari4/26/2021467
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 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-right 📋Edge1/15/2020 Safari4/26/2021467
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 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-padding-top 📋Edge1/15/2020 Safari4/26/2021467
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 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-snap-align 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align.center 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align.end 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align.none 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-align.start 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-stop 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-snap-stop.always 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-snap-stop.normal 📋Edge1/15/2020 Safari9/20/2021614
css.properties.scroll-snap-type 📋Safari9/19/2017 Edge1/15/2020848
Edge: Edge supports an earlier draft of CSS Scroll Snap without axis values.Firefox: On macOS Monterey, scroll snapping does not complete reliably. See bug 1749352.Firefox: An earlier draft of CSS Scroll Snap without axis values.Firefox for Android: An earlier draft of CSS Scroll Snap without axis values.Internet Explorer: Internet Explorer supports an earlier draft of CSS Scroll Snap without axis values.Safari: Older Safari versions support an earlier draft of CSS Scroll Snap without axis values.Safari on iOS: Older Safari on iOS versions support an earlier draft of CSS Scroll Snap without axis values.WebView on iOS: Older WebView on iOS versions support an earlier draft of CSS Scroll Snap without axis values.
css.properties.scroll-snap-type.block 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.both 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.inline 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.none 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.x 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-snap-type.y 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-timeline 📋Edge7/21/2023 Safari9/15/2025787
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 📋Edge7/21/2023 Safari9/15/2025787
css.properties.scroll-timeline-axis 📋Edge7/21/2023 Safari9/15/2025787
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 📋Edge7/21/2023 Safari9/15/2025787
css.properties.scroll-timeline-axis.inline 📋Edge7/21/2023 Safari9/15/2025787
css.properties.scroll-timeline-axis.x 📋Edge7/21/2023 Safari9/15/2025787
css.properties.scroll-timeline-axis.y 📋Edge7/21/2023 Safari9/15/2025787
css.properties.scroll-timeline-name 📋Edge7/21/2023 Safari9/15/2025787
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 📋Edge7/21/2023 Safari9/15/2025787
css.properties.scrollbar-color 📋Edge1/25/2024 Safari12/12/2025687
css.properties.scrollbar-color.auto 📋Edge1/25/2024 Safari12/12/2025687
css.properties.scrollbar-gutter 📋Edge9/24/2021 Safari12/11/20241174
css.properties.scrollbar-gutter.auto 📋Edge9/24/2021 Safari12/11/20241174
css.properties.scrollbar-gutter.stable 📋Edge9/24/2021 Safari12/11/20241174
css.properties.scrollbar-width 📋Edge1/25/2024 Safari12/11/2024321
css.properties.scrollbar-width.auto 📋Edge1/25/2024 Safari12/11/2024321
css.properties.scrollbar-width.none 📋Edge1/25/2024 Safari12/11/2024321
css.properties.scrollbar-width.thin 📋Edge1/25/2024 Safari12/11/2024321
css.properties.shape-image-threshold 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-margin 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.border-box 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.circle Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.content-box 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.gradient 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.image 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.inset Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.margin-box 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.none 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.padding-box 📋Safari3/27/2017 Edge1/15/20201024
css.properties.shape-outside.polygon Safari3/27/2017 Edge1/15/20201024
css.properties.shape-rendering 📋Safari6/8/2009 Edge1/15/20203873
css.properties.shape-rendering.auto 📋Safari6/8/2009 Edge1/15/20203873
css.properties.shape-rendering.crispEdges 📋Safari6/8/2009 Edge1/15/20203873
css.properties.shape-rendering.geometricPrecision 📋Safari6/8/2009 Edge1/15/20203873
css.properties.shape-rendering.optimizeSpeed 📋Safari6/8/2009 Edge1/15/20203873
css.properties.stop-color 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stop-opacity 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke.none 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-dasharray 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-dasharray.none 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-dashoffset 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-linecap 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-linecap.butt 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-linecap.round 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-linecap.square 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-linejoin 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-linejoin.bevel 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-linejoin.miter 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-linejoin.round 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-miterlimit 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-opacity 📋Safari6/8/2009 Edge4/5/20172858
css.properties.stroke-width 📋Safari6/8/2009 Edge4/5/20172858
css.properties.tab-size 📋Safari10/22/2013 Edge1/15/20202276
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 📋Edge1/15/2020 Safari3/24/202069
css.properties.table-layout 📋Safari6/23/2003 Edge7/29/20154419
css.properties.table-layout.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.table-layout.fixed 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-align 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-align.center 📋Safari6/8/2009 Edge1/15/20203873
css.properties.text-align.end 📋Safari3/18/2008 Edge1/15/20204320
css.properties.text-align.justify 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-align.left 📋Safari6/8/2009 Edge1/15/20203873
css.properties.text-align.match-parent 📋Edge1/15/2020 Safari3/14/2022789
css.properties.text-align.right 📋Safari6/8/2009 Edge1/15/20203873
css.properties.text-align.start 📋Safari3/18/2008 Edge1/15/20204320
css.properties.text-align-last 📋Edge7/29/2015 Safari9/12/20222602
Internet Explorer: IE only supports text-align-last when text-align is set to justify.Internet Explorer: The start and end values are not supported.
css.properties.text-align-last.auto 📋Edge7/29/2015 Safari9/12/20222602
css.properties.text-align-last.center 📋Edge7/29/2015 Safari9/12/20222602
css.properties.text-align-last.end 📋Edge1/15/2020 Safari9/12/2022971
css.properties.text-align-last.justify 📋Edge7/29/2015 Safari9/12/20222602
css.properties.text-align-last.left 📋Edge7/29/2015 Safari9/12/20222602
css.properties.text-align-last.right 📋Edge7/29/2015 Safari9/12/20222602
css.properties.text-align-last.start 📋Edge1/15/2020 Safari9/12/2022971
css.properties.text-anchor 📋Safari6/8/2009 Edge8/2/20162612
css.properties.text-anchor.end 📋Safari6/8/2009 Edge8/2/20162612
css.properties.text-anchor.middle 📋Safari6/8/2009 Edge8/2/20162612
css.properties.text-anchor.start 📋Safari6/8/2009 Edge8/2/20162612
css.properties.text-autospace 📋Safari3/31/2025 Edge9/5/2025158
css.properties.text-autospace.no-autospace 📋Safari3/31/2025 Edge9/5/2025158
css.properties.text-autospace.normal 📋Safari3/31/2025 Edge9/5/2025158
css.properties.text-box 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box.auto 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box.none 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box.normal 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box.text 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box.trim-both 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box.trim-end 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box.trim-start 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box-edge 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box-edge.auto 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box-edge.text 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box-trim 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box-trim.none 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box-trim.trim-both 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box-trim.trim-end 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-box-trim.trim-start 📋Safari12/11/2024 Edge2/6/202557
css.properties.text-combine-upright 📋Edge1/15/2020 Safari3/14/2022789
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 📋Edge1/15/2020 Safari3/14/2022789
css.properties.text-combine-upright.none 📋Edge1/15/2020 Safari3/14/2022789
css.properties.text-decoration 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.auto 📋Edge11/19/2020 Safari12/12/20251849
css.properties.text-decoration.blink 📋Safari6/23/2003 Edge7/29/20154419
Chrome: The blink value does not have any effect.Chrome Android: The blink value does not have any effect.Firefox: The blink value does not have any effect.Firefox for Android: The blink value does not have any effect.Quest Browser: The blink value does not have any effect.Opera: The blink value does not have any effect.Opera Android: The blink value does not have any effect.Safari: The blink value does not have any effect.Safari on iOS: The blink value does not have any effect.Samsung Internet: The blink value does not have any effect.WebView Android: The blink value does not have any effect.WebView on iOS: The blink value does not have any effect.
css.properties.text-decoration.currentColor 📋Edge1/15/2020 Safari12/12/20252158
css.properties.text-decoration.dashed 📋Edge1/15/2020 Safari12/12/20252158
css.properties.text-decoration.dotted 📋Edge1/15/2020 Safari12/12/20252158
css.properties.text-decoration.double 📋Edge1/15/2020 Safari12/12/20252158
css.properties.text-decoration.from-font 📋Edge11/19/2020 Safari12/12/20251849
css.properties.text-decoration.grammar-error 📋Edge1/25/2024 Safari12/12/2025687
css.properties.text-decoration.includes_color-and-style Edge1/15/2020 Safari12/12/20252158
css.properties.text-decoration.includes_thickness Edge11/19/2020 Safari12/12/20251849
css.properties.text-decoration.line-through 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.overline 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.solid 📋Edge1/15/2020 Safari12/12/20252158
css.properties.text-decoration.spelling-error 📋Edge1/25/2024 Safari12/12/2025687
css.properties.text-decoration.transparent 📋Edge1/15/2020 Safari12/12/20252158
css.properties.text-decoration.underline 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.wavy 📋Edge1/15/2020 Safari12/12/20252158
css.properties.text-decoration-color 📋Safari3/25/2019 Edge1/15/2020296
css.properties.text-decoration-color.currentColor 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-color.transparent 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-line 📋Safari3/25/2019 Edge1/15/2020296
css.properties.text-decoration-line.blink 📋Safari10/16/2014 Edge1/15/20201917
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 📋Edge1/25/2024 Safari12/12/2025687
css.properties.text-decoration-line.line-through 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-line.none 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-line.overline 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-line.spelling-error 📋Edge1/25/2024 Safari12/12/2025687
css.properties.text-decoration-line.underline 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-skip-ink 📋Edge1/15/2020 Safari3/14/2022789
css.properties.text-decoration-skip-ink.auto 📋Edge1/15/2020 Safari3/14/2022789
css.properties.text-decoration-skip-ink.none 📋Edge1/15/2020 Safari3/14/2022789
css.properties.text-decoration-style 📋Safari3/25/2019 Edge1/15/2020296
css.properties.text-decoration-style.dashed 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-style.dotted 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-style.double 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-style.solid 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-style.wavy 📋Safari10/16/2014 Edge1/15/20201917
css.properties.text-decoration-thickness 📋Safari3/25/2019 Edge3/4/2021710
Chrome: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Chrome Android: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Edge: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Quest Browser: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Opera: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Opera Android: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.Samsung Internet: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.WebView Android: The text-decoration-thickness property has no effect unless text-underline-offset, text-decoration-color, or text-decoration-style are set to a non-initial value. See bug 40734940.
css.properties.text-decoration-thickness.auto 📋Safari3/25/2019 Edge11/19/2020605
css.properties.text-decoration-thickness.from-font 📋Safari3/25/2019 Edge11/19/2020605
css.properties.text-decoration-thickness.percentage Edge11/19/2020 Safari3/5/20241202
css.properties.text-emphasis 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis.circle 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.currentColor 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.dot 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.double-circle 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.filled 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.none 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.open 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.sesame 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.transparent 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis.triangle 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis-color 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-color.currentColor 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis-color.transparent 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-emphasis-position 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-position.left Safari10/16/2014 Edge1/15/20201917
css.properties.text-emphasis-position.over Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-position.right Safari10/16/2014 Edge1/15/20201917
css.properties.text-emphasis-position.under Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.circle 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.dot 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.double-circle 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.filled 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.none 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.open 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.sesame 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-style.triangle 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-indent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-indent.each-line 📋Safari9/20/2021 Edge3/12/20261634
css.properties.text-indent.hanging 📋Safari9/20/2021 Edge3/12/20261634
css.properties.text-orientation 📋Edge1/15/2020 Safari9/16/2020245
css.properties.text-orientation.mixed 📋Edge1/15/2020 Safari3/24/202069
css.properties.text-orientation.sideways 📋Safari10/22/2013 Edge1/15/20202276
css.properties.text-orientation.upright 📋Edge1/15/2020 Safari3/24/202069
css.properties.text-overflow 📋Safari4/15/2005 Edge7/29/20153757
Firefox: Until Firefox 10, handling of text-overflow on blocks with inline overflow on both horizontal sides was incorrect. Before Firefox 10, if only one value was specified (such as text-overflow: ellipsis;), text was ellipsed on both sides of the block, instead of only the end edge based on the block's text direction.Firefox for Android: Until Firefox for Android 10, handling of text-overflow on blocks with inline overflow on both horizontal sides was incorrect. Before Firefox for Android 10, if only one value was specified (such as text-overflow: ellipsis;), text was ellipsed on both sides of the block, instead of only the end edge based on the block's text direction.
css.properties.text-overflow.clip 📋Safari4/15/2005 Edge7/29/20153757
css.properties.text-overflow.ellipsis 📋Safari4/15/2005 Edge7/29/20153757
css.properties.text-rendering 📋Safari6/7/2010 Edge1/15/20203509
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 Safari6/7/2010 Edge1/15/20203509
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 Safari7/25/2012 Edge1/15/20202730
Chrome: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Chrome Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Edge: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Firefox: Firefox treats geometricPrecision the same as optimizeLegibility.Firefox for Android: Firefox treats geometricPrecision the same as optimizeLegibility.Quest Browser: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Opera: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Opera Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.Samsung Internet: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.WebView Android: Supports true geometric precision without rounding up or down to the nearest supported font size in the operating system.
css.properties.text-rendering.optimizeLegibility 📋Safari6/7/2010 Edge1/15/20203509
css.properties.text-rendering.optimizeSpeed 📋Safari6/7/2010 Edge1/15/20203509
css.properties.text-shadow 📋Safari10/24/2003 Edge7/29/20154296
Firefox: Firefox versions before 57 have a bug whereby transitions will not work when transitioning from a text-shadow with a color specified to a text-shadow without a color specified (bug 726550).Firefox: From Firefox 4, the blur radius is capped at 300 for performance reasons.Firefox: Firefox theoretically supports infinite text-shadows (don't try it).Firefox: If the <color> value is unspecified, then Firefox uses the value of the element's color property.Firefox for Android: Firefox for Android versions before 57 have a bug whereby transitions will not work when transitioning from a text-shadow with a color specified to a text-shadow without a color specified (bug 726550).Firefox for Android: From Firefox for Android 4, the blur radius is capped at 300 for performance reasons.Firefox for Android: Firefox for Android theoretically supports infinite text-shadows (don't try it).Firefox for Android: If the <color> value is unspecified, then Firefox for Android uses the value of the element's color property.Opera: Opera supports a maximum of 6-9 text-shadows for performance reasons. The blur radius is limited to 100px.Opera: Opera 9.5 to 10.1 adheres to the old, reverse painting order (in CSS2, the first specified shadow is on the bottom).Safari: In Safari, any shadows that do not explicitly specify a color are transparent.Safari: Safari 1.1 to 3.2 only supports one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari 4.0 (WebKit 528) and later support multiple text-shadows.Safari on iOS: In Safari, any shadows that do not explicitly specify a color are transparent.Safari on iOS: Safari iOS 1 and 2 only support one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari iOS 3 (WebKit 528) and later support multiple text-shadows.WebView on iOS: In Safari, any shadows that do not explicitly specify a color are transparent.WebView on iOS: Safari iOS 1 and 2 only support one text-shadow (displays the first shadow of a comma-separated list and ignores the rest). Safari iOS 3 (WebKit 528) and later support multiple text-shadows.
css.properties.text-shadow.none 📋Safari10/24/2003 Edge7/29/20154296
css.properties.text-transform 📋Safari6/23/2003 Edge7/29/20154419
Chrome: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Chrome Android: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Quest Browser: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Opera: Since Opera 15, the text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.Safari: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.Samsung Internet: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.WebView Android: The text-transform property does not work for ::first-line pseudo-elements (nor for the one-colon syntax). See bug 40214861.WebView on iOS: The text-transform property does not work for ::first-line pseudo-elements (also not for the old one-colon syntax). See bug 3409.
css.properties.text-transform.capitalize 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 14, some punctuation characters could interfere with correct capitalization. See bug 731536.Firefox for Android: Before Firefox for Android 14, some punctuation characters could interfere with correct capitalization. See bug 731536.
css.properties.text-transform.lowercase 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-transform.lowercase_sigma Safari7/25/2012 Edge7/29/20151099
css.properties.text-transform.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-transform.turkic_is Safari10/16/2014 Edge7/29/2015286
css.properties.text-transform.uppercase 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-transform.uppercase_eszett Safari6/23/2003 Edge10/2/20185580
css.properties.text-underline-offset 📋Safari3/25/2019 Edge11/19/2020605
css.properties.text-underline-offset.auto 📋Safari3/25/2019 Edge11/19/2020605
css.properties.text-underline-offset.percentage 📋Edge11/19/2020 Safari12/11/20241483
css.properties.text-underline-position 📋Edge7/29/2015 Safari3/25/20191335
css.properties.text-underline-position.auto 📋Safari3/25/2019 Edge1/15/2020296
css.properties.text-underline-position.from-font 📋Safari3/25/2019 Edge11/19/2020605
css.properties.text-underline-position.left 📋Edge1/15/2020 Safari12/11/20241792
css.properties.text-underline-position.right 📋Edge1/15/2020 Safari12/11/20241792
css.properties.text-underline-position.under 📋Safari3/25/2019 Edge1/15/2020296
css.properties.text-wrap 📋Edge6/2/2023 Safari3/5/2024277
css.properties.text-wrap.auto 📋Safari3/5/2024 Edge10/17/2024226
css.properties.text-wrap.balance 📋Edge6/2/2023 Safari5/13/2024346
css.properties.text-wrap.nowrap 📋Edge6/2/2023 Safari3/5/2024277
css.properties.text-wrap.pretty 📋Edge9/15/2023 Safari9/15/2025731
css.properties.text-wrap.stable 📋Safari5/13/2024 Edge10/17/2024157
css.properties.text-wrap.wrap 📋Edge6/2/2023 Safari3/5/2024277
css.properties.text-wrap-mode 📋Safari3/5/2024 Edge10/17/2024226
css.properties.text-wrap-mode.nowrap Safari3/5/2024 Edge10/17/2024226
css.properties.text-wrap-mode.wrap Safari3/5/2024 Edge10/17/2024226
css.properties.text-wrap-style 📋Safari5/13/2024 Edge10/17/2024157
css.properties.text-wrap-style.auto 📋Safari5/13/2024 Edge10/17/2024157
css.properties.text-wrap-style.balance 📋Safari5/13/2024 Edge10/17/2024157
css.properties.text-wrap-style.pretty 📋Edge10/17/2024 Safari9/15/2025333
css.properties.text-wrap-style.stable 📋Safari5/13/2024 Edge10/17/2024157
css.properties.timeline-scope 📋Edge8/21/2023 Safari9/15/2025756
css.properties.timeline-scope.none 📋Edge8/21/2023 Safari9/15/2025756
css.properties.top 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: In Internet Explorer versions before 7, when both top and bottom are specified, the element position is overconstrained and the top property has precedence; the computed value of bottom is set to -top, while its specified value is ignored.
css.properties.top.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.properties.top.anchor-size 📋Edge1/17/2025 Safari9/15/2025241
css.properties.top.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.touch-action 📋Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.manipulation Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.none Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-x Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-y Edge7/29/2015 Safari9/19/20191513
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pinch-zoom Edge7/29/2015 Safari9/19/20191513
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 📋Edge7/29/2015 Safari9/30/201563
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 Safari6/8/2009 Edge7/29/20152242
css.properties.transform.none 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transform-box 📋Safari9/19/2017 Edge1/15/2020848
css.properties.transform-box.border-box 📋Safari9/19/2017 Edge10/13/20232215
css.properties.transform-box.content-box 📋Safari3/24/2020 Edge10/13/20231298
css.properties.transform-box.fill-box 📋Safari9/19/2017 Edge1/15/2020848
css.properties.transform-box.stroke-box 📋Safari3/24/2020 Edge10/13/20231298
css.properties.transform-box.view-box 📋Safari9/19/2017 Edge1/15/2020848
css.properties.transform-origin 📋Edge7/29/2015 Safari9/30/201563
css.properties.transform-origin.bottom 📋Safari4/29/2005 Edge7/29/20153743
css.properties.transform-origin.center 📋Safari4/29/2005 Edge7/29/20153743
css.properties.transform-origin.left 📋Safari4/29/2005 Edge7/29/20153743
css.properties.transform-origin.right 📋Safari4/29/2005 Edge7/29/20153743
css.properties.transform-origin.svg_elements Safari7/25/2012 Edge4/30/20182105
Firefox: Keywords and percentages refer to the canvas instead of the object itself. See bug 1209061.Firefox for Android: Keywords and percentages refer to the canvas instead of the object itself. See bug 1209061.Safari: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).Safari on iOS: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).WebView on iOS: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).
css.properties.transform-origin.three_value_syntax Safari6/7/2010 Edge7/29/20151878
css.properties.transform-origin.top 📋Safari4/29/2005 Edge7/29/20153743
css.properties.transform-style 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari6/8/2009 Edge7/29/20152242
css.properties.transform-style.preserve-3d 📋Safari6/8/2009 Edge7/29/20152242
css.properties.transition 📋Edge7/29/2015 Safari9/30/201563
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 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.allow-discrete 📋Edge7/29/2015 Safari9/20/2016419
css.properties.transition.ease 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.ease-in 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.ease-in-out 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.ease-out 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.linear 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.none 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.normal 📋Edge7/29/2015 Safari9/20/2016419
css.properties.transition.step-end 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.step-start 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition.transition-behavior Edge9/15/2023 Safari3/5/2024172
css.properties.transition-behavior 📋Edge9/15/2023 Safari3/5/2024172
css.properties.transition-behavior.allow-discrete 📋Edge9/15/2023 Safari3/5/2024172
css.properties.transition-behavior.normal 📋Edge9/15/2023 Safari3/5/2024172
css.properties.transition-behavior.transitionable_content-visibility 📋Edge9/15/2023 Safari9/16/2024367
css.properties.transition-behavior.transitionable_display 📋Edge9/15/2023 Safari9/16/2024367
css.properties.transition-delay 📋Edge7/29/2015 Safari9/30/201563
css.properties.transition-duration 📋Edge7/29/2015 Safari9/30/201563
css.properties.transition-property 📋Edge7/29/2015 Safari9/30/201563
css.properties.transition-property.IDENT_value Safari6/8/2009 Edge7/29/20152242
css.properties.transition-property.all 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition-property.none 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function 📋Edge7/29/2015 Safari9/30/201563
css.properties.transition-timing-function.ease 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.ease-in 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.ease-in-out 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.ease-out 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.jump Edge1/15/2020 Safari9/16/2020245
css.properties.transition-timing-function.linear 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.step-end 📋Safari3/18/2008 Edge7/29/20152689
css.properties.transition-timing-function.step-start 📋Safari3/18/2008 Edge7/29/20152689
css.properties.translate 📋Safari4/26/2021 Edge8/5/2022466
css.properties.translate.none 📋Safari4/26/2021 Edge8/5/2022466
css.properties.unicode-bidi 📋Safari4/15/2005 Edge7/29/20153757
css.properties.unicode-bidi.bidi-override 📋Safari4/15/2005 Edge7/29/20153757
css.properties.unicode-bidi.embed 📋Safari4/15/2005 Edge7/29/20153757
css.properties.unicode-bidi.isolate 📋Safari9/19/2017 Edge1/15/2020848
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 📋Safari9/19/2017 Edge1/15/2020848
css.properties.unicode-bidi.normal 📋Safari4/15/2005 Edge7/29/20153757
css.properties.unicode-bidi.plaintext 📋Safari9/19/2017 Edge1/15/2020848
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 Safari10/26/2007 Edge7/29/20152833
Firefox: While the CSS property is parsed and accepted, it does not have any effect.Firefox for Android: While the CSS property is parsed and accepted, it does not have any effect.
css.properties.user-modify.read-write-plaintext-only Safari10/26/2007 Edge7/29/20152833
css.properties.user-select 📋Safari10/26/2007 Edge1/15/20204464
css.properties.user-select.all Edge1/15/2020 Safari9/12/2022971
css.properties.user-select.auto Safari4/29/2005 Edge7/29/20153743
css.properties.user-select.none Safari4/29/2005 Edge7/29/20153743
css.properties.user-select.text Safari4/29/2005 Edge7/29/20153743
css.properties.vector-effect 📋Safari7/20/2011 Edge1/15/20203101
css.properties.vector-effect.non-scaling-stroke 📋Safari7/20/2011 Edge1/15/20203101
css.properties.vector-effect.none 📋Safari7/20/2011 Edge1/15/20203101
css.properties.vertical-align 📋Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.baseline 📋Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.bottom 📋Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.middle 📋Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.sub 📋Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.super 📋Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.text-bottom 📋Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.text-top 📋Safari6/23/2003 Edge7/29/20154419
css.properties.vertical-align.top 📋Safari6/23/2003 Edge7/29/20154419
css.properties.view-timeline 📋Edge7/21/2023 Safari9/15/2025787
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline.none 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-timeline-axis 📋Edge7/21/2023 Safari9/15/2025787
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline-axis.block 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-timeline-axis.inline 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-timeline-axis.x 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-timeline-axis.y 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-timeline-inset 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-timeline-inset.auto 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-timeline-name 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-timeline-name.none 📋Edge7/21/2023 Safari9/15/2025787
css.properties.view-transition-class 📋Edge5/17/2024 Safari12/11/2024208
css.properties.view-transition-class.none 📋Edge5/17/2024 Safari12/11/2024208
css.properties.view-transition-name 📋Edge3/13/2023 Safari9/16/2024553
css.properties.view-transition-name.match-element 📋Safari3/31/2025 Edge5/29/202559
css.properties.view-transition-name.none 📋Edge3/13/2023 Safari9/16/2024553
css.properties.visibility 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Internet Explorer doesn't support visibility: initial.Internet Explorer: Internet Explorer doesn't support visibility: unset.Internet Explorer: Up to Internet Explorer 7, descendants of hidden elements will still be invisible even if they have visibility set to visible.
css.properties.visibility.collapse 📋Safari4/15/2005 Edge7/29/20153757
Chrome: Before Chrome 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome: Before Chrome 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome: Since Chrome 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Chrome Android: Before Chrome Android 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome Android: Before Chrome Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Chrome Android: Since Chrome Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Edge: For Edge 79 through Edge 91, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Edge: Since Edge 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Firefox: Firefox doesn't hide borders when hiding <col> and <colgroup> elements if border-collapse: collapse is set.Firefox: Before Firefox 88, collapse is not supported on ruby annotations.Firefox for Android: Firefox for Android doesn't hide borders when hiding <col> and <colgroup> elements if border-collapse: collapse is set.Firefox for Android: Before Firefox for Android 88, collapse is not supported on ruby annotations.Quest Browser: Before Quest Browser 5.0, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Quest Browser: Before Quest Browser 17.0, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Quest Browser: Since Quest Browser 17.0, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Opera: Before Opera 49, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera: Before Opera 78, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera: Since Opera 78, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Opera Android: Before Opera Android 46, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera Android: Before Opera Android 65, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Opera Android: Since Opera Android 65, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.Safari: Safari treats visibility: collapse like hidden, leaving a white gap.Safari: Safari supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.Safari on iOS: Safari on iOS treats visibility: collapse like hidden, leaving a white gap.Safari on iOS: Safari on iOS supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.Samsung Internet: Before Samsung Internet 8.0, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Samsung Internet: Before Samsung Internet 16.0, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.Samsung Internet: Since Samsung Internet 16.0, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.WebView Android: Before WebView Android 62, visibility: collapse has the same effect as hidden for <tr>, <thead>, <tbody>, and <tfoot> elements, flex items, and ruby annotations, leaving a blank gap. It has no effect on <col> and <colgroup> elements.WebView Android: Before WebView Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, and <tfoot> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap. It has no effect on <col> and <colgroup> elements.WebView Android: Since WebView Android 92, visibility: collapse supports <tr>, <thead>, <tbody>, <tfoot>, <col> and <colgroup> elements. For flex items and ruby annotations, it has the same effect as hidden, leaving a blank gap.WebView on iOS: WebView on iOS treats visibility: collapse like hidden, leaving a white gap.WebView on iOS: WebView on iOS supports the collapse value only on <tr>, <thead>, <tbody>, and <tfoot>, but not on <col> and <colgroup> elements.
css.properties.visibility.hidden 📋Safari6/23/2003 Edge7/29/20154419
css.properties.visibility.visible 📋Safari6/23/2003 Edge7/29/20154419
css.properties.white-space 📋Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.break-spaces 📋Edge1/15/2020 Safari3/24/202069
css.properties.white-space.collapse 📋Edge6/2/2023 Safari9/16/2024472
css.properties.white-space.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.nowrap 📋Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.pre 📋Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.pre-line 📋Safari10/26/2007 Edge7/29/20152833
css.properties.white-space.pre-wrap 📋Safari10/26/2007 Edge7/29/20152833
Internet Explorer: From Internet Explorer 5.5 to 7, word-wrap: break-word; can be used for line breaks in pre elements.
css.properties.white-space.preserve 📋Edge6/2/2023 Safari9/16/2024472
css.properties.white-space.preserve-breaks 📋Edge6/2/2023 Safari9/16/2024472
css.properties.white-space.textarea_support Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.wrap 📋Edge6/2/2023 Safari9/16/2024472
css.properties.white-space-collapse 📋Edge6/2/2023 Safari3/5/2024277
css.properties.white-space-collapse.break-spaces 📋Edge6/2/2023 Safari3/5/2024277
css.properties.white-space-collapse.collapse 📋Edge6/2/2023 Safari3/5/2024277
css.properties.white-space-collapse.preserve 📋Edge6/2/2023 Safari3/5/2024277
css.properties.white-space-collapse.preserve-breaks 📋Edge6/2/2023 Safari3/5/2024277
css.properties.widows 📋Safari4/15/2005 Edge7/29/20153757
css.properties.width 📋Safari6/23/2003 Edge7/29/20154419
css.properties.width.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.properties.width.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.width.fit-content 📋Safari9/19/2017 Edge1/15/2020848
css.properties.width.is_animatable Safari10/22/2013 Edge7/29/2015645
css.properties.width.max-content 📋Safari9/19/2017 Edge1/15/2020848
css.properties.width.min-content 📋Safari9/19/2017 Edge1/15/2020848
css.properties.width.stretch 📋Safari10/22/2013 Edge6/26/20254265
css.properties.will-change 📋Safari3/21/2016 Edge1/15/20201395
css.properties.will-change.auto 📋Safari3/21/2016 Edge1/15/20201395
css.properties.will-change.contents 📋Safari3/21/2016 Edge1/15/20201395
css.properties.will-change.scroll-position 📋Safari3/21/2016 Edge1/15/20201395
css.properties.word-break 📋Safari10/26/2007 Edge7/29/20152833
Internet Explorer: No version of Internet Explorer supports the initial value.Internet Explorer: Don't use -ms-word-break, which is a synonym for word-break.
css.properties.word-break.break-all 📋Safari10/26/2007 Edge7/29/20152833
css.properties.word-break.break-word 📋Safari10/26/2007 Edge7/29/20152833
css.properties.word-break.keep-all 📋Edge7/29/2015 Safari9/30/201563
css.properties.word-break.normal 📋Safari10/26/2007 Edge7/29/20152833
css.properties.word-spacing 📋Safari6/23/2003 Edge7/29/20154419
css.properties.word-spacing.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.word-spacing.percentages Safari10/22/2013 Edge2/14/20264498
css.properties.word-spacing.svg_elements Safari7/20/2011 Edge7/29/20151470
css.properties.writing-mode 📋Edge7/29/2015 Safari3/27/2017607
Firefox: Firefox 42 added support for bidirectional and RTL scripts in vertical modes.Firefox for Android: Firefox for Android 42 added support for bidirectional and RTL scripts in vertical modes.Internet Explorer: Internet Explorer's implementation differs from the specification.Internet Explorer: Internet Explorer's implementation differs from the specification.
css.properties.writing-mode.horizontal-tb Edge7/29/2015 Safari9/30/201563
css.properties.writing-mode.lr Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.lr-tb Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.rl Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.rl-tb Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.sideways-lr Edge1/17/2025 Safari3/31/202573
css.properties.writing-mode.sideways-rl Edge1/17/2025 Safari3/31/202573
css.properties.writing-mode.tb Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.tb-rl Edge7/29/2015 Safari3/27/2017607
css.properties.writing-mode.vertical-lr Edge7/29/2015 Safari9/30/201563
css.properties.writing-mode.vertical-rl Edge7/29/2015 Safari9/30/201563
css.properties.writing-mode.vertical_oriented_form_controls Safari3/5/2024 Edge4/18/202444
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 📋Safari9/30/2015 Edge1/15/20201568
css.properties.y 📋Safari9/30/2015 Edge1/15/20201568
css.properties.z-index 📋Safari6/23/2003 Edge7/29/20154419
css.properties.z-index.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.z-index.negative_values Safari6/23/2003 Edge7/29/20154419
css.properties.zoom 📋Safari3/18/2008 Edge7/29/20152689
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 Safari6/7/2010 Edge1/15/20203509
css.selectors.-webkit-meter-bar Safari7/20/2011 Edge1/15/20203101
css.selectors.-webkit-meter-even-less-good-value Safari7/20/2011 Edge1/15/20203101
css.selectors.-webkit-meter-inner-element Safari10/22/2013 Edge1/15/20202276
css.selectors.-webkit-meter-optimum-value Safari7/20/2011 Edge1/15/20203101
css.selectors.-webkit-meter-suboptimum-value Safari7/20/2011 Edge1/15/20203101
css.selectors.-webkit-progress-bar Safari10/22/2013 Edge1/15/20202276
css.selectors.-webkit-progress-inner-element Safari10/22/2013 Edge1/15/20202276
css.selectors.-webkit-progress-value Safari10/22/2013 Edge1/15/20202276
css.selectors.-webkit-resizer Safari6/8/2009 Edge1/15/20203873
css.selectors.-webkit-scrollbar Safari6/8/2009 Edge1/15/20203873
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 Safari6/8/2009 Edge1/15/20203873
css.selectors.-webkit-scrollbar-corner Safari6/8/2009 Edge1/15/20203873
css.selectors.-webkit-scrollbar-thumb Safari6/8/2009 Edge1/15/20203873
css.selectors.-webkit-scrollbar-track Safari6/8/2009 Edge1/15/20203873
css.selectors.-webkit-scrollbar-track-piece Safari6/8/2009 Edge1/15/20203873
css.selectors.-webkit-search-cancel-button Safari10/26/2007 Edge1/15/20204464
css.selectors.-webkit-search-results-button Safari10/26/2007 Edge1/15/20204464
css.selectors.-webkit-slider-runnable-track Edge1/15/2020 Safari9/16/20241706
css.selectors.-webkit-slider-thumb Edge1/15/2020 Safari9/16/20241706
css.selectors.active 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.active.non_a_elements Safari6/23/2003 Edge7/29/20154419
Safari on iOS: By default, Safari on iOS does not use the :active state unless there is a touchstart event handler on the relevant element or on the <body> element.WebView on iOS: By default, WebView on iOS does not use the :active state unless there is a touchstart event handler on the relevant element or on the <body> element.
css.selectors.active-view-transition 📋Edge5/17/2024 Safari9/16/2024122
css.selectors.active-view-transition-type 📋Edge5/17/2024 Safari12/11/2024208
css.selectors.after 📋Safari6/8/2009 Edge7/29/20152242
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 Safari10/22/2013 Edge7/29/2015645
css.selectors.any-link 📋Safari9/30/2015 Edge1/15/20201568
css.selectors.any-link.not_match_link Edge1/15/2020 Safari9/20/2021614
css.selectors.attribute 📋Safari10/26/2007 Edge7/29/20152833
css.selectors.attribute.case_insensitive_modifier Safari9/30/2015 Edge1/15/20201568
css.selectors.autofill 📋Safari9/20/2021 Edge2/9/2023507
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 📋Edge1/15/2020 Safari3/14/2022789
css.selectors.backdrop.dialog Edge1/15/2020 Safari3/14/2022789
css.selectors.backdrop.fullscreen Edge7/29/2015 Safari3/27/20232798
css.selectors.backdrop.inherit_from_originating_element Edge2/23/2024 Safari3/5/202411
css.selectors.backdrop.popover Edge6/2/2023 Safari9/18/2023108
css.selectors.before 📋Safari6/8/2009 Edge7/29/20152242
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 Safari10/22/2013 Edge7/29/2015645
css.selectors.checked 📋Safari3/18/2008 Edge7/29/20152689
Chrome: On macOS, styling <option> elements has no effect.Edge: On macOS, styling <option> elements has no effect.Firefox: From Firefox 56, <option> elements cannot be styled.Firefox: On macOS, styling <option> elements has no effect.Firefox for Android: From Firefox 56, <option> elements cannot be styled.Opera: On macOS, styling <option> elements has no effect.Safari: Styling <option> elements has no effect.Safari on iOS: Styling <option> elements has no effect.WebView on iOS: Styling <option> elements has no effect.
css.selectors.child 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.class 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.cue 📋Safari10/22/2013 Edge1/15/20202276
Firefox: From Firefox 69, only allowed properties apply to the ::cue pseudo-element with no argument. See Permitted properties for a list of the allowed properties.
css.selectors.cue.selector_argument Safari10/22/2013 Edge1/15/20202276
css.selectors.default 📋Safari6/7/2010 Edge1/15/20203509
css.selectors.defined 📋Safari9/20/2016 Edge1/15/20201212
css.selectors.descendant 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.details-content 📋Edge11/14/2024 Safari3/31/2025137
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 📋Safari3/27/2023 Edge12/7/2023255
css.selectors.disabled 📋Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 79, Edge did not recognize :disabled on the <fieldset> element.Internet Explorer: Internet Explorer does not recognize :disabled on the <fieldset> element.
css.selectors.empty 📋Safari3/18/2008 Edge7/29/20152689
css.selectors.enabled 📋Safari3/18/2008 Edge7/29/20152689
css.selectors.file-selector-button 📋Edge3/4/2021 Safari4/26/202153
css.selectors.first 📋Safari7/25/2012 Edge7/29/20151099
css.selectors.first-child 📋Safari3/18/2008 Edge7/29/20152689
Internet Explorer: Internet Explorer 7 doesn't update :first-child styles when elements are added dynamically.Internet Explorer: In Internet Explorer 8, if an element is inserted dynamically by clicking on a link, then the :first-child style isn't applied until the link loses focus.
css.selectors.first-letter 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.first-line 📋Safari6/23/2003 Edge7/29/20154419
Chrome: Before Chrome 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome: Before Chrome 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome Android: Before Chrome Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Chrome Android: Before Chrome Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Quest Browser: Before Quest Browser 5.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Quest Browser: Before Quest Browser 5.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Opera: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera Android: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Opera Android: From Opera 15 to Opera 49 (exclusive), the text-transform property does not work on ::first-line or :first-line pseudo-elements. See bug 40214861.Safari: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Safari on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.Samsung Internet: Before Samsung Internet 8.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.Samsung Internet: Before Samsung Internet 8.0, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView Android: Before WebView Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView Android: Before WebView Android 62, the text-transform property does not work on ::first-line pseudo-elements. See bug 40214861.WebView on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.WebView on iOS: The text-transform property does not work for ::first-line or :first-line pseudo-elements. See bug 3409.
css.selectors.first-of-type 📋Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.focus 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.focus-visible 📋Edge10/9/2020 Safari3/14/2022521
css.selectors.focus-within 📋Safari3/27/2017 Edge1/15/20201024
css.selectors.fullscreen 📋Edge7/29/2015 Safari3/27/20232798
Safari on iOS: Only available on iPad, not on iPhone.Safari on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.Safari on iOS: Only available on iPad, not on iPhone.WebView on iOS: Only available on iPad, not on iPhone.WebView on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.WebView on iOS: Only available on iPad, not on iPhone.
css.selectors.future 📋Safari10/22/2013 Edge1/15/20202276
css.selectors.grammar-error 📋Edge1/25/2024 Safari3/5/202440
css.selectors.has 📋Safari3/14/2022 Edge9/1/2022171
css.selectors.highlight 📋Edge9/1/2022 Safari12/11/2023466
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 📋Safari9/20/2016 Edge1/15/20201212
css.selectors.hostfunction 📋Safari9/20/2016 Edge1/15/20201212
Safari: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy.Safari on iOS: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy.WebView on iOS: Certain CSS selectors do not work (:host > .local-child) and styling slotted content (::slotted) is buggy.
css.selectors.hover 📋Safari4/29/2005 Edge7/29/20153743
Safari on iOS: As of Safari for iOS 7.1.2, tapping a clickable element causes the element to enter the :hover state. The element will remain in the :hover state until a different element has entered the :hover state.WebView on iOS: As of Safari for iOS 7.1.2, tapping a clickable element causes the element to enter the :hover state. The element will remain in the :hover state until a different element has entered the :hover state.
css.selectors.hover.a_elements Safari4/29/2005 Edge7/29/20153743
css.selectors.hover.all_elements Safari4/29/2005 Edge7/29/20153743
Edge: In Edge, hovering over an element and then scrolling up or down without moving the pointer will leave the element in the :hover state until the pointer is moved.Internet Explorer: In Internet Explorer 8 to Internet Explorer 11, hovering over an element and then scrolling up or down without moving the pointer will leave the element in the :hover state until the pointer is moved. See bug 926665.Internet Explorer: In Internet Explorer 9 (and possibly earlier), if a <table> has a parent with a non-auto width, overflow-x: auto;, the <table> has enough content to horizontally overflow its parent, and there are :hover styles set on elements within the table, then hovering over said elements will cause the <table>'s height to increase. See a live demo that triggers the bug. One workaround for the bug is to set min-height: 0%; (the % unit must be specified, since unitless and px don't work) on the <table>'s parent element.
css.selectors.id 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.in-range 📋Safari7/20/2011 Edge11/12/20151576
Chrome: Before Chrome 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome 52, it was changed to only match enabled read-write inputs.Chrome Android: Before Chrome Android 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome Android 52, it was changed to only match enabled read-write inputs.Firefox: Before Firefox 50, :in-range matched disabled and read-only inputs (see bug 1264157). In Firefox 50, it was changed to only match enabled read-write inputs.Quest Browser: Before Quest Browser 5.0, :in-range matched disabled and read-only inputs (see bug 41248615). In Quest Browser 5.0, it was changed to only match enabled read-write inputs.Opera: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Opera Android: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Safari: In Safari, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Safari on iOS: In Safari on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Samsung Internet: Before version 6.0, :in-range matched disabled and read-only inputs (see bug 41248615). In version 6.0, it was changed to only match enabled read-write inputs.WebView Android: Before version 52, :in-range matched disabled and read-only inputs (see bug 41248615). In version 52, it was changed to only match enabled read-write inputs.WebView on iOS: In WebView on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.
css.selectors.indeterminate 📋Safari10/26/2007 Edge7/29/20152833
css.selectors.indeterminate.checkbox Safari10/26/2007 Edge7/29/20152833
css.selectors.indeterminate.progress Safari7/20/2011 Edge7/29/20151470
css.selectors.indeterminate.radio Safari9/20/2016 Edge1/15/20201212
css.selectors.invalid 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.invalid.form Safari9/30/2015 Edge1/15/20201568
css.selectors.is 📋Safari9/16/2020 Edge1/21/2021127
Chrome: Doesn't support combinators.Chrome Android: Doesn't support combinators.Edge: Doesn't support combinators.Firefox: Doesn't support combinators.Firefox: See bug 906353.Firefox for Android: Doesn't support combinators.Firefox for Android: See bug 906353.Quest Browser: Doesn't support combinators.Opera: Doesn't support combinators.Opera Android: Doesn't support combinators.Safari: Doesn't support combinators.Safari on iOS: Doesn't support combinators.WebView Android: Doesn't support combinators.WebView on iOS: Doesn't support combinators.
css.selectors.is.forgiving_selector_list Safari9/16/2020 Edge1/21/2021127
css.selectors.lang 📋Safari3/18/2008 Edge7/29/20152689
css.selectors.last-child 📋Safari3/18/2008 Edge7/29/20152689
css.selectors.last-of-type 📋Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.left 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.link 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.link.not_match_link Edge7/29/2015 Safari9/20/20212245
css.selectors.list 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.marker 📋Safari4/12/2018 Edge10/9/2020911
Safari: Safari support is limited to color and font-size.Safari on iOS: Safari on iOS support is limited to color and font-size.WebView on iOS: WebView on iOS support is limited to color and font-size.
css.selectors.marker.animation_and_transition_support Edge10/9/2020 Safari4/26/2021199
css.selectors.modal 📋Safari7/20/2022 Edge9/1/202243
css.selectors.namespace 📋Safari10/26/2007 Edge7/29/20152833
css.selectors.nesting 📋Edge12/7/2023 Safari12/11/20234
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 Edge12/5/2025 Safari12/12/20257
css.selectors.next-sibling 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.Internet Explorer: Internet Explorer 7 doesn't update the style correctly when an element is dynamically placed before an element that matched the selector.Internet Explorer: In Internet Explorer 8, if an element is inserted dynamically by clicking on a link the first-child style isn't applied until the link loses focus.
css.selectors.not 📋Safari3/18/2008 Edge7/29/20152689
css.selectors.not.selector_list Safari9/30/2015 Edge1/21/20211940
css.selectors.nth-child 📋Safari3/18/2008 Edge7/29/20152689
Opera: Before Opera 15, Opera does not handle dynamically inserted elements for :nth-child().Opera Android: Before Opera 15, Opera does not handle dynamically inserted elements for :nth-child().
css.selectors.nth-child.of_syntax Safari9/30/2015 Edge3/13/20232721
css.selectors.nth-last-child 📋Safari3/18/2008 Edge7/29/20152689
css.selectors.nth-last-child.of_syntax Safari9/30/2015 Edge3/13/20232721
css.selectors.nth-last-of-type 📋Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.nth-of-type 📋Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.only-child 📋Safari3/18/2008 Edge7/29/20152689
css.selectors.only-child.no_parent_required Edge1/15/2020 Safari9/18/20231342
css.selectors.only-of-type 📋Safari3/18/2008 Edge7/29/20152689
Edge: Before Edge 16, Microsoft Edge treats all unknown elements (such as custom elements) as the same element type.Internet Explorer: Internet Explorer treats all unknown elements (such as custom elements) as the same element type.
css.selectors.optional 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.out-of-range 📋Safari7/20/2011 Edge11/12/20151576
css.selectors.part 📋Edge1/15/2020 Safari3/24/202069
css.selectors.past 📋Safari10/22/2013 Edge1/15/20202276
css.selectors.picture-in-picture 📋Safari3/24/2020 Edge2/9/20231052
css.selectors.placeholder 📋Safari3/27/2017 Edge1/15/20201024
css.selectors.placeholder-shown 📋Safari9/30/2015 Edge1/15/20201568
css.selectors.placeholder-shown.non_text_types Safari9/30/2015 Edge1/15/20201568
css.selectors.popover-open 📋Edge6/2/2023 Safari9/18/2023108
css.selectors.read-only 📋Safari6/8/2009 Edge11/12/20152348
css.selectors.read-write 📋Safari6/8/2009 Edge11/12/20152348
css.selectors.required 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.right 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.root 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.scope 📋Safari10/22/2013 Edge1/15/20202276
Firefox: Firefox 55 removes support for <style scoped> but not for the :scope pseudo-class, which is still supported. <style scoped> made it possible to explicitly set up element scopes, but ongoing discussions about the design of this feature as well as lack of other implementations resulted in the decision to remove it.Firefox for Android: Firefox for Android 55 removes support for <style scoped> but not for the :scope pseudo-class, which is still supported. <style scoped> made it possible to explicitly set up element scopes, but ongoing discussions about the design of this feature as well as lack of other implementations resulted in the decision to remove it.
css.selectors.scope.dom_api Safari10/22/2013 Edge1/15/20202276
css.selectors.selection 📋Safari10/24/2003 Edge7/29/20154296
css.selectors.slotted 📋Safari9/20/2016 Edge1/15/20201212
css.selectors.spelling-error 📋Edge1/25/2024 Safari3/5/202440
css.selectors.state 📋Safari3/5/2024 Edge5/17/202473
Chrome: Uses a dashed-ident (such as :--foo) instead of :state().Chrome Android: Uses a dashed-ident (such as :--foo) instead of :state().Edge: Uses a dashed-ident (such as :--foo) instead of :state().Quest Browser: Uses a dashed-ident (such as :--foo) instead of :state().Opera: Uses a dashed-ident (such as :--foo) instead of :state().Opera Android: Uses a dashed-ident (such as :--foo) instead of :state().Samsung Internet: Uses a dashed-ident (such as :--foo) instead of :state().WebView Android: Uses a dashed-ident (such as :--foo) instead of :state().
css.selectors.subsequent-sibling 📋Safari10/26/2007 Edge7/29/20152833
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.target 📋Safari4/15/2005 Edge7/29/20153757
css.selectors.target-text 📋Edge3/4/2021 Safari12/11/20241378
css.selectors.type 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.type.namespaces Safari4/15/2005 Edge7/29/20153757
css.selectors.universal 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.universal.namespaces Safari4/15/2005 Edge7/29/20153757
css.selectors.user-invalid 📋Safari5/18/2023 Edge11/2/2023168
css.selectors.user-valid 📋Safari5/18/2023 Edge11/2/2023168
css.selectors.valid 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.valid.form Safari9/30/2015 Edge1/15/20201568
css.selectors.view-transition 📋Edge1/12/2023 Safari9/16/2024613
css.selectors.view-transition-group 📋Edge1/12/2023 Safari9/16/2024613
css.selectors.view-transition-image-pair 📋Edge1/12/2023 Safari9/16/2024613
css.selectors.view-transition-new 📋Edge1/12/2023 Safari9/16/2024613
css.selectors.view-transition-old 📋Edge1/12/2023 Safari9/16/2024613
css.selectors.visited 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.visited.not_match_link Edge7/29/2015 Safari9/20/20212245
css.selectors.visited.privacy_measures Safari6/7/2010 Edge7/29/20151878
css.selectors.where 📋Safari9/16/2020 Edge1/21/2021127
css.selectors.where.forgiving_selector_list Safari9/16/2020 Edge1/21/2021127
css.types.abs 📋Safari3/14/2022 Edge6/26/20251200
css.types.acos 📋Safari3/14/2022 Edge3/13/2023364
css.types.anchor 📋Edge5/17/2024 Safari9/15/2025486
css.types.anchor-size 📋Edge5/17/2024 Safari9/15/2025486
css.types.anchor-size.inset_margin Edge1/17/2025 Safari9/15/2025241
css.types.angle 📋Safari6/8/2009 Edge7/29/20152242
css.types.angle.deg Safari6/8/2009 Edge7/29/20152242
css.types.angle.grad Safari6/8/2009 Edge7/29/20152242
css.types.angle.rad Safari6/8/2009 Edge7/29/20152242
css.types.angle.turn Safari6/8/2009 Edge7/29/20152242
css.types.angle-percentage 📋Safari6/8/2009 Edge7/29/20152242
css.types.asin 📋Safari3/14/2022 Edge3/13/2023364
css.types.atan 📋Safari3/14/2022 Edge3/13/2023364
css.types.atan2 📋Safari3/14/2022 Edge3/13/2023364
css.types.attr 📋Safari3/18/2008 Edge7/29/20152689
css.types.attr.declaration-value 📋Edge2/6/2025 Safari3/31/202553
css.types.basic-shape 📋Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.animation Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.circle 📋Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.ellipse 📋Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.inset 📋Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.path 📋Edge1/15/2020 Safari3/24/202069
css.types.basic-shape.path.clip-path 📋Safari3/24/2020 Edge1/21/2021303
css.types.basic-shape.path.offset-path 📋Edge1/15/2020 Safari9/12/2022971
css.types.basic-shape.polygon 📋Safari3/27/2017 Edge1/15/20201024
css.types.basic-shape.rect 📋Edge11/2/2023 Safari12/11/202339
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 📋Safari3/31/2025 Edge4/4/20254
css.types.basic-shape.xywh 📋Edge11/2/2023 Safari12/11/202339
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 📋Safari10/16/2014 Edge1/15/20201917
css.types.calc 📋Safari10/22/2013 Edge7/29/2015645
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 Safari3/27/2023 Edge11/2/2023220
css.types.calc.gradient_color_stops Safari7/25/2012 Edge7/29/20151099
css.types.calc.nested Safari9/19/2017 Edge10/17/201728
css.types.calc.number_values Safari7/25/2012 Edge7/29/20151099
css.types.calc.typed_division_produces_unitless_number 📋Edge9/5/2025 Safari9/15/202510
css.types.calc-keyword 📋Edge3/3/2022 Safari3/14/202211
css.types.calc-keyword.NaN Edge3/3/2022 Safari9/12/2022193
css.types.calc-keyword.e Safari3/14/2022 Edge2/9/2023332
css.types.calc-keyword.infinity Edge3/3/2022 Safari9/12/2022193
css.types.calc-keyword.pi Safari3/14/2022 Edge1/12/2023304
css.types.clamp 📋Edge1/15/2020 Safari3/24/202069
css.types.color 📋Safari6/23/2003 Edge7/29/20154419
css.types.color.color 📋Safari9/20/2021 Edge3/13/2023539
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 📋Safari12/12/2025 Edge1/21/202640
css.types.color.color.mixed_type_parameters Safari9/20/2021 Edge3/13/2023539
css.types.color.color.relative_syntax 📋Edge11/2/2023 Safari9/16/2024319
Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).
css.types.color.color-mix 📋Safari12/13/2022 Edge3/13/202390
css.types.color.currentcolor 📋Safari6/8/2009 Edge7/29/20152242
css.types.color.hsl 📋Safari3/18/2008 Edge7/29/20152689
css.types.color.hsl.alpha_parameter Safari3/25/2019 Edge1/15/2020296
css.types.color.hsl.mixed_type_parameters Edge1/25/2024 Safari9/16/2024235
css.types.color.hsl.relative_syntax 📋Edge5/17/2024 Safari9/16/2024122
Chrome: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Chrome Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Edge: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).Samsung Internet: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).
css.types.color.hsl.space_separated_parameters Safari3/25/2019 Edge1/15/2020296
css.types.color.hwb 📋Safari9/20/2021 Edge4/28/2022220
css.types.color.hwb.mixed_type_parameters Edge1/25/2024 Safari9/16/2024235
css.types.color.hwb.relative_syntax 📋Edge5/17/2024 Safari9/16/2024122
Chrome: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Chrome Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Edge: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).Samsung Internet: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).
css.types.color.lab 📋Safari9/20/2021 Edge3/13/2023539
css.types.color.lab.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.lab.relative_syntax 📋Safari3/27/2023 Edge11/2/2023220
css.types.color.lch 📋Safari9/20/2021 Edge3/13/2023539
css.types.color.lch.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.lch.relative_syntax 📋Edge11/2/2023 Safari9/16/2024319
Safari: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Safari on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).WebView on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).
css.types.color.light-dark 📋Edge3/22/2024 Safari5/13/202452
css.types.color.named-color 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: Internet Explorer 8 and later support gray color keywords spelled with an e (grey, darkgrey, darkslategrey, dimgrey, lightgrey, and lightslategrey). Internet Explorer 3 to Internet Explorer 7 only support the keywords spelled with a (gray, darkgray, darkslategray, dimgray, lightgray, and lightslategray).
css.types.color.named-color.rebeccapurple Edge7/29/2015 Safari9/30/201563
css.types.color.named-color.transparent 📋Safari3/18/2008 Edge7/29/20152689
css.types.color.oklab 📋Safari3/14/2022 Edge3/13/2023364
css.types.color.oklab.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.oklab.relative_syntax 📋Safari3/27/2023 Edge2/23/2024333
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 📋Safari3/14/2022 Edge3/13/2023364
css.types.color.oklch.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.oklch.relative_syntax 📋Edge2/23/2024 Safari9/16/2024206
Chrome: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Chrome Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Edge: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Opera: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Opera Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Safari: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Safari on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Samsung Internet: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.WebView Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.WebView on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).
css.types.color.rgb 📋Safari6/23/2003 Edge7/29/20154419
css.types.color.rgb.alpha_parameter Safari3/25/2019 Edge1/15/2020296
css.types.color.rgb.float_values Safari3/25/2019 Edge1/15/2020296
css.types.color.rgb.mixed_type_parameters Edge2/23/2024 Safari9/16/2024206
css.types.color.rgb.relative_syntax 📋Edge2/23/2024 Safari9/16/2024206
Chrome: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Chrome Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Edge: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Opera: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Opera Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Safari: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.Safari on iOS: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.Samsung Internet: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.WebView Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.WebView on iOS: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.
css.types.color.rgb.space_separated_parameters Safari3/25/2019 Edge1/15/2020296
css.types.color.rgb_hexadecimal_notation 📋Safari6/23/2003 Edge7/29/20154419
css.types.color.rgb_hexadecimal_notation.alpha_hexadecimal_notation Safari9/20/2016 Edge1/15/20201212
css.types.color.system-color 📋Safari6/23/2003 Edge7/29/20154419
css.types.color.system-color.accentcolor_accentcolortext 📋Safari5/18/2023 Edge7/21/202364
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.transparent Safari6/23/2003 Edge7/29/20154419
css.types.cos 📋Safari3/14/2022 Edge3/13/2023364
css.types.counter 📋Safari10/26/2007 Edge7/29/20152833
css.types.counters 📋Safari10/26/2007 Edge7/29/20152833
css.types.dimension 📋Safari6/23/2003 Edge7/29/20154419
css.types.easing-function 📋Safari3/18/2008 Edge7/29/20152689
css.types.easing-function.cubic-bezier 📋Safari7/25/2012 Edge7/29/20151099
css.types.easing-function.linear-function 📋Edge5/5/2023 Safari12/11/2023220
css.types.easing-function.steps 📋Safari7/20/2011 Edge7/29/20151470
css.types.easing-function.steps.jump Edge1/15/2020 Safari9/16/2020245
css.types.env 📋Safari4/12/2018 Edge1/15/2020643
css.types.env.safe-area-inset-bottom 📋Safari9/19/2017 Edge1/15/2020848
css.types.env.safe-area-inset-left 📋Safari9/19/2017 Edge1/15/2020848
css.types.env.safe-area-inset-right 📋Safari9/19/2017 Edge1/15/2020848
css.types.env.safe-area-inset-top 📋Safari9/19/2017 Edge1/15/2020848
css.types.exp 📋Safari3/14/2022 Edge12/7/2023633
css.types.filter-function 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.blur 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.brightness 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.contrast 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.drop-shadow 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.grayscale 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.hue-rotate 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.invert 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.opacity 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.saturate 📋Safari7/25/2012 Edge7/29/20151099
css.types.filter-function.sepia 📋Safari7/25/2012 Edge7/29/20151099
css.types.flex 📋Edge7/29/2015 Safari3/27/2017607
css.types.global_keywords Safari6/23/2003 Edge7/29/20154419
css.types.global_keywords.inherit 📋Safari6/23/2003 Edge7/29/20154419
css.types.global_keywords.initial 📋Safari2/2/2004 Edge11/12/20154301
css.types.global_keywords.revert 📋Safari3/21/2016 Edge7/16/20201578
css.types.global_keywords.revert-layer 📋Edge3/3/2022 Safari3/14/202211
css.types.global_keywords.unset 📋Edge11/12/2015 Safari3/21/2016130
css.types.gradient 📋Safari10/22/2013 Edge7/29/2015645
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 📋Safari3/25/2019 Edge1/15/2020296
css.types.gradient.conic-gradient.doubleposition Safari3/25/2019 Edge1/15/2020296
css.types.gradient.conic-gradient.hue_interpolation_method Safari12/13/2022 Edge3/13/202390
css.types.gradient.conic-gradient.interpolation_color_space Safari12/13/2022 Edge3/13/202390
css.types.gradient.conic-gradient.single_color_stop 📋Safari3/31/2025 Edge4/4/20254
css.types.gradient.linear-gradient 📋Safari10/22/2013 Edge7/29/2015645
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 Safari3/25/2019 Edge1/15/2020296
css.types.gradient.linear-gradient.hue_interpolation_method Safari12/13/2022 Edge3/13/202390
css.types.gradient.linear-gradient.interpolation_color_space Safari12/13/2022 Edge3/13/202390
css.types.gradient.linear-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.linear-gradient.premultiplied_gradients Edge1/15/2020 Safari9/20/2021614
css.types.gradient.linear-gradient.single_color_stop 📋Safari3/31/2025 Edge4/4/20254
css.types.gradient.linear-gradient.to Safari10/22/2013 Edge7/29/2015645
css.types.gradient.linear-gradient.unitless_0_angle Safari10/22/2013 Edge7/29/2015645
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 📋Safari10/22/2013 Edge7/29/2015645
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 Safari10/22/2013 Edge7/29/2015645
css.types.gradient.radial-gradient.doubleposition Safari3/25/2019 Edge1/15/2020296
css.types.gradient.radial-gradient.hue_interpolation_method Safari12/13/2022 Edge3/13/202390
css.types.gradient.radial-gradient.interpolation_color_space Safari12/13/2022 Edge3/13/202390
css.types.gradient.radial-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.radial-gradient.premultiplied_gradients Edge1/15/2020 Safari9/20/2021614
css.types.gradient.radial-gradient.single_color_stop 📋Safari3/31/2025 Edge4/4/20254
css.types.gradient.repeating-conic-gradient 📋Safari3/25/2019 Edge1/15/2020296
css.types.gradient.repeating-conic-gradient.hue_interpolation_method Safari12/13/2022 Edge3/13/202390
css.types.gradient.repeating-conic-gradient.interpolation_color_space Safari12/13/2022 Edge3/13/202390
css.types.gradient.repeating-conic-gradient.single_color_stop 📋Safari3/31/2025 Edge4/4/20254
css.types.gradient.repeating-linear-gradient 📋Safari10/22/2013 Edge7/29/2015645
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 Safari3/25/2019 Edge1/15/2020296
css.types.gradient.repeating-linear-gradient.hue_interpolation_method Safari12/13/2022 Edge3/13/202390
css.types.gradient.repeating-linear-gradient.interpolation_color_space Safari12/13/2022 Edge3/13/202390
css.types.gradient.repeating-linear-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.repeating-linear-gradient.single_color_stop 📋Safari3/31/2025 Edge4/4/20254
css.types.gradient.repeating-linear-gradient.to Safari10/22/2013 Edge7/29/2015645
css.types.gradient.repeating-linear-gradient.unitless_0_angle Safari10/22/2013 Edge7/29/2015645
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 📋Safari10/22/2013 Edge7/29/2015645
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 Safari10/22/2013 Edge7/29/2015645
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 Safari3/25/2019 Edge1/15/2020296
css.types.gradient.repeating-radial-gradient.hue_interpolation_method Safari12/13/2022 Edge3/13/202390
css.types.gradient.repeating-radial-gradient.interpolation_color_space Safari12/13/2022 Edge3/13/202390
css.types.gradient.repeating-radial-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.repeating-radial-gradient.single_color_stop 📋Safari3/31/2025 Edge4/4/20254
css.types.hypot 📋Safari3/14/2022 Edge12/7/2023633
css.types.image 📋Safari6/23/2003 Edge7/29/20154419
css.types.image.cross-fade 📋Safari9/20/2016 Edge1/15/20201212
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 📋Edge5/5/2023 Safari9/18/2023136
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.integer 📋Safari6/23/2003 Edge7/29/20154419
css.types.length 📋Safari6/23/2003 Edge7/29/20154419
css.types.length.Q Edge1/15/2020 Safari3/24/202069
css.types.length.cap Edge10/13/2023 Safari12/11/202359
css.types.length.ch Safari10/22/2013 Edge7/29/2015645
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 Safari9/12/202211
css.types.length.em Safari6/23/2003 Edge7/29/20154419
css.types.length.ex Safari6/23/2003 Edge7/29/20154419
css.types.length.ic Safari3/14/2022 Edge10/3/2022203
css.types.length.lh 📋Edge1/12/2023 Safari3/27/202374
css.types.length.rcap 📋Edge10/13/2023 Safari12/11/202359
css.types.length.rch 📋Edge3/13/2023 Safari12/11/2023273
css.types.length.rem Safari6/7/2010 Edge7/29/20151878
css.types.length.rex 📋Edge3/13/2023 Safari12/11/2023273
css.types.length.ric 📋Edge3/13/2023 Safari12/11/2023273
css.types.length.rlh 📋Edge3/13/2023 Safari3/27/202314
css.types.length.vb Safari3/14/2022 Edge12/5/2022266
css.types.length.vh Safari7/25/2012 Edge7/29/20151099
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length.vi Safari3/14/2022 Edge12/5/2022266
css.types.length.viewport_percentage_units_dynamic Safari3/14/2022 Edge12/5/2022266
css.types.length.viewport_percentage_units_large Safari3/14/2022 Edge12/5/2022266
css.types.length.viewport_percentage_units_small Safari3/14/2022 Edge12/5/2022266
css.types.length.vmax Safari10/22/2013 Edge10/17/20171456
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 Safari10/22/2013 Edge7/29/2015645
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length.vw Safari7/25/2012 Edge7/29/20151099
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length-percentage 📋Safari6/23/2003 Edge7/29/20154419
css.types.line-style 📋Safari6/23/2003 Edge7/29/20154419
css.types.log 📋Safari3/14/2022 Edge12/7/2023633
css.types.max 📋Safari4/12/2018 Edge1/15/2020643
css.types.min 📋Safari4/12/2018 Edge1/15/2020643
css.types.mod 📋Safari3/14/2022 Edge5/17/2024795
css.types.mod.mixed_type_parameters 📋Safari12/11/2023 Edge5/17/2024158
css.types.number 📋Safari6/23/2003 Edge7/29/20154419
css.types.number.scientific_notation Edge7/29/2015 Safari3/27/2017607
css.types.overflow 📋Safari6/23/2003 Edge7/29/20154419
Internet Explorer: From version 4 to 6, Internet Explorer enlarges an element with visible (default value) to fit the content inside it.
css.types.overflow.clip Edge4/15/2021 Safari9/12/2022515
css.types.overflow.overlay Safari9/17/2018 Edge6/2/20231719
Chrome: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Chrome Android: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Edge: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.Quest Browser: Before version false, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version false, the keyword aliases to the standard auto keyword. See bug 40444262.Opera: Before version 100, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 100, the keyword aliases to the standard auto keyword. See bug 40444262.Safari: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.Safari on iOS: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.WebView Android: Before version 114, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 114, the keyword aliases to the standard auto keyword. See bug 40444262.WebView on iOS: Before version 12, the overlay keyword caused non-standard behavior, allowing scrollbars to overlay content without taking up layout space. From version 12, the keyword aliases to the standard auto keyword. See bug 189811.
css.types.percentage 📋Safari6/23/2003 Edge7/29/20154419
css.types.position 📋Safari6/23/2003 Edge7/29/20154419
css.types.position.four_value_syntax Safari10/22/2013 Edge7/29/2015645
css.types.position.keyword_value_syntax Safari6/23/2003 Edge7/29/20154419
css.types.pow 📋Safari3/14/2022 Edge12/7/2023633
css.types.progress 📋Edge6/26/2025 Safari9/15/202581
css.types.ratio 📋Safari6/7/2010 Edge7/29/20151878
css.types.ray 📋Safari9/12/2022 Edge8/21/2023343
css.types.ray.position Edge8/21/2023 Safari12/11/2023112
css.types.ray.size Edge8/21/2023 Safari9/18/202328
css.types.rem 📋Safari3/14/2022 Edge5/17/2024795
css.types.rem.mixed_type_parameters 📋Safari12/11/2023 Edge5/17/2024158
css.types.resolution 📋Edge7/29/2015 Safari9/12/20222602
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.types.resolution.dpcm Edge7/29/2015 Safari9/12/20222602
css.types.resolution.dpi Edge7/29/2015 Safari9/12/20222602
css.types.resolution.dppx Edge7/29/2015 Safari9/12/20222602
css.types.resolution.x Edge1/15/2020 Safari9/12/2022971
css.types.round 📋Safari3/14/2022 Edge5/17/2024795
css.types.round.mixed_type_parameters 📋Safari12/11/2023 Edge5/17/2024158
css.types.shape 📋Safari4/15/2005 Edge7/29/20153757
css.types.shape.rect Safari4/15/2005 Edge7/29/20153757
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 📋Edge6/26/2025 Safari12/12/2025169
css.types.sibling-index 📋Edge6/26/2025 Safari12/12/2025169
css.types.sign 📋Safari3/14/2022 Edge6/26/20251200
css.types.sign.typed_division_produces_unitless_number 📋Edge9/5/2025 Safari9/15/202510
css.types.sin 📋Safari3/14/2022 Edge3/13/2023364
css.types.sqrt 📋Safari3/14/2022 Edge12/7/2023633
css.types.string 📋Safari6/23/2003 Edge7/29/20154419
css.types.string.unicode_escaped_characters Safari6/23/2003 Edge7/29/20154419
css.types.tan 📋Safari3/14/2022 Edge3/13/2023364
css.types.text-edge 📋Safari12/11/2024 Edge2/6/202557
css.types.text-edge.alphabetic 📋Safari12/11/2024 Edge2/6/202557
css.types.text-edge.cap 📋Safari12/11/2024 Edge2/6/202557
css.types.text-edge.ex 📋Safari12/11/2024 Edge2/6/202557
css.types.text-edge.text 📋Safari12/11/2024 Edge2/6/202557
css.types.time 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function 📋Safari3/18/2008 Edge7/29/20152689
Internet Explorer: Internet Explorer 9 supports 2D but not 3D transforms. In version 9, mixing 2D and 3D transform functions invalidates the entire property.
css.types.transform-function.matrix 📋Safari3/18/2008 Edge7/29/20152689
Firefox: Before Firefox 16, the translation values of matrix() could be <length>s, in addition to the standard <number>.
css.types.transform-function.matrix3d 📋Safari6/8/2009 Edge7/29/20152242
Firefox: Before Firefox 16, the translation values of matrix3d() could be <length>s, in addition to the standard <number>.
css.types.transform-function.perspective 📋Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.perspective.none 📋Edge1/6/2022 Safari3/14/202267
css.types.transform-function.rotate 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.rotate3d 📋Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.rotateX 📋Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.rotateY 📋Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.rotateZ 📋Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.scale 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.scale3d 📋Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.scaleX 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.scaleY 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.scaleZ 📋Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.skew 📋Safari3/18/2008 Edge7/29/20152689
Firefox: Firefox 14 removed experimental support for skew(), but it was reintroduced in Firefox 15.
css.types.transform-function.skewX 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.skewY 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.translate 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.translate3d 📋Safari6/8/2009 Edge7/29/20152242
css.types.transform-function.translateX 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.translateY 📋Safari3/18/2008 Edge7/29/20152689
css.types.transform-function.translateZ 📋Safari6/8/2009 Edge7/29/20152242
css.types.url 📋Safari6/23/2003 Edge7/29/20154419
css.types.var 📋Safari3/21/2016 Edge4/5/2017380