No-vary-search and prerender on Android updates#29114
Merged
Conversation
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
Elchi3
approved these changes
Feb 27, 2026
Member
Elchi3
left a comment
There was a problem hiding this comment.
Thanks @tunetheweb, I have no testing device and I think this should land for now. We can always improve if we have better information.
One wording suggestion for you to consider
Co-authored-by: Florian Scholz <fs@florianscholz.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This an update to #28689 due to the following changes for No-Vary-Search support on HTTP Cache:
While reviewing the changes for webview I also noticed that the data was incorrect about prerender overall (No-Vary-Search was originally a for that, but since expanded to HTTP Cache) so corrected that too.
Test results and supporting details
It's difficult to test these changes. I tried browser stack but it's on 142 and can't see how to update. My own personal testing device has 145 and also auto upgrades.
If you have access to a 143 device then you can follow test instructions here: #28689
Saying that, here's the change request enabling it from 143 and specifically mentioning webview is not included: https://critique.corp.google.com/cl/872578913
As to the Prerender partial support on webview, that's based on https://goo.gle/android-prerender which was released in Android 1.13.0 as per doc docs, which roughly coincides with Chrome 135.
Related issues
An update to #28689