Deprecated across Chrome and Edge

Summary

A count of the number of APIs that were removed from A first and B last.
	Last removed from Chrome	Last removed from Edge
First removed from Chrome		1
First removed from Edge	1

A count of the number of APIs that were removed from A first and B last.

Last removed from Chrome

Last removed from Edge

First removed from Chrome

First removed from Edge

Average time for an API to be removed across Chrome and Edge

2 APIs took an average of 2060.58 days to be removed

API breakdown:

HTTP: 2060.58 days

Average time to landing by year of first deprecation

If a feature is deprecated in the earliest browser in 20XX it took Y days on average to become deprecated in the last browser (when considering Chrome and Edge). TTA (time to available).
	HTTP APIs	HTTP TTA
2018	1	2880.08
2022	1	1241.08

If a feature is deprecated in the earliest browser in 20XX it took Y days on average to become deprecated in the last browser (when considering Chrome and Edge). TTA (time to available).

HTTP APIs

HTTP TTA

2018

2880.08

2022

1241.08

Deprecated APIs

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

Raw Data

HTTP Data

API	First Browser	Date	Last Browser	Date	Days	Notes
http.headers.Expect-CT 📋	Chrome	10/25/2022	Edge	10/27/2022		Chrome: Before later builds of Chrome 64, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Chrome Android: Before later builds of Chrome Android 64, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Edge: Before later builds of Edge 79, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Quest Browser: Before later builds of Quest Browser 5.0, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Opera: Before later builds of Opera 51, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Opera Android: Before later builds of Opera Android 47, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Samsung Internet: Before later builds of Samsung Internet 9.0, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.
http.headers.X-XSS-Protection	Edge	4/30/2018	Chrome	10/22/2019

API

First Browser

Date

Last Browser

Date

Days

Notes

http.headers.Expect-CT 📋

Chrome

10/25/2022

Edge

10/27/2022

Chrome: Before later builds of Chrome 64, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Chrome Android: Before later builds of Chrome Android 64, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Edge: Before later builds of Edge 79, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Quest Browser: Before later builds of Quest Browser 5.0, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Opera: Before later builds of Opera 51, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Opera Android: Before later builds of Opera Android 47, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.Samsung Internet: Before later builds of Samsung Internet 9.0, invalid Expect-CT reports would be sent. Newer versions do not send reports after 10 weeks from the build date. See bug 41356303.

http.headers.X-XSS-Protection

Edge

4/30/2018

Chrome

10/22/2019