For a given set of browsers, what APIs are not yet in all of them.
| Not in Firefox | Not in Safari | |
|---|---|---|
| In Firefox | 28 | |
| In Safari | 5 |
Below is a list of features that are not in all of Firefox and Safari
| API | First Browser | Date | Days in Limbo | Notes |
|---|---|---|---|---|
| http.headers.Access-Control-Allow-Headers.authorization_not_covered_by_wildcard | Firefox | 7/4/2023 | 1125 | |
| http.headers.Authorization.Digest.SHA-256 | Firefox | 10/5/2021 | 1762 | |
| http.headers.Clear-Site-Data.cache 📋 | Safari | 9/18/2023 | 1049 | |
| http.headers.Content-Encoding.zstd 📋 | Firefox | 5/14/2024 | 810 | |
| http.headers.Content-Security-Policy.block-all-mixed-content | Safari | 9/20/2016 | 3603 | Chrome: Will be removed, see bug 40260100.Chrome Android: Will be removed, see bug 40260100.Quest Browser: Will be removed, see bug 40260100.Opera: Will be removed, see bug 40260100.Opera Android: Will be removed, see bug 40260100.Samsung Internet: Will be removed, see bug 40260100.WebView Android: Will be removed, see bug 40260100. |
| http.headers.Content-Security-Policy.form-action.blocks_redirects | Safari | 4/12/2018 | 3034 | |
| http.headers.Content-Security-Policy.prefetch-src | Safari | 1/23/2023 | 1287 | |
| http.headers.Cross-Origin-Embedder-Policy.credentialless 📋 | Firefox | 10/24/2023 | 1013 | |
| http.headers.DNT | Firefox | 3/22/2011 | 5612 | |
| http.headers.Early-Data 📋 | Firefox | 1/23/2018 | 3113 | |
| http.headers.Priority 📋 | Firefox | 7/9/2024 | 754 | |
| http.headers.Report-To | Firefox | 9/3/2024 | 698 | |
| http.headers.Reporting-Endpoints 📋 | Firefox | 9/3/2024 | 698 | |
| http.headers.Sec-GPC 📋 | Firefox | 11/21/2023 | 985 | Firefox: Opt-in to GPC using the Website Privacy Preference setting ( about:preferences#privacy) checkbox 'Tell websites not to sell or share my data', or by setting the preference privacy.globalprivacycontrol.enabled to true. |
| http.headers.Sec-Purpose 📋 | Firefox | 7/4/2023 | 1125 | |
| http.headers.Sec-Purpose.prefetch | Firefox | 7/4/2023 | 1125 | Chrome: Doesn't support Sec-Purpose for <link rel="prefetch">. In Chrome, the legacy Purpose: prefetch header is used to indicate a link request is a prefetch. See bug 40236973.Chrome Android: Doesn't support Sec-Purpose for <link rel="prefetch">. In Chrome Android, the legacy Purpose: prefetch header is used to indicate a link request is a prefetch. See bug 40236973.Edge: Doesn't support Sec-Purpose for <link rel="prefetch">. In Edge, the legacy Purpose: prefetch header is used to indicate a link request is a prefetch. See bug 40236973.Firefox: Sec-Purpose: prefetch replaces the non-standard X-moz: prefetch header that was used to indicate a link prefetch request in earlier versions.Firefox: Prefetch requests should also include the header Accept header string for navigations, but Accept: */* is sent instead.Firefox for Android: Sec-Purpose: prefetch replaces the non-standard X-moz: prefetch header that was used to indicate a link prefetch request in earlier versions.Firefox for Android: Prefetch requests should also include the header Accept header string for navigations, but Accept: */* is sent instead.Quest Browser: Doesn't support Sec-Purpose for <link rel="prefetch">. In Quest Browser, the legacy Purpose: prefetch header is used to indicate a link request is a prefetch. See bug 40236973.Opera: Doesn't support Sec-Purpose for <link rel="prefetch">. In Opera, the legacy Purpose: prefetch header is used to indicate a link request is a prefetch. See bug 40236973.Samsung Internet: Doesn't support Sec-Purpose for <link rel="prefetch">. In Samsung Internet, the legacy Purpose: prefetch header is used to indicate a link request is a prefetch. See bug 40236973.WebView Android: Doesn't support Sec-Purpose for <link rel="prefetch">. In WebView Android, the legacy Purpose: prefetch header is used to indicate a link request is a prefetch. See bug 40236973. |
| http.headers.Server-Timing.trailer | Firefox | 12/10/2019 | 2427 | Firefox: Only the Server-Timing header is a recognized trailer, and it is only exposed to DevTools in the network Timing tab (bug 1403051). Developers cannot access trailers via the Fetch API or XHR.Firefox for Android: Only the Server-Timing header is a recognized trailer, and it is only exposed to DevTools in the network Timing tab (bug 1403051). Developers cannot access trailers via the Fetch API or XHR. |
| http.headers.Service-Worker-Navigation-Preload 📋 | Safari | 3/14/2022 | 1602 | |
| http.headers.Set-Cookie.Partitioned 📋 | Firefox | 10/1/2024 | 670 | |
| http.headers.Set-Cookie.SameSite.Lax_default | Firefox | 9/3/2019 | 2525 | |
| http.headers.Set-Cookie.SameSite.none_requires_secure | Firefox | 10/1/2024 | 670 | |
| http.headers.Set-Cookie.SameSite.schemeful | Firefox | 7/28/2020 | 2196 | |
| http.headers.Trailer 📋 | Firefox | 12/10/2019 | 2427 | Firefox: Only the Server-Timing header is a recognized trailer, and it is only exposed to DevTools in the network Timing tab (bug 1403051). Developers cannot access trailers via the Fetch API or XHR.Firefox for Android: Only the Server-Timing header is a recognized trailer, and it is only exposed to DevTools in the network Timing tab (bug 1403051). Developers cannot access trailers via the Fetch API or XHR. |
| http.headers.WWW-Authenticate.Digest.SHA-256 | Firefox | 10/5/2021 | 1762 | |
| http.headers.X-DNS-Prefetch-Control | Firefox | 10/24/2006 | 7222 | |
| http.mixed-content.allow_file_urls 📋 | Firefox | 8/6/2013 | 4744 | |
| http.mixed-content.allow_localhost_url 📋 | Firefox | 12/15/2020 | 2056 | |
| http.mixed-content.allow_loopback_url 📋 | Firefox | 8/8/2017 | 3281 | |
| http.mixed-content.auto_upgrade_images 📋 | Firefox | 6/11/2024 | 782 | Firefox: Set security.mixed_content.upgrade_display_content preference to true to allow HTTP fetching and display of upgradable content.Firefox: Set security.mixed_content.block_display_content preference to true to block all mixed content.Firefox for Android: Set security.mixed_content.upgrade_display_content preference to true to allow HTTP fetching and display of upgradable content.Firefox for Android: Set security.mixed_content.block_display_content preference to true to block all mixed content. |
| http.mixed-content.auto_upgrade_video_audio 📋 | Firefox | 6/11/2024 | 782 | Firefox: Set security.mixed_content.upgrade_display_content preference to true to allow HTTP fetching and display of upgradable content.Firefox: Set security.mixed_content.block_display_content preference to true to block all mixed content.Firefox for Android: Set security.mixed_content.upgrade_display_content preference to true to allow HTTP fetching and display of upgradable content.Firefox for Android: Set security.mixed_content.block_display_content preference to true to block all mixed content. |
| http.mixed-content.block_mixed_downloads 📋 | Firefox | 7/13/2021 | 1846 | |
| http.status.103.preload | Firefox | 2/20/2024 | 894 | |
| http.status.425 📋 | Firefox | 1/23/2018 | 3113 |