-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 Remove older performance info #26711
🚀 Remove older performance info #26711
Conversation
Code LGTM. I don't have the context on why we had these special cases and why its okay to remove now, any chance you can either explain or point me to things to read? |
These branches handled older implementations in Chromium of the API solidified in Chromium 77. Now that it's stable, and has been released for awhile we can stop collecting data on the older APIs. |
Do we have stats on the % of users that are still on versions before 77, or is there some kind of heuristic/rule-of-thumb that is safe to use? |
https://amp.dev/support/faq/supported-browsers/ Chromium 76 just left the window for supported browsers, we support Chromium 78 and beyond as of today. |
There were several codepaths in
performance-impl
that supported behaviour for capturing data from Chromium user-agents older than version 77 (including for just 76).Removing the older methods makes the implementation smaller, slightly more efficient, and easier to understand.