Skip to content
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

Add Clear-Site-Data Clear Cache interaction with prerender #361

Merged
merged 4 commits into from
Feb 10, 2025

Conversation

srwei
Copy link
Contributor

@srwei srwei commented Feb 6, 2025

Copy link

github-actions bot commented Feb 6, 2025

Preview:

@domenic
Copy link
Collaborator

domenic commented Feb 6, 2025

ipr — PR has contribution issues. The following users' affiliation could not be determined: @srwei.

For this, you can work to link your GitHub account and your W3C account, and ensure your W3C account joins the WICG.

Copy link
Collaborator

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looked good and then I looked at the build result and realized we had some minor updates to make. But the normative content is solid and we can merge as soon as those minor fixes are done.

@domenic domenic merged commit d60ce7c into WICG:main Feb 10, 2025
2 checks passed
aarongable pushed a commit to chromium/chromium that referenced this pull request Feb 12, 2025
This change cancels all the existing prerenders when browsing data
removal is run on cached data. This can be triggered by the Delete Browsing Data option or with Clear-Site-Data response headers. Developer Tools will now also show the previously successful prerender(s) as failed. A new PrerenderFinalStatus is added specifically for this case.

nav-speculation spec PR: WICG/nav-speculation#361

NO_IFTTT=Changes for PrerenderFinalStatus will be done in separate repositories.

Bug: 40262311
Change-Id: Ie82895e555f3a9d4e2576686223e67443d198353
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6173154
Reviewed-by: Ayu Ishii <[email protected]>
Reviewed-by: Alex Rudenko <[email protected]>
Commit-Queue: Steven Wei <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1419494}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Feb 12, 2025
This change cancels all the existing prerenders when browsing data
removal is run on cached data. This can be triggered by the Delete Browsing Data option or with Clear-Site-Data response headers. Developer Tools will now also show the previously successful prerender(s) as failed. A new PrerenderFinalStatus is added specifically for this case.

nav-speculation spec PR: WICG/nav-speculation#361

NO_IFTTT=Changes for PrerenderFinalStatus will be done in separate repositories.

Bug: 40262311
Change-Id: Ie82895e555f3a9d4e2576686223e67443d198353
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6173154
Reviewed-by: Ayu Ishii <[email protected]>
Reviewed-by: Alex Rudenko <[email protected]>
Commit-Queue: Steven Wei <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1419494}
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this pull request Feb 12, 2025
This change cancels all the existing prerenders when browsing data
removal is run on cached data. This can be triggered by the Delete Browsing Data option or with Clear-Site-Data response headers. Developer Tools will now also show the previously successful prerender(s) as failed. A new PrerenderFinalStatus is added specifically for this case.

nav-speculation spec PR: WICG/nav-speculation#361

NO_IFTTT=Changes for PrerenderFinalStatus will be done in separate repositories.

Bug: 40262311
Change-Id: Ie82895e555f3a9d4e2576686223e67443d198353
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6173154
Reviewed-by: Ayu Ishii <[email protected]>
Reviewed-by: Alex Rudenko <[email protected]>
Commit-Queue: Steven Wei <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1419494}
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request Feb 18, 2025
…moval is run., a=testonly

Automatic update from web-platform-tests
Cancels prerenders when browsing data removal is run.

This change cancels all the existing prerenders when browsing data
removal is run on cached data. This can be triggered by the Delete Browsing Data option or with Clear-Site-Data response headers. Developer Tools will now also show the previously successful prerender(s) as failed. A new PrerenderFinalStatus is added specifically for this case.

nav-speculation spec PR: WICG/nav-speculation#361

NO_IFTTT=Changes for PrerenderFinalStatus will be done in separate repositories.

Bug: 40262311
Change-Id: Ie82895e555f3a9d4e2576686223e67443d198353
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6173154
Reviewed-by: Ayu Ishii <[email protected]>
Reviewed-by: Alex Rudenko <[email protected]>
Commit-Queue: Steven Wei <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1419494}

--

wpt-commits: c1577d03f55f932e33a86fe0553b1f0fa5bfd8d1
wpt-pr: 50666
i3roly pushed a commit to i3roly/firefox-dynasty that referenced this pull request Feb 19, 2025
…moval is run., a=testonly

Automatic update from web-platform-tests
Cancels prerenders when browsing data removal is run.

This change cancels all the existing prerenders when browsing data
removal is run on cached data. This can be triggered by the Delete Browsing Data option or with Clear-Site-Data response headers. Developer Tools will now also show the previously successful prerender(s) as failed. A new PrerenderFinalStatus is added specifically for this case.

nav-speculation spec PR: WICG/nav-speculation#361

NO_IFTTT=Changes for PrerenderFinalStatus will be done in separate repositories.

Bug: 40262311
Change-Id: Ie82895e555f3a9d4e2576686223e67443d198353
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6173154
Reviewed-by: Ayu Ishii <[email protected]>
Reviewed-by: Alex Rudenko <[email protected]>
Commit-Queue: Steven Wei <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1419494}

--

wpt-commits: c1577d03f55f932e33a86fe0553b1f0fa5bfd8d1
wpt-pr: 50666
jamienicol pushed a commit to jamienicol/gecko that referenced this pull request Feb 25, 2025
…moval is run., a=testonly

Automatic update from web-platform-tests
Cancels prerenders when browsing data removal is run.

This change cancels all the existing prerenders when browsing data
removal is run on cached data. This can be triggered by the Delete Browsing Data option or with Clear-Site-Data response headers. Developer Tools will now also show the previously successful prerender(s) as failed. A new PrerenderFinalStatus is added specifically for this case.

nav-speculation spec PR: WICG/nav-speculation#361

NO_IFTTT=Changes for PrerenderFinalStatus will be done in separate repositories.

Bug: 40262311
Change-Id: Ie82895e555f3a9d4e2576686223e67443d198353
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6173154
Reviewed-by: Ayu Ishii <[email protected]>
Reviewed-by: Alex Rudenko <[email protected]>
Commit-Queue: Steven Wei <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1419494}

--

wpt-commits: c1577d03f55f932e33a86fe0553b1f0fa5bfd8d1
wpt-pr: 50666
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants