Time to Stable

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

Example Comparisons
Browsers
Features

Summary

A count of the number of APIs that landed in A first and B last.
Last in ChromeLast in FirefoxLast in SafariLast in Edge
First in Chrome 352212357
First in Firefox 16333881
First in Safari 51641033
First in Edge 53823

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

3419 APIs took an average of 2374.41 days to become available to use.

API breakdown:

Average time to landing by year of first landing

If a feature landed in the earliest browser in 20XX it took Y days on average to become available in the last browser (when considering Chrome, Firefox, Safari, and Edge). TTA (time to available).
CSS APIsCSS TTAHTML APIsHTML TTA
2003 4244476.121114419.00
2004 1474354.652323970.81
2005 713775.1743689.50
2006 113568.2743625.00
2007 903148.9322833.00
2008 1013093.48272857.78
2009 872562.4642246.50
2010 562887.50522192.73
2011 782610.40382467.05
2012 1151656.25232566.00
2013 1202024.2091449.78
2014 1772212.05111584.91
2015 2791654.5391466.11
2016 771901.64191496.32
2017 1781130.5171262.14
2018 771226.61141507.64
2019 150971.8014905.36
2020 481078.0231438.67
2021 35740.863657.67
2022 124417.388843.75
2023 83500.7711261.18
2024 194497.232153.50
2025 83172.437289.29

The Tortoise and the Hare

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

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

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

Sprinters

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

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

For a given year, if a feature landed in Browser X first, how many days it take on average to be available in Chrome, Firefox, Safari, and Edge. TTA (time to available).
Year CSSCSS TTAHTMLHTML TTA
2003
  Safari 4244476.121114419.00
2004
  Firefox 824452.502203952.76
  Safari 654231.20124301.67
2005
  Firefox 523752.3313529.00
  Safari 193837.6833743.00
2006
  Firefox 113568.2743625.00
2007
  Safari 903148.9322833.00
2008
  Safari 532793.42192689.00
  Chrome 133568.1573353.00
  Firefox 353371.5412598.00
2009
  Firefox 83239.380NaN
  Safari 622511.1832242.00
  Chrome 172430.9412260.00
2010
  Safari 313134.58112658.82
  Chrome 212533.62412067.68
  Firefox 42830.500NaN
2011
  Firefox 352818.80172628.29
  Chrome 251911.96212336.52
  Safari 183175.220NaN
2012
  Firefox 511640.120NaN
  Chrome 611574.23173055.82
  Safari 33598.3361178.17
2013
  Firefox 321460.7271604.57
  Chrome 541839.962908.00
  Safari 342847.150NaN
2014
  Firefox 1112374.4111919.00
  Chrome 601952.40101551.50
  Safari 61804.830NaN
2015
  Chrome 391799.1561240.67
  Safari 161972.130NaN
  Firefox 1881718.4411658.00
  Edge 361022.9722046.50
2016
  Safari 101987.1021395.00
  Firefox 322036.220NaN
  Chrome 341772.62171508.24
  Edge 11127.000NaN
2017
  Chrome 461362.7051345.00
  Safari 24891.0411024.00
  Firefox 1021117.7511086.00
  Edge 6525.170NaN
2018
  Firefox 271526.670NaN
  Edge 3694.000NaN
  Chrome 421105.02111462.91
  Safari 5947.2031671.67
2019
  Firefox 1201000.640NaN
  Safari 12689.924773.75
  Chrome 18967.4410958.00
2020
  Safari 5798.400NaN
  Edge 3699.3311398.00
  Chrome 121430.5821459.00
  Firefox 281017.430NaN
2021
  Chrome 15672.473657.67
  Safari 11803.360NaN
  Firefox 9778.440NaN
2022
  Edge 14227.500NaN
  Firefox 14350.500NaN
  Safari 79448.852347.50
  Chrome 17482.5961009.17
2023
  Firefox 24487.420NaN
  Chrome 54514.987319.00
  Safari 5411.404160.00
2024
  Chrome 184512.972153.50
  Safari 6204.670NaN
  Firefox 4212.000NaN
2025
  Chrome 34250.357289.29
  Safari 41133.070NaN
  Firefox 843.000NaN

Plodders

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

For a feature that first landed in year X, how many days did it take on average for the last browser to catch up across Chrome, Firefox, Safari, and Edge. TTA (time to available).
Year CSS countCSS TTAHTML countHTML TTA
2003
  Edge 4194459.231114419.00
  Firefox 55891.600NaN
2004
  Edge 1424309.082273953.56
  Safari 55648.8014521.00
  Firefox 0NaN15475.00
  Chrome 0NaN34591.00
2005
  Edge 693780.4843689.50
  Safari 23592.000NaN
2006
  Edge 103363.1033200.00
  Safari 15620.0014900.00
2007
  Firefox 143781.500NaN
  Edge 753031.6122833.00
  Chrome 13092.000NaN
2008
  Edge 932966.03272857.78
  Safari 34724.330NaN
  Firefox 54485.400NaN
2009
  Edge 822517.3342246.50
  Firefox 42707.500NaN
  Safari 15683.000NaN
2010
  Edge 522834.69492056.90
  Firefox 43574.0025251.00
  Safari 0NaN12732.00
2011
  Safari 202892.35132870.08
  Edge 572522.86252257.48
  Chrome 11961.000NaN
2012
  Safari 331818.9152902.60
  Edge 741507.08111766.73
  Firefox 62740.1773581.57
  Chrome 21240.000NaN
2013
  Edge 872247.4731251.33
  Safari 211066.0521497.00
  Chrome 41205.0041575.00
  Firefox 82520.880NaN
2014
  Safari 362505.6171516.86
  Edge 1352150.3621198.00
  Firefox 51880.0022210.00
  Chrome 11631.000NaN
2015
  Firefox 351546.091909.00
  Edge 2001580.5971300.29
  Chrome 5333.4013184.00
  Safari 392300.460NaN
2016
  Firefox 102191.6061749.00
  Safari 282412.5451575.00
  Edge 381457.1181257.63
  Chrome 11589.000NaN
2017
  Edge 1351065.7021055.00
  Firefox 171154.0641252.75
  Safari 251493.4411714.00
  Chrome 1406.000NaN
2018
  Edge 10948.1021264.50
  Safari 611310.5141557.00
  Firefox 5821.0081543.75
  Chrome 1922.000NaN
2019
  Safari 125992.667867.57
  Edge 15821.473690.67
  Firefox 10936.5041132.50
2020
  Firefox 71342.0021549.50
  Safari 221157.5511217.00
  Edge 19888.680NaN
2021
  Safari 20673.551755.00
  Firefox 8668.632609.00
  Edge 71015.710NaN
2022
  Firefox 67393.188843.75
  Safari 25405.000NaN
  Edge 31491.710NaN
  Chrome 144.000NaN
2023
  Safari 36562.610NaN
  Edge 9257.332193.00
  Firefox 38499.849276.33
2024
  Firefox 175518.691280.00
  Safari 11372.09127.00
  Edge 8199.880NaN
2025
  Firefox 70195.434346.50
  Edge 1243.080NaN
  Safari 1115.003213.00

Stable APIs

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

Raw Data

Quick Links:

CSS Data

API First Browser Date Last Browser Date Days Notes
css.at-rules.charset 📋Firefox11/29/2005 Edge7/29/20153529
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 Firefox2/14/2023166
css.at-rules.counter-style 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.additive-symbols 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.fallback 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.negative 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.pad 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.prefix 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.range 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.suffix 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.counter-style.symbols 📋Firefox10/14/2014 Safari9/18/20233261
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 📋Firefox10/14/2014 Safari9/18/20233261
css.at-rules.font-face 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.OpenType_COLRv0 Firefox7/22/2014 Edge1/15/20202003
css.at-rules.font-face.WOFF 📋Firefox6/30/2009 Edge7/29/20152220
css.at-rules.font-face.WOFF_2 📋Chrome7/16/2014 Safari9/20/2016797
Safari: Supported only on macOS 10.12 (Sierra) and later.
css.at-rules.font-face.font-display 📋Chrome7/25/2017 Edge1/15/2020904
css.at-rules.font-face.font-family 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-face.font-feature-settings 📋Firefox12/1/2014 Edge9/5/20253931
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 Firefox9/5/2018527
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 📋Chrome7/20/2021 Safari9/18/2023790
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 Firefox9/5/2018351
css.at-rules.font-face.src.tech_keyword Firefox11/15/2022 Safari9/18/2023307
css.at-rules.font-face.unicode-range 📋Safari3/18/2008 Edge7/29/20152689
css.at-rules.font-feature-values 📋Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.annotation Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.character-variant Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.historical-forms Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.ornaments Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.styleset Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.stylistic Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-feature-values.swash Firefox12/1/2014 Edge3/13/20233024
css.at-rules.font-palette-values 📋Safari3/14/2022 Firefox11/15/2022246
css.at-rules.font-palette-values.base-palette 📋Safari3/14/2022 Firefox11/15/2022246
css.at-rules.font-palette-values.font-family 📋Safari3/14/2022 Firefox11/15/2022246
css.at-rules.font-palette-values.override-colors 📋Safari3/14/2022 Firefox11/15/2022246
css.at-rules.import 📋Safari6/23/2003 Edge7/29/20154419
css.at-rules.import.layer 📋Firefox2/8/2022 Safari3/14/202234
css.at-rules.import.supports 📋Firefox7/4/2023 Safari5/13/2024314
css.at-rules.keyframes 📋Firefox10/9/2012 Safari9/30/20151086
css.at-rules.keyframes.ignore_important_declarations Firefox2/19/2013 Edge1/15/20202521
css.at-rules.layer 📋Firefox2/8/2022 Safari3/14/202234
css.at-rules.media 📋Firefox11/9/2004 Edge7/29/20153914
css.at-rules.media.-webkit-device-pixel-ratio 📋Safari10/26/2007 Firefox10/23/20184015
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 Firefox10/23/20184015
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 Firefox10/23/20184015
Firefox: Implemented as an alias for min--moz-device-pixel-ratio.Firefox for Android: Implemented as an alias for min--moz-device-pixel-ratio.
css.at-rules.media.-webkit-transform-3d 📋Chrome5/21/2009 Firefox9/20/20162679
css.at-rules.media.any-hover 📋Chrome3/3/2015 Firefox12/11/20181379
css.at-rules.media.any-pointer 📋Chrome3/3/2015 Firefox12/11/20181379
css.at-rules.media.aspect-ratio 📋Firefox6/30/2009 Edge7/29/20152220
css.at-rules.media.calc 📋Firefox3/13/2018 Edge1/15/2020673
css.at-rules.media.color 📋Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.color-gamut 📋Safari9/20/2016 Firefox2/14/20232338
css.at-rules.media.color-gamut.p3 📋Safari9/20/2016 Firefox2/14/20232338
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 Firefox2/14/20232338
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 Firefox2/14/20232338
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.device-aspect-ratio 📋Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.device-height 📋Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.device-width 📋Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.display-mode 📋Chrome4/14/2015 Edge1/15/20201737
css.at-rules.media.display-mode.browser 📋Chrome4/14/2015 Edge1/15/20201737
Firefox for Android: display-mode: browser is always true.Safari: In a Safari browser window, display-mode: browser is always true, even in a macOS Full Screen window or when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In the Safari app, display-mode: browser is always true, even when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).WebView on iOS: In the Safari app, display-mode: browser is always true, even when using the Fullscreen API. In an installed web application, other display-mode values are true only when given by a supported manifest display member value. See mdn/browser-compat-data#18807 (comment).
css.at-rules.media.display-mode.fullscreen 📋Chrome12/1/2015 Edge1/15/20201506
Firefox: In Firefox's "Full Screen" user interface, browser tabs and other user interface appear but display-mode: fullscreen is true.Safari: In a Safari browser window, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In the Safari app, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).Safari on iOS: In an installed web application with the display manifest member set to standalone, display-mode: fullscreen is true, even though the system status bar is visible. See bug 264218.WebView on iOS: In the Safari app, display-mode: fullscreen is never true, even when using the Fullscreen API. See mdn/browser-compat-data#18807 (comment).WebView on iOS: In an installed web application with the display manifest member set to standalone, display-mode: fullscreen is true, even though the system status bar is visible. See bug 264218.
css.at-rules.media.display-mode.minimal-ui 📋Chrome4/14/2015 Edge1/15/20201737
Firefox: display-mode: minimal-ui is never true.Safari: display-mode: minimal-ui is never true.Safari on iOS: display-mode: minimal-ui is never true.WebView on iOS: display-mode: minimal-ui is never true.
css.at-rules.media.display-mode.standalone 📋Chrome4/14/2015 Edge1/15/20201737
Firefox: display-mode: standalone is never true.Safari on iOS: In an installed web application with the display manifest member set to standalone, display-mode: standalone is false and display-mode: fullscreen is true. See bug 264218.WebView on iOS: In an installed web application with the display manifest member set to standalone, display-mode: standalone is false and display-mode: fullscreen is true. See bug 264218.
css.at-rules.media.dynamic-range 📋Safari3/24/2020 Firefox5/3/2022770
css.at-rules.media.forced-colors 📋Edge1/15/2020 Safari9/12/2022971
css.at-rules.media.grid 📋Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.height 📋Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.hover 📋Chrome10/7/2014 Firefox12/11/20181526
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 Firefox11/9/2004 Edge7/29/20153914
css.at-rules.media.monochrome 📋Firefox10/24/2006 Edge1/15/20204831
css.at-rules.media.nested-queries Firefox3/13/2012 Edge7/29/20151233
css.at-rules.media.or_syntax Firefox12/11/2018 Safari3/27/20231567
css.at-rules.media.orientation 📋Firefox10/24/2006 Edge7/29/20153200
css.at-rules.media.overflow-block 📋Firefox3/19/2019 Safari9/18/20231644
css.at-rules.media.overflow-inline 📋Firefox3/19/2019 Safari9/18/20231644
css.at-rules.media.pointer 📋Chrome3/3/2015 Firefox12/11/20181379
css.at-rules.media.prefers-color-scheme 📋Safari3/25/2019 Edge1/15/2020296
css.at-rules.media.prefers-contrast 📋Safari4/26/2021 Firefox5/31/2022400
css.at-rules.media.prefers-reduced-motion 📋Safari3/27/2017 Edge1/15/20201024
css.at-rules.media.range_syntax Firefox6/28/2022 Safari3/27/2023272
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 📋Firefox11/8/2011 Safari9/12/20223961
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.at-rules.media.scan 📋Firefox10/23/2018 Safari3/27/20231616
css.at-rules.media.scripting 📋Firefox5/9/2023 Edge12/7/2023212
css.at-rules.media.update 📋Firefox6/28/2022 Safari9/18/2023447
css.at-rules.media.width 📋Firefox10/24/2006 Edge7/29/20153200
css.at-rules.namespace 📋Safari6/23/2003 Edge7/29/20154419
css.at-rules.page 📋Chrome5/21/2009 Safari12/11/20245683
css.at-rules.page.size 📋Chrome10/25/2011 Safari12/11/20244796
css.at-rules.page.size.jis-b4 📋Chrome5/19/2020 Safari12/11/20241667
css.at-rules.page.size.jis-b5 📋Chrome5/19/2020 Safari12/11/20241667
css.at-rules.position-try 📋Chrome5/14/2024 Firefox1/13/2026609
css.at-rules.property 📋Chrome8/25/2020 Firefox7/9/20241414
css.at-rules.property.inherits 📋Chrome8/25/2020 Firefox7/9/20241414
css.at-rules.property.initial-value 📋Chrome8/25/2020 Firefox7/9/20241414
css.at-rules.property.syntax 📋Chrome8/25/2020 Firefox7/9/20241414
css.at-rules.scope 📋Chrome10/10/2023 Firefox12/9/2025791
css.at-rules.starting-style 📋Chrome9/12/2023 Firefox8/6/2024329
css.at-rules.supports 📋Firefox6/25/2013 Safari9/30/2015827
css.at-rules.supports.font-format Firefox10/18/2022 Safari9/18/2023335
css.at-rules.supports.font-tech Firefox10/18/2022 Safari9/18/2023335
css.at-rules.supports.selector Firefox9/3/2019 Safari4/26/2021601
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-text-fill-color 📋Safari10/26/2007 Firefox9/20/20163252
css.properties.-webkit-text-security Safari10/26/2007 Firefox6/6/20235702
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.accent-color 📋Chrome8/31/2021 Safari3/14/2022195
Chrome Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Quest Browser: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Opera Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.Safari: Safari does not maintain minimum contrast for legibility of the control. See bug 244233.Safari on iOS: Safari on iOS does not maintain minimum contrast for legibility of the control. See bug 244233.Samsung Internet: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.WebView Android: Chrome for Android does not maintain minimum contrast for legibility of the control. See bug 343503163.WebView on iOS: WebView on iOS does not maintain minimum contrast for legibility of the control. See bug 244233.
css.properties.accent-color.auto Chrome8/31/2021 Safari3/14/2022195
css.properties.align-content 📋Chrome8/20/2013 Safari9/30/2015771
css.properties.align-content.block_context 📋Safari3/5/2024 Firefox4/16/202442
css.properties.align-content.flex_context 📋Chrome7/31/2012 Safari9/30/20151156
css.properties.align-content.flex_context.baseline Safari9/30/2015 Edge1/15/20201568
css.properties.align-content.flex_context.first_baseline Firefox3/7/2017 Edge1/15/20201044
css.properties.align-content.flex_context.safe_unsafe Firefox10/23/2018 Safari7/29/20242106
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 Firefox3/7/2017 Edge1/15/20201044
css.properties.align-content.flex_context.start_end Firefox3/8/2016 Safari7/20/20222325
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 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.align-content.normal 📋Chrome8/20/2013 Safari9/30/2015771
css.properties.align-items 📋Firefox4/2/2013 Safari9/30/2015911
css.properties.align-items.anchor-center 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.align-items.flex_context 📋Firefox4/2/2013 Chrome7/20/20161205
Chrome: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome implements the new behavior beginning with Chrome 52.Chrome Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome Android implements the new behavior beginning with Chrome Android 52.Firefox: Multi-line flexbox has been supported since Firefox 28.Firefox for Android: Multi-line flexbox has been supported since Firefox for Android 28.Internet Explorer: In Internet Explorer 10 and 11, if column flex items have align-items: center; set on them and their content is too large, then they will overflow the bounds of their container. See Flexbug #2.Opera: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Opera implements the new behavior beginning with Opera 39.Opera Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Opera Android implements the new behavior beginning with Opera Android 41.Samsung Internet: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Samsung Internet implements the new behavior beginning with Samsung Internet 6.0.WebView Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. WebView Android implements the new behavior beginning with WebView Android 52.
css.properties.align-items.flex_context.baseline Chrome7/31/2012 Edge1/15/20202724
css.properties.align-items.flex_context.first_baseline Firefox3/7/2017 Edge1/15/20201044
css.properties.align-items.flex_context.last_baseline Firefox3/7/2017 Safari12/13/20222107
css.properties.align-items.flex_context.safe_unsafe Firefox10/23/2018 Safari7/29/20242106
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 Firefox3/8/2016 Safari3/14/20222197
css.properties.align-items.grid_context 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.align-items.grid_context.start_end Firefox3/7/2017 Edge1/15/20201044
css.properties.align-self 📋Firefox4/2/2013 Safari9/30/2015911
css.properties.align-self.anchor-center 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.align-self.auto 📋Chrome7/31/2012 Edge1/15/20202724
css.properties.align-self.flex_context 📋Firefox4/2/2013 Edge7/29/2015848
Chrome: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome implements the new behavior beginning with Chrome 52.Chrome Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Chrome Android implements the new behavior beginning with Chrome Android 52.Firefox: Before Firefox 27, only single-line flexbox is supported.Firefox for Android: Before Firefox for Android 27, only single-line flexbox is supported.Samsung Internet: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. Samsung Internet implements the new behavior beginning with Samsung Internet 6.0.WebView Android: Older versions of the specification treat absolute positioned children as though they are a 0 by 0 flex item. Later specification versions take the children out of the flow and set their positions based on align and justify properties. WebView Android implements the new behavior beginning with WebView Android 52.
css.properties.align-self.flex_context.baseline 📋Chrome7/31/2012 Edge1/15/20202724
css.properties.align-self.flex_context.first_baseline Firefox3/7/2017 Edge1/15/20201044
css.properties.align-self.flex_context.last_baseline Firefox3/7/2017 Safari12/13/20222107
css.properties.align-self.flex_context.safe_unsafe Firefox10/23/2018 Safari7/29/20242106
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 Firefox3/8/2016 Safari3/14/20222197
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 📋Firefox3/7/2017 Edge10/17/2017224
Internet Explorer: Internet Explorer 10 and 11 have the property -ms-grid-row-align, which acts in a similar way to align-self.
css.properties.align-self.normal 📋Chrome7/31/2012 Edge1/15/20202724
css.properties.align-self.stretch 📋Chrome7/31/2012 Edge1/15/20202724
css.properties.all 📋Firefox2/4/2014 Edge1/15/20202171
css.properties.anchor-name 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.anchor-name.none 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.anchor-scope 📋Chrome11/12/2024 Firefox1/13/2026427
css.properties.anchor-scope.all 📋Chrome11/12/2024 Firefox1/13/2026427
css.properties.anchor-scope.none 📋Chrome11/12/2024 Firefox1/13/2026427
css.properties.animation 📋Firefox10/9/2012 Safari9/30/20151086
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 Firefox7/4/2023295
css.properties.animation-composition.accumulate 📋Safari9/12/2022 Firefox7/4/2023295
css.properties.animation-composition.add 📋Safari9/12/2022 Firefox7/4/2023295
css.properties.animation-composition.replace 📋Safari9/12/2022 Firefox7/4/2023295
css.properties.animation-delay 📋Firefox10/9/2012 Safari9/30/20151086
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 📋Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-direction.alternate 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-direction.alternate-reverse 📋Chrome5/15/2012 Edge7/29/20151170
css.properties.animation-direction.normal 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-direction.reverse 📋Chrome5/15/2012 Edge7/29/20151170
css.properties.animation-duration 📋Firefox10/9/2012 Safari9/30/20151086
Internet Explorer: Once the element has loaded, changing the value of this property has no effect.
css.properties.animation-fill-mode 📋Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-fill-mode.backwards 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-fill-mode.both 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-fill-mode.forwards 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-fill-mode.none 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.animation-iteration-count 📋Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-iteration-count.infinite 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-name 📋Firefox10/9/2012 Safari9/30/20151086
css.properties.animation-name.none 📋Safari6/8/2009 Edge7/29/20152242
css.properties.animation-play-state 📋Firefox10/9/2012 Safari9/30/20151086
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-timeline 📋Firefox2/14/2023 Safari9/15/2025944
css.properties.animation-timeline.scroll 📋Firefox2/14/2023 Safari9/15/2025944
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 📋Firefox6/6/2023 Safari9/15/2025832
css.properties.animation-timing-function 📋Firefox10/9/2012 Safari9/30/20151086
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 Firefox1/29/2019 Safari9/16/2020596
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 📋Chrome5/19/2020 Safari3/14/2022664
css.properties.appearance.button 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.checkbox 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.listbox 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.menulist 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.menulist-button 📋Safari10/26/2007 Firefox8/25/20204687
Firefox: See bug 1481615.Firefox for Android: See bug 1481615.
css.properties.appearance.meter 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.none 📋Safari10/26/2007 Firefox6/13/20173518
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 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.radio 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.searchfield 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.textarea 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.appearance.textfield 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.aspect-ratio 📋Chrome1/19/2021 Safari9/20/2021244
css.properties.aspect-ratio.auto 📋Chrome1/19/2021 Safari9/20/2021244
css.properties.backdrop-filter 📋Chrome7/30/2019 Safari9/16/20241875
Firefox: Before Firefox 123, the property was not supported on systems with unknown GPU vendor (see bug 1868737).Firefox for Android: Before Firefox for Android 123, the property was not supported on systems with unknown GPU vendor (see bug 1868737).
css.properties.backdrop-filter.none 📋Safari9/30/2015 Firefox7/26/20222491
css.properties.backface-visibility 📋Firefox10/9/2012 Safari3/14/20223443
css.properties.backface-visibility.hidden 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.backface-visibility.visible 📋Chrome6/7/2011 Edge7/29/20151513
css.properties.background 📋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 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.bottom 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.center 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.content-box 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.fixed 📋Chrome10/25/2011 Edge4/5/20171989
css.properties.background.left 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.background.local 📋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 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Firefox10/24/2006 Safari3/14/20225620
Safari: fixed is recognized but has no effect. See related bug 219324.Safari on iOS: fixed is recognized but has no effect. See bug 275247.WebView on iOS: fixed is recognized but has no effect. See bug 275247.
css.properties.background-attachment.local 📋Chrome12/11/2008 Safari3/14/20224841
Safari: local is recognized but has no effect. See bug 219324.Safari on iOS: local is recognized but has no effect. See bug 219324.Safari on iOS: If -webkit-overflow-scrolling: touch is set, then local has no effect.WebView on iOS: local is recognized but has no effect. See bug 219324.WebView on iOS: If -webkit-overflow-scrolling: touch is set, then local has no effect.
css.properties.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 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.background-clip 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: Chrome accepts alternate synonyms to its values: padding, border, and content.Chrome Android: Chrome Android accepts alternate synonyms to its values: padding, border, and content.Edge: Since Edge 79, accepts alternate synonyms to its values: padding, border, and content.Firefox: Used the -moz-background-clip: padding | border syntax.Internet Explorer: In IE 7 and IE 8 of Internet Explorer, this property always behaved like background-clip: padding-box when overflow was hidden, auto, or scroll.Quest Browser: Quest Browser accepts alternate synonyms to its values: padding, border, and content.Opera: Opera accepts alternate synonyms to its values: padding, border, and content.Opera Android: Opera accepts alternate synonyms to its values: padding, border, and content.Safari: Safari accepts alternate synonyms to its values: padding, border, and content.Safari on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.Samsung Internet: Samsung Internet accepts alternate synonyms to its values: padding, border, and content.WebView Android: WebView Android accepts alternate synonyms to its values: padding, border, and content.WebView on iOS: Safari accepts alternate synonyms to its values: padding, border, and content.
css.properties.background-clip.border-box 📋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 📋Firefox9/20/2016 Edge12/7/20232634
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 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Chrome12/11/2008 Edge7/29/20152421
Chrome: Some versions support only experimental gradients prefixed with -webkit.Chrome Android: Some versions support only experimental gradients prefixed with -webkit.Firefox: Some versions support only experimental gradients prefixed with -moz.Firefox for Android: Some versions support only experimental gradients prefixed with -moz.Quest Browser: Some versions support only experimental gradients prefixed with -webkit.Opera: Some versions support only experimental gradients prefixed with -o.Opera Android: Some versions support only experimental gradients prefixed with -webkit.Safari: Some versions support only experimental gradients prefixed with -webkit.Safari on iOS: Some versions support only experimental gradients prefixed with -webkit.Samsung Internet: Some versions support only experimental gradients prefixed with -webkit.WebView Android: Some versions support only experimental gradients prefixed with -webkit.WebView on iOS: Some versions support only experimental gradients prefixed with -webkit.
css.properties.background-image.image-set 📋Firefox6/1/2021 Safari9/18/2023839
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 Firefox6/5/2012 Edge7/29/20151149
css.properties.background-position.top 📋Safari6/23/2003 Edge1/15/20206050
css.properties.background-position-x 📋Safari6/23/2003 Firefox9/20/20164838
css.properties.background-position-x.side-relative_values Firefox9/20/2016 Edge1/21/20263410
css.properties.background-position-y 📋Safari6/23/2003 Firefox9/20/20164838
css.properties.background-position-y.side-relative_values Firefox9/20/2016 Edge1/21/20263410
css.properties.background-repeat 📋Safari6/23/2003 Edge7/29/20154419
css.properties.background-repeat.2-value Chrome9/15/2009 Edge7/29/20152143
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 📋Chrome10/1/2013 Firefox9/20/20161085
css.properties.background-repeat.space 📋Chrome10/1/2013 Firefox9/20/20161085
css.properties.background-size 📋Chrome9/15/2009 Edge7/29/20152143
Chrome: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Chrome Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Quest Browser: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Opera Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Opera Android: Opera 9.5's computation of the background positioning area is incorrect for fixed backgrounds. Opera 9.5 also interprets the two-value form as a horizontal scaling factor and, from appearances, a vertical clipping dimension. This has been fixed in Opera 10.Safari: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Safari on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.Samsung Internet: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView Android: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.WebView on iOS: WebKit-based browsers originally implemented an older draft of CSS3 background-size in which an omitted second value is treated as duplicating the first value; this draft does not include the contain or cover keywords.
css.properties.background-size.auto 📋Safari10/26/2007 Edge7/29/20152833
css.properties.background-size.contain 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.background-size.cover 📋Chrome9/15/2009 Edge7/29/20152143
css.properties.block-size 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.block-size.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.block-size.auto 📋Chrome12/2/2010 Edge1/15/20203331
css.properties.block-size.fit-content 📋Chrome3/9/2017 Firefox11/2/20211699
css.properties.block-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.block-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.border 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.currentColor 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.dashed 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.dotted 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.double 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.groove 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.hidden 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.inset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.medium 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.none 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.outset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.ridge 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.solid 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.thick 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.thin 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block.transparent 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-color 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-color.currentColor 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-color.transparent 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-end 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.currentColor 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.dashed 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.dotted 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.double 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.groove 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.hidden 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.inset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.medium 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.outset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.ridge 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.solid 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.thick 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.thin 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end.transparent 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-color 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-color.currentColor 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-color.transparent 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.dashed 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.dotted 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.double 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.groove 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.hidden 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.inset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.outset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.ridge 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-style.solid 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-width 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-width.medium 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-width.thick 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-end-width.thin 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.currentColor 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.dashed 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.dotted 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.double 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.groove 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.hidden 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.inset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.medium 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.outset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.ridge 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.solid 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.thick 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.thin 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start.transparent 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-color 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-color.currentColor 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-color.transparent 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.dashed 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.dotted 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.double 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.groove 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.hidden 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.inset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.outset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.ridge 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-style.solid 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-width 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-width.medium 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-width.thick 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-start-width.thin 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-block-style 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.dashed 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.dotted 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.double 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.groove 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.hidden 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.inset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.none 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.outset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.ridge 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-style.solid 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-width 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-width.medium 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-width.thick 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-block-width.thin 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-bottom 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-bottom-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-bottom-left-radius 📋Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-left-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-bottom-left-radius.percentages Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-right-radius 📋Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-bottom-right-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-bottom-right-radius.percentages Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-bottom-style 📋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 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-end-end-radius 📋Firefox3/19/2019 Safari9/20/2021916
css.properties.border-end-start-radius 📋Firefox3/19/2019 Safari9/20/2021916
css.properties.border-image 📋Chrome12/13/2011 Edge7/29/20151324
Chrome: Before Chrome 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Chrome Android: Before Chrome Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Edge: Before Edge 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Firefox: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox: Until Firefox 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox: From Firefox 48 until Firefox 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox: Until Firefox 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox: Before Firefox 15, an earlier version of the specification was implemented, prefixed.Firefox for Android: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox for Android: Until Firefox for Android 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox for Android: From Firefox for Android 48 until Firefox for Android 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox for Android: Until Firefox for Android 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox for Android: Before Firefox for Android 15, an earlier version of the specification was implemented, prefixed.Quest Browser: Before Quest Browser false, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera: Before Opera 98, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera Android: A border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Samsung Internet: Before Samsung Internet 23.0, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).WebView Android: Before WebView 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).
css.properties.border-image.fill Chrome12/13/2011 Edge7/29/20151324
css.properties.border-image.gradient 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 Chrome12/13/2011 Edge7/29/20151324
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 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-repeat 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-repeat.repeat 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-repeat.round 📋Firefox8/28/2012 Safari3/21/20161301
css.properties.border-image-repeat.space 📋Edge7/29/2015 Chrome1/25/2017546
css.properties.border-image-repeat.stretch 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-slice 📋Chrome10/25/2011 Edge7/29/20151373
Firefox: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox: Until Firefox 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox: From Firefox 48 until Firefox 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox: Until Firefox 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).Firefox for Android: Small SVGs are incorrectly stretched, because percentages in border-image-slice are computed to integers instead of floats (bug 1284797).Firefox for Android: Until Firefox for Android 47, SVGs without viewport were not sliced correctly (bug 619500).Firefox for Android: From Firefox for Android 48 until Firefox for Android 49, SVGs without viewport are displayed the same as SVGs with viewport, but if the slices are not exactly 50%, they are incorrectly stretched (bug 1264809).Firefox for Android: Until Firefox for Android 57, an issue persisted for SVGs without viewport when e10s was disabled (bug 1290782).
css.properties.border-image-source 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-source.none 📋Chrome10/25/2011 Edge7/29/20151373
css.properties.border-image-width 📋Chrome12/13/2011 Edge7/29/20151324
Chrome: Before Chrome 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Chrome Android: Before Chrome Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Edge: Before Edge 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Quest Browser: Before Quest Browser false, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera: Before Opera 98, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Opera Android: Before Opera Android 75, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).Samsung Internet: Before Samsung Internet 23.0, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).WebView Android: Before WebView Android 112, a border image's absolute or percentage length width may not take precedence over a narrower border-width (bug 40541033).
css.properties.border-image-width.auto 📋Chrome12/13/2011 Edge7/29/20151324
css.properties.border-inline 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.currentColor 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.dashed 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.dotted 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.double 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.groove 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.hidden 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.inset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.medium 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.none 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.outset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.ridge 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.solid 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.thick 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.thin 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline.transparent 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-color 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-color.currentColor 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-color.transparent 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-end 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.currentColor 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.dashed 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.dotted 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.double 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.groove 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.hidden 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.inset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.medium 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.outset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.ridge 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.solid 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.thick 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.thin 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end.transparent 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-color 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-color.currentColor 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-color.transparent 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.dashed 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.dotted 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.double 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.groove 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.hidden 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.inset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.outset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.ridge 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-style.solid 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-width 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-width.medium 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-width.thick 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-end-width.thin 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.currentColor 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.dashed 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.dotted 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.double 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.groove 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.hidden 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.inset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.medium 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.outset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.ridge 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.solid 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.thick 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.thin 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start.transparent 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-color 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-color.currentColor 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-color.transparent 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.dashed 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.dotted 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.double 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.groove 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.hidden 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.inset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.outset 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.ridge 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-style.solid 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-width 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-width.medium 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-width.thick 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-start-width.thin 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.border-inline-style 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.dashed 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.dotted 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.double 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.groove 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.hidden 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.inset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.none 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.outset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.ridge 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-style.solid 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-width 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-width.medium 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-width.thick 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-inline-width.thin 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.border-left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-left.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Chrome1/25/2010 Edge7/29/20152011
Chrome: Chrome ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.Firefox: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox: To conform to the CSS3 standard, Firefox 4 changes the handling of <percentage> values to match the specification. You can specify an ellipse as a border on an arbitrary sized element with border-radius: 50%;. Firefox 4 also makes rounded corners clip content and images if overflow: visible is not set.Firefox for Android: Before Firefox 50, border styles of rounded corners (with border-radius) were always rendered as if border-style was solid. This has been fixed in Firefox 50.Opera: Before Opera 11.60, replaced elements with border-radius do not have rounded corners.Safari: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.Safari on iOS: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.WebView on iOS: Safari ignores border-radius on <select> elements unless -webkit-appearance is overridden to an appropriate value.
css.properties.border-radius.4_values_for_4_corners Chrome1/25/2010 Edge7/29/20152011
css.properties.border-radius.elliptical_borders 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 Chrome12/2/2010 Edge7/29/20151700
Firefox: Before Firefox 4, <percentage> values are implemented in a non-standard way. Both horizontal and vertical radii were relative to the width of the border box.Opera: Before Opera 11.5, the implementation of <percentage> values was buggy.
css.properties.border-right 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-right.currentColor 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Firefox3/19/2019 Safari9/20/2021916
css.properties.border-start-start-radius 📋Firefox3/19/2019 Safari9/20/2021916
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 📋Chrome11/12/2013 Edge4/5/20171240
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 📋Chrome11/12/2013 Edge4/5/20171240
css.properties.border-top-color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.border-top-left-radius 📋Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-left-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-top-left-radius.percentages Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-right-radius 📋Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox 50.Firefox for Android: Before Firefox for Android 50, border styles of rounded corners were always rendered as if border-style was solid. This has been fixed in Firefox for Android 50.
css.properties.border-top-right-radius.elliptical_corners Safari10/26/2007 Edge7/29/20152833
css.properties.border-top-right-radius.percentages Chrome1/25/2010 Edge7/29/20152011
Firefox: Before Firefox 4, the <percentage> was relative to the width of the box even when specifying the radius for a height. This implied that -moz-border-radius-bottomright was always drawing an arc of circle, and never an ellipse, when followed by a single value.
css.properties.border-top-style 📋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 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.bottom.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.bottom.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.box-align Safari10/26/2007 Firefox9/20/20163252
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 Firefox9/20/20163252
css.properties.box-flex Safari10/26/2007 Firefox9/20/20163252
css.properties.box-ordinal-group Safari10/26/2007 Firefox9/20/20163252
css.properties.box-orient Safari10/26/2007 Firefox9/20/20163252
css.properties.box-pack Safari10/26/2007 Firefox9/20/20163252
css.properties.box-shadow 📋Chrome3/8/2011 Edge7/29/20151604
Chrome: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Chrome Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Firefox: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Firefox for Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Internet Explorer: To use box-shadow in Internet Explorer 9 or later, you must set border-collapse to separate.Internet Explorer: Since version 5.5, Internet Explorer supports Microsoft's DropShadow and Shadow Filter. You can use this proprietary extension to cast a drop shadow (though the syntax and the effect are different from CSS3)Quest Browser: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Opera: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Opera Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Safari: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Safari on iOS: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.Samsung Internet: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.WebView Android: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.WebView on iOS: Shadows affect layout in this browser. For example, if you cast an outer shadow to a box with a width of 100%, then you'll see a scrollbar.
css.properties.box-shadow.inset Chrome12/11/2008 Edge7/29/20152421
Internet Explorer: inset must be the last keyword in the declaration.
css.properties.box-shadow.multiple_shadows Safari10/26/2007 Edge7/29/20152833
css.properties.box-shadow.none 📋Safari10/26/2007 Edge7/29/20152833
css.properties.box-shadow.spread_radius Chrome12/11/2008 Edge7/29/20152421
css.properties.box-sizing 📋Chrome3/8/2011 Edge7/29/20151604
Chrome: box-sizing is not respected when the height is calculated from window.getComputedStyle().Chrome Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox: Before Firefox 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Firefox for Android: Before Firefox for Android 23, box-sizing is not respected when the height is calculated from window.getComputedStyle().Internet Explorer: box-sizing is not respected when the height is calculated from window.getComputedStyle().Quest Browser: box-sizing is not respected when the height is calculated from window.getComputedStyle().Opera Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().Samsung Internet: box-sizing is not respected when the height is calculated from window.getComputedStyle().WebView Android: box-sizing is not respected when the height is calculated from window.getComputedStyle().
css.properties.box-sizing.border-box 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.box-sizing.content-box 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.break-after 📋Edge7/29/2015 Firefox1/29/20191280
css.properties.break-after.auto Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.left Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.page Chrome4/13/2016 Edge1/15/20201372
css.properties.break-after.paged_context 📋Edge7/29/2015 Firefox1/29/20191280
css.properties.break-after.paged_context.page Edge7/29/2015 Firefox1/29/20191280
css.properties.break-after.right Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before 📋Edge7/29/2015 Firefox1/29/20191280
css.properties.break-before.auto Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.left Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.page Chrome4/13/2016 Edge1/15/20201372
css.properties.break-before.paged_context 📋Edge7/29/2015 Firefox1/29/20191280
css.properties.break-before.paged_context.page Edge7/29/2015 Firefox1/29/20191280
css.properties.break-before.right Chrome4/13/2016 Edge1/15/20201372
css.properties.break-inside 📋Edge7/29/2015 Firefox1/29/20191280
css.properties.break-inside.auto Chrome4/13/2016 Edge1/15/20201372
css.properties.break-inside.avoid Chrome4/13/2016 Edge1/15/20201372
css.properties.break-inside.avoid-column Chrome4/13/2016 Firefox9/7/20211973
css.properties.break-inside.avoid-page Chrome4/13/2016 Firefox9/7/20211973
css.properties.break-inside.multicol_context 📋Edge7/29/2015 Firefox1/29/20191280
css.properties.break-inside.multicol_context.avoid-column Edge7/29/2015 Firefox9/7/20212232
css.properties.break-inside.paged_context 📋Edge7/29/2015 Firefox1/29/20191280
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 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.caret-color.auto 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.caret-color.currentColor 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.caret-color.transparent 📋Chrome3/9/2017 Edge1/15/20201042
css.properties.clear 📋Safari6/23/2003 Edge7/29/20154419
css.properties.clear.both 📋Safari6/23/2003 Edge7/29/20154419
css.properties.clear.inline-end 📋Firefox8/8/2017 Edge10/13/20232257
css.properties.clear.inline-start 📋Firefox8/8/2017 Edge10/13/20232257
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 📋Firefox6/30/2009 Edge1/15/20203851
Edge: Only supports clip paths defined by url().Internet Explorer: Only supports clip paths defined by url().
css.properties.clip-path.basic_shape 📋Chrome11/6/2012 Edge1/15/20202626
css.properties.clip-path.border-box 📋Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-path.content-box 📋Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-path.fill-box 📋Firefox1/24/2017 Edge11/2/20232473
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 Firefox6/30/2009 Edge1/15/20203851
css.properties.clip-path.is_animatable Firefox9/20/2016 Edge1/15/20201212
css.properties.clip-path.margin-box 📋Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-path.padding-box 📋Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-path.path Firefox12/10/2019 Edge1/21/2021408
css.properties.clip-path.stroke-box 📋Firefox1/24/2017 Edge11/2/20232473
Firefox: This value was supported before Firefox 51, but as an alias to border-box.Firefox for Android: This value was supported before Firefox for Android 51, but as an alias to border-box.
css.properties.clip-path.svg_elements Chrome11/6/2012 Firefox3/7/20171582
css.properties.clip-path.view-box 📋Firefox6/13/2017 Edge11/2/20232333
css.properties.clip-rule 📋Firefox6/30/2009 Edge1/15/20203851
css.properties.clip-rule.evenodd 📋Firefox6/30/2009 Edge1/15/20203851
css.properties.clip-rule.nonzero 📋Firefox6/30/2009 Edge1/15/20203851
css.properties.color 📋Safari6/23/2003 Edge7/29/20154419
css.properties.color.transparent 📋Safari6/23/2003 Edge7/29/20154419
css.properties.color-interpolation 📋Firefox6/17/2008 Edge1/15/20204229
css.properties.color-interpolation.auto 📋Firefox6/17/2008 Edge1/15/20204229
css.properties.color-interpolation.linearRGB 📋Firefox6/17/2008 Edge1/15/20204229
css.properties.color-interpolation.sRGB 📋Firefox6/17/2008 Edge1/15/20204229
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 📋Firefox6/25/2013 Edge1/15/20202395
css.properties.color-interpolation-filters.sRGB 📋Firefox6/25/2013 Edge1/15/20202395
css.properties.color-scheme 📋Safari9/19/2019 Firefox1/11/2022845
css.properties.color-scheme.dark Safari9/19/2019 Firefox1/11/2022845
css.properties.color-scheme.light Safari9/19/2019 Firefox1/11/2022845
css.properties.color-scheme.normal Safari9/19/2019 Firefox1/11/2022845
css.properties.color-scheme.only Safari9/19/2019 Edge2/3/2022868
css.properties.column-count 📋Edge7/29/2015 Firefox3/7/2017587
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 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.column-fill 📋Edge7/29/2015 Firefox3/7/2017587
css.properties.column-fill.auto 📋Firefox11/20/2012 Chrome4/13/20161240
css.properties.column-fill.balance 📋Firefox11/20/2012 Chrome4/13/20161240
css.properties.column-gap 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.column-gap.flex_context 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.column-gap.grid_context 📋Edge10/17/2017 Safari9/17/2018335
css.properties.column-gap.multicol_context 📋Edge7/29/2015 Firefox3/7/2017587
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 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.column-rule 📋Edge7/29/2015 Firefox3/7/2017587
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 Firefox3/7/2017587
css.properties.column-rule-color.transparent 📋Safari10/26/2007 Edge7/29/20152833
css.properties.column-rule-style 📋Edge7/29/2015 Firefox3/7/2017587
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 Firefox3/7/2017587
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 Firefox12/10/20191595
css.properties.column-span.all 📋Chrome9/2/2010 Firefox12/10/20193386
css.properties.column-span.none 📋Chrome9/2/2010 Firefox12/10/20193386
css.properties.column-width 📋Edge7/29/2015 Firefox11/15/2016475
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 Firefox11/29/2005 Edge7/29/20153529
css.properties.columns 📋Edge7/29/2015 Firefox3/7/2017587
Firefox: Before version 37, multiple columns didn't work with display: table-caption elements.Firefox for Android: Before version 37, multiple columns didn't work with display: table-caption elements.
css.properties.columns.auto 📋Safari10/26/2007 Chrome4/13/20163092
css.properties.contain 📋Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.content 📋Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.inline-size 📋Firefox5/31/2022 Safari9/12/2022104
css.properties.contain.layout 📋Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.none 📋Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.paint 📋Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.size 📋Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.strict 📋Chrome7/20/2016 Safari3/14/20222063
css.properties.contain.style 📋Chrome7/20/2016 Firefox7/26/20222197
Chrome: Before Chrome 115, style containment did not affect quotes, see bug 40592922.Chrome Android: Before Chrome Android 115, style containment did not affect quotes, see bug 40592922.Edge: Before Edge 115, style containment did not affect quotes, see bug 40592922.Quest Browser: Before Quest Browser false, style containment did not affect quotes, see bug 40592922.Opera: Before Opera 101, style containment did not affect quotes, see bug 40592922.Opera Android: Before Opera Android 77, style containment did not affect quotes, see bug 40592922.Safari: Style containment does not affect quotes, see bug 232083.Safari on iOS: Style containment does not affect quotes, see bug 232083.Samsung Internet: Before Samsung Internet 23.0, style containment did not affect quotes, see bug 40592922.WebView Android: Before WebView Android 115, style containment did not affect quotes, see bug 40592922.WebView on iOS: Style containment does not affect quotes, see bug 232083.
css.properties.contain-intrinsic-block-size 📋Chrome10/19/2021 Safari9/18/2023699
css.properties.contain-intrinsic-block-size.none 📋Chrome2/1/2022 Safari9/18/2023594
css.properties.contain-intrinsic-height 📋Chrome10/19/2021 Safari9/18/2023699
css.properties.contain-intrinsic-height.none 📋Chrome2/1/2022 Safari9/18/2023594
css.properties.contain-intrinsic-inline-size 📋Chrome10/19/2021 Safari9/18/2023699
css.properties.contain-intrinsic-inline-size.none 📋Chrome2/1/2022 Safari9/18/2023594
css.properties.contain-intrinsic-size 📋Chrome5/19/2020 Safari9/18/20231217
css.properties.contain-intrinsic-size.auto_none Firefox8/29/2023 Safari9/18/202320
css.properties.contain-intrinsic-size.none 📋Chrome2/1/2022 Safari9/18/2023594
css.properties.contain-intrinsic-width 📋Chrome10/19/2021 Safari9/18/2023699
css.properties.contain-intrinsic-width.none 📋Chrome2/1/2022 Safari9/18/2023594
css.properties.container 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container.inline-size 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container.none 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container.normal 📋Safari9/12/2022 Firefox2/14/2023155
css.properties.container.scroll-state 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container.size 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container-name 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container-name.none 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type.inline-size 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type.normal 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type.size 📋Edge9/1/2022 Firefox2/14/2023166
css.properties.container-type.weak_containment 📋Chrome9/17/2024 Safari3/31/2025195
css.properties.content 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.alt_text Chrome9/10/2019 Firefox7/9/20241764
css.properties.content.close-quote 📋Safari6/23/2003 Edge7/29/20154419
css.properties.content.element_replacement Chrome7/9/2013 Edge1/15/20202381
css.properties.content.gradient 📋Chrome3/26/2013 Firefox5/9/20233696
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 📋Firefox6/1/2021 Safari9/18/2023839
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 📋Chrome8/25/2020 Safari9/16/20241483
css.properties.content-visibility.auto 📋Chrome8/25/2020 Safari9/15/20251847
Safari: Skipped content is not findable via find-in-page.Safari on iOS: Skipped content is not findable via find-in-page.WebView on iOS: Skipped content is not findable via find-in-page.
css.properties.content-visibility.hidden 📋Chrome8/25/2020 Safari9/16/20241483
css.properties.content-visibility.visible 📋Chrome8/25/2020 Safari9/16/20241483
css.properties.counter-increment 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.counter-increment.list-item 📋Firefox11/9/2004 Safari9/30/20153977
css.properties.counter-increment.none 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.counter-reset 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.counter-reset.list-item 📋Firefox11/9/2004 Safari9/30/20153977
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 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.counter-set 📋Firefox7/9/2019 Safari12/11/20231616
css.properties.counter-set.list-item 📋Firefox7/9/2019 Safari12/11/20231616
css.properties.counter-set.none 📋Firefox7/9/2019 Safari12/11/20231616
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.cursor.col-resize 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
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 Firefox2/4/2014 Chrome7/24/20181631
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 📋Firefox2/4/2014 Edge1/15/20202171
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox6/17/2008 Edge7/29/20152598
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox11/29/2005 Edge7/29/20153529
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 Firefox11/29/2005 Edge7/29/20153529
Firefox: Firefox 4 added macOS support.
css.properties.cursor.url_positioning_syntax Firefox11/29/2005 Edge1/15/20205160
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 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox9/17/2013 Safari9/30/2015743
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 📋Firefox9/17/2013 Safari9/30/2015743
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 📋Firefox7/22/2014 Edge4/5/2017988
css.properties.cx 📋Chrome5/19/2015 Edge1/15/20201702
css.properties.cy 📋Chrome5/19/2015 Edge1/15/20201702
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 📋Firefox3/31/2015 Edge1/15/20201751
css.properties.display.flex Firefox4/2/2013 Safari9/30/2015911
Firefox: Firefox 28 added multi-line flexbox support.Firefox for Android: Firefox for Android 28 added multi-line flexbox support.Internet Explorer: IE incorrectly positions inline block content inside flex containers. See the discussion on Microsoft Answers.Internet Explorer: IE incorrectly positions inline block content inside flex containers. See the discussion on Microsoft Answers.
css.properties.display.flow-root Chrome4/19/2017 Edge1/15/20201001
css.properties.display.grid Firefox3/7/2017 Edge10/17/2017224
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 Firefox4/2/2013 Safari9/30/2015911
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 Firefox3/7/2017 Edge10/17/2017224
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.list-item 📋Safari6/23/2003 Edge7/29/20154419
css.properties.display.multi-keyword_values Firefox10/22/2019 Edge7/21/20231368
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 Firefox11/9/2004 Edge4/5/20174530
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 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.alphabetic 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.auto 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.central 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.hanging 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.ideographic 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.mathematical 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.dominant-baseline.middle 📋Firefox11/9/2004 Edge1/15/20205545
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.fill 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.fill.none 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.fill-opacity 📋Firefox11/9/2004 Edge4/5/20174530
css.properties.fill-rule 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.fill-rule.evenodd 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.fill-rule.nonzero 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.filter 📋Firefox1/13/2015 Chrome8/31/2016596
Internet Explorer: Internet Explorer 4 to 9 implemented a non-standard filter property. The syntax was completely different from this one and is not documented here.
css.properties.filter.blur 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.brightness 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.contrast 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.drop-shadow 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.grayscale 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.hue-rotate 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.invert 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.none 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.opacity 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.filter.saturate 📋Chrome3/28/2012 Edge7/29/20151218
Chrome: In Chrome 18 to 19, the saturate() function only takes integers instead of decimal or percentage values. From Chrome 20, this bug is fixed.
css.properties.filter.sepia 📋Chrome3/28/2012 Edge7/29/20151218
css.properties.flex 📋Firefox6/25/2013 Safari9/30/2015827
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox: Before Firefox 32, Firefox wasn't able to animate values starting or stopping at 0.Firefox: Until Firefox 61, flex items that are sized according to their content are sized using fit-content, not max-content.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Firefox for Android: Before Firefox for Android 32, Firefox for Android wasn't able to animate values starting or stopping at 0.Firefox for Android: Until Firefox for Android 61, flex items that are sized according to their content are sized using fit-content, not max-content.Internet Explorer: Internet Explorer 11 ignores uses of calc() in the flex-basis part of the flex syntax. This can be worked around by using the longhand properties instead of the shorthand. See Flexbug #8 for more info.Internet Explorer: Internet Explorer 11 considers a unitless value in the flex-basis part to be syntactically invalid (and will thus be ignored). A workaround is to always include a unit in the flex-basis part of the flex shorthand value. See Flexbug #4 for more info.Internet Explorer: Internet Explorer 10 and 11 ignore uses of calc() in the flex-basis part of the flex syntax. This can be worked around by using the longhand properties instead of the shorthand. See Flexbug #8 for more info.Internet Explorer: Internet Explorer 10 and 11 consider a unitless value in the flex-basis part to be syntactically invalid (and will thus be ignored). A workaround is to always include a unit in the flex-basis part of the flex shorthand value. See Flexbug #4 for more info.
css.properties.flex.auto 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex.content 📋Firefox6/26/2018 Edge9/24/20211186
css.properties.flex.fit-content 📋Chrome9/21/2021 Safari9/12/2022356
css.properties.flex.max-content 📋Firefox3/19/2019 Safari9/12/20221273
css.properties.flex.min-content 📋Firefox3/19/2019 Safari9/12/20221273
css.properties.flex.none 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-basis 📋Firefox6/25/2013 Safari9/30/2015827
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Internet Explorer: When a non-auto flex-basis is specified, Internet Explorer 10 and 11 always uses a content-box box model to calculate the size of a flex item, even if box-sizing: border-box is applied to the element. See Flexbug #7 for more info.
css.properties.flex-basis.auto Chrome9/25/2012 Safari9/30/20151100
css.properties.flex-basis.content Firefox6/26/2018 Safari3/14/20221357
css.properties.flex-basis.fit-content Chrome9/21/2021 Safari9/12/2022356
css.properties.flex-basis.max-content Firefox3/19/2019 Safari9/12/20221273
css.properties.flex-basis.min-content Firefox3/19/2019 Safari9/12/20221273
css.properties.flex-direction 📋Firefox6/25/2013 Safari9/30/2015827
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.
css.properties.flex-direction.column 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-direction.column-reverse 📋Chrome7/31/2012 Firefox9/22/20202975
Firefox: Before Firefox 81, overflow with column-reverse was unsupported. See bug 1042151.Firefox for Android: Before Firefox for Android 81, overflow with column-reverse was unsupported. See bug 1042151.
css.properties.flex-direction.row 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-direction.row-reverse 📋Chrome7/31/2012 Firefox9/22/20202975
Firefox: Before Firefox 81, overflow with column-reverse was unsupported. See bug 1042151.Firefox for Android: Before Firefox for Android 81, overflow with column-reverse was unsupported. See bug 1042151.
css.properties.flex-flow 📋Chrome8/20/2013 Safari9/30/2015771
css.properties.flex-flow.column 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.column-reverse 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.nowrap 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.row 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.row-reverse 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.wrap 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-flow.wrap-reverse 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-grow 📋Firefox4/2/2013 Safari9/30/2015911
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 📋Firefox4/2/2013 Safari9/30/2015911
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox: Before Firefox 32, Firefox wasn't able to animate values starting or stopping at 0.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.Firefox for Android: Before Firefox for Android 32, Firefox for Android wasn't able to animate values starting or stopping at 0.Internet Explorer: Internet Explorer 10 uses 0 instead of 1 as the initial value for the flex-shrink property. A workaround is to always set an explicit value for flex-shrink. See Flexbug #6 for more info.
css.properties.flex-wrap 📋Chrome8/20/2013 Safari9/30/2015771
Internet Explorer: Partial support due to large number of bugs present. See Flexbugs.
css.properties.flex-wrap.nowrap 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-wrap.wrap 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.flex-wrap.wrap-reverse 📋Chrome7/31/2012 Edge7/29/20151093
css.properties.float 📋Safari6/23/2003 Edge7/29/20154419
css.properties.float.inline-end 📋Firefox8/8/2017 Edge10/13/20232257
css.properties.float.inline-start 📋Firefox8/8/2017 Edge10/13/20232257
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 📋Firefox6/17/2008 Edge7/29/20152598
css.properties.flood-color.currentColor 📋Firefox6/17/2008 Edge7/29/20152598
css.properties.flood-color.transparent 📋Firefox6/17/2008 Edge7/29/20152598
css.properties.flood-opacity 📋Firefox6/17/2008 Edge7/29/20152598
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 Firefox12/15/2015 Edge1/15/20201492
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 Chrome1/10/2023 Safari12/12/20251067
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 Chrome1/25/2017 Firefox9/7/20211686
Firefox: Supported on macOS only.
css.properties.font-feature-settings 📋Firefox12/1/2014 Edge4/5/2017856
Firefox: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox: From Firefox 129 the -webkit-font-feature-settings alias has been added to support sites that are still supporting the vendor prefix.Firefox: From Firefox 4 to Firefox 14 (inclusive), Firefox supported an older, slightly different syntax. See OpenType Font Feature support in Firefox 4.Firefox for Android: The ISO/IEC CD 14496-22 3rd edition suggests using the ssty feature to provide glyph variants more suitable for use in scripts (for example primes used as superscripts). Starting with Firefox for Android 29, this is done automatically by the MathML rendering engine. The ISO/IEC CD 14496-22 3rd edition also suggests applying the dtls feature to letters when placing mathematical accents to get dotless forms (for example dotless i, j with a hat). Starting with Firefox for Android 35, this is done automatically by the MathML rendering engine. You can override the default values determined by the MathML rendering engine with CSS.Firefox for Android: From Firefox for Android 129 the -webkit-font-feature-settings alias has been added to support sites that are still supporting the vendor prefix.Firefox for Android: From Firefox for Android 4 to Firefox for Android 14 (inclusive), Firefox for Android supported an older, slightly different syntax. See OpenType Font Feature support in Firefox for Android 4.
css.properties.font-feature-settings.normal 📋Chrome12/13/2011 Edge4/5/20171940
css.properties.font-kerning 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.font-kerning.auto 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.font-kerning.none 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.font-kerning.normal 📋Chrome2/20/2014 Edge1/15/20202155
css.properties.font-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 Firefox11/15/2022246
css.properties.font-palette.dark 📋Safari3/14/2022 Firefox11/15/2022246
css.properties.font-palette.light 📋Safari3/14/2022 Firefox11/15/2022246
css.properties.font-palette.normal 📋Safari3/14/2022 Firefox11/15/2022246
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 Firefox10/22/2019 Safari3/27/20231252
css.properties.font-size-adjust 📋Firefox6/17/2008 Edge7/25/20245882
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 📋Firefox6/17/2008 Edge7/25/20245882
css.properties.font-size-adjust.two-values Firefox9/7/2021 Edge7/25/20241052
css.properties.font-smooth Safari6/8/2009 Edge1/15/20203873
Firefox: Only works on macOS.
css.properties.font-stretch 📋Firefox12/20/2011 Safari9/19/20172100
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 📋Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.expanded 📋Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.extra-condensed 📋Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.extra-expanded 📋Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.normal 📋Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.percentage Chrome10/17/2017 Edge10/2/2018350
css.properties.font-stretch.semi-condensed 📋Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.semi-expanded 📋Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.ultra-condensed 📋Firefox12/20/2011 Safari9/19/20172100
css.properties.font-stretch.ultra-expanded 📋Firefox12/20/2011 Safari9/19/20172100
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 📋Chrome10/17/2017 Edge1/15/2020820
Chrome: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Chrome Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Edge: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Quest Browser: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Opera Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Safari on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.Samsung Internet: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView Android: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.WebView on iOS: Angles from 14 to 90 have the same effect as font-style: oblique (with a slant of 14 degrees). Angles from -90 to 13 have the same effect as font-style: normal (without a slant). In some cases (e.g. with vertical writing-mode), a negative angle produces a slant. See bug 425388876.
css.properties.font-synthesis 📋Firefox12/1/2014 Edge1/6/20222593
css.properties.font-synthesis.none 📋Firefox12/1/2014 Edge1/6/20222593
css.properties.font-synthesis.small-caps Safari3/27/2017 Edge1/6/20221746
css.properties.font-synthesis.style Firefox12/1/2014 Edge1/6/20222593
css.properties.font-synthesis.weight Firefox12/1/2014 Edge1/6/20222593
css.properties.font-synthesis-small-caps 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-small-caps.auto 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-small-caps.none 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-style 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-style.auto 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-style.none 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-weight 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-weight.auto 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.font-synthesis-weight.none 📋Chrome1/4/2022 Safari3/27/2023447
css.properties.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 Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant.historical-forms 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant.none 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant.normal 📋Safari6/23/2003 Edge7/29/20154419
css.properties.font-variant.sub 📋Firefox12/1/2014 Edge2/9/20232992
css.properties.font-variant.super 📋Firefox12/1/2014 Edge2/9/20232992
css.properties.font-variant.turkic_is Firefox7/17/2012 Edge7/29/20151107
css.properties.font-variant-alternates 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.annotation 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.character_variant 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.historical-forms 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.normal 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.ornaments 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.styleset 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.stylistic 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-alternates.swash 📋Firefox12/1/2014 Edge3/13/20233024
css.properties.font-variant-caps 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.all-petite-caps 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.all-small-caps 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.normal 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.petite-caps 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.small-caps 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.titling-caps 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-caps.unicase 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.full-width 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.jis04 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.jis78 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.jis83 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.jis90 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.normal 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.proportional-width 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.ruby 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.simplified 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-east-asian.traditional 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-emoji 📋Safari5/13/2024 Firefox7/22/2025435
css.properties.font-variant-ligatures 📋Chrome4/8/2014 Edge1/15/20202108
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 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.diagonal-fractions 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.lining-nums 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.normal 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.oldstyle-nums 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.ordinal 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.proportional-nums 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.slashed-zero 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.stacked-fractions 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-numeric.tabular-nums 📋Firefox12/1/2014 Edge1/15/20201871
css.properties.font-variant-position 📋Firefox12/1/2014 Edge9/15/20233210
css.properties.font-variant-position.normal 📋Firefox12/1/2014 Edge9/15/20233210
css.properties.font-variant-position.sub 📋Firefox12/1/2014 Edge9/15/20233210
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 📋Firefox12/1/2014 Edge9/15/20233210
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 Firefox9/5/2018351
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 Firefox9/5/2018351
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 Firefox6/26/2018280
css.properties.gap 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.gap.flex_context 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.gap.grid_context 📋Edge10/17/2017 Safari9/17/2018335
css.properties.gap.grid_context.calc_values Firefox3/7/2017 Safari3/25/2019748
css.properties.gap.grid_context.percentage_values Firefox3/7/2017 Chrome4/17/2018406
css.properties.gap.multicol_context 📋Edge10/17/2017 Safari4/26/20211287
css.properties.gap.normal 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid 📋Firefox3/7/2017 Edge10/17/2017224
Samsung Internet: This was added early so is out of sync with the equivalent Chromium version.
css.properties.grid.none 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-area 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-area.auto 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-columns 📋Chrome3/9/2017 Firefox10/22/2019957
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 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-columns.max-content 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-columns.min-content 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-flow 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-flow.column 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-auto-flow.dense 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-auto-flow.row 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-auto-rows 📋Chrome3/9/2017 Firefox10/22/2019957
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 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-rows.max-content 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-auto-rows.min-content 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column.auto 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column-end 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column-end.auto 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column-start 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-column-start.auto 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row.auto 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row-end 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row-end.auto 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row-start 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-row-start.auto 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template.none 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-areas 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-areas.none 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-columns.animation Firefox3/19/2019 Edge10/27/20221318
css.properties.grid-template-columns.auto 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns.fit-content 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-columns.max-content 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns.min-content 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns.minmax 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-columns.none 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-columns.repeat 📋Chrome3/9/2017 Firefox5/5/20201153
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 📋Firefox12/10/2019 Edge9/15/20231375
css.properties.grid-template-rows 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-rows.animation Firefox3/19/2019 Edge10/27/20221318
css.properties.grid-template-rows.auto 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-rows.fit-content 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-rows.max-content 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-rows.min-content 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-rows.minmax 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.grid-template-rows.none 📋Firefox3/7/2017 Edge1/15/20201044
css.properties.grid-template-rows.repeat 📋Chrome3/9/2017 Firefox5/5/20201153
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 📋Firefox12/10/2019 Edge9/15/20231375
css.properties.height 📋Safari6/23/2003 Edge7/29/20154419
css.properties.height.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.height.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.height.fit-content 📋Chrome10/13/2015 Firefox11/2/20212212
css.properties.height.max-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.height.min-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.height.stretch 📋Safari9/30/2015 Firefox12/9/20253723
css.properties.hyphenate-character 📋Firefox3/8/2022 Safari9/18/2023559
css.properties.hyphenate-character.auto 📋Chrome9/2/2010 Firefox3/8/20224205
css.properties.hyphens 📋Firefox12/15/2015 Safari9/18/20232834
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 Firefox11/8/2011 Edge11/19/20203299
css.properties.hyphens.language_czech Safari3/21/2016 Firefox9/3/20243088
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 Chrome12/1/20161961
Firefox: For English, Firefox uses an en-US dictionaryFirefox for Android: For English, Firefox for Android uses an en-US dictionarySafari: For English, Safari uses different en-GB and en-US dictionaries.Safari on iOS: For English, Safari on iOS uses different en-GB and en-US dictionaries.WebView on iOS: For English, WebView on iOS uses different en-GB and en-US dictionaries.
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 Firefox12/20/2011 Edge11/19/20203257
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 Firefox11/8/2011 Edge11/19/20203299
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 Firefox12/20/2011 Edge4/6/20234125
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 📋Firefox12/10/2013 Edge4/13/20202316
css.properties.image-orientation.from-image 📋Firefox12/10/2013 Edge4/13/20202316
css.properties.image-orientation.none 📋Firefox12/10/2013 Edge4/13/20202316
css.properties.image-rendering 📋Firefox1/21/2010 Edge1/15/20203646
css.properties.image-rendering.auto 📋Firefox1/21/2010 Edge1/15/20203646
css.properties.image-rendering.crisp-edges 📋Chrome8/2/2011 Edge1/15/20203088
css.properties.image-rendering.pixelated 📋Chrome3/3/2015 Firefox10/5/20212408
css.properties.inline-size 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.inline-size.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.inline-size.auto 📋Chrome12/2/2010 Edge1/15/20203331
css.properties.inline-size.fit-content 📋Chrome3/9/2017 Firefox11/2/20211699
css.properties.inline-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.inline-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.inset 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.inset.anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.inset.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.inset.auto 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.inset-block 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-block.anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.inset-block.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.inset-block.auto 📋Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-block-end 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-block-end.anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.inset-block-end.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.inset-block-end.auto 📋Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-block-start 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-block-start.anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.inset-block-start.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.inset-block-start.auto 📋Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-inline 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-inline.anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.inset-inline.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.inset-inline.auto 📋Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-inline-end 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-inline-end.anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.inset-inline-end.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.inset-inline-end.auto 📋Firefox9/22/2015 Safari4/26/20212043
css.properties.inset-inline-start 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.inset-inline-start.anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.inset-inline-start.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.inset-inline-start.auto 📋Firefox9/22/2015 Safari4/26/20212043
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 📋Firefox4/2/2013 Safari9/30/2015911
css.properties.justify-content.flex_context 📋Firefox4/2/2013 Chrome7/20/20161205
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 Firefox10/23/2018 Safari7/29/20242106
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 Firefox3/7/2017 Edge1/15/20201044
css.properties.justify-content.flex_context.start_end Firefox3/8/2016 Safari3/14/20222197
css.properties.justify-content.flex_context.stretch Safari9/30/2015 Edge1/15/20201568
css.properties.justify-content.grid_context 📋Firefox3/7/2017 Edge10/17/2017224
css.properties.justify-content.left Chrome7/31/2012 Edge1/15/20202724
css.properties.justify-content.normal Chrome7/31/2012 Edge1/15/20202724
css.properties.justify-content.right Chrome7/31/2012 Edge1/15/20202724
css.properties.justify-items 📋Firefox4/2/2013 Chrome7/20/20161205
css.properties.justify-items.anchor-center 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.justify-items.center Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-items.flex_context 📋Firefox4/2/2013 Chrome7/20/20161205
css.properties.justify-items.grid_context 📋Firefox3/8/2016 Edge10/17/2017588
css.properties.justify-items.left Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-items.legacy 📋Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-items.right Firefox4/2/2013 Edge1/15/20202479
css.properties.justify-self 📋Firefox3/8/2016 Edge10/17/2017588
css.properties.justify-self.anchor-center 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.justify-self.auto Firefox3/8/2016 Edge1/15/20201408
css.properties.justify-self.grid_context 📋Firefox3/8/2016 Edge10/17/2017588
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 Firefox3/8/2016 Edge1/15/20201408
css.properties.justify-self.normal Firefox3/8/2016 Edge1/15/20201408
css.properties.justify-self.right Firefox3/8/2016 Edge1/15/20201408
css.properties.justify-self.stretch Firefox3/8/2016 Edge1/15/20201408
css.properties.left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.left.anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.left.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
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 Chrome12/11/2008 Firefox1/7/20204044
css.properties.lighting-color 📋Firefox6/17/2008 Edge7/29/20152598
css.properties.lighting-color.currentColor 📋Firefox6/17/2008 Edge7/29/20152598
css.properties.lighting-color.transparent 📋Firefox6/17/2008 Edge7/29/20152598
css.properties.line-break 📋Edge8/2/2016 Firefox9/3/20191127
css.properties.line-break.anywhere 📋Firefox9/3/2019 Edge5/21/2020261
css.properties.line-break.auto 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.line-break.loose 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.line-break.normal 📋Safari4/29/2005 Edge1/15/20205374
css.properties.line-break.strict 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.line-clamp 📋Safari6/7/2010 Firefox7/9/20193319
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.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.bengali 📋Safari6/7/2010 Edge1/15/20203509
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 📋Firefox3/18/2014 Safari9/20/20212743
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 📋Firefox11/9/2004 Edge1/15/20205545
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 📋Firefox10/14/2014 Safari9/20/20212533
css.properties.list-style-type.disclosure-open 📋Firefox10/14/2014 Safari9/20/20212533
css.properties.list-style-type.ethiopic-halehame Firefox11/9/2004 Safari9/18/20236887
css.properties.list-style-type.ethiopic-halehame-am Firefox11/9/2004 Safari9/18/20236887
css.properties.list-style-type.ethiopic-halehame-ti-er Firefox11/9/2004 Edge1/15/20205545
css.properties.list-style-type.ethiopic-halehame-ti-et Firefox11/9/2004 Edge1/15/20205545
css.properties.list-style-type.ethiopic-numeric 📋Firefox10/14/2014 Safari9/20/20212533
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.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 Firefox11/9/2004 Edge1/15/20205545
css.properties.list-style-type.hangul-consonant Firefox11/9/2004 Edge1/15/20205545
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 📋Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.japanese-informal 📋Firefox3/18/2014 Safari9/20/20212743
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 📋Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.korean-hanja-formal 📋Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.korean-hanja-informal 📋Firefox3/18/2014 Safari9/20/20212743
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-latin 📋Safari6/23/2003 Edge7/29/20154419
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.oriya 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.persian 📋Safari6/7/2010 Edge1/15/20203509
css.properties.list-style-type.simp-chinese-formal 📋Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.simp-chinese-informal 📋Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.square 📋Safari6/23/2003 Edge7/29/20154419
css.properties.list-style-type.string Firefox7/2/2015 Safari4/26/20212125
css.properties.list-style-type.tamil 📋Firefox10/14/2014 Safari9/20/20212533
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.trad-chinese-formal 📋Firefox3/18/2014 Safari9/20/20212743
css.properties.list-style-type.trad-chinese-informal 📋Firefox3/18/2014 Safari9/20/20212743
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-latin 📋Safari6/23/2003 Edge7/29/20154419
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 📋Chrome1/14/2025 Firefox1/13/2026364
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 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.margin-block.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.margin-block.auto 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.margin-block-end 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-block-end.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.margin-block-end.auto 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-block-start 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-block-start.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.margin-block-start.auto 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-bottom 📋Safari6/23/2003 Edge7/29/20154419
css.properties.margin-bottom.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
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 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.margin-inline.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.margin-inline.auto 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.margin-inline-end 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-inline-end.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.margin-inline-end.auto 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-inline-start 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-inline-start.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.margin-inline-start.auto 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.margin-left 📋Safari6/23/2003 Edge7/29/20154419
css.properties.margin-left.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
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 📋Chrome1/14/2025 Firefox1/13/2026364
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 📋Chrome1/14/2025 Firefox1/13/2026364
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 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.marker.none 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-end 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-end.none 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-mid 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-mid.none 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-start 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.marker-start.none 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.mask 📋Firefox4/19/2017 Edge12/7/20232423
Chrome: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Chrome: While the property is recognized, values applied to it don't have any effect.Chrome Android: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Chrome Android: While the property is recognized, values applied to it don't have any effect.Edge: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Edge: While the property is recognized, values applied to it don't have any effect.Firefox: Only supports mask: url(file.svg#mask_id) or mask: url(#mask_id), where the URL is a reference to an SVG <mask> element.Firefox for Android: Only supports mask: url(file.svg#mask_id) or mask: url(#mask_id), where the URL is a reference to an SVG <mask> element.Quest Browser: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Quest Browser: While the property is recognized, values applied to it don't have any effect.Opera: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Opera: While the property is recognized, values applied to it don't have any effect.Opera Android: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Opera Android: While the property is recognized, values applied to it don't have any effect.Safari: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Safari: While the property is recognized, values applied to it don't have any effect.Safari on iOS: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Safari on iOS: While the property is recognized, values applied to it don't have any effect.Samsung Internet: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.Samsung Internet: While the property is recognized, values applied to it don't have any effect.WebView Android: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.WebView Android: While the property is recognized, values applied to it don't have any effect.WebView on iOS: The prefixed property can be used with SVG and HTML with a slightly different syntax, which allows setting the non-standard -webkit-mask-attachment property.WebView on iOS: While the property is recognized, values applied to it don't have any effect.
css.properties.mask-clip 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-composite 📋Firefox4/19/2017 Edge12/7/20232423
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 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-composite.exclude 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-composite.intersect 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-composite.subtract 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-image 📋Firefox4/19/2017 Edge12/7/20232423
Chrome: From version 8, Chrome added support for gradient values. Initially, Chrome supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Chrome Android: From version 18, Chrome Android added support for gradient values. Initially, Chrome Android supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Quest Browser: From version 5.0, Quest Browser added support for gradient values. Initially, Quest Browser supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Safari: Initially, Safari supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Safari on iOS: Initially, Safari on iOS supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.Samsung Internet: From version 1.0, Samsung Internet added support for gradient values. Initially, Samsung Internet supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.WebView Android: Initially, Android supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.WebView on iOS: Initially, WebView on iOS supported only -webkit- prefixed values for gradients (such as -webkit-linear-gradient()). Later, support for unprefixed values was added.
css.properties.mask-image.multiple_mask_images Chrome12/11/2008 Edge10/2/20183582
css.properties.mask-image.svg_masks Safari6/8/2009 Edge10/2/20183403
css.properties.mask-mode 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-mode.alpha 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-mode.luminance 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-mode.match-source 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-origin 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-position 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-repeat 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-size 📋Firefox4/19/2017 Edge12/7/20232423
css.properties.mask-type 📋Chrome1/10/2013 Edge1/15/20202561
css.properties.mask-type.alpha 📋Chrome1/10/2013 Edge1/15/20202561
css.properties.mask-type.luminance 📋Chrome1/10/2013 Edge1/15/20202561
css.properties.math-shift 📋Chrome1/10/2023 Safari12/12/20251067
css.properties.math-shift.compact 📋Chrome1/10/2023 Safari12/12/20251067
css.properties.math-shift.normal 📋Chrome1/10/2023 Safari12/12/20251067
css.properties.math-style 📋Safari4/26/2021 Firefox8/29/2023855
css.properties.math-style.compact 📋Safari4/26/2021 Firefox8/29/2023855
css.properties.math-style.normal 📋Safari4/26/2021 Firefox8/29/2023855
css.properties.max-block-size 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.max-block-size.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.max-block-size.fit-content Chrome3/9/2017 Firefox11/2/20211699
css.properties.max-block-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-block-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-block-size.none 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.max-height 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: CSS 2.1 leaves the behavior of max-height with table undefined. Firefox supports applying max-height to table elements.Opera: CSS 2.1 leaves the behavior of max-height with table undefined. Opera supports applying max-height to table elements.
css.properties.max-height.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.max-height.fit-content 📋Chrome10/13/2015 Firefox11/2/20212212
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.max-height.max-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.max-height.min-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.max-height.none 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.max-inline-size 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.max-inline-size.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.max-inline-size.fit-content Chrome3/9/2017 Firefox11/2/20211699
css.properties.max-inline-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-inline-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.max-inline-size.none 📋Firefox9/22/2015 Edge1/15/20201576
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 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.max-width.fit-content 📋Chrome10/13/2015 Firefox11/2/20212212
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.max-width.max-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.max-width.min-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.max-width.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.min-block-size 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.min-block-size.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.min-block-size.auto 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.min-block-size.fit-content Chrome3/9/2017 Firefox11/2/20211699
css.properties.min-block-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-block-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-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 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.min-height.auto Chrome7/31/2012 Edge7/29/20151093
Firefox: Firefox 18 and later used auto as the initial value for min-height.Firefox for Android: Firefox for Android 18 and later used auto as the initial value for min-height.
css.properties.min-height.fit-content Chrome10/13/2015 Firefox11/2/20212212
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.min-height.max-content Chrome10/13/2015 Edge1/15/20201555
css.properties.min-height.min-content Chrome10/13/2015 Edge1/15/20201555
css.properties.min-inline-size 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.min-inline-size.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.min-inline-size.auto 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.min-inline-size.fit-content Chrome3/9/2017 Firefox11/2/20211699
css.properties.min-inline-size.max-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-inline-size.min-content Chrome3/9/2017 Edge1/15/20201042
css.properties.min-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 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.min-width.auto Chrome7/31/2012 Edge7/29/20151093
Chrome: Chrome uses auto as the initial value for min-width.Chrome Android: Chrome Android uses auto as the initial value for min-width.Edge: Edge uses auto as the initial value for min-width.Firefox: Firefox 18 and later (until the value was removed), used auto as the initial value for min-width.Firefox for Android: Firefox for Android 18 and later (until the value was removed), used auto as the initial value for min-width.Quest Browser: Quest Browser uses auto as the initial value for min-width.Opera: Opera uses auto as the initial value for min-width.Opera Android: Opera Android uses auto as the initial value for min-width.Samsung Internet: Samsung Internet uses auto as the initial value for min-width.WebView Android: WebView Android uses auto as the initial value for min-width.
css.properties.min-width.fit-content Chrome10/13/2015 Firefox11/2/20212212
Firefox: Firefox implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.Firefox for Android: Firefox for Android implements the definitions given in CSS3 Basic Box. This defines available and not fit-available. Also, the definition of fit-content is simpler than in CSS3 Sizing.
css.properties.min-width.max-content Chrome10/13/2015 Edge1/15/20201555
css.properties.min-width.min-content Chrome10/13/2015 Edge1/15/20201555
css.properties.mix-blend-mode 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.color 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.color-burn 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.color-dodge 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.darken 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.difference 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.exclusion 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.hard-light 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.hue 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.lighten 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.luminosity 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.multiply 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.normal 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.overlay 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.plus-lighter 📋Safari3/21/2016 Firefox4/5/20222206
css.properties.mix-blend-mode.saturation 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.screen 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.mix-blend-mode.soft-light 📋Firefox9/2/2014 Edge1/15/20201961
css.properties.object-fit 📋Chrome1/14/2014 Edge1/15/20202192
Edge: Only supported for <img> elements.
css.properties.object-fit.contain 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-fit.cover 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-fit.fill 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-fit.none 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-fit.scale-down 📋Chrome1/14/2014 Edge1/15/20202192
css.properties.object-position 📋Chrome1/14/2014 Edge1/15/20202192
Edge: Only supported for <img> elements.
css.properties.object-position.bottom 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-position.center 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-position.left 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-position.right 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.object-position.top 📋Chrome1/14/2014 Edge10/17/20171372
css.properties.offset 📋Chrome12/1/2016 Safari9/12/20222111
css.properties.offset.auto 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.border-box 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.bottom 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.center 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.content-box 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.fill-box 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.left 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.none 📋Chrome9/5/2017 Safari9/12/20221833
css.properties.offset.normal 📋Chrome8/15/2023 Firefox1/23/2024161
css.properties.offset.padding-box 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.right 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.stroke-box 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.top 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset.view-box 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-anchor 📋Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.auto 📋Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.bottom 📋Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.center 📋Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.left 📋Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.right 📋Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-anchor.top 📋Firefox1/7/2020 Edge8/21/20231322
css.properties.offset-distance 📋Chrome12/1/2016 Safari9/12/20222111
css.properties.offset-path 📋Chrome12/1/2016 Safari3/14/20221929
Samsung Internet: path() is the only value type supported.
css.properties.offset-path.basic_shape 📋Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.border-box 📋Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.content-box 📋Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.fill-box 📋Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.none 📋Firefox1/7/2020 Safari9/16/20241714
css.properties.offset-path.padding-box 📋Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.path Chrome1/23/2018 Safari9/12/20221693
css.properties.offset-path.ray 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-path.stroke-box 📋Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-path.url 📋Chrome8/15/2023 Firefox1/23/2024161
css.properties.offset-path.view-box 📋Chrome8/15/2023 Safari9/16/2024398
css.properties.offset-position 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.auto 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.bottom 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.center 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.left 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.normal 📋Chrome8/15/2023 Firefox1/23/2024161
css.properties.offset-position.right 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-position.top 📋Safari9/12/2022 Firefox1/23/2024498
css.properties.offset-rotate 📋Chrome1/25/2017 Safari9/12/20222056
css.properties.offset-rotate.auto 📋Chrome10/13/2015 Safari9/12/20222526
css.properties.offset-rotate.reverse 📋Chrome10/13/2015 Safari9/12/20222526
css.properties.opacity 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.opacity.percentages Chrome10/22/2019 Safari3/24/2020154
css.properties.order 📋Firefox4/2/2013 Safari9/30/2015911
Firefox: Since Firefox 28, multi-line flexbox is supported.Firefox for Android: Since Firefox for Android 28, multi-line flexbox is supported.
css.properties.outline 📋Firefox4/19/2021 Safari3/27/2023707
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 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.overflow.clip 📋Firefox9/22/2020 Safari9/12/2022720
css.properties.overflow.hidden 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.overflow.multiple_keywords Firefox6/26/2018 Safari3/24/2020637
css.properties.overflow.scroll 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.overflow.visible 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.overflow-block 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-block.auto 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-block.clip 📋Firefox9/22/2020 Safari9/15/20251819
css.properties.overflow-block.hidden 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-block.scroll 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-block.visible 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline.auto 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline.clip 📋Firefox9/22/2020 Safari9/15/20251819
css.properties.overflow-inline.hidden 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline.scroll 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-inline.visible 📋Firefox9/3/2019 Safari9/15/20252204
css.properties.overflow-wrap 📋Chrome11/6/2012 Edge10/2/20182156
css.properties.overflow-wrap.anywhere 📋Firefox1/29/2019 Safari3/14/20221140
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 📋Firefox9/22/2020 Safari9/12/2022720
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 📋Firefox9/22/2020 Safari9/12/2022720
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 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior.auto 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior.contain 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior.none 📋Chrome12/6/2017 Safari9/12/20221741
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-block 📋Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-block.auto 📋Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-block.contain 📋Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-block.none 📋Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-inline 📋Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-inline.auto 📋Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-inline.contain 📋Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-inline.none 📋Chrome9/10/2019 Safari9/12/20221098
css.properties.overscroll-behavior-x 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-x.auto 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-x.contain 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-x.none 📋Chrome12/6/2017 Safari9/12/20221741
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.overscroll-behavior-y 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-y.auto 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-y.contain 📋Chrome12/6/2017 Safari9/12/20221741
css.properties.overscroll-behavior-y.none 📋Chrome12/6/2017 Safari9/12/20221741
Edge: The none value incorrectly behaves as contain (allowing for the elastic bounce effect).
css.properties.padding 📋Safari6/23/2003 Edge7/29/20154419
css.properties.padding-block 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.padding-block-end 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.padding-block-start 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.padding-bottom 📋Safari6/23/2003 Edge7/29/20154419
css.properties.padding-inline 📋Firefox3/19/2019 Safari4/26/2021769
css.properties.padding-inline-end 📋Firefox9/22/2015 Edge1/15/20201576
css.properties.padding-inline-start 📋Firefox9/22/2015 Edge1/15/20201576
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 Firefox2/14/20237176
css.properties.page.auto 📋Safari6/23/2003 Firefox2/14/20237176
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 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.paint-order.markers 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.paint-order.normal 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.paint-order.stroke 📋Chrome5/20/2014 Edge1/15/20202066
css.properties.perspective 📋Firefox10/9/2012 Safari9/30/20151086
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 📋Firefox10/9/2012 Safari9/30/20151086
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 Firefox4/19/2017 Edge1/15/20201001
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 📋Firefox3/8/2016 Edge1/15/20201408
css.properties.place-items.anchor-center 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.place-items.flex_context Firefox3/8/2016 Edge1/15/20201408
css.properties.place-items.grid_context Firefox3/8/2016 Edge1/15/20201408
css.properties.place-self 📋Firefox3/8/2016 Edge1/15/20201408
css.properties.place-self.anchor-center 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.place-self.flex_context Firefox3/8/2016 Edge1/15/20201408
css.properties.place-self.grid_context Firefox3/8/2016 Edge1/15/20201408
css.properties.pointer-events 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.all 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.auto 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.fill 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.html_elements Chrome5/21/2009 Edge7/29/20152260
css.properties.pointer-events.none 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.painted 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.stroke 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.visible 📋Firefox11/29/2005 Edge7/29/20153529
css.properties.pointer-events.visibleFill 📋Safari6/8/2009 Firefox11/15/20162717
css.properties.pointer-events.visiblePainted 📋Safari6/8/2009 Firefox11/15/20162717
css.properties.pointer-events.visibleStroke 📋Safari6/8/2009 Firefox11/15/20162717
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 Firefox3/13/20181244
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 📋Firefox9/2/2014 Safari9/19/20191843
css.properties.position-anchor 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.position-anchor.auto 📋Chrome5/14/2024 Firefox1/13/2026609
Chrome: The generic auto value exists, but it does not yet have the effect described in the spec.Chrome Android: The generic auto value exists, but it does not yet have the effect described in the spec.Edge: The generic auto value exists, but it does not yet have the effect described in the spec.Opera: The generic auto value exists, but it does not yet have the effect described in the spec.Opera Android: The generic auto value exists, but it does not yet have the effect described in the spec.Samsung Internet: The generic auto value exists, but it does not yet have the effect described in the spec.WebView Android: The generic auto value exists, but it does not yet have the effect described in the spec.
css.properties.position-area 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.block-end 📋Safari9/15/2025 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
Chrome: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When bottom is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.center 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.end 📋Safari9/15/2025 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
Chrome: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When left is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-area.none 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.right 📋Safari9/15/2025 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/202674
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 Firefox2/24/202674
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 Firefox2/24/202674
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 Firefox2/24/202674
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 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-bottom 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-inline-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-left 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-right 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-self-block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-self-block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-self-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-self-inline-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-self-inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-self-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-self-x-end 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-area.span-self-x-start 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-area.span-self-y-end 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-area.span-self-y-start 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-area.span-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-top 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-x-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-x-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-y-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.span-y-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-area.top 📋Safari9/15/2025 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
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 Firefox2/24/2026162
Chrome: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.position-try.block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.bottom 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.center 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.flip-block 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.position-try.flip-inline 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.position-try.flip-start 📋Chrome5/14/2024 Firefox1/13/2026609
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 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.left 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.none 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.position-try.right 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.self-block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.self-block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.self-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.self-inline-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.self-inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.self-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.self-x-end 📋Safari12/12/2025 Firefox2/24/202674
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 Firefox2/24/202674
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 Firefox2/24/202674
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 Firefox2/24/202674
Chrome: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try.span-all 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-bottom 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-inline-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-left 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-right 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-self-block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-self-block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-self-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-self-inline-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-self-inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-self-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-self-x-end 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-try.span-self-x-start 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-try.span-self-y-end 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-try.span-self-y-start 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-try.span-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-top 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-x-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-x-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-y-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.span-y-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.top 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.x-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.x-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.y-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try.y-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks 📋Chrome8/20/2024 Firefox1/13/2026511
css.properties.position-try-fallbacks.block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.bottom 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.center 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.flip-block 📋Chrome8/20/2024 Firefox1/13/2026511
css.properties.position-try-fallbacks.flip-inline 📋Chrome8/20/2024 Firefox1/13/2026511
css.properties.position-try-fallbacks.flip-start 📋Chrome8/20/2024 Firefox1/13/2026511
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 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.left 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.none 📋Chrome8/20/2024 Firefox1/13/2026511
css.properties.position-try-fallbacks.position-area 📋Chrome8/20/2024 Firefox1/13/2026511
Chrome: inset-area values had to be wrapped inside an inset-area() function.Chrome Android: inset-area values had to be wrapped inside an inset-area() function.Edge: inset-area values had to be wrapped inside an inset-area() function.Opera: inset-area values had to be wrapped inside an inset-area() function.Opera Android: inset-area values had to be wrapped inside an inset-area() function.Samsung Internet: inset-area values had to be wrapped inside an inset-area() function.WebView Android: inset-area values had to be wrapped inside an inset-area() function.
css.properties.position-try-fallbacks.right 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.self-block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.self-block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.self-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.self-inline-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.self-inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.self-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.self-x-end 📋Safari12/12/2025 Firefox2/24/202674
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 Firefox2/24/202674
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 Firefox2/24/202674
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 Firefox2/24/202674
Chrome: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Chrome Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Edge: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Firefox: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Firefox for Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 2008537.Opera: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Opera Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.Samsung Internet: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When self-y-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.WebView Android: When y-self-start is used as a single keyword, or alongside span-all, it unexpectedly allows the anchored box to overflow the viewport, obscuring content. Use place-self: anchor-center as a workaround. See bug 438334710.
css.properties.position-try-fallbacks.span-all 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-bottom 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-inline-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-left 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-right 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-self-block-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-self-block-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-self-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-self-inline-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-self-inline-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-self-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-self-x-end 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-try-fallbacks.span-self-x-start 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-try-fallbacks.span-self-y-end 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-try-fallbacks.span-self-y-start 📋Chrome12/2/2025 Firefox1/13/202642
css.properties.position-try-fallbacks.span-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-top 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-x-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-x-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-y-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.span-y-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.top 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.x-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.x-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.y-end 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-fallbacks.y-start 📋Chrome9/17/2024 Firefox1/13/2026483
css.properties.position-try-order 📋Chrome5/14/2024 Firefox2/24/2026651
css.properties.position-try-order.most-block-size 📋Chrome5/14/2024 Firefox2/24/2026651
css.properties.position-try-order.most-height 📋Chrome5/14/2024 Firefox2/24/2026651
css.properties.position-try-order.most-inline-size 📋Chrome5/14/2024 Firefox2/24/2026651
css.properties.position-try-order.most-width 📋Chrome5/14/2024 Firefox2/24/2026651
css.properties.position-try-order.normal 📋Chrome5/14/2024 Firefox2/24/2026651
css.properties.position-visibility 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.position-visibility.always 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.position-visibility.anchors-visible 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.position-visibility.no-overflow 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.print-color-adjust 📋Firefox2/8/2022 Edge5/1/20251178
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 📋Firefox11/29/2005 Safari9/30/20153592
css.properties.quotes.auto 📋Firefox10/22/2019 Safari4/26/2021552
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 📋Firefox11/29/2005 Safari9/30/20153592
css.properties.r 📋Chrome5/19/2015 Edge1/15/20201702
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 Firefox10/23/2018 Edge10/13/20231816
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 Firefox10/23/2018 Edge10/13/20231816
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 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.right.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.right.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.rotate 📋Firefox1/7/2020 Edge8/5/2022941
css.properties.rotate.none 📋Firefox1/7/2020 Edge8/5/2022941
css.properties.rotate.x_y_z_angle Firefox1/7/2020 Edge8/5/2022941
css.properties.row-gap 📋Chrome12/1/2015 Edge10/17/2017686
css.properties.row-gap.flex_context 📋Firefox10/23/2018 Safari4/26/2021916
css.properties.row-gap.grid_context 📋Edge10/17/2017 Safari9/17/2018335
css.properties.row-gap.normal 📋Chrome12/1/2015 Edge10/17/2017686
css.properties.ruby-align 📋Firefox5/12/2015 Safari12/11/20243501
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 📋Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-align.space-around 📋Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-align.space-between 📋Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-align.start 📋Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-position 📋Firefox5/12/2015 Safari12/11/20243501
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.over Firefox5/12/2015 Safari12/11/20243501
css.properties.ruby-position.under Firefox5/12/2015 Safari12/11/20243501
css.properties.rx 📋Chrome5/19/2015 Safari3/5/20243213
Safari: Before Safari 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.Safari on iOS: Before Safari on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.WebView on iOS: Before WebView on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.
css.properties.rx.auto 📋Chrome8/31/2016 Safari3/5/20242743
css.properties.ry 📋Chrome5/19/2015 Safari3/5/20243213
Safari: Before Safari 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.Safari on iOS: Before Safari on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.WebView on iOS: Before WebView on iOS 17.4, the value was recognized, but had no effect, and was only recognized as an attribute applied to the SVG element. See bug 266090.
css.properties.ry.auto 📋Chrome8/31/2016 Safari3/5/20242743
css.properties.scale 📋Firefox1/7/2020 Edge8/5/2022941
css.properties.scale.none 📋Firefox1/7/2020 Edge8/5/2022941
css.properties.scroll-behavior 📋Firefox2/24/2015 Safari3/14/20222575
css.properties.scroll-behavior.auto 📋Firefox2/24/2015 Safari3/14/20222575
css.properties.scroll-behavior.smooth 📋Firefox2/24/2015 Safari3/14/20222575
css.properties.scroll-margin 📋Chrome9/4/2018 Firefox7/13/20211043
Firefox: The scroll-margin property can cause an element's visibility to be incorrectly calculated for element.focus(). See bug 1708303.Firefox for Android: The scroll-margin property can cause an element's visibility to be incorrectly calculated for element.focus(). See bug 1708303.Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-block 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-block-end 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-block-start 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-bottom 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-inline 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-inline-end 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-inline-start 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-margin-left 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-right 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-margin-top 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Before version 14.1, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.Safari on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.WebView on iOS: Before version 14.5, scroll margin is not applied for scrolls to fragment target or scrollIntoView(), see bug 189265.
css.properties.scroll-padding 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding.auto 📋Safari9/19/2017 Edge1/15/2020848
css.properties.scroll-padding-block 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block.auto 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block-end 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block-end.auto 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block-start 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-block-start.auto 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-bottom 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding-bottom.auto 📋Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-inline 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline.auto 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline-end 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline-end.auto 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline-start 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-inline-start.auto 📋Chrome9/4/2018 Safari9/20/20211112
css.properties.scroll-padding-left 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding-left.auto 📋Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-right 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding-right.auto 📋Firefox7/9/2019 Safari9/20/2021804
css.properties.scroll-padding-top 📋Chrome9/4/2018 Safari4/26/2021965
Safari: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.Safari on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.WebView on iOS: Scroll padding is not applied for scrolls to fragment target or scrollIntoView(), see bug 179379.
css.properties.scroll-padding-top.auto 📋Firefox7/9/2019 Safari9/20/2021804
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 📋Chrome6/4/2019 Firefox7/26/20221148
css.properties.scroll-snap-stop.always 📋Chrome6/4/2019 Firefox7/26/20221148
css.properties.scroll-snap-stop.normal 📋Chrome6/4/2019 Firefox7/26/20221148
css.properties.scroll-snap-type 📋Safari9/19/2017 Firefox4/5/20221659
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 📋Firefox7/2/2015 Edge1/15/20201658
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 📋Firefox3/14/2023 Safari9/15/2025916
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-axis 📋Firefox3/14/2023 Safari9/15/2025916
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-name 📋Firefox3/14/2023 Safari9/15/2025916
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.scrollbar-color 📋Firefox12/11/2018 Safari12/12/20252558
css.properties.scrollbar-color.auto 📋Firefox12/11/2018 Safari12/12/20252558
css.properties.scrollbar-gutter 📋Chrome9/21/2021 Safari12/11/20241177
css.properties.scrollbar-gutter.auto 📋Chrome9/21/2021 Safari12/11/20241177
css.properties.scrollbar-gutter.stable 📋Chrome9/21/2021 Safari12/11/20241177
css.properties.scrollbar-width 📋Firefox12/11/2018 Safari12/11/20242192
css.properties.scrollbar-width.auto 📋Firefox12/11/2018 Safari12/11/20242192
css.properties.scrollbar-width.none 📋Firefox12/11/2018 Safari12/11/20242192
css.properties.scrollbar-width.thin 📋Firefox12/11/2018 Safari12/11/20242192
css.properties.shape-image-threshold 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-margin 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.border-box 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.circle Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.content-box 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.gradient 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.image 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.inset Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.margin-box 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.none 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.padding-box 📋Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-outside.polygon Chrome8/26/2014 Edge1/15/20201968
css.properties.shape-rendering 📋Firefox6/17/2008 Edge1/15/20204229
css.properties.shape-rendering.auto 📋Firefox6/17/2008 Edge1/15/20204229
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 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.stop-opacity 📋Firefox6/17/2008 Edge4/5/20173214
css.properties.stroke 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke.none 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-dasharray 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-dasharray.none 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-dashoffset 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linecap 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linecap.butt 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linecap.round 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linecap.square 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linejoin 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linejoin.bevel 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linejoin.miter 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-linejoin.round 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-miterlimit 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-opacity 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.stroke-width 📋Firefox11/29/2005 Edge4/5/20174145
css.properties.tab-size 📋Chrome7/31/2012 Firefox8/10/20213297
Chrome: This property is not yet animatable.Chrome Android: This property is not yet animatable.Edge: This property is not yet animatable.Firefox: Before Firefox 53, this property was not animatable.Firefox for Android: Before Firefox for Android 53, this property was not animatable.Quest Browser: This property is not yet animatable.Samsung Internet: This property is not yet animatable.
css.properties.tab-size.length 📋Chrome4/14/2015 Safari3/24/20201806
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 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.text-align.end 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.text-align.justify 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-align.left 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.text-align.match-parent 📋Chrome12/13/2011 Safari3/14/20223744
css.properties.text-align.right 📋Firefox11/9/2004 Edge1/15/20205545
css.properties.text-align.start 📋Firefox11/9/2004 Edge1/15/20205545
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 📋Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.center 📋Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.end 📋Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.justify 📋Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.left 📋Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.right 📋Firefox4/24/2012 Safari9/12/20223793
css.properties.text-align-last.start 📋Firefox4/24/2012 Safari9/12/20223793
css.properties.text-anchor 📋Firefox6/17/2008 Edge8/2/20162968
css.properties.text-anchor.end 📋Firefox6/17/2008 Edge8/2/20162968
css.properties.text-anchor.middle 📋Firefox6/17/2008 Edge8/2/20162968
css.properties.text-anchor.start 📋Firefox6/17/2008 Edge8/2/20162968
css.properties.text-autospace 📋Safari3/31/2025 Firefox11/11/2025225
css.properties.text-autospace.no-autospace 📋Safari3/31/2025 Firefox11/11/2025225
css.properties.text-autospace.normal 📋Safari3/31/2025 Firefox11/11/2025225
css.properties.text-combine-upright 📋Chrome1/20/2016 Safari3/14/20222245
Chrome: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Chrome Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Firefox: Before version 81, Firefox implemented the property as animatable. This was corrected to spec in 81.Firefox for Android: Before version 81, Firefox for Android implemented the property as animatable. This was corrected to spec in 81.Quest Browser: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Opera: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Opera Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Safari: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Safari on iOS: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.Samsung Internet: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.WebView Android: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.WebView on iOS: This property was initially named -webkit-text-combine according to a 2011 version of the CSS3 Writing Modes specification, supporting the values none and horizontal without digits.
css.properties.text-combine-upright.all 📋Chrome1/20/2016 Safari3/14/20222245
css.properties.text-combine-upright.none 📋Chrome1/20/2016 Safari3/14/20222245
css.properties.text-decoration 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.auto 📋Firefox10/22/2019 Safari12/12/20252243
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 📋Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.dashed 📋Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.dotted 📋Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.double 📋Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.from-font 📋Firefox10/22/2019 Safari12/12/20252243
css.properties.text-decoration.grammar-error 📋Chrome1/23/2024 Safari12/12/2025689
css.properties.text-decoration.includes_color-and-style Firefox8/16/2011 Safari12/12/20255232
css.properties.text-decoration.includes_thickness Firefox10/22/2019 Safari12/12/20252243
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 📋Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.spelling-error 📋Chrome1/23/2024 Safari12/12/2025689
css.properties.text-decoration.transparent 📋Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration.underline 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-decoration.wavy 📋Firefox11/15/2016 Safari12/12/20253314
css.properties.text-decoration-color 📋Firefox2/24/2015 Edge1/15/20201786
css.properties.text-decoration-color.currentColor 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-color.transparent 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-line 📋Firefox2/24/2015 Edge1/15/20201786
css.properties.text-decoration-line.blink 📋Firefox12/10/2013 Edge1/15/20202227
Chrome: The blink value does not have any effect.Chrome Android: The blink value does not have any effect.Edge: The blink value does not have any effect.Firefox: The blink value does not have any effect.Firefox for Android: The blink value does not have any effect.Quest Browser: The blink value does not have any effect.Samsung Internet: The blink value does not have any effect.WebView Android: The blink value does not have any effect.
css.properties.text-decoration-line.grammar-error 📋Chrome1/23/2024 Safari12/12/2025689
css.properties.text-decoration-line.line-through 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-line.none 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-line.overline 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-line.spelling-error 📋Chrome1/23/2024 Safari12/12/2025689
css.properties.text-decoration-line.underline 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-skip-ink 📋Chrome1/23/2018 Safari3/14/20221511
css.properties.text-decoration-skip-ink.auto 📋Chrome1/23/2018 Safari3/14/20221511
css.properties.text-decoration-skip-ink.none 📋Chrome1/23/2018 Safari3/14/20221511
css.properties.text-decoration-style 📋Firefox2/24/2015 Edge1/15/20201786
css.properties.text-decoration-style.dashed 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style.dotted 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style.double 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style.solid 📋Firefox8/16/2011 Edge1/15/20203074
css.properties.text-decoration-style.wavy 📋Firefox8/16/2011 Edge1/15/20203074
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 Firefox3/10/2020 Safari3/5/20241456
css.properties.text-emphasis 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis.circle 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.currentColor 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.dot 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.double-circle 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.filled 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.none 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.open 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.sesame 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.transparent 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis.triangle 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis-color 📋Safari10/22/2013 Edge3/3/20223054
css.properties.text-emphasis-color.currentColor 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis-color.transparent 📋Chrome2/21/2013 Edge1/15/20202519
css.properties.text-emphasis-position 📋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 Firefox12/13/20223339
css.properties.text-emphasis-position.right Safari10/16/2014 Edge1/15/20201917
css.properties.text-emphasis-position.under Safari10/22/2013 Firefox12/13/20223339
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 📋Firefox9/22/2015 Safari9/16/20201821
css.properties.text-orientation.mixed 📋Firefox9/22/2015 Safari3/24/20201645
css.properties.text-orientation.sideways 📋Chrome6/7/2011 Edge1/15/20203144
css.properties.text-orientation.upright 📋Chrome6/7/2011 Safari3/24/20203213
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 📋Firefox11/9/2004 Edge1/15/20205545
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 Firefox11/9/2004 Edge1/15/20205545
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 Firefox11/9/2004 Edge1/15/20205545
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 Firefox7/17/2012 Edge7/29/20151107
css.properties.text-transform.none 📋Safari6/23/2003 Edge7/29/20154419
css.properties.text-transform.turkic_is Firefox7/17/2012 Edge7/29/20151107
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 📋Firefox3/10/2020 Safari12/11/20241737
css.properties.text-underline-position 📋Chrome2/20/2014 Firefox3/10/20202210
css.properties.text-underline-position.auto 📋Chrome2/20/2014 Firefox3/10/20202210
css.properties.text-underline-position.from-font 📋Safari3/25/2019 Edge11/19/2020605
css.properties.text-underline-position.left 📋Chrome12/4/2018 Safari12/11/20242199
css.properties.text-underline-position.right 📋Chrome12/4/2018 Safari12/11/20242199
css.properties.text-underline-position.under 📋Chrome2/20/2014 Firefox3/10/20202210
css.properties.text-wrap 📋Chrome5/30/2023 Safari3/5/2024280
css.properties.text-wrap.auto 📋Firefox12/19/2023 Edge10/17/2024303
css.properties.text-wrap.balance 📋Chrome5/30/2023 Safari5/13/2024349
css.properties.text-wrap.nowrap 📋Chrome5/30/2023 Firefox3/19/2024294
css.properties.text-wrap.stable 📋Firefox12/19/2023 Edge10/17/2024303
css.properties.text-wrap.wrap 📋Chrome5/30/2023 Firefox3/19/2024294
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 📋Firefox3/19/2024 Edge10/17/2024212
css.properties.text-wrap-style.auto 📋Firefox3/19/2024 Edge10/17/2024212
css.properties.text-wrap-style.balance 📋Firefox3/19/2024 Edge10/17/2024212
css.properties.text-wrap-style.stable 📋Firefox3/19/2024 Edge10/17/2024212
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 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.top.anchor-size 📋Chrome1/14/2025 Firefox1/13/2026364
css.properties.top.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.touch-action 📋Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.manipulation Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.none Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-x Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pan-y Chrome7/16/2014 Safari9/19/20191891
Firefox: Not applicable to Firefox platforms that support neither pointer nor touch events.
css.properties.touch-action.pinch-zoom Edge7/29/2015 Firefox1/26/20212008
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 📋Firefox10/9/2012 Safari9/30/20151086
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 📋Firefox8/8/2017 Edge1/15/2020890
css.properties.transform-box.border-box 📋Firefox8/8/2017 Edge10/13/20232257
css.properties.transform-box.content-box 📋Safari3/24/2020 Firefox4/16/20241484
css.properties.transform-box.fill-box 📋Firefox8/8/2017 Edge1/15/2020890
css.properties.transform-box.stroke-box 📋Safari3/24/2020 Firefox4/16/20241484
css.properties.transform-box.view-box 📋Firefox8/8/2017 Edge1/15/2020890
css.properties.transform-origin 📋Firefox10/9/2012 Safari9/30/20151086
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 Chrome5/15/2012 Edge4/30/20182176
Firefox: Keywords and percentages refer to the canvas instead of the object itself. See bug 1209061.Firefox for Android: Keywords and percentages refer to the canvas instead of the object itself. See bug 1209061.Safari: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).Safari on iOS: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).WebView on iOS: Only supported for transformations applied using the CSS transform property (e.g. .className { transform: rotate(45deg); transform-origin: center; }). It has no effect on transformations applied using the transform SVG attribute (e.g. <rect style="transform-origin: center;" transform="rotate(45)" />).
css.properties.transform-origin.three_value_syntax Safari6/7/2010 Edge7/29/20151878
css.properties.transform-origin.top 📋Safari4/29/2005 Edge7/29/20153743
css.properties.transform-style 📋Firefox10/9/2012 Safari9/30/20151086
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 📋Firefox10/9/2012 Safari9/30/20151086
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 📋Firefox3/22/2011 Safari9/20/20162009
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 📋Firefox3/22/2011 Safari9/20/20162009
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 Chrome9/12/2023 Firefox8/6/2024329
css.properties.transition-behavior 📋Chrome9/12/2023 Firefox8/6/2024329
css.properties.transition-behavior.allow-discrete 📋Chrome9/12/2023 Firefox8/6/2024329
css.properties.transition-behavior.normal 📋Chrome9/12/2023 Firefox8/6/2024329
css.properties.transition-delay 📋Firefox10/9/2012 Safari9/30/20151086
css.properties.transition-duration 📋Firefox10/9/2012 Safari9/30/20151086
css.properties.transition-property 📋Firefox10/9/2012 Safari9/30/20151086
css.properties.transition-property.IDENT_value Chrome12/11/2008 Edge7/29/20152421
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 📋Firefox10/9/2012 Safari9/30/20151086
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 Firefox1/29/2019 Safari9/16/2020596
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 📋Firefox1/7/2020 Edge8/5/2022941
css.properties.translate.none 📋Firefox1/7/2020 Edge8/5/2022941
css.properties.unicode-bidi 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.unicode-bidi.bidi-override 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.unicode-bidi.embed 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.unicode-bidi.isolate 📋Chrome1/20/2016 Edge1/15/20201456
Chrome: Before Chrome 47, -webkit-isolate could lock up the browser.Chrome: Since Chrome 19, the syntax from a previous version of the specification, where the isolate keyword could be used together with bidi-override, is allowed.Firefox: From Firefox 10 to Firefox 16 (inclusive), the isolate keyword could be used together with bidi-override, which was the syntax from a previous version of the specification. From Firefox 17, only one value is allowed. Use isolate-override instead the previous isolate bidi-override.Firefox for Android: From Firefox for Android 10 to Firefox for Android 16 (inclusive), the isolate keyword could be used together with bidi-override, which was the syntax from a previous version of the specification. From Firefox for Android 17, only one value is allowed. Use isolate-override instead the previous isolate bidi-override.Opera: Before Opera 34, -webkit-isolate could lock up the browser.Opera: Since Opera 15, the syntax from a previous version of the specification, where the isolate keyword could be used together with bidi-override, is allowed.Safari: Before Safari 9, -webkit-isolate could lock up the browser.Safari on iOS: Before Safari on iOS 9, -webkit-isolate could lock up the browser.WebView on iOS: Before WebView on iOS 9, -webkit-isolate could lock up the browser.
css.properties.unicode-bidi.isolate-override 📋Chrome1/20/2016 Edge1/15/20201456
css.properties.unicode-bidi.normal 📋Firefox11/9/2004 Edge7/29/20153914
css.properties.unicode-bidi.plaintext 📋Chrome1/20/2016 Edge1/15/20201456
Firefox: Before Firefox 50, the plaintext value was ignored for vertical writing modes (bug 1302734).Firefox: Before Firefox 15, plaintext didn't do anything to an inline element. The specification changed and the implementation was changed in Firefox 15.Firefox for Android: Before Firefox for Android 50, the plaintext value was ignored for vertical writing modes (bug 1302734).Firefox for Android: Before Firefox for Android 15, plaintext didn't do anything to an inline element. The specification changed and the implementation was changed in Firefox for Android 15.
css.properties.user-select 📋Safari10/26/2007 Edge1/15/20204464
css.properties.user-select.all Firefox11/9/2004 Safari9/12/20226516
css.properties.user-select.auto Firefox11/9/2004 Edge7/29/20153914
css.properties.user-select.none Safari4/29/2005 Edge7/29/20153743
css.properties.user-select.text Firefox11/9/2004 Edge7/29/20153914
css.properties.vector-effect 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.vector-effect.non-scaling-stroke 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.vector-effect.none 📋Chrome9/2/2010 Edge1/15/20203422
css.properties.vertical-align 📋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 📋Firefox6/6/2023 Safari9/15/2025832
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline-axis 📋Firefox6/6/2023 Safari9/15/2025832
Firefox: Now supports the x and y values, and also the deprecated horizontal and vertical values.
css.properties.view-timeline-name 📋Firefox3/14/2023 Safari9/15/2025916
css.properties.view-transition-class 📋Chrome5/14/2024 Firefox10/14/2025518
css.properties.view-transition-class.none 📋Chrome5/14/2024 Firefox10/14/2025518
css.properties.view-transition-name 📋Chrome3/7/2023 Firefox10/14/2025952
css.properties.view-transition-name.match-element 📋Safari3/31/2025 Firefox10/14/2025197
css.properties.view-transition-name.none 📋Chrome3/7/2023 Firefox10/14/2025952
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 📋Firefox11/9/2004 Edge7/29/20153914
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 📋Chrome7/30/2019 Safari3/24/2020238
css.properties.white-space.collapse 📋Chrome5/30/2023 Safari9/16/2024475
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 📋Chrome5/30/2023 Safari9/16/2024475
css.properties.white-space.preserve-breaks 📋Chrome5/30/2023 Safari9/16/2024475
css.properties.white-space.textarea_support Safari6/23/2003 Edge7/29/20154419
css.properties.white-space.wrap 📋Chrome5/30/2023 Safari9/16/2024475
css.properties.white-space-collapse 📋Chrome5/30/2023 Firefox3/19/2024294
css.properties.white-space-collapse.break-spaces 📋Chrome5/30/2023 Firefox3/19/2024294
css.properties.white-space-collapse.collapse 📋Chrome5/30/2023 Firefox3/19/2024294
css.properties.white-space-collapse.preserve 📋Chrome5/30/2023 Firefox3/19/2024294
css.properties.white-space-collapse.preserve-breaks 📋Chrome5/30/2023 Firefox3/19/2024294
css.properties.width 📋Safari6/23/2003 Edge7/29/20154419
css.properties.width.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.properties.width.auto 📋Safari6/23/2003 Edge7/29/20154419
css.properties.width.fit-content 📋Chrome10/13/2015 Firefox11/2/20212212
css.properties.width.is_animatable Firefox10/9/2012 Edge7/29/20151023
css.properties.width.max-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.width.min-content 📋Chrome10/13/2015 Edge1/15/20201555
css.properties.width.stretch 📋Safari10/22/2013 Firefox12/9/20254431
css.properties.will-change 📋Chrome7/16/2014 Edge1/15/20202009
css.properties.will-change.auto 📋Chrome7/16/2014 Edge1/15/20202009
css.properties.will-change.contents 📋Chrome7/16/2014 Edge1/15/20202009
css.properties.will-change.scroll-position 📋Chrome7/16/2014 Edge1/15/20202009
css.properties.word-break 📋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 Firefox5/21/20194225
css.properties.word-break.keep-all 📋Firefox8/28/2012 Safari9/30/20151128
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 Chrome12/11/2008 Firefox1/7/20204044
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 Chrome1/20/2016175
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 Firefox12/15/2015 Safari3/31/20253394
css.properties.writing-mode.sideways-rl Firefox12/15/2015 Safari3/31/20253394
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 Chrome1/20/2016175
css.properties.writing-mode.vertical-rl Edge7/29/2015 Chrome1/20/2016175
css.properties.writing-mode.vertical_oriented_form_controls Firefox11/21/2023 Edge4/18/2024149
Chrome: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Chrome: Supported for select, button, textarea and textual input elements.Chrome: Only supported for select and button elements.Chrome Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Chrome Android: Supported for select, button, textarea and textual input elements.Chrome Android: Only supported for select and button elements.Edge: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Edge: Supported for select, button, textarea and textual input elements.Edge: Only supported for select and button elements.Opera: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Opera: Supported for select, button, textarea and textual input elements.Opera: Only supported for select and button elements.Opera Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Opera Android: Supported for select, button, textarea and textual input elements.Opera Android: Only supported for select and button elements.Safari: Support for range sliders, textual inputs, and textareas onlySafari on iOS: Support for range sliders, textual inputs, and textareas onlySamsung Internet: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.Samsung Internet: Supported for select, button, textarea and textual input elements.WebView Android: Supported for select, button, textarea, textual input, range slider, meter, and progress elements.WebView Android: Supported for select, button, textarea and textual input elements.WebView Android: Only supported for select and button elements.WebView on iOS: Support for range sliders, textual inputs, and textareas only
css.properties.x 📋Chrome4/14/2015 Edge1/15/20201737
css.properties.y 📋Chrome4/14/2015 Edge1/15/20201737
css.properties.z-index 📋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 Firefox5/14/20245901
Firefox: Before Firefox 131, SVG elements are not zoomed properly. See bug 1905023 and bug 878346.Firefox for Android: Before Firefox for Android 131, SVG elements are not zoomed properly. See bug 1905023 and bug 878346.
css.selectors.active 📋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 📋Chrome5/14/2024 Firefox10/14/2025518
css.selectors.active-view-transition-type 📋Chrome5/14/2024 Firefox1/13/2026609
css.selectors.after 📋Firefox11/29/2005 Edge7/29/20153529
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 Firefox3/22/2011 Edge7/29/20151590
css.selectors.any-link 📋Safari9/30/2015 Edge1/15/20201568
css.selectors.any-link.not_match_link Chrome3/6/2018 Safari9/20/20211294
css.selectors.attribute 📋Firefox11/9/2004 Edge7/29/20153914
css.selectors.attribute.case_insensitive_modifier Safari9/30/2015 Edge1/15/20201568
css.selectors.autofill 📋Firefox2/23/2021 Edge2/9/2023716
Firefox: The :autofill pseudo-class matches autofilled username and password fields, but not other autocompleted fields. See bug 1923525.Firefox: The :-webkit-autofill pseudo-class matches autofilled username and password fields, but not other autocompleted fields. See bug 1923525.Firefox for Android: The :autofill pseudo-class matches autofilled username and password fields, but not other autocompleted fields. See bug 1923525.Firefox for Android: The :-webkit-autofill pseudo-class matches autofilled username and password fields, but not other autocompleted fields. See bug 1923525.
css.selectors.backdrop 📋Chrome8/26/2014 Safari3/14/20222757
css.selectors.backdrop.dialog Chrome1/14/2014 Safari3/14/20222981
css.selectors.backdrop.fullscreen Edge7/29/2015 Safari3/27/20232798
css.selectors.backdrop.inherit_from_originating_element Firefox11/21/2023 Safari3/5/2024105
css.selectors.backdrop.popover Chrome5/30/2023 Firefox4/16/2024322
css.selectors.before 📋Firefox11/29/2005 Edge7/29/20153529
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 Firefox3/22/2011 Edge7/29/20151590
css.selectors.checked 📋Firefox11/9/2004 Edge7/29/20153914
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 📋Chrome3/26/2013 Edge1/15/20202486
Firefox: From Firefox 69, only allowed properties apply to the ::cue pseudo-element with no argument. See Permitted properties for a list of the allowed properties.
css.selectors.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 📋Chrome11/12/2024 Firefox9/16/2025308
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 📋Firefox9/20/2016 Edge12/7/20232634
css.selectors.disabled 📋Firefox11/9/2004 Edge7/29/20153914
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 📋Firefox11/9/2004 Edge7/29/20153914
css.selectors.enabled 📋Firefox11/9/2004 Edge7/29/20153914
css.selectors.file-selector-button 📋Firefox10/20/2020 Safari4/26/2021188
css.selectors.first 📋Chrome3/28/2012 Firefox8/1/20234143
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 📋Firefox3/7/2017 Edge1/15/20201044
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.has 📋Safari3/14/2022 Firefox12/19/2023645
css.selectors.highlight 📋Edge9/1/2022 Firefox6/24/20251027
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 📋Firefox11/9/2004 Edge7/29/20153914
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 Firefox11/9/2004 Edge7/29/20153914
css.selectors.hover.all_elements Firefox11/9/2004 Edge7/29/20153914
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 📋Chrome3/8/2011 Edge11/12/20151710
Chrome: Before Chrome 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome 52, it was changed to only match enabled read-write inputs.Chrome Android: Before Chrome Android 52, :in-range matched disabled and read-only inputs (see bug 41248615). In Chrome Android 52, it was changed to only match enabled read-write inputs.Firefox: Before Firefox 50, :in-range matched disabled and read-only inputs (see bug 1264157). In Firefox 50, it was changed to only match enabled read-write inputs.Quest Browser: Before Quest Browser 5.0, :in-range matched disabled and read-only inputs (see bug 41248615). In Quest Browser 5.0, it was changed to only match enabled read-write inputs.Opera: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Opera Android: Before Opera 39, :in-range matched disabled and read-only inputs (see bug 41248615). In Opera 39, it was changed to only match enabled read-write inputs.Safari: In Safari, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Safari on iOS: In Safari on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.Samsung Internet: Before version 6.0, :in-range matched disabled and read-only inputs (see bug 41248615). In version 6.0, it was changed to only match enabled read-write inputs.WebView Android: Before version 52, :in-range matched disabled and read-only inputs (see bug 41248615). In version 52, it was changed to only match enabled read-write inputs.WebView on iOS: In WebView on iOS, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.
css.selectors.indeterminate 📋Firefox10/24/2006 Edge7/29/20153200
css.selectors.indeterminate.checkbox Safari10/26/2007 Edge7/29/20152833
css.selectors.indeterminate.progress Chrome9/2/2010 Edge7/29/20151791
css.selectors.indeterminate.radio Chrome11/18/2014 Edge1/15/20201884
css.selectors.invalid 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.invalid.form Firefox6/5/2012 Edge1/15/20202780
css.selectors.is 📋Firefox6/30/2020 Edge1/21/2021205
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 📋Firefox11/9/2004 Edge7/29/20153914
css.selectors.last-child 📋Firefox11/9/2004 Edge7/29/20153914
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.link 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.link.not_match_link Chrome12/11/2008 Safari9/20/20214666
css.selectors.list 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.marker 📋Safari4/12/2018 Chrome10/20/2020922
Safari: Safari support is limited to color and font-size.Safari on iOS: Safari on iOS support is limited to color and font-size.WebView on iOS: WebView on iOS support is limited to color and font-size.
css.selectors.marker.animation_and_transition_support Firefox8/25/2020 Safari4/26/2021244
css.selectors.modal 📋Safari7/20/2022 Chrome9/2/202244
css.selectors.namespace 📋Firefox11/9/2004 Edge7/29/20153914
css.selectors.nesting 📋Firefox8/29/2023 Safari12/11/2023104
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 Firefox8/19/2025 Safari12/12/2025115
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 📋Firefox11/9/2004 Edge7/29/20153914
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 Firefox5/9/20232778
css.selectors.nth-last-child 📋Safari3/18/2008 Edge7/29/20152689
css.selectors.nth-last-child.of_syntax Safari9/30/2015 Firefox5/9/20232778
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 📋Firefox11/29/2005 Edge7/29/20153529
css.selectors.only-child.no_parent_required Firefox3/7/2017 Safari9/18/20232386
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 📋Chrome3/8/2011 Edge11/12/20151710
css.selectors.part 📋Chrome3/12/2019 Safari3/24/2020378
css.selectors.placeholder 📋Firefox1/24/2017 Edge1/15/20201086
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 📋Chrome5/30/2023 Firefox4/16/2024322
css.selectors.read-only 📋Chrome12/11/2008 Firefox6/30/20204219
css.selectors.read-write 📋Chrome12/11/2008 Firefox6/30/20204219
css.selectors.required 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.root 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.scope 📋Chrome5/21/2013 Edge1/15/20202430
Firefox: Firefox 55 removes support for <style scoped> but not for the :scope pseudo-class, which is still supported. <style scoped> made it possible to explicitly set up element scopes, but ongoing discussions about the design of this feature as well as lack of other implementations resulted in the decision to remove it.Firefox for Android: Firefox for Android 55 removes support for <style scoped> but not for the :scope pseudo-class, which is still supported. <style scoped> made it possible to explicitly set up element scopes, but ongoing discussions about the design of this feature as well as lack of other implementations resulted in the decision to remove it.
css.selectors.scope.dom_api Chrome5/21/2013 Edge1/15/20202430
css.selectors.selection 📋Safari10/24/2003 Firefox9/5/20185430
css.selectors.slotted 📋Chrome4/13/2016 Edge1/15/20201372
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 📋Firefox11/9/2004 Edge7/29/20153914
Internet Explorer: Before Internet Explorer 10, the combinator only works in standards mode.
css.selectors.target 📋Firefox11/9/2004 Edge7/29/20153914
css.selectors.target-text 📋Chrome3/2/2021 Safari12/11/20241380
css.selectors.type 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.type.namespaces Firefox11/9/2004 Edge7/29/20153914
css.selectors.universal 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.universal.namespaces Firefox11/9/2004 Edge7/29/20153914
css.selectors.user-invalid 📋Firefox4/19/2021 Edge11/2/2023927
css.selectors.user-valid 📋Firefox4/19/2021 Edge11/2/2023927
css.selectors.valid 📋Safari6/7/2010 Edge7/29/20151878
css.selectors.valid.form Firefox6/5/2012 Edge1/15/20202780
css.selectors.view-transition 📋Chrome1/10/2023 Firefox10/14/20251008
css.selectors.view-transition-group 📋Chrome1/10/2023 Firefox10/14/20251008
css.selectors.view-transition-image-pair 📋Chrome1/10/2023 Firefox10/14/20251008
css.selectors.view-transition-new 📋Chrome1/10/2023 Firefox10/14/20251008
css.selectors.view-transition-old 📋Chrome1/10/2023 Firefox10/14/20251008
css.selectors.visited 📋Safari6/23/2003 Edge7/29/20154419
css.selectors.visited.not_match_link Chrome12/11/2008 Safari9/20/20214666
css.selectors.visited.privacy_measures Safari6/7/2010 Edge7/29/20151878
css.selectors.where 📋Firefox6/30/2020 Edge1/21/2021205
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 📋Chrome5/14/2024 Firefox1/13/2026609
css.types.anchor-size 📋Chrome5/14/2024 Firefox1/13/2026609
css.types.angle 📋Chrome5/21/2009 Edge7/29/20152260
css.types.angle.deg Chrome5/21/2009 Edge7/29/20152260
css.types.angle.grad Chrome5/21/2009 Edge7/29/20152260
css.types.angle.rad Chrome5/21/2009 Edge7/29/20152260
css.types.angle.turn Chrome5/21/2009 Edge7/29/20152260
css.types.angle-percentage 📋Chrome5/21/2009 Edge7/29/20152260
css.types.asin 📋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 📋Firefox11/9/2004 Edge7/29/20153914
css.types.attr.declaration-value 📋Firefox10/24/2023 Safari3/31/2025524
css.types.basic-shape 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.animation Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.circle 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.ellipse 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.inset 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.path 📋Chrome7/20/2016 Safari3/24/20201343
css.types.basic-shape.path.clip-path 📋Firefox1/7/2020 Edge1/21/2021380
css.types.basic-shape.path.offset-path 📋Chrome1/25/2017 Safari9/12/20222056
css.types.basic-shape.polygon 📋Chrome8/26/2014 Edge1/15/20201968
css.types.basic-shape.rect 📋Chrome10/31/2023 Firefox1/23/202484
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 Firefox2/24/2026330
css.types.basic-shape.xywh 📋Chrome10/31/2023 Firefox1/23/202484
Chrome: Only supported on the offset-path property.Chrome Android: Only supported on the offset-path property.Edge: Only supported on the offset-path property.Opera: Only supported on the offset-path property.Opera Android: Only supported on the offset-path property.Samsung Internet: Only supported on the offset-path property.WebView Android: Only supported on the offset-path property.
css.types.blend-mode 📋Chrome5/20/2014 Edge1/15/20202066
css.types.calc 📋Firefox10/9/2012 Edge7/29/20151023
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 Firefox7/9/2024470
css.types.calc.gradient_color_stops Chrome5/15/2012 Edge7/29/20151170
css.types.calc.nested Chrome5/25/2016 Edge10/17/2017510
css.types.calc.number_values Safari7/25/2012 Firefox8/2/20161469
css.types.calc-keyword 📋Chrome3/1/2022 Firefox12/13/2022287
css.types.calc-keyword.NaN Chrome3/1/2022 Firefox6/6/2023462
css.types.calc-keyword.e Safari3/14/2022 Edge2/9/2023332
css.types.calc-keyword.infinity Chrome3/1/2022 Firefox6/6/2023462
css.types.calc-keyword.pi Safari3/14/2022 Edge1/12/2023304
css.types.clamp 📋Chrome12/10/2019 Firefox4/7/2020119
css.types.color 📋Safari6/23/2003 Edge7/29/20154419
css.types.color.color 📋Safari9/20/2021 Firefox5/9/2023596
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 📋Firefox12/9/2025 Edge1/21/202643
css.types.color.color.mixed_type_parameters Safari9/20/2021 Firefox5/9/2023596
css.types.color.color.relative_syntax 📋Chrome10/31/2023 Safari9/16/2024321
Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified as percentages with units (%).
css.types.color.color-mix 📋Safari12/13/2022 Firefox5/9/2023147
css.types.color.currentcolor 📋Firefox11/29/2005 Edge7/29/20153529
css.types.color.hsl 📋Firefox11/9/2004 Edge7/29/20153914
css.types.color.hsl.alpha_parameter Firefox3/7/2017 Edge1/15/20201044
css.types.color.hsl.mixed_type_parameters Chrome1/23/2024 Safari9/16/2024237
css.types.color.hsl.relative_syntax 📋Chrome5/14/2024 Safari9/16/2024125
Chrome: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Chrome Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Edge: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).Samsung Internet: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView Android: s and l channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require s and l values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for s and l).
css.types.color.hsl.space_separated_parameters Firefox3/7/2017 Edge1/15/20201044
css.types.color.hwb 📋Safari9/20/2021 Edge4/28/2022220
css.types.color.hwb.mixed_type_parameters Chrome1/23/2024 Safari9/16/2024237
css.types.color.hwb.relative_syntax 📋Chrome5/14/2024 Safari9/16/2024125
Chrome: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Chrome Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Edge: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Opera Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.Safari: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).Safari on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).Samsung Internet: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView Android: w and b channel values incorrectly resolve to numbers between 0-1 rather than 0-100. As a result, channel value calculations require w and b values to be specified as decimal percentage equivalents (e.g. 0.2 for 20%). See bug 330096624.WebView on iOS: Implementation based on older spec version. As a result, calculations with channel values do not work correctly, requiring values to be specified with units (deg for h, % for w and b).
css.types.color.lab 📋Safari9/20/2021 Firefox5/9/2023596
css.types.color.lab.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.lab.relative_syntax 📋Safari3/27/2023 Firefox7/9/2024470
css.types.color.lch 📋Safari9/20/2021 Firefox5/9/2023596
css.types.color.lch.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.lch.relative_syntax 📋Chrome10/31/2023 Safari9/16/2024321
Safari: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Safari on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).WebView on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).
css.types.color.light-dark 📋Firefox11/21/2023 Safari5/13/2024174
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 Chrome10/7/2014 Safari9/30/2015358
css.types.color.named-color.transparent 📋Safari3/18/2008 Edge7/29/20152689
css.types.color.oklab 📋Safari3/14/2022 Firefox5/9/2023421
css.types.color.oklab.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.oklab.relative_syntax 📋Safari3/27/2023 Firefox7/9/2024470
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 Firefox5/9/2023421
css.types.color.oklch.mixed_type_parameters Safari12/13/2022 Edge8/21/2023251
css.types.color.oklch.relative_syntax 📋Chrome2/20/2024 Safari9/16/2024209
Chrome: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Chrome Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Edge: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Opera: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Opera Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.Safari: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Safari on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).Samsung Internet: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.WebView Android: l channel values incorrectly resolve to numbers between 0-100 rather than 0-1. As a result, channel value calculations require l values to be specified as percentage numbers without units (e.g. 20 for 0.2). See bug 40940488.WebView on iOS: Implementation based on older spec version. As a result, calculations with h channel values do not work correctly, requiring values to be specified with units (deg).
css.types.color.rgb 📋Safari6/23/2003 Edge7/29/20154419
css.types.color.rgb.alpha_parameter Firefox3/7/2017 Edge1/15/20201044
css.types.color.rgb.float_values Firefox3/7/2017 Edge1/15/20201044
css.types.color.rgb.mixed_type_parameters Firefox5/9/2023 Safari9/16/2024496
css.types.color.rgb.relative_syntax 📋Chrome2/20/2024 Safari9/16/2024209
Chrome: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Chrome Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Edge: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Opera: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Opera Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.Safari: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.Safari on iOS: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.Samsung Internet: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.WebView Android: Channel values incorrectly resolve to numbers between 0-1 rather than 0-255. As a result, channel value calculations require values to be specified as decimal percentage equivalents (e.g. 0.3 for 30%, which would be equivalent to a 76.5 <number> value). See bug 41490327.WebView on iOS: Implementation based on older spec version. As a result, channel value calculations do not work correctly, requiring values to be specified as percentages with units (e.g. 30%, which would be equivalent to a 76.5 <number> value). See bug 267647.
css.types.color.rgb.space_separated_parameters Firefox3/7/2017 Edge1/15/20201044
css.types.color.rgb_hexadecimal_notation 📋Safari6/23/2003 Edge7/29/20154419
css.types.color.rgb_hexadecimal_notation.alpha_hexadecimal_notation Firefox9/20/2016 Edge1/15/20201212
css.types.color.system-color 📋Safari6/23/2003 Edge7/29/20154419
css.types.color.system-color.accentcolor_accentcolortext 📋Firefox7/26/2022 Edge7/21/2023360
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 📋Firefox11/9/2004 Edge7/29/20153914
css.types.counters 📋Firefox11/29/2005 Edge7/29/20153529
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 📋Firefox3/22/2011 Edge7/29/20151590
css.types.easing-function.linear-function 📋Firefox4/11/2023 Safari12/11/2023244
css.types.easing-function.steps 📋Chrome12/2/2010 Edge7/29/20151700
css.types.easing-function.steps.jump Firefox1/29/2019 Safari9/16/2020596
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 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.blur 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.brightness 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.contrast 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.drop-shadow 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.grayscale 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.hue-rotate 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.invert 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.opacity 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.saturate 📋Chrome3/28/2012 Edge7/29/20151218
css.types.filter-function.sepia 📋Chrome3/28/2012 Edge7/29/20151218
css.types.flex 📋Chrome8/20/2013 Safari3/27/20171315
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 Chrome7/27/20201589
css.types.global_keywords.revert-layer 📋Firefox2/8/2022 Safari3/14/202234
css.types.global_keywords.unset 📋Firefox2/4/2014 Safari3/21/2016776
css.types.gradient 📋Firefox1/21/2010 Edge7/29/20152015
Firefox: Gradients are limited to background-image, border-image, and mask-image.Firefox for Android: Gradients are limited to background-image, border-image, and mask-image.
css.types.gradient.conic-gradient 📋Chrome9/4/2018 Firefox11/17/2020805
css.types.gradient.conic-gradient.doubleposition Chrome1/29/2019 Firefox11/17/2020658
css.types.gradient.conic-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.conic-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.conic-gradient.single_color_stop 📋Firefox3/4/2025 Edge4/4/202531
css.types.gradient.linear-gradient 📋Firefox10/9/2012 Edge7/29/20151023
Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Internet Explorer: Internet Explorer 5.5 through 9.0 supported gradients via a proprietary filter: -ms-filter: progid:DXImageTransform.Microsoft.Gradient().Opera: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Safari: Safari 4 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in linear-gradient(). This old outdated syntax is still supported for compatibility purposes.Safari: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Safari on iOS: Safari on iOS 3.2 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in linear-gradient(). This old outdated syntax is still supported for compatibility purposes.Safari on iOS: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.WebView on iOS: WebView on iOS 3.2 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in linear-gradient(). This old outdated syntax is still supported for compatibility purposes.WebView on iOS: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.
css.types.gradient.linear-gradient.doubleposition Chrome12/4/2018 Edge1/15/2020407
css.types.gradient.linear-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.linear-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.linear-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.linear-gradient.premultiplied_gradients Chrome8/20/2013 Safari9/20/20212953
css.types.gradient.linear-gradient.single_color_stop 📋Firefox3/4/2025 Edge4/4/202531
css.types.gradient.linear-gradient.to Firefox1/31/2012 Edge7/29/20151275
css.types.gradient.linear-gradient.unitless_0_angle Chrome3/26/2013 Firefox8/8/20171596
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 📋Firefox10/9/2012 Edge7/29/20151023
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 Firefox1/31/2012 Edge7/29/20151275
css.types.gradient.radial-gradient.doubleposition Chrome12/4/2018 Edge1/15/2020407
css.types.gradient.radial-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.radial-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.radial-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.radial-gradient.premultiplied_gradients Chrome8/20/2013 Safari9/20/20212953
css.types.gradient.radial-gradient.single_color_stop 📋Firefox3/4/2025 Edge4/4/202531
css.types.gradient.repeating-conic-gradient 📋Chrome9/4/2018 Firefox11/17/2020805
css.types.gradient.repeating-conic-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-conic-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-conic-gradient.single_color_stop 📋Firefox3/4/2025 Edge4/4/202531
css.types.gradient.repeating-linear-gradient 📋Firefox10/9/2012 Edge7/29/20151023
Firefox: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Firefox for Android: Before Firefox for Android 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Internet Explorer: Internet Explorer 5.5 through 9.0 supported gradients via a proprietary filter: -ms-filter: progid:DXImageTransform.Microsoft.Gradient().Opera: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Opera Android: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Safari: Safari 4 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in repeating-linear-gradient(). This old outdated syntax is still supported for compatibility purposes.Safari: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.Safari on iOS: Safari on iOS 3.2 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in repeating-linear-gradient(). This old outdated syntax is still supported for compatibility purposes.Safari on iOS: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.WebView on iOS: WebView on iOS 3.2 was supporting an experimental -webkit-gradient(linear,…) function. It is more limited than the later standard version: you cannot specify both a position and an angle like in repeating-linear-gradient(). This old outdated syntax is still supported for compatibility purposes.WebView on iOS: Considers <angle> to start to the right, instead of the top. I.e. it considered an angle of 0deg as a direction indicator pointing to the right.
css.types.gradient.repeating-linear-gradient.doubleposition Chrome12/4/2018 Edge1/15/2020407
css.types.gradient.repeating-linear-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-linear-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-linear-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.repeating-linear-gradient.single_color_stop 📋Firefox3/4/2025 Edge4/4/202531
css.types.gradient.repeating-linear-gradient.to Firefox1/31/2012 Edge7/29/20151275
css.types.gradient.repeating-linear-gradient.unitless_0_angle Chrome3/26/2013 Firefox8/8/20171596
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 📋Firefox10/9/2012 Edge7/29/20151023
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 Firefox10/9/2012 Edge7/29/20151023
Firefox: Before Firefox 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox: Since Firefox 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.Firefox for Android: Before Firefox for Android 36, gradients weren't applied on the pre-multiplied color space, leading to shades of grey unexpectedly appearing when used with transparency.Firefox for Android: Since Firefox for Android 42, the prefixed version of gradients can be disabled by setting layout.css.prefixes.gradients to false.
css.types.gradient.repeating-radial-gradient.doubleposition Chrome12/4/2018 Edge1/15/2020407
css.types.gradient.repeating-radial-gradient.hue_interpolation_method Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-radial-gradient.interpolation_color_space Safari12/13/2022 Firefox6/11/2024546
css.types.gradient.repeating-radial-gradient.interpolation_hints Safari10/22/2013 Edge1/15/20202276
css.types.gradient.repeating-radial-gradient.single_color_stop 📋Firefox3/4/2025 Edge4/4/202531
css.types.hypot 📋Safari3/14/2022 Edge12/7/2023633
css.types.image 📋Safari6/23/2003 Edge7/29/20154419
css.types.image.image-set 📋Firefox6/1/2021 Safari9/18/2023839
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 Firefox9/20/2016 Safari3/24/20201281
css.types.length.cap Firefox2/8/2022 Safari12/11/2023671
css.types.length.ch Firefox11/9/2004 Edge7/29/20153914
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 Firefox2/14/2023166
css.types.length.em Safari6/23/2003 Edge7/29/20154419
css.types.length.ex Safari6/23/2003 Edge7/29/20154419
css.types.length.ic Firefox2/8/2022 Edge10/3/2022237
css.types.length.lh 📋Chrome1/10/2023 Firefox11/21/2023315
css.types.length.rcap 📋Chrome10/10/2023 Firefox1/13/2026826
css.types.length.rch 📋Chrome3/7/2023 Firefox1/13/20261043
css.types.length.rem Firefox1/21/2010 Edge7/29/20152015
css.types.length.rex 📋Chrome3/7/2023 Firefox1/13/20261043
css.types.length.ric 📋Chrome3/7/2023 Firefox1/13/20261043
css.types.length.rlh 📋Chrome3/7/2023 Firefox11/21/2023259
css.types.length.vb Safari3/14/2022 Edge12/5/2022266
css.types.length.vh Chrome6/26/2012 Edge7/29/20151128
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length.vi 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 Firefox2/19/2013 Edge10/17/20171701
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 Firefox2/19/2013 Edge7/29/2015890
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length.vw Chrome6/26/2012 Edge7/29/20151128
Firefox: Starting with version 21, viewport-percentage lengths are invalid in @page.Firefox for Android: Starting with version 21, viewport-percentage lengths are invalid in @page.
css.types.length-percentage 📋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 Firefox4/7/2020726
css.types.min 📋Safari4/12/2018 Firefox4/7/2020726
css.types.mod 📋Safari3/14/2022 Edge5/17/2024795
css.types.mod.mixed_type_parameters 📋Firefox9/26/2023 Edge5/17/2024234
css.types.number 📋Safari6/23/2003 Edge7/29/20154419
css.types.number.scientific_notation Firefox4/29/2014 Safari3/27/20171063
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 Firefox9/22/2020 Safari9/12/2022720
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 Firefox6/5/2012 Edge7/29/20151149
css.types.position.keyword_value_syntax Safari6/23/2003 Edge7/29/20154419
css.types.pow 📋Safari3/14/2022 Edge12/7/2023633
css.types.ratio 📋Firefox6/30/2009 Edge7/29/20152220
css.types.ray 📋Safari9/12/2022 Firefox1/23/2024498
css.types.ray.position Chrome8/15/2023 Firefox1/23/2024161
css.types.ray.size Chrome8/15/2023 Firefox1/23/2024161
css.types.rem 📋Safari3/14/2022 Edge5/17/2024795
css.types.rem.mixed_type_parameters 📋Firefox9/26/2023 Edge5/17/2024234
css.types.resolution 📋Firefox11/8/2011 Safari9/12/20223961
Firefox: Supports <integer> values only.Firefox for Android: Supports <integer> values only.
css.types.resolution.dpcm Firefox11/8/2011 Safari9/12/20223961
css.types.resolution.dpi Firefox11/8/2011 Safari9/12/20223961
css.types.resolution.dppx Firefox10/9/2012 Safari9/12/20223625
css.types.resolution.x Chrome7/24/2018 Safari9/12/20221511
css.types.round 📋Safari3/14/2022 Edge5/17/2024795
css.types.round.mixed_type_parameters 📋Firefox9/26/2023 Edge5/17/2024234
css.types.shape 📋Firefox11/9/2004 Edge7/29/20153914
css.types.shape.rect Firefox11/9/2004 Edge7/29/20153914
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.sign 📋Safari3/14/2022 Edge6/26/20251200
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.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 📋Firefox10/5/2021 Safari3/14/2022160
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 📋Firefox7/22/2014 Edge4/5/2017988

HTML Data

API First Browser Date Last Browser Date Days Notes
html.elements.a 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Starting with Firefox 41, <a> without href attribute is no longer classified as interactive content: clicking it inside <label> will activate labelled content (bug 1167816).Firefox for Android: Starting with Firefox for Android 41, <a> without href attribute is no longer classified as interactive content: clicking it inside <label> will activate labelled content (bug 1167816).
html.elements.a.charset 📋Safari6/23/2003 Edge7/29/20154419
html.elements.a.download 📋Chrome9/16/2011 Edge10/2/20182573
Chrome: Starting in Chrome 65, cross-origin downloads are not supported on the <a> element.Chrome Android: Starting in Chrome Android 65, cross-origin downloads are not supported on the <a> element.Edge: Starting in Edge 79, cross-origin downloads are not supported on the <a> element.Edge: Until Edge 14 (build 14357), attempting to download data URIs caused Edge to crash (bug 7160092).Edge: Edge 17 or older didn't follow the attributes' value to determine filename (bug 7260192).Firefox for Android: The attribute's filename value only affects the suggested file name for the blob: and data: URI schemes. Other schemes ignore the suggested filename. See bug 1845642.Quest Browser: Starting in Quest Browser 5.0, cross-origin downloads are not supported on the <a> element.Opera: Starting in Opera 52, cross-origin downloads are not supported on the <a> element.Opera Android: Starting in Opera Android 47, cross-origin downloads are not supported on the <a> element.Samsung Internet: Starting in Samsung Internet 9.0, cross-origin downloads are not supported on the <a> element.WebView Android: Starting in WebView Android 65, cross-origin downloads are not supported on the <a> element.
html.elements.a.href 📋Safari6/23/2003 Edge7/29/20154419
html.elements.a.href.href_top Chrome12/11/2008 Edge7/29/20152421
html.elements.a.hreflang 📋Safari6/23/2003 Edge7/29/20154419
html.elements.a.implicit_noopener Safari3/25/2019 Edge1/21/2021668
html.elements.a.name 📋Safari6/23/2003 Edge7/29/20154419
html.elements.a.ping 📋Firefox11/9/2004 Edge4/30/20184920
Firefox: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.Firefox for Android: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.
html.elements.a.referrerpolicy 📋Chrome5/25/2016 Safari9/16/20201575
html.elements.a.rel 📋Safari6/23/2003 Edge7/29/20154419
html.elements.a.rel.noopener 📋Chrome3/2/2016 Edge1/15/20201414
Firefox: Before Firefox 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox 63, these windows have the same features enabled by default as any other window.Firefox for Android: Before Firefox for Android 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox for Android 63, these windows have the same features enabled by default as any other window.
html.elements.a.rel.noreferrer 📋Safari6/7/2010 Edge11/12/20151984
Internet Explorer: Only supported in IE11 in later versions of Windows 10 (creators update). (Per caniuse.com.)
html.elements.a.rev 📋Safari6/23/2003 Edge7/29/20154419
html.elements.a.target 📋Safari6/23/2003 Edge7/29/20154419
html.elements.a.text_fragments Chrome2/4/2020 Firefox10/1/20241701
html.elements.a.type 📋Safari6/23/2003 Edge7/29/20154419
html.elements.abbr 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.acronym 📋Safari6/23/2003 Edge7/29/20154419
html.elements.address 📋Safari6/23/2003 Edge7/29/20154419
html.elements.area 📋Safari6/23/2003 Edge7/29/20154419
html.elements.area.alt 📋Safari6/23/2003 Edge7/29/20154419
html.elements.area.coords 📋Safari6/23/2003 Edge7/29/20154419
html.elements.area.download 📋Firefox4/2/2013 Safari3/27/20171455
html.elements.area.href 📋Safari6/23/2003 Edge7/29/20154419
html.elements.area.implicit_noopener Safari3/25/2019 Edge1/21/2021668
html.elements.area.nohref 📋Safari6/23/2003 Edge7/29/20154419
html.elements.area.ping 📋Firefox11/9/2004 Edge4/30/20184920
Firefox: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.Firefox for Android: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.
html.elements.area.referrerpolicy 📋Chrome5/25/2016 Safari9/16/20201575
html.elements.area.rel 📋Safari6/7/2010 Edge7/29/20151878
html.elements.area.rel.noopener 📋Chrome3/2/2016 Edge1/15/20201414
Firefox: Before Firefox 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox 63, these windows have the same features enabled by default as any other window.Firefox for Android: Before Firefox for Android 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox for Android 63, these windows have the same features enabled by default as any other window.
html.elements.area.rel.noreferrer 📋Safari6/7/2010 Edge11/12/20151984
Internet Explorer: Only supported in IE11 in later versions of Windows 10 (creators update). (Per caniuse.com.)
html.elements.area.shape 📋Safari6/23/2003 Edge7/29/20154419
html.elements.area.target 📋Safari6/23/2003 Edge7/29/20154419
html.elements.article 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.aside 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.audio 📋Safari3/18/2008 Edge7/29/20152689
Firefox: For Firefox to play audio, the server must serve the file using the correct MIME type.Firefox for Android: For Firefox for Android to play audio, the server must serve the file using the correct MIME type.
html.elements.audio.controls 📋Safari3/18/2008 Edge7/29/20152689
html.elements.audio.crossorigin 📋Chrome2/20/2014 Firefox3/10/20202210
Firefox: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.Firefox for Android: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.
html.elements.audio.loop 📋Safari3/18/2008 Edge7/29/20152689
html.elements.audio.muted 📋Chrome10/25/2011 Edge10/2/20182534
html.elements.audio.preload 📋Safari3/18/2008 Edge7/29/20152689
Chrome: Defaults to metadata in Chrome 64.Chrome Android: Defaults to metadata in Chrome Android 64.Quest Browser: Defaults to metadata in Quest Browser 5.0.Opera: Defaults to metadata in Opera 51.Opera Android: Defaults to metadata in Opera 51.Samsung Internet: Defaults to metadata in Samsung Internet 9.0.WebView Android: Defaults to metadata in Chrome 64.
html.elements.audio.src 📋Safari3/18/2008 Edge7/29/20152689
html.elements.b 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.base 📋Firefox11/9/2004 Edge7/29/20153914
Internet Explorer: Before Internet Explorer 7, <base> can be positioned anywhere in the document and the nearest value of <base> is used.
html.elements.base.href 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.base.href.forbid_data_javascript_urls Chrome4/19/2017 Firefox6/11/20242610
html.elements.base.href.relative_url Safari10/26/2007 Edge7/29/20152833
html.elements.base.target 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.bdi 📋Chrome12/13/2011 Edge1/15/20202955
html.elements.bdo 📋Safari6/8/2009 Edge7/29/20152242
html.elements.big 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.blockquote 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.blockquote.cite Firefox11/9/2004 Edge7/29/20153914
html.elements.body 📋Safari6/23/2003 Edge7/29/20154419
html.elements.body.alink Firefox11/9/2004 Edge7/29/20153914
html.elements.body.background Firefox11/9/2004 Edge7/29/20153914
html.elements.body.bgcolor Firefox11/9/2004 Edge7/29/20153914
html.elements.body.bottommargin Chrome12/11/2008 Edge1/15/20204052
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.leftmargin Chrome12/11/2008 Edge1/15/20204052
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.link Firefox11/9/2004 Edge7/29/20153914
html.elements.body.rightmargin Chrome12/11/2008 Edge1/15/20204052
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.text Firefox11/9/2004 Edge7/29/20153914
html.elements.body.topmargin Chrome12/11/2008 Edge1/15/20204052
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.vlink Firefox11/9/2004 Edge7/29/20153914
html.elements.br 📋Safari6/23/2003 Edge7/29/20154419
html.elements.br.clear Firefox11/9/2004 Edge7/29/20153914
html.elements.button 📋Safari6/23/2003 Edge7/29/20154419
html.elements.button.command 📋Chrome4/1/2025 Safari12/12/2025255
html.elements.button.command.request-close 📋Chrome8/5/2025 Safari12/12/2025129
html.elements.button.commandfor 📋Chrome4/1/2025 Safari12/12/2025255
html.elements.button.commandfor.implicit_anchor_reference 📋Chrome4/1/2025 Firefox1/13/2026287
html.elements.button.disabled 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.button.form Chrome2/3/2011 Edge10/17/20172448
html.elements.button.formaction Chrome2/3/2011 Edge7/29/20151637
html.elements.button.formenctype Chrome2/3/2011 Edge7/29/20151637
html.elements.button.formmethod Chrome2/3/2011 Edge7/29/20151637
html.elements.button.formnovalidate Chrome2/3/2011 Edge7/29/20151637
html.elements.button.formtarget Chrome2/3/2011 Edge7/29/20151637
html.elements.button.name Firefox11/9/2004 Edge7/29/20153914
html.elements.button.popovertarget 📋Chrome5/30/2023 Firefox4/16/2024322
html.elements.button.popovertarget.implicit_anchor_reference 📋Chrome2/4/2025 Firefox1/13/2026343
html.elements.button.popovertargetaction 📋Chrome5/30/2023 Firefox4/16/2024322
html.elements.button.type Firefox11/9/2004 Edge7/29/20153914
html.elements.button.value Firefox11/9/2004 Edge7/29/20153914
html.elements.canvas 📋Safari4/29/2005 Edge7/29/20153743
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.canvas.height 📋Safari4/29/2005 Edge7/29/20153743
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.canvas.width 📋Safari4/29/2005 Edge7/29/20153743
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.caption 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.caption.align Firefox11/9/2004 Edge7/29/20153914
html.elements.center 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.cite 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.code 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.col 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.col.align 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.col.span 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.col.valign 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.col.width 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup.align 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup.span 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup.valign 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.colgroup.width 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.data 📋Firefox6/25/2013 Chrome10/17/20171575
html.elements.data.value 📋Firefox6/25/2013 Chrome10/17/20171575
html.elements.datalist 📋Firefox3/22/2011 Safari3/25/20192925
Firefox for Android: The dropdown menu containing available options does not appear. See bug 1535985.
html.elements.datalist.input_type_email 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_number 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_range 📋Chrome6/26/2012 Firefox2/14/20233885
html.elements.datalist.input_type_search 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_tel 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_text 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.datalist.input_type_url 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.dd 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element was implemented using the HTMLSpanElement interface instead of HTMLElement.
html.elements.del 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.del.cite Firefox11/9/2004 Edge7/29/20153914
html.elements.del.datetime Firefox11/9/2004 Edge7/29/20153914
html.elements.details 📋Chrome6/7/2011 Edge1/15/20203144
Firefox: Before Firefox 57, there was a bug meaning that <details> elements can't be made open by default using the open attribute if they have a CSS animation active on them.Firefox for Android: There is a bug meaning that <details> elements can't be made open by default using the open attribute if they have a CSS animation active on them.
html.elements.details.name Chrome12/5/2023 Firefox9/3/2024273
html.elements.details.open Chrome6/7/2011 Edge1/15/20203144
html.elements.details.search_match_opens Chrome1/4/2022 Firefox2/24/20261512
Firefox: The browser does not correctly scroll to the matching text. See bug 2006040.Firefox for Android: The browser does not correctly scroll to the matching text. See bug 2006040.Safari: The browser does not correctly scroll to the matching text. See bug 304174.Safari on iOS: The browser does not correctly scroll to the matching text. See bug 304174.WebView on iOS: The browser does not correctly scroll to the matching text. See bug 304174.
html.elements.dfn 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.dialog 📋Chrome8/26/2014 Safari3/14/20222757
html.elements.dialog.open Chrome8/26/2014 Safari3/14/20222757
html.elements.dir 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.dir.compact Firefox11/9/2004 Edge7/29/20153914
html.elements.div 📋Safari6/23/2003 Edge7/29/20154419
html.elements.div.align Firefox11/9/2004 Edge7/29/20153914
html.elements.dl 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.dt 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.em 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.embed 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.embed.align 📋Firefox11/9/2004 Edge1/15/20205545
html.elements.embed.height 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.embed.name 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.embed.src 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.embed.type 📋Firefox11/9/2004 Edge1/15/20205545
html.elements.embed.width 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.fieldset 📋Firefox11/9/2004 Edge7/29/20153914
Chrome: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.Chrome Android: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.Edge: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 4511145.Quest Browser: Before version 12.0, this element did not support flexbox and grid layouts within this element. See bug 41027853.Samsung Internet: Before version 14.0, this element did not support flexbox and grid layouts within this element. See bug 41027853.WebView Android: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.
html.elements.fieldset.disabled 📋Firefox3/22/2011 Edge1/15/20203221
Edge: Does not work with nested fieldsets. For example: <fieldset disabled><fieldset><!--Still enabled--></fieldset></fieldset>Internet Explorer: Not all form control descendants of a disabled fieldset are properly disabled in IE11; see IE bug 817488: input[type='file'] not disabled inside disabled fieldset and IE bug 962368: Can still edit input[type='text'] within fieldset[disabled].
html.elements.fieldset.form 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.fieldset.name 📋Firefox3/22/2011 Edge7/29/20151590
html.elements.figcaption 📋Chrome12/2/2010 Edge7/29/20151700
html.elements.figure 📋Chrome12/2/2010 Edge7/29/20151700
html.elements.font 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.font.color Firefox11/9/2004 Edge7/29/20153914
html.elements.font.face Firefox11/9/2004 Edge7/29/20153914
html.elements.font.size Firefox11/9/2004 Edge7/29/20153914
html.elements.footer 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.form 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.form.accept-charset 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.form.action 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.form.autocomplete 📋Firefox3/22/2011 Edge7/29/20151590
Chrome: The Google Chrome UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Chrome might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Chrome Android: The Chrome Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Chrome Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Quest Browser: The Quest Browser UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Quest Browser might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Opera: The Opera UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Opera might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Opera Android: The Opera Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Opera Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Samsung Internet: The Samsung Internet UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Samsung Internet might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.WebView Android: The WebView Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, WebView Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.
html.elements.form.autocomplete.one-time-code Safari9/17/2018 Firefox1/17/20231583
html.elements.form.autocomplete.webauthn 📋Chrome11/29/2022 Firefox1/23/2024420
html.elements.form.enctype 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.form.method 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.form.name 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.form.novalidate 📋Chrome3/8/2011 Safari3/27/20172211
html.elements.form.rel 📋Safari3/14/2022 Firefox3/14/2023365
html.elements.form.target 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.frame 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.frameborder Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.marginheight Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.marginwidth Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.name Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.noresize Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.scrolling Firefox11/9/2004 Edge7/29/20153914
html.elements.frame.src Firefox11/9/2004 Edge7/29/20153914
html.elements.frameset 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.frameset.cols Firefox11/9/2004 Edge7/29/20153914
html.elements.frameset.rows Firefox11/9/2004 Edge7/29/20153914
html.elements.h1 📋Safari6/23/2003 Edge7/29/20154419
html.elements.h2 📋Safari6/23/2003 Edge7/29/20154419
html.elements.h3 📋Safari6/23/2003 Edge7/29/20154419
html.elements.h4 📋Safari6/23/2003 Edge7/29/20154419
html.elements.h5 📋Safari6/23/2003 Edge7/29/20154419
html.elements.h6 📋Safari6/23/2003 Edge7/29/20154419
html.elements.head 📋Safari6/23/2003 Edge7/29/20154419
html.elements.header 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.hgroup 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.hr 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.hr.align Firefox11/9/2004 Edge7/29/20153914
html.elements.hr.color Firefox11/9/2004 Safari3/27/20174521
html.elements.hr.hr_in_select Safari9/18/2023 Firefox1/23/2024127
Chrome: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Chrome: Does not expose the <hr> in the accessibility tree.Edge: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Edge: Does not expose the <hr> in the accessibility tree.Firefox: Does not expose the <hr> in the accessibility tree.Opera: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Opera: Does not expose the <hr> in the accessibility tree.Safari: Does not expose the <hr> in the accessibility tree.Safari on iOS: Does not expose the <hr> in the accessibility tree.WebView on iOS: Does not expose the <hr> in the accessibility tree.
html.elements.hr.noshade Firefox11/9/2004 Edge7/29/20153914
html.elements.hr.size Firefox11/9/2004 Edge7/29/20153914
html.elements.hr.width Firefox11/9/2004 Edge7/29/20153914
html.elements.html 📋Safari6/23/2003 Edge7/29/20154419
html.elements.html.version 📋Safari6/23/2003 Edge7/29/20154419
html.elements.html.xmlns Safari6/23/2003 Edge7/29/20154419
html.elements.i 📋Safari6/23/2003 Edge7/29/20154419
html.elements.iframe 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: The resize CSS property doesn't have any effect on this element due to bug 680823.Firefox for Android: The resize CSS property doesn't have any effect on this element due to bug 680823.Safari: Safari has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.Safari on iOS: Safari on iOS has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.WebView on iOS: WebView on iOS has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.
html.elements.iframe.align 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.allow 📋Chrome7/25/2017 Firefox3/10/2020959
html.elements.iframe.allow.camera 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.display-capture 📋Safari9/19/2019 Edge9/24/2021736
html.elements.iframe.allow.microphone 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.screen-wake-lock 📋Edge7/16/2020 Firefox5/14/20241398
html.elements.iframe.allowfullscreen 📋Firefox1/8/2013 Safari3/27/20171539
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.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.
html.elements.iframe.cross-origin-top-navigation-by-user-activation Chrome7/24/2018 Firefox10/14/20252639
Chrome: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Chrome Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Edge: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Firefox: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Firefox for Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Quest Browser: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Opera: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Opera Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Safari: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.Safari on iOS: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.Samsung Internet: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.WebView Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.WebView on iOS: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.
html.elements.iframe.frameborder 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.height 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.loading 📋Chrome9/10/2019 Firefox12/19/20231561
html.elements.iframe.longdesc 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.marginheight 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.marginwidth 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.name 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.referrerpolicy 📋Chrome5/25/2016 Safari9/16/20201575
html.elements.iframe.sandbox 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.iframe.sandbox.allow-downloads 📋Chrome5/19/2020 Safari9/18/20231217
html.elements.iframe.sandbox.allow-forms 📋Chrome5/25/2010 Edge1/15/20203522
html.elements.iframe.sandbox.allow-modals 📋Chrome10/13/2015 Edge1/15/20201555
html.elements.iframe.sandbox.allow-pointer-lock 📋Chrome11/6/2012 Edge1/15/20202626
html.elements.iframe.sandbox.allow-popups 📋Chrome2/8/2012 Edge7/29/20151267
html.elements.iframe.sandbox.allow-popups-to-escape-sandbox 📋Chrome10/13/2015 Edge1/15/20201555
html.elements.iframe.sandbox.allow-same-origin 📋Chrome5/25/2010 Edge1/15/20203522
Chrome: Chrome 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Chrome Android: Chrome Android 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Edge: Edge 79 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Quest Browser: Quest Browser 6.0 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Opera: Opera 57 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Opera Android: Opera Android 49 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Safari: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Safari on iOS: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Samsung Internet: Samsung Internet 10.0 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.WebView Android: WebView Android 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.WebView on iOS: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.
html.elements.iframe.sandbox.allow-scripts 📋Chrome5/25/2010 Edge1/15/20203522
html.elements.iframe.sandbox.allow-storage-access-by-user-activation Safari4/12/2018 Edge5/5/20231849
html.elements.iframe.sandbox.allow-top-navigation 📋Safari6/7/2010 Edge1/15/20203509
html.elements.iframe.sandbox.allow-top-navigation-by-user-activation 📋Chrome4/19/2017 Firefox7/28/20201196
html.elements.iframe.scrolling 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.src 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.iframe.srcdoc 📋Chrome6/26/2012 Edge1/15/20202759
html.elements.iframe.width 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img 📋Safari6/23/2003 Edge7/29/20154419
html.elements.img.align 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.alt 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.aspect_ratio_computed_from_attributes Chrome12/10/2019 Safari9/20/2021650
Safari: Safari doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).Safari on iOS: Safari on iOS doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).WebView on iOS: WebView on iOS doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).
html.elements.img.border 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.crossorigin 📋Chrome8/2/2011 Edge7/29/20151457
html.elements.img.decoding 📋Chrome3/6/2018 Edge1/15/2020680
html.elements.img.fetchpriority 📋Chrome4/26/2022 Firefox10/29/2024917
html.elements.img.height 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.hspace 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.ismap 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.loading 📋Chrome9/10/2019 Safari3/14/2022916
html.elements.img.longdesc 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.name 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.referrerpolicy 📋Chrome5/25/2016 Safari9/16/20201575
html.elements.img.sizes 📋Chrome10/7/2014 Safari3/21/2016531
html.elements.img.src 📋Safari6/23/2003 Edge7/29/20154419
html.elements.img.srcset 📋Chrome4/8/2014 Edge7/29/2015477
html.elements.img.usemap 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.usemap.case_sensitive Firefox1/24/2017 Edge1/15/20201086
html.elements.img.vspace 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.img.width 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.input 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 89, manipulating the content of <input> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Firefox for Android: Before Firefox for Android 89, manipulating the content of <input> elements using Document.execCommand() commands requires workarounds (see bug 1220696).
html.elements.input.accept 📋Safari6/23/2003 Edge7/29/20154419
Safari on iOS: Does not support audio/* MIME type. See bug 242110.WebView on iOS: Does not support audio/* MIME type. See bug 242110.
html.elements.input.align 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.alt 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.autocomplete 📋Firefox3/22/2011 Edge7/29/20151590
html.elements.input.checked 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.dirname 📋Chrome2/8/2012 Firefox8/1/20234192
html.elements.input.disabled 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.form 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.formaction 📋Safari6/7/2010 Edge7/29/20151878
html.elements.input.formenctype 📋Safari6/7/2010 Edge7/29/20151878
html.elements.input.formmethod 📋Safari6/7/2010 Edge7/29/20151878
html.elements.input.formnovalidate 📋Chrome1/25/2010 Edge7/29/20152011
html.elements.input.formtarget 📋Safari6/7/2010 Edge7/29/20151878
html.elements.input.max 📋Chrome1/25/2010 Edge7/29/20152011
html.elements.input.maxlength 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.min 📋Chrome1/25/2010 Edge7/29/20152011
html.elements.input.minlength 📋Chrome1/21/2015 Edge4/30/20181195
html.elements.input.multiple 📋Chrome5/21/2009 Edge7/29/20152260
html.elements.input.name 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.pattern 📋Chrome1/25/2010 Edge7/29/20152011
html.elements.input.placeholder 📋Safari6/8/2009 Edge7/29/20152242
html.elements.input.popovertarget 📋Chrome5/30/2023 Firefox4/16/2024322
html.elements.input.popovertarget.implicit_anchor_reference 📋Chrome2/4/2025 Firefox1/13/2026343
html.elements.input.popovertargetaction 📋Chrome5/30/2023 Firefox4/16/2024322
html.elements.input.readonly 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.required 📋Chrome1/25/2010 Edge7/29/20152011
html.elements.input.size 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.src 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.step 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.input.type_button 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_checkbox 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_color 📋Chrome6/26/2012 Safari3/25/20192463
Firefox for Android: Firefox for Android doesn't allow the user to choose a custom color, only one of the predefined ones.
html.elements.input.type_date 📋Chrome6/26/2012 Safari4/26/20213226
html.elements.input.type_date.disables_invalid_values_in_picker_ui Chrome6/26/2012 Safari4/26/20213226
html.elements.input.type_datetime-local 📋Chrome6/26/2012 Firefox10/5/20213388
Firefox: Only displays a date picker without a time picker, see bug 1726107 and bug 1726108.Firefox for Android: Only displays a date picker without a time picker, see bug 1726107 and bug 1726108.Safari: Safari only displays a date picker and does not display a time picker.
html.elements.input.type_email 📋Firefox11/9/2004 Edge7/29/20153914
Safari on iOS: Doesn't do validation, but instead offers a custom 'email' keyboard, which is designed to make entering email addresses easier.Safari on iOS: The custom 'email' keyboard does not provide a comma key, so users cannot enter multiple email addresses.Safari on iOS: Automatically applies a default style of opacity: 0.4 to disable textual <input> elements, including those of type 'email'. Other major browsers don't currently share this particular default style.WebView on iOS: Doesn't do validation, but instead offers a custom 'email' keyboard, which is designed to make entering email addresses easier.WebView on iOS: The custom 'email' keyboard does not provide a comma key, so users cannot enter multiple email addresses.WebView on iOS: Automatically applies a default style of opacity: 0.4 to disable textual <input> elements, including those of type 'email'. Other major browsers don't currently share this particular default style.
html.elements.input.type_email.list 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_file 📋Safari6/23/2003 Edge7/29/20154419
Firefox: You can set as well as get the value of HTMLInputElement.files in all modern browsers; this was most recently added to Firefox, in version 57 (see bug 1384030).
html.elements.input.type_hidden 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_image 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_number 📋Chrome10/19/2010 Edge7/29/20151744
Chrome: Prevents users from typing non-numeric content.Chrome Android: Prevents users from typing non-numeric content.Firefox: Allows users to type non-numeric content, with the value reflecting an empty string.Firefox for Android: Allows users to type non-numeric content, with the value reflecting an empty string.Quest Browser: Prevents users from typing non-numeric content.Opera: Prevents users from typing non-numeric content.Opera Android: Prevents users from typing non-numeric content.Safari: Allows users to type non-numeric content, with the value reflecting an empty string.Safari on iOS: Allows users to type non-numeric content, with the value reflecting an empty string.Samsung Internet: Prevents users from typing non-numeric content.WebView Android: Prevents users from typing non-numeric content.WebView on iOS: Allows users to type non-numeric content, with the value reflecting an empty string.
html.elements.input.type_number.list 📋Chrome9/25/2012 Safari3/25/20192372
html.elements.input.type_password 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_radio 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_range 📋Safari3/18/2008 Edge7/29/20152689
WebView Android: Pre-Chromium Android WebView recognizes the range type, but doesn't implement a range-specific control.
html.elements.input.type_range.list 📋Chrome6/26/2012 Firefox2/14/20233885
html.elements.input.type_range.tick_marks Chrome5/29/2018 Firefox1/17/20231694
html.elements.input.type_range.vertical_orientation Edge7/29/2015 Chrome4/16/20243184
Chrome: Vertical orientation available via the writing-mode property (see Creating vertical controls).Chrome: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Chrome Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Chrome Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Edge: Vertical orientation available by setting the writing-mode: bt-lr style on the input element.Firefox: Vertical orientation available via the writing-mode property (see Creating vertical controls).Firefox: Supported using the non-standard orient="vertical" attribute.Firefox for Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Firefox for Android: Supported using the non-standard orient="vertical" attribute.Internet Explorer: Vertical orientation available by setting the writing-mode: bt-lr style on the input element.Quest Browser: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Opera: Vertical orientation available via the writing-mode property (see Creating vertical controls).Opera: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Opera Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Opera Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Safari: Vertical orientation available via the writing-mode property (see Creating vertical controls).Safari: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Safari on iOS: Vertical orientation available via the writing-mode property (see Creating vertical controls).Safari on iOS: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Samsung Internet: Vertical orientation available via the writing-mode property (see Creating vertical controls).Samsung Internet: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.WebView Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).WebView Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.WebView on iOS: Vertical orientation available via the writing-mode property (see Creating vertical controls).WebView on iOS: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.
html.elements.input.type_reset 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Unlike other browsers, Firefox by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.Firefox for Android: Unlike other browsers, Firefox for Android by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.
html.elements.input.type_search 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.input.type_search.list 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_submit 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Unlike other browsers, Firefox by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.Firefox for Android: Unlike other browsers, Firefox for Android by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.
html.elements.input.type_tel 📋Safari6/8/2009 Edge7/29/20152242
Chrome: The field type doesn't demonstrate any special behavior.Safari: The field type doesn't demonstrate any special behavior.
html.elements.input.type_tel.list 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_text 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_text.list 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.input.type_time 📋Chrome6/26/2012 Safari4/26/20213226
html.elements.input.type_url 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.type_url.list 📋Firefox3/22/2011 Safari3/25/20192925
html.elements.input.usemap 📋Safari6/23/2003 Edge7/29/20154419
html.elements.input.webkitdirectory Chrome10/19/2010 Safari4/12/20182732
Chrome Android: In Chrome for Android 131, choosing a directory crashes the browser (see bug 376834374).Chrome Android: Before version 131, users cannot choose a directory, only individual files (see bug 40248532.Safari on iOS: Before version 18.4, the attribute can be set but users cannot choose a directory, only individual files (see bug 271705).WebView Android: In Chrome for Android 131, choosing a directory crashes the browser (see bug 376834374).WebView Android: Before version 131, users cannot choose a directory, only individual files (see bug 40248532.WebView on iOS: Before version 18.4, the attribute can be set but users cannot choose a directory, only individual files (see bug 271705).
html.elements.ins 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.ins.cite Firefox11/9/2004 Edge7/29/20153914
html.elements.ins.datetime Firefox11/9/2004 Edge7/29/20153914
html.elements.kbd 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, creating a <kbd> element incorrectly resulted in an HTMLSpanElement object, instead of the expected HTMLElement.
html.elements.label 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.label.for 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.legend 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.legend.align Firefox11/9/2004 Edge7/29/20153914
html.elements.li 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.li.type 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.li.value 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.link 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.link.as 📋Chrome4/13/2016 Edge4/30/2018747
html.elements.link.charset 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.link.crossorigin 📋Firefox1/8/2013 Edge4/30/20181938
Firefox: Before Firefox 83, crossorigin is not supported for rel="icon".Firefox for Android: Before Firefox for Android 83, crossorigin is not supported for rel="icon".
html.elements.link.disabled 📋Firefox11/9/2004 Edge7/29/20153914
Chrome: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Chrome Android: In Chrome Android and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Edge: Since Edge 79, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Quest Browser: In Quest Browser and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Opera: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Opera Android: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Samsung Internet: In Samsung Internet and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.WebView Android: In WebView Android and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.
html.elements.link.fetchpriority 📋Chrome4/26/2022 Firefox10/29/2024917
html.elements.link.href 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.link.hreflang 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.link.imagesizes 📋Chrome3/12/2019 Safari12/11/20231735
html.elements.link.imagesrcset 📋Chrome3/12/2019 Safari12/11/20231735
html.elements.link.integrity 📋Chrome9/1/2015 Edge4/30/2018972
html.elements.link.media 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.link.referrerpolicy 📋Chrome5/25/2016 Safari9/16/20201575
html.elements.link.rel 📋Safari6/23/2003 Edge7/29/20154419
html.elements.link.rel.dns-prefetch 📋Safari6/7/2010 Firefox6/11/20245118
Firefox: Only HTTP pages were supported.Firefox for Android: Only HTTP pages were supported.
html.elements.link.rel.icon Firefox10/24/2006 Edge7/29/20153200
Chrome: If both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.).Edge: In version 79 and later (Blink-based Edge), if both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.)Firefox: Before Firefox 83, the crossorigin attribute is not supported for rel="icon".Firefox: The media attribute is not supported for rel="icon", see bug 1603885.Opera: In version 15 and later (Blink-based Opera), if both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.)Safari: If both ICO and PNG are available, will ALWAYS use ICO file, regardless of sizes set. (Per caniuse.com.)Safari on iOS: Does not use favicons at all (but may have alternative for bookmarks, etc.). (Per caniuse.com.)WebView on iOS: Does not use favicons at all (but may have alternative for bookmarks, etc.). (Per caniuse.com.)
html.elements.link.rel.modulepreload 📋Chrome4/17/2018 Safari9/18/20231980
html.elements.link.rel.modulepreload.as-script 📋Chrome4/17/2018 Safari9/18/20231980
html.elements.link.rel.preconnect 📋Firefox7/2/2015 Edge1/15/20201658
Firefox: Before Firefox 41, it doesn't obey the crossorigin attribute.Firefox for Android: Before Firefox for Android 41, it doesn't obey the crossorigin attribute.
html.elements.link.rel.prefetch 📋Firefox10/24/2006 Safari3/24/20204900
Chrome: Requires secure contextChrome Android: Requires secure contextEdge: Requires secure contextFirefox: Requires secure contextFirefox for Android: Requires secure contextQuest Browser: Requires secure contextOpera: Requires secure contextOpera Android: Requires secure contextSamsung Internet: Requires secure contextWebView Android: Requires secure context
html.elements.link.rel.preload 📋Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-fetch Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-font Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-image Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-script Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-style Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rev 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.link.sizes 📋Chrome10/25/2011 Edge1/15/20203004
html.elements.link.target 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.link.type 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.main 📋Chrome3/26/2013 Edge7/29/2015855
html.elements.map 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 5, in Quirks Mode, empty maps were no longer skipped over in favor of non-empty ones when matching.Firefox: Before Firefox 17, the default styling of the <map> HTML element was display: block;. This is now display: inline; and matches the behavior of the other browsers. It was already the case in Quirks Mode.
html.elements.map.name Safari6/23/2003 Edge7/29/20154419
html.elements.mark 📋Chrome10/19/2010 Edge7/29/20151744
html.elements.marquee 📋Safari2/2/2004 Firefox1/29/20195475
Firefox: Implements the HTMLDivElement interface.Firefox for Android: Implements the HTMLDivElement interface.
html.elements.marquee.behavior Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.bgcolor Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.direction Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.height Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.hspace Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.loop Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.scrollamount Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.scrolldelay Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.truespeed Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.vspace Safari2/2/2004 Edge7/29/20154195
html.elements.marquee.width Safari2/2/2004 Edge7/29/20154195
html.elements.menu 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.meta 📋Safari6/23/2003 Edge7/29/20154419
html.elements.meta.charset 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.meta.content 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.meta.http-equiv 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.meta.http-equiv.content-language 📋Firefox11/9/2004 Chrome6/5/20174591
html.elements.meta.http-equiv.content-security-policy 📋Firefox11/9/2004 Chrome6/5/20174591
html.elements.meta.http-equiv.content-type 📋Firefox11/9/2004 Chrome6/5/20174591
html.elements.meta.http-equiv.refresh 📋Safari6/23/2003 Edge7/29/20154419
html.elements.meta.name 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.meta.name.color-scheme 📋Safari3/25/2019 Firefox1/11/20221023
html.elements.meta.name.referrer 📋Chrome2/8/2012 Edge1/15/20202898
Chrome: Until Chrome 46, content values weren't constrained to the values listed in the spec.Chrome Android: Until Chrome Android 46, content values weren't constrained to the values listed in the spec.Firefox: The referrer value wasn't taken into account when navigation was happening via the context menu or middle click until Firefox 39.Firefox for Android: The referrer value wasn't taken into account when navigation was happening via the context menu or middle click until Firefox for Android 39.Internet Explorer: Browsers initially supported an early draft of the specification which can only use a meta tag and is only compatible with the origin value from the new spec.Quest Browser: Until Quest Browser 5.0, content values weren't constrained to the values listed in the spec.Opera: Until Opera 33, content values weren't constrained to the values listed in the spec.Opera Android: Until Opera Android 33, content values weren't constrained to the values listed in the spec.Samsung Internet: Until Samsung Internet 5.0, content values weren't constrained to the values listed in the spec.WebView Android: Until WebView Android 46, content values weren't constrained to the values listed in the spec.
html.elements.meta.scheme 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.meter 📋Chrome9/2/2010 Edge11/12/20151897
html.elements.meter.high 📋Chrome9/2/2010 Edge11/12/20151897
html.elements.meter.low 📋Chrome9/2/2010 Edge11/12/20151897
html.elements.meter.max 📋Chrome9/2/2010 Edge11/12/20151897
html.elements.meter.min 📋Chrome9/2/2010 Edge11/12/20151897
html.elements.meter.optimum 📋Chrome9/2/2010 Edge11/12/20151897
html.elements.meter.value 📋Chrome9/2/2010 Edge11/12/20151897
html.elements.nav 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.nobr 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.noembed 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.noframes 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.noscript 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.archive 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.border 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.classid 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.codetype 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.data 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.declare 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.form 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.height 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.name 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.standby 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.type 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.usemap 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.object.width 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.ol 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.ol.compact Firefox11/9/2004 Edge7/29/20153914
html.elements.ol.reversed 📋Chrome3/28/2012 Edge1/15/20202849
html.elements.ol.start 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.ol.type 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.optgroup 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.optgroup.disabled 📋Firefox11/9/2004 Edge7/29/20153914
Safari: Before Safari 7, the attribute can be set, but has no effect.Safari on iOS: The attribute can be set, but has no effect.WebView on iOS: The attribute can be set, but has no effect.
html.elements.optgroup.label 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.option 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.option.disabled 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.option.label 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before 77, Firefox didn't display the value of the label attribute as option text if element's content was empty. See bug 40545.Firefox: Historically, Firefox has allowed keyboard and mouse events to bubble up from the <option> element to the parent <select> element, although this behavior is inconsistent across many browsers. For better Web compatibility (and for technical reasons), they will not bubble up when Firefox is in multi-process mode and the <select> element is displayed as a drop-down list. The behavior is unchanged if the <select> is presented inline and it has either the multiple attribute defined or a size attribute set to more than 1. Rather than watching <option> elements for events, you should watch for change events on <select>. See bug 1090602 for details.Firefox: When Mozilla introduced dedicated content threads to Firefox (through the Electrolysis, or e10s, project), support for styling <option> elements was removed temporarily. Starting in Firefox 54, you can apply foreground and background colors to <option> elements again, using the color and background-color CSS properties. See bug 910022 for more information. Note that this is still disabled in Linux due to lack of contrast (see bug 1338283 for progress on this).Firefox for Android: Before 77, Firefox didn't display the value of the label attribute as option text if element's content was empty. See bug 40545.
html.elements.option.selected 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.option.value 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.output 📋Chrome3/8/2011 Edge10/2/20182765
html.elements.output.for 📋Chrome3/8/2011 Edge10/2/20182765
html.elements.output.form 📋Chrome3/8/2011 Edge10/2/20182765
html.elements.output.name 📋Chrome3/8/2011 Edge10/2/20182765
html.elements.p 📋Safari6/23/2003 Edge7/29/20154419
html.elements.param 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.param.name Firefox11/9/2004 Edge7/29/20153914
html.elements.param.type Firefox11/9/2004 Edge7/29/20153914
html.elements.param.value Firefox11/9/2004 Edge7/29/20153914
html.elements.param.valuetype Firefox11/9/2004 Edge7/29/20153914
html.elements.picture 📋Chrome10/7/2014 Safari3/21/2016531
html.elements.plaintext 📋Chrome12/11/2008 Edge7/29/20152421
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.pre 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.pre.width Firefox11/9/2004 Edge7/29/20153914
Chrome: Specifying the width attribute has no layout effect.Chrome Android: Specifying the width attribute has no layout effect.Edge: Specifying the width attribute has no layout effect.Firefox: Since Firefox 29, specifying the width attribute has no layout effect.Firefox for Android: Since Firefox for Android 29, specifying the width attribute has no layout effect.Internet Explorer: Specifying the width attribute has no layout effect.Quest Browser: Specifying the width attribute has no layout effect.Opera: Specifying the width attribute has no layout effect.Opera Android: Specifying the width attribute has no layout effect.Safari: Specifying the width attribute has no layout effect.Safari on iOS: Specifying the width attribute has no layout effect.Samsung Internet: Specifying the width attribute has no layout effect.WebView Android: Specifying the width attribute has no layout effect.WebView on iOS: Specifying the width attribute has no layout effect.
html.elements.progress 📋Chrome9/2/2010 Edge7/29/20151791
Firefox: Before Firefox 14, the <progress> element was incorrectly classified as a form element, and therefore had a form attribute. This has been fixed.Firefox: Firefox provides the ::-moz-progress-bar pseudo-element, which lets you style the part of the interior of the progress bar representing the amount of work completed so far.Firefox for Android: Before Firefox for Android 14, the <progress> element was incorrectly classified as a form element, and therefore had a form attribute. This has been fixed.Firefox for Android: Firefox for Android provides the ::-moz-progress-bar pseudo-element, which lets you style the part of the interior of the progress bar representing the amount of work completed so far.Safari on iOS: Safari on iOS does not support indeterminate progress bars (they are rendered like 0%-completed progress bars).WebView on iOS: WebView on iOS does not support indeterminate progress bars (they are rendered like 0%-completed progress bars).
html.elements.progress.max 📋Chrome9/2/2010 Edge7/29/20151791
html.elements.progress.value 📋Chrome9/2/2010 Edge7/29/20151791
html.elements.q 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.q.cite 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.rb 📋Chrome5/25/2010 Edge1/15/20203522
Chrome: Blink has support for parsing the rb element, but not for rendering rb content as expected.Chrome Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.Edge: Blink has support for parsing the rb element, but not for rendering rb content as expected.Quest Browser: Blink has support for parsing the rb element, but not for rendering rb content as expected.Opera: Blink has support for parsing the rb element, but not for rendering rb content as expected.Opera Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.Safari: Safari has support for parsing the rb element, but not for rendering rb content as expected.Safari on iOS: Safari on iOS has support for parsing the rb element, but not for rendering rb content as expected.Samsung Internet: Blink has support for parsing the rb element, but not for rendering rb content as expected.WebView Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.WebView on iOS: WebView on iOS has support for parsing the rb element, but not for rendering rb content as expected.
html.elements.rp 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.rt 📋Chrome5/25/2010 Edge7/29/20151891
Chrome: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Chrome Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Quest Browser: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Opera: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Opera Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Safari: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.Safari on iOS: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.Samsung Internet: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.WebView Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.WebView on iOS: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.
html.elements.rtc 📋Firefox10/14/2014 Edge1/15/20201919
html.elements.ruby 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.s 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.samp 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.script 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Starting in Firefox 4, inserting <script> elements that have been created by calling document.createElement("script") no longer enforces execution in insertion order. This change lets Firefox properly abide by the specification. To make script-inserted external scripts execute in their insertion order, set .async=false on them.
html.elements.script.async 📋Chrome12/11/2008 Edge7/29/20152421
html.elements.script.crossorigin 📋Chrome5/15/2012 Edge8/2/20161540
Safari: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.Safari on iOS: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.WebView on iOS: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.
html.elements.script.defer 📋Safari10/26/2007 Edge7/29/20152833
Chrome: Chrome does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Chrome Android: Chrome Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Firefox: Since Firefox 3.6, the defer attribute is ignored on scripts that don't have the src attribute. However, in Firefox 3.5 even inline scripts are deferred if the defer attribute is set.Internet Explorer: Before version 10, Internet Explorer implemented defer by a proprietary specification. Since version 10 it conforms to the W3C specification.Quest Browser: Quest Browser does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Opera: Opera does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Opera Android: Opera Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Samsung Internet: Samsung Internet does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348WebView Android: WebView Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348
html.elements.script.fetchpriority 📋Chrome4/26/2022 Firefox10/29/2024917
html.elements.script.integrity 📋Chrome9/1/2015 Edge4/30/2018972
html.elements.script.nomodule 📋Chrome9/5/2017 Firefox5/9/2018246
html.elements.script.referrerpolicy 📋Chrome10/16/2018 Safari9/16/2020701
html.elements.script.src 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.script.type 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.script.type.importmap 📋Chrome3/2/2021 Safari3/27/2023755
html.elements.script.type.importmap.integrity 📋Chrome7/23/2024 Firefox4/29/2025280
html.elements.script.type.module Safari3/27/2017 Edge1/15/20201024
Chrome: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Chrome Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Edge: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Quest Browser: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Opera: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Opera Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Safari: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).Safari on iOS: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).Samsung Internet: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.WebView Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.WebView on iOS: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).
html.elements.search 📋Safari9/18/2023 Edge10/13/202325
html.elements.section 📋Chrome5/25/2010 Edge7/29/20151891
html.elements.select 📋Safari6/23/2003 Edge7/29/20154419
Chrome: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Chrome Android: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Firefox: Historically, Firefox has allowed keyboard and mouse events to bubble up from the <option> element to the parent <select> element, although this behavior is inconsistent across many browsers. For better Web compatibility (and for technical reasons), when Firefox is in multi-process mode the <select> element is displayed as a drop-down list. The behavior is unchanged if the <select> is presented inline and it has either the multiple attribute defined or a size attribute set to more than 1. Rather than watching <option> elements for events, you should watch for change events on <select>. See bug 1090602 for details.Firefox for Android: Firefox for Android, by default, sets a background-image gradient on all <select multiple> elements. This can be disabled using background-image: none.Quest Browser: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Safari: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Safari on iOS: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Samsung Internet: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.WebView Android: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.WebView on iOS: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.
html.elements.select.autocomplete 📋Safari3/21/2016 Edge1/15/20201395
html.elements.select.disabled 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.select.form 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.select.hr_in_select Safari9/18/2023 Firefox1/23/2024127
Chrome: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Chrome: Does not expose the <hr> in the accessibility tree.Edge: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Edge: Does not expose the <hr> in the accessibility tree.Firefox: Does not expose the <hr> in the accessibility tree.Opera: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Opera: Does not expose the <hr> in the accessibility tree.Safari: Does not expose the <hr> in the accessibility tree.Safari on iOS: Does not expose the <hr> in the accessibility tree.WebView on iOS: Does not expose the <hr> in the accessibility tree.
html.elements.select.multiple 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.select.name 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.select.required 📋Chrome3/8/2011 Edge7/29/20151604
html.elements.select.size 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.slot 📋Chrome8/31/2016 Edge1/15/20201232
html.elements.slot.name Chrome8/31/2016 Edge1/15/20201232
html.elements.small 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.source 📋Safari3/18/2008 Edge7/29/20152689
Firefox: Until Firefox 15, Firefox picked the first source element that has a type matching the MIME-type of a supported media format; see bug 449363 for details.Firefox for Android: Until Firefox for Android 15, Firefox for Android picked the first source element that has a type matching the MIME-type of a supported media format; see bug 449363 for details.
html.elements.source.height 📋Chrome4/13/2021 Firefox12/13/2022609
html.elements.source.media 📋Safari3/18/2008 Edge7/29/20152689
Firefox: media is supported in <source> within <picture>, <audio>, and <video>. In Firefox 53-119, media is supported only in <source> within <picture>.Firefox for Android: media is supported in <source> within <picture>, <audio>, and <video>. In Firefox for Android 53-119, media is supported only in <source> within <picture>.
html.elements.source.sizes 📋Chrome10/7/2014 Safari3/21/2016531
Chrome: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Chrome Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Samsung Internet: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).WebView Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).
html.elements.source.src 📋Safari3/18/2008 Edge7/29/20152689
html.elements.source.srcset 📋Chrome10/7/2014 Safari3/21/2016531
Chrome: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Chrome Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Samsung Internet: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).WebView Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).
html.elements.source.type 📋Safari3/18/2008 Edge7/29/20152689
html.elements.source.width 📋Chrome4/13/2021 Firefox12/13/2022609
html.elements.span 📋Safari6/23/2003 Edge7/29/20154419
html.elements.strike 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.strong 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, creating a <strong> element incorrectly resulted in an HTMLSpanElement object, instead of the expected HTMLElement.
html.elements.style 📋Safari6/23/2003 Edge7/29/20154419
html.elements.style.media 📋Safari6/23/2003 Edge7/29/20154419
html.elements.style.type 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before 75, Firefox accepted any CSS media (MIME) type, with optional parameters. Starting in 75, this has been restricted to the string 'text/css', per the spec.
html.elements.sub 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.summary 📋Chrome6/7/2011 Edge1/15/20203144
html.elements.sup 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.table 📋Safari6/23/2003 Edge7/29/20154419
html.elements.table.align Safari6/23/2003 Edge7/29/20154419
html.elements.table.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.table.border Safari6/23/2003 Edge7/29/20154419
html.elements.table.cellpadding Safari6/23/2003 Edge7/29/20154419
html.elements.table.cellspacing Safari6/23/2003 Edge7/29/20154419
html.elements.table.frame Safari6/23/2003 Edge7/29/20154419
html.elements.table.rules Safari6/23/2003 Edge7/29/20154419
html.elements.table.summary Safari6/23/2003 Edge7/29/20154419
html.elements.table.width Safari6/23/2003 Edge7/29/20154419
html.elements.tbody 📋Safari6/23/2003 Edge7/29/20154419
html.elements.tbody.align Firefox11/9/2004 Edge7/29/20153914
html.elements.tbody.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.tbody.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.td 📋Safari6/23/2003 Edge7/29/20154419
html.elements.td.abbr Safari6/23/2003 Edge7/29/20154419
html.elements.td.align Firefox11/9/2004 Edge7/29/20153914
html.elements.td.axis Safari6/23/2003 Edge7/29/20154419
html.elements.td.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.td.colspan Safari6/23/2003 Edge7/29/20154419
html.elements.td.headers Safari6/23/2003 Edge7/29/20154419
html.elements.td.rowspan Safari6/23/2003 Edge7/29/20154419
html.elements.td.scope Safari6/23/2003 Edge7/29/20154419
html.elements.td.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.td.width Safari6/23/2003 Edge7/29/20154419
html.elements.template 📋Chrome3/26/2013 Edge11/12/2015961
html.elements.template.shadowrootclonable 📋Chrome4/16/2024 Safari5/13/202427
html.elements.template.shadowrootdelegatesfocus 📋Safari3/27/2023 Edge3/22/2024361
html.elements.template.shadowrootmode 📋Chrome3/7/2023 Firefox2/20/2024350
html.elements.template.shadowrootreferencetarget Chrome2/4/2025 Firefox3/24/2026413
html.elements.textarea 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 6, when a <textarea> was focused, the insertion point was placed at the end of the text by default. Other major browsers place the insertion point at the beginning of the text.Firefox: A default background-image gradient is applied to all <textarea> elements, which can be disabled using background-image: none.Firefox: Before Firefox 89, manipulating the content of <textarea> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Firefox for Android: Before Firefox for Android 6, when a <textarea> was focused, the insertion point was placed at the end of the text by default. Other major browsers place the insertion point at the beginning of the text.Firefox for Android: A default background-image gradient is applied to all <textarea> elements, which can be disabled using background-image: none.Firefox for Android: Before Firefox for Android 89, manipulating the content of <textarea> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Safari on iOS: Unlike other major browsers, a default style of opacity: 0.4 is applied to disabled <textarea> elements.WebView on iOS: Unlike other major browsers, a default style of opacity: 0.4 is applied to disabled <textarea> elements.
html.elements.textarea.autocomplete 📋Safari3/21/2016 Edge1/15/20201395
html.elements.textarea.autocomplete.one-time-code Safari9/17/2018 Firefox1/17/20231583
html.elements.textarea.cols 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.dirname 📋Chrome2/8/2012 Firefox8/1/20234192
html.elements.textarea.disabled 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.form 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.maxlength 📋Chrome1/25/2010 Edge7/29/20152011
Safari: Before Safari 17, newline characters counted as two characters instead of one. See bug 249916.Safari on iOS: Before Safari on iOS 17, newline characters counted as two characters instead of one. See bug 249916.WebView on iOS: Before WebView on iOS 17, newline characters counted as two characters instead of one. See bug 249916.
html.elements.textarea.minlength 📋Chrome1/21/2015 Edge4/30/20181195
html.elements.textarea.name 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.placeholder 📋Chrome1/25/2010 Edge7/29/20152011
html.elements.textarea.placeholder.line_breaks Chrome7/16/2014 Safari9/12/20222980
html.elements.textarea.readonly 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.required 📋Chrome1/25/2010 Edge7/29/20152011
html.elements.textarea.rows 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.textarea.wrap 📋Firefox3/22/2011 Edge7/29/20151590
html.elements.tfoot 📋Safari6/23/2003 Edge7/29/20154419
html.elements.tfoot.align Firefox11/9/2004 Edge7/29/20153914
html.elements.tfoot.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.tfoot.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.th 📋Safari6/23/2003 Edge7/29/20154419
html.elements.th.abbr Safari6/23/2003 Edge7/29/20154419
html.elements.th.align Firefox11/9/2004 Edge7/29/20153914
html.elements.th.axis Safari6/23/2003 Edge7/29/20154419
html.elements.th.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.th.colspan Safari6/23/2003 Edge7/29/20154419
html.elements.th.headers Safari6/23/2003 Edge7/29/20154419
html.elements.th.rowspan Safari6/23/2003 Edge7/29/20154419
html.elements.th.scope Safari6/23/2003 Edge7/29/20154419
html.elements.th.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.th.width Safari6/23/2003 Edge7/29/20154419
html.elements.thead 📋Safari6/23/2003 Edge7/29/20154419
Safari: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.Safari on iOS: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.WebView on iOS: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.
html.elements.thead.align Firefox11/9/2004 Edge7/29/20153914
html.elements.thead.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.thead.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.time 📋Firefox6/25/2013 Chrome10/17/20171575
html.elements.time.datetime Firefox6/25/2013 Chrome10/17/20171575
html.elements.title 📋Safari6/23/2003 Edge7/29/20154419
html.elements.tr 📋Safari6/23/2003 Edge7/29/20154419
html.elements.tr.align Firefox11/9/2004 Edge7/29/20153914
html.elements.tr.bgcolor Safari6/23/2003 Edge7/29/20154419
html.elements.tr.valign Firefox11/9/2004 Edge7/29/20153914
html.elements.track 📋Safari7/25/2012 Edge7/29/20151099
Chrome Android: Doesn't work for fullscreen video.Quest Browser: Doesn't work for fullscreen video.Samsung Internet: Doesn't work for fullscreen video.WebView Android: Doesn't work for fullscreen video.
html.elements.track.default 📋Safari7/25/2012 Edge7/29/20151099
html.elements.track.kind 📋Safari7/25/2012 Edge7/29/20151099
html.elements.track.label 📋Safari7/25/2012 Edge7/29/20151099
html.elements.track.src 📋Safari7/25/2012 Firefox11/15/20161574
Firefox: Before Firefox 50, setting the src didn't work, though it didn't raise an error.Firefox for Android: Before Firefox for Android 50, setting the src didn't work, though it didn't raise an error.
html.elements.track.srclang 📋Safari7/25/2012 Edge7/29/20151099
html.elements.tt 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.u 📋Safari6/23/2003 Edge7/29/20154419
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.ul 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.ul.compact 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.ul.type 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.var 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.video 📋Safari3/18/2008 Edge7/29/20152689
html.elements.video.aspect_ratio_computed_from_attributes Chrome12/10/2019 Safari9/16/2020281
html.elements.video.autoplay 📋Safari3/18/2008 Edge7/29/20152689
html.elements.video.autoplay.requires_muted_audio Chrome5/29/2018 Safari9/12/20221567
Firefox for Android: Between versions 79 and 91, the default behavior was to block videos from autoplaying, regardless of whether audio was muted.
html.elements.video.controls 📋Safari3/18/2008 Edge7/29/20152689
html.elements.video.crossorigin 📋Chrome2/20/2014 Firefox3/10/20202210
Firefox: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.Firefox for Android: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.
html.elements.video.disablepictureinpicture 📋Chrome9/4/2018 Firefox1/23/20241967
Firefox: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox for Android: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox for Android: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.
html.elements.video.height 📋Safari3/18/2008 Edge7/29/20152689
html.elements.video.loop 📋Safari3/18/2008 Edge7/29/20152689
html.elements.video.muted 📋Safari6/7/2010 Edge7/29/20151878
html.elements.video.poster 📋Safari3/18/2008 Edge7/29/20152689
html.elements.video.preload 📋Safari3/18/2008 Edge7/29/20152689
Chrome: Defaults to metadata in Chrome 64.Chrome Android: Defaults to metadata in Chrome Android 64.Quest Browser: Defaults to metadata in Quest Browser 5.0.Opera: Defaults to metadata in Opera 51.Opera Android: Defaults to metadata in Opera Android 47.Samsung Internet: Defaults to metadata in Samsung Internet 9.0.WebView Android: Defaults to metadata in WebView Android 64.
html.elements.video.src 📋Safari3/18/2008 Edge7/29/20152689
html.elements.video.width 📋Safari3/18/2008 Edge7/29/20152689
html.elements.wbr 📋Firefox11/9/2004 Edge7/29/20153914
html.elements.xmp 📋Firefox11/9/2004 Edge7/29/20153914
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.global_attributes.accesskey 📋Firefox11/9/2004 Edge7/29/20153914
html.global_attributes.autofocus 📋Chrome12/10/2019 Firefox2/14/20231162
Chrome: Supported for the <button>, <input>, <select>, and <textarea> elements.Chrome Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Edge: Supported for the <button>, <input>, <select>, and <textarea> elements.Firefox: Supported for the <button>, <input>, <select>, and <textarea> elements.Firefox for Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Internet Explorer: Supported for the <button>, <input>, <select>, and <textarea> elements.Quest Browser: Supported for the <button>, <input>, <select>, and <textarea> elements.Opera: Supported for the <button>, <input>, <select>, and <textarea> elements.Opera Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Safari: Supported for the <button>, <input>, <select>, and <textarea> elements.Safari on iOS: If there's no hardware keyboard connected, then the autofocus attribute has no effect (for example, the focus event doesn't fire and the element does not match the :focus selector).Samsung Internet: Supported for the <button>, <input>, <select>, and <textarea> elements.WebView Android: Supported for the <button>, <input>, <select>, and <textarea> elements.WebView on iOS: If there's no hardware keyboard connected, then the autofocus attribute has no effect (for example, the focus event doesn't fire and the element does not match the :focus selector).
html.global_attributes.class 📋Firefox11/9/2004 Edge7/29/20153914
html.global_attributes.contenteditable 📋Firefox6/17/2008 Edge7/29/20152598
html.global_attributes.contenteditable.plaintext-only Safari6/7/2010 Firefox3/4/20255384
html.global_attributes.data_attributes 📋Chrome10/19/2010 Edge7/29/20151744
html.global_attributes.dir 📋Firefox11/9/2004 Edge4/5/20174530
html.global_attributes.draggable 📋Firefox10/24/2006 Edge7/29/20153200
html.global_attributes.enterkeyhint 📋Chrome9/10/2019 Firefox11/2/2021784
html.global_attributes.exportparts 📋Chrome3/12/2019 Safari3/24/2020378
html.global_attributes.hidden 📋Chrome3/8/2011 Edge7/29/20151604
Safari: This attribute has no effect on <option> elements.Safari on iOS: This attribute has no effect on <option> elements.WebView on iOS: This attribute has no effect on <option> elements.
html.global_attributes.hidden.until-found 📋Chrome5/24/2022 Firefox2/24/20261372
Firefox: The browser does not correctly scroll to the matching text. See bug 2006040.Firefox for Android: The browser does not correctly scroll to the matching text. See bug 2006040.Safari: The browser does not correctly scroll to the matching text. See bug 304174.Safari on iOS: The browser does not correctly scroll to the matching text. See bug 304174.WebView on iOS: The browser does not correctly scroll to the matching text. See bug 304174.
html.global_attributes.id 📋Safari6/23/2003 Edge7/29/20154419
Firefox: id is a true global attribute only since Firefox 32.Firefox for Android: id is a true global attribute only since Firefox for Android 32.
html.global_attributes.inert 📋Safari5/16/2022 Firefox4/11/2023330
html.global_attributes.inputmode 📋Chrome4/17/2018 Firefox12/7/20211330
Safari on iOS: Before iOS 13, inputmode="none" had no effect.WebView on iOS: Before iOS 13, inputmode="none" had no effect.
html.global_attributes.lang 📋Firefox11/9/2004 Edge7/29/20153914
html.global_attributes.nonce 📋Chrome9/5/2017 Safari5/16/20221714
Firefox: Firefox does not prevent nonce exfiltration through content attributes.Firefox for Android: Firefox for Android does not prevent nonce exfiltration through content attributes.Safari: Safari does not prevent nonce exfiltration through content attributes.Safari on iOS: Safari on iOS does not prevent nonce exfiltration through content attributes.WebView on iOS: WebView on iOS does not prevent nonce exfiltration through content attributes.
html.global_attributes.part 📋Chrome3/12/2019 Safari3/24/2020378
html.global_attributes.popover 📋Chrome5/30/2023 Firefox4/16/2024322
html.global_attributes.slot 📋Chrome8/31/2016 Edge1/15/20201232
html.global_attributes.spellcheck 📋Firefox10/24/2006 Edge7/29/20153200
Chrome Android: Only supported on <textarea>.Firefox for Android: Only supported on <textarea>.Opera Android: Only supported on <textarea>.Safari on iOS: Only supported on <textarea>.Samsung Internet: Only supported on <textarea>.WebView Android: Only supported on <textarea>.WebView on iOS: Only supported on <textarea>.
html.global_attributes.style 📋Safari6/23/2003 Edge7/29/20154419
html.global_attributes.tabindex 📋Firefox11/29/2005 Edge7/29/20153529
html.global_attributes.title 📋Firefox11/9/2004 Edge7/29/20153914
html.global_attributes.title.multi-line_titles Edge7/29/2015 Firefox1/23/2018909
html.global_attributes.translate 📋Chrome5/15/2012 Firefox3/14/20233955