Fix Android support for Chrome 135 beta APIs #28660
Merged
+10
−30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
data:api
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
Elchi3
approved these changes
Dec 17, 2025
Member
Elchi3
left a comment
Elchi3
left a comment
There was a problem hiding this comment.
I suspect this is a one off error due to me using incomplete collector result data. I'm glad it didn't seem to have happened more.
If I had more time I would investigate the deltas for Chrome and Chrome Android and Android WebView more to make sure they are accurate. Maybe something for 2026.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
#27003 by @Elchi3 ran the BCD Collector for Chrome 135 beta but it seems to have set the Android support to false for any new entries but I see no reason for this.
Some of these have been corrected manually (e.g. in #27003) but these have not.
@Elchi3 do you know why this was? Should I raise an issue for this? I don't see the same for the latest Chrome 144 beta nor, 134/136 either side of this bad one. So maybe a one off issue?
Test results and supporting details
To be honest I have not tested these all, but I see no reason they were set to unsupported since, unless there is an exceptional reason, most changes to Chrome are also supported in Chrome Android and there are no reasons for these.
Related issues