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 152429
First in Firefox 318
First in Safari 368
First in Edge 11

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

162 APIs took an average of 2669.40 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).
HTTP APIsHTTP TTA
2003 584501.90
2004 45545.00
2006 43607.75
2008 12598.00
2009 102242.00
2010 21951.00
2011 51324.00
2012 21978.00
2013 161457.44
2014 11283.00
2015 101350.10
2016 91195.22
2017 141509.71
2018 61433.83
2019 101073.10
2020 4671.00
2022 6535.33

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 HTTPHTTP TTA
2003
  Safari 584501.90
2004
  Firefox 45545.00
2006
  Firefox 43607.75
2008
  Firefox 12598.00
2009
  Safari 102242.00
2010
  Chrome 21951.00
2011
  Chrome 51324.00
2012
  Chrome 12849.00
  Firefox 11107.00
2013
  Chrome 141329.50
  Firefox 22353.00
2014
  Chrome 11283.00
2015
  Firefox 22439.50
  Chrome 71101.86
  Edge 1909.00
2016
  Firefox 31055.33
  Chrome 51275.80
  Safari 11212.00
2017
  Chrome 101730.20
  Firefox 31044.00
  Edge 1702.00
2018
  Chrome 41568.00
  Firefox 11791.00
  Safari 1540.00
2019
  Chrome 91111.33
  Safari 1729.00
2020
  Chrome 4671.00
2022
  Chrome 6535.33

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 HTTP countHTTP TTA
2003
  Edge 574476.23
  Firefox 15965.00
2004
  Edge 45545.00
2006
  Edge 43607.75
2008
  Edge 12598.00
2009
  Edge 102242.00
2010
  Edge 21951.00
2011
  Edge 51324.00
2012
  Edge 21978.00
2013
  Edge 141470.93
  Firefox 21363.00
2014
  Safari 11283.00
2015
  Safari 22072.50
  Edge 61224.83
  Firefox 11098.00
  Chrome 1909.00
2016
  Safari 51113.40
  Edge 41297.50
2017
  Safari 81777.00
  Edge 5934.40
  Firefox 12248.00
2018
  Edge 1680.00
  Safari 21819.00
  Firefox 31428.33
2019
  Safari 5970.00
  Firefox 51176.20
2020
  Safari 4671.00
2022
  Safari 1251.00
  Firefox 5592.20

Stable APIs

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

Raw Data

Quick Links:

HTTP Data

API First Browser Date Last Browser Date Days Notes
http.data-url 📋Firefox10/24/2006 Edge7/29/20153200
Edge: Before Edge 79, the maximum size supported is 4GB.Internet Explorer: Since Internet Explorer 9, the maximum size supported is 4GB.Internet Explorer: In Internet Explorer 8, the maximum size supported is 32kB.
http.data-url.css_files Firefox10/24/2006 Edge7/29/20153200
http.data-url.html_files Firefox10/24/2006 Edge1/15/20204831
http.data-url.js_files Firefox10/24/2006 Edge7/29/20153200
http.data-url.top_level_navigation_blocked Chrome7/25/2017 Safari9/16/20201149
http.headers.Accept 📋Safari6/23/2003 Edge7/29/20154419
Firefox: In Firefox 66, the default Accept header value changed to */*.Firefox for Android: In Firefox for Android 66, the default Accept header value changed to */*.
http.headers.Accept-Encoding 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Accept-Language 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Accept-Ranges 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Access-Control-Allow-Credentials 📋Safari6/8/2009 Edge7/29/20152242
http.headers.Access-Control-Allow-Headers 📋Safari6/8/2009 Edge7/29/20152242
http.headers.Access-Control-Allow-Headers.wildcard Chrome12/6/2017 Edge1/15/2020770
http.headers.Access-Control-Allow-Methods 📋Safari6/8/2009 Edge7/29/20152242
http.headers.Access-Control-Allow-Methods.wildcard Chrome12/6/2017 Edge1/15/2020770
http.headers.Access-Control-Allow-Origin 📋Safari6/8/2009 Edge7/29/20152242
http.headers.Access-Control-Expose-Headers 📋Safari6/8/2009 Edge7/29/20152242
http.headers.Access-Control-Expose-Headers.wildcard Chrome3/6/2018 Edge1/15/2020680
http.headers.Access-Control-Max-Age 📋Safari6/8/2009 Edge7/29/20152242
http.headers.Access-Control-Request-Headers 📋Safari6/8/2009 Edge7/29/20152242
http.headers.Access-Control-Request-Method 📋Safari6/8/2009 Edge7/29/20152242
http.headers.Age 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Alt-Svc 📋Firefox5/12/2015 Safari9/18/20233051
Firefox: Only supports draft-04Firefox for Android: Only supports draft-04
http.headers.Authorization 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Authorization.Basic 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Authorization.Digest 📋Safari6/23/2003 Edge1/15/20206050
http.headers.Authorization.Digest.md5 Safari6/23/2003 Edge1/15/20206050
http.headers.Authorization.NTLM Firefox11/9/2004 Edge1/15/20205545
http.headers.Authorization.Negotiate 📋Firefox11/9/2004 Edge1/15/20205545
http.headers.Cache-Control 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Cache-Control.stale-while-revalidate Chrome6/4/2019 Safari9/16/2020470
http.headers.Clear-Site-Data 📋Chrome9/5/2017 Safari9/18/20232204
http.headers.Clear-Site-Data.cookies 📋Chrome9/5/2017 Safari9/18/20232204
http.headers.Clear-Site-Data.secure_context_required Chrome9/5/2017 Safari9/18/20232204
http.headers.Clear-Site-Data.storage 📋Chrome9/5/2017 Safari9/18/20232204
http.headers.Clear-Site-Data.wildcard 📋Firefox10/23/2018 Safari9/18/20231791
http.headers.Connection 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Content-Disposition 📋Safari6/23/2003 Edge7/29/20154419
Chrome: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 352093465.Chrome Android: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 352093465.Firefox: From version 82, if an <a> element's download attribute is set (for a same-origin URL) then the inline directive is ignored. Earlier versions did not match the specification and respected the header directive over the attribute. See bug 1658877.Firefox for Android: From version 82, if an <a> element's download attribute is set (for a same-origin URL) then the inline directive is ignored. Earlier versions did not match the specification and respected the header directive over the attribute. See bug 1658877.Quest Browser: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 352093465.Opera: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 352093465.Opera Android: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 352093465.Safari: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 18384.Safari on iOS: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 18384.Samsung Internet: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 352093465.WebView Android: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 352093465.WebView on iOS: When saving documents, the document title is used instead of the filename parameter if the disposition type is inline. See bug 18384.
http.headers.Content-Encoding 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Content-Encoding.br 📋Firefox1/26/2016 Safari9/19/2017602
Safari: Unsupported before macOS 10.13 High Sierra.
http.headers.Content-Language 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Content-Length 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Content-Length.cors_response_safelist Safari3/25/2019 Firefox3/23/2021729
http.headers.Content-Location 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Content-Range 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Content-Security-Policy 📋Chrome2/21/2013 Edge8/2/20161258
Internet Explorer: Only supporting 'sandbox' directive.
http.headers.Content-Security-Policy.base-uri 📋Firefox1/13/2015 Edge1/15/20201828
http.headers.Content-Security-Policy.child-src 📋Chrome1/21/2015 Edge4/5/2017805
http.headers.Content-Security-Policy.connect-src 📋Chrome2/21/2013 Firefox11/15/20161363
Firefox: Before Firefox 50, ping attributes of <a> elements weren't covered by connect-src.
http.headers.Content-Security-Policy.default-src 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.font-src 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.form-action 📋Chrome1/21/2015 Edge4/5/2017805
http.headers.Content-Security-Policy.frame-ancestors 📋Chrome1/21/2015 Firefox1/23/20181098
Firefox: Before Firefox 58, frame-ancestors is ignored in Content-Security-Policy-Report-Only.Firefox for Android: Before Firefox for Android 58, frame-ancestors is ignored in Content-Security-Policy-Report-Only.
http.headers.Content-Security-Policy.frame-src 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.img-src 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.manifest-src 📋Chrome1/21/2015 Edge1/15/20201820
http.headers.Content-Security-Policy.media-src 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.meta-element-support Chrome2/21/2013 Edge10/2/20182049
http.headers.Content-Security-Policy.object-src 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.report-sample Chrome6/5/2017 Safari3/14/20221743
http.headers.Content-Security-Policy.report-to 📋Chrome10/16/2018 Firefox9/3/20242149
http.headers.Content-Security-Policy.report-uri 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.sandbox 📋Chrome2/21/2013 Firefox11/15/20161363
http.headers.Content-Security-Policy.script-src 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.script-src.external_scripts 📋Chrome6/5/2017 Firefox8/1/20232248
http.headers.Content-Security-Policy.script-src.wasm-unsafe-eval Chrome1/4/2022 Safari9/12/2022251
http.headers.Content-Security-Policy.script-src-attr 📋Chrome6/4/2019 Firefox12/13/20221288
http.headers.Content-Security-Policy.script-src-elem 📋Chrome6/4/2019 Firefox12/13/20221288
http.headers.Content-Security-Policy.strict-dynamic Chrome7/20/2016 Safari3/14/20222063
http.headers.Content-Security-Policy.style-src 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Security-Policy.style-src-attr 📋Chrome6/4/2019 Firefox12/13/20221288
http.headers.Content-Security-Policy.style-src-elem 📋Chrome6/4/2019 Firefox12/13/20221288
http.headers.Content-Security-Policy.unsafe-hashes Chrome9/4/2018 Firefox1/17/20231596
http.headers.Content-Security-Policy.upgrade-insecure-requests 📋Chrome5/19/2015 Edge4/30/20181077
http.headers.Content-Security-Policy.worker-src 📋Chrome6/5/2017 Safari5/16/20221806
Chrome: Chrome 59 and higher skips the deprecated child-src directive.Chrome Android: Chrome Android 59 and higher skips the deprecated child-src directive.Quest Browser: Quest Browser 5.0 and higher skips the deprecated child-src directive.Opera: Opera 46 and higher skips the deprecated child-src directive.Opera Android: Opera Android 43 and higher skips the deprecated child-src directive.WebView Android: WebView Android 59 and higher skips the deprecated child-src directive.
http.headers.Content-Security-Policy.worker_support Safari9/20/2016 Edge1/15/20201212
http.headers.Content-Security-Policy-Report-Only 📋Chrome2/21/2013 Edge8/2/20161258
http.headers.Content-Type 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Cookie 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Cross-Origin-Embedder-Policy 📋Chrome5/19/2020 Safari12/13/2021573
http.headers.Cross-Origin-Opener-Policy 📋Chrome5/19/2020 Safari12/13/2021573
http.headers.Cross-Origin-Resource-Policy 📋Safari9/17/2018 Firefox3/10/2020540
Chrome: Until version 75, downloads for files with this header would fail in Chrome. See bug 41452948.Chrome: From version 80 to 85, linearized PDFs served inline with this header fail to render properly. See bug 40127935. From version 86, partial PDF loading is disabled.Chrome Android: Until version 75, downloads for files with this header would fail in Chrome Android. See bug 41452948.Chrome Android: From version 80 to 85, linearized PDFs served inline with this header fail to render properly. See bug 40127935. From version 86, partial PDF loading is disabled.Quest Browser: Until version 7.0, downloads for files with this header would fail in Quest Browser. See bug 41452948.Quest Browser: From version 9.0 to 85, linearized PDFs served inline with this header fail to render properly. See bug 40127935. From version 12.0, partial PDF loading is disabled.Opera: Until version 62, downloads for files with this header would fail in Opera. See bug 41452948.Opera: From version 67 to 85, linearized PDFs served inline with this header fail to render properly. See bug 40127935. From version 72, partial PDF loading is disabled.Opera Android: Until version 54, downloads for files with this header would fail in Opera Android. See bug 41452948.Opera Android: From version 57 to 85, linearized PDFs served inline with this header fail to render properly. See bug 40127935. From version 61, partial PDF loading is disabled.WebView Android: Until version 75, downloads for files with this header would fail in WebView Android. See bug 41452948.WebView Android: From version 80 to 85, linearized PDFs served inline with this header fail to render properly. See bug 40127935. From version 86, partial PDF loading is disabled.
http.headers.Date 📋Safari6/23/2003 Edge7/29/20154419
http.headers.ETag 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Expires 📋Safari6/23/2003 Edge7/29/20154419
http.headers.From 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Host 📋Safari6/23/2003 Edge7/29/20154419
http.headers.If-Match 📋Safari6/23/2003 Edge7/29/20154419
http.headers.If-Modified-Since 📋Safari6/23/2003 Edge7/29/20154419
http.headers.If-None-Match 📋Safari6/23/2003 Edge7/29/20154419
http.headers.If-Range 📋Safari6/23/2003 Edge7/29/20154419
http.headers.If-Unmodified-Since 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Keep-Alive 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Last-Modified 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Link 📋Chrome6/21/2022 Firefox11/21/2023518
http.headers.Link.fetchpriority 📋Chrome6/21/2022 Firefox10/29/2024861
http.headers.Location 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Origin 📋Safari6/23/2003 Firefox10/22/20195965
Edge: Before Edge 79, this header was not sent with POST requests.Firefox: Not sent with POST requests, see bug 446344.Firefox for Android: Not sent with POST requests, see bug 446344.
http.headers.Pragma 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Proxy-Authenticate 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Range 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Range.cors_safe Chrome3/1/2022 Firefox8/29/2023546
http.headers.Referer 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Referer.length_limit_4096B Chrome9/10/2019 Safari9/16/2020372
http.headers.Referrer-Policy 📋Firefox11/15/2016 Edge1/15/20201156
http.headers.Referrer-Policy.default_strict-origin-when-cross-origin Chrome8/25/2020 Safari9/20/2021391
http.headers.Referrer-Policy.same-origin Firefox3/7/2017 Edge1/15/20201044
http.headers.Referrer-Policy.strict-origin Firefox3/7/2017 Edge1/15/20201044
http.headers.Referrer-Policy.strict-origin-when-cross-origin Firefox3/7/2017 Edge1/15/20201044
http.headers.Refresh 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Sec-Fetch-Dest 📋Chrome2/4/2020 Safari3/27/20231147
http.headers.Sec-Fetch-Mode 📋Chrome7/30/2019 Safari3/27/20231336
http.headers.Sec-Fetch-Site 📋Chrome7/30/2019 Safari3/27/20231336
http.headers.Sec-Fetch-User 📋Chrome7/30/2019 Safari3/27/20231336
http.headers.Sec-WebSocket-Accept 📋Chrome12/13/2011 Edge7/29/20151324
http.headers.Sec-WebSocket-Extensions 📋Chrome12/13/2011 Edge7/29/20151324
http.headers.Sec-WebSocket-Key 📋Chrome12/13/2011 Edge7/29/20151324
http.headers.Sec-WebSocket-Protocol 📋Chrome12/13/2011 Edge7/29/20151324
http.headers.Sec-WebSocket-Version 📋Chrome12/13/2011 Edge7/29/20151324
http.headers.Server 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Server-Timing 📋Chrome3/6/2018 Safari3/27/20231847
http.headers.Service-Worker 📋Chrome10/7/2014 Safari4/12/20181283
http.headers.Service-Worker-Allowed 📋Chrome4/14/2015 Safari4/12/20181094
http.headers.Set-Cookie 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Set-Cookie.HttpOnly Firefox6/17/2008 Edge7/29/20152598
http.headers.Set-Cookie.Max-Age Safari6/23/2003 Edge7/29/20154419
http.headers.Set-Cookie.SameSite 📋Chrome5/25/2016 Safari9/19/20191212
Safari: Safari 13 on macOS 10.14 (Mojave), treats SameSite=None and invalid values as Strict. This is fixed in version 10.15 (Catalina) and later.Safari: Treats SameSite=None and invalid values as Strict in macOS before 10.15 Catalina. See bug 198181.Safari on iOS: Treats SameSite=None and invalid values as Strict in iOS before 13. See bug 198181.WebView on iOS: Treats SameSite=None and invalid values as Strict in iOS before 13. See bug 198181.
http.headers.Set-Cookie.SameSite.Lax Chrome5/25/2016 Safari9/17/2018845
http.headers.Set-Cookie.SameSite.None Edge10/17/2017 Safari9/19/2019702
Chrome: Rejects cookies with SameSite=None. See SameSite=None: Known Incompatible Clients.Chrome Android: Rejects cookies with SameSite=None. See SameSite=None: Known Incompatible Clients.Quest Browser: Rejects cookies with SameSite=None. See SameSite=None: Known Incompatible Clients.Opera: Rejects cookies with SameSite=None. See SameSite=None: Known Incompatible Clients.Opera Android: Rejects cookies with SameSite=None. See SameSite=None: Known Incompatible Clients.Safari: Not supported before macOS version 10.15 (Catalina).Samsung Internet: Rejects cookies with SameSite=None. See SameSite=None: Known Incompatible Clients.WebView Android: Rejects cookies with SameSite=None. See SameSite=None: Known Incompatible Clients.
http.headers.Set-Cookie.SameSite.Strict Chrome5/25/2016 Safari9/17/2018845
http.headers.Set-Cookie.cookie_prefixes Chrome3/2/2016 Edge1/15/20201414
http.headers.SourceMap 📋Chrome3/28/2012 Edge1/15/20202849
Chrome: Not supported for ECMAScript Modules (<script type="module">). See bug 40854862.Chrome Android: Not supported for ECMAScript Modules (<script type="module">). See bug 40854862.Quest Browser: Not supported for ECMAScript Modules (<script type="module">). See bug 40854862.Opera: Not supported for ECMAScript Modules (<script type="module">). See bug 40854862.Opera Android: Not supported for ECMAScript Modules (<script type="module">). See bug 40854862.Samsung Internet: Not supported for ECMAScript Modules (<script type="module">). See bug 40854862.WebView Android: Not supported for ECMAScript Modules (<script type="module">). See bug 40854862.
http.headers.Strict-Transport-Security 📋Chrome1/25/2010 Edge7/29/20152011
http.headers.TE 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Timing-Allow-Origin 📋Firefox3/8/2016 Edge1/15/20201408
http.headers.Transfer-Encoding 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Upgrade 📋Chrome5/25/2010 Edge7/29/20151891
http.headers.Upgrade-Insecure-Requests 📋Chrome7/21/2015 Edge4/30/20181014
http.headers.User-Agent 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Vary 📋Safari6/23/2003 Edge7/29/20154419
http.headers.Via 📋Safari6/23/2003 Edge7/29/20154419
http.headers.WWW-Authenticate 📋Safari6/23/2003 Edge7/29/20154419
http.headers.WWW-Authenticate.Basic 📋Safari6/23/2003 Edge7/29/20154419
http.headers.WWW-Authenticate.Digest 📋Safari6/23/2003 Edge7/29/20154419
http.headers.WWW-Authenticate.Digest.md5 Safari6/23/2003 Edge7/29/20154419
http.headers.WWW-Authenticate.NTLM Firefox11/9/2004 Edge1/15/20205545
http.headers.WWW-Authenticate.Negotiate 📋Firefox11/9/2004 Edge1/15/20205545
http.headers.Warning 📋Safari6/23/2003 Edge7/29/20154419
http.headers.X-Content-Type-Options 📋Edge7/29/2015 Chrome1/23/2018909
Chrome: Not supported for stylesheets.Chrome Android: Not supported for stylesheets.Quest Browser: Not supported for stylesheets.Opera: Not supported for stylesheets.Opera Android: Not supported for stylesheets.Samsung Internet: Not supported for stylesheets.WebView Android: Not supported for stylesheets.
http.headers.X-Frame-Options 📋Safari6/8/2009 Edge7/29/20152242
http.headers.X-Frame-Options.SAMEORIGIN Safari6/8/2009 Edge7/29/20152242
Chrome: Starting in Chrome 61, this applies to all of a frame's ancestors.Chrome Android: Starting in Chrome Android 61, this applies to all of a frame's ancestors.Firefox: Starting in Firefox 59, this applies to all of a frame's ancestors.Firefox for Android: Starting in Firefox for Android 59, this applies to all of a frame's ancestors.Quest Browser: Starting in Quest Browser 5.0, this applies to all of a frame's ancestors.Opera: Starting in Opera 48, this applies to all of a frame's ancestors.Opera Android: Starting in Opera Android 45, this applies to all of a frame's ancestors.Samsung Internet: Starting in Samsung Internet 8.0, this applies to all of a frame's ancestors.WebView Android: Starting in WebView Android 61, this applies to all of a frame's ancestors.
http.methods.CONNECT 📋Safari6/23/2003 Edge7/29/20154419
http.methods.DELETE 📋Safari6/23/2003 Edge7/29/20154419
http.methods.GET 📋Safari6/23/2003 Edge7/29/20154419
http.methods.HEAD 📋Safari6/23/2003 Edge7/29/20154419
http.methods.OPTIONS 📋Safari6/23/2003 Edge7/29/20154419
http.methods.POST 📋Safari6/23/2003 Edge7/29/20154419
http.methods.PUT 📋Safari6/23/2003 Edge7/29/20154419
http.mixed-content 📋Firefox8/6/2013 Edge1/15/20202353
http.mixed-content.blockable_mixed_content 📋Firefox8/6/2013 Edge1/15/20202353
Chrome: From version 79 blocks iframes, scripts, and stylesheets.Chrome Android: From version 79 blocks iframes, scripts, and stylesheets.Edge: From version 79 blocks iframes, scripts, and stylesheets.Quest Browser: From version 8.0 blocks iframes, scripts, and stylesheets.Opera: From version 66 blocks iframes, scripts, and stylesheets.Opera Android: From version 57 blocks iframes, scripts, and stylesheets.Samsung Internet: From version 12.0 blocks iframes, scripts, and stylesheets.WebView Android: From version 79 blocks iframes, scripts, and stylesheets.
http.status.103 📋Chrome6/21/2022 Firefox11/21/2023518
Chrome: Supported in HTTP/2 and later only.Chrome Android: Supported in HTTP/2 and later only.Edge: Supported in HTTP/2 and later only.Quest Browser: Supported in HTTP/2 and later only.Opera: Supported in HTTP/2 and later only.Opera Android: Supported in HTTP/2 and later only.Safari: Supported in HTTP/2 and later only.Safari on iOS: Supported in HTTP/2 and later only.Samsung Internet: Supported in HTTP/2 and later only.WebView Android: Supported in HTTP/2 and later only.WebView on iOS: Supported in HTTP/2 and later only.
http.status.103.preconnect Chrome6/21/2022 Firefox11/21/2023518
http.status.308 📋Firefox7/17/2012 Edge7/29/20151107
Internet Explorer: Does not work below Windows 10.