Skip to content

test(webkit): CacheStorage entry should survive page.reload()#41701

Open
yury-s wants to merge 1 commit into
microsoft:mainfrom
yury-s:fix-41618
Open

test(webkit): CacheStorage entry should survive page.reload()#41701
yury-s wants to merge 1 commit into
microsoft:mainfrom
yury-s:fix-41618

Conversation

@yury-s

@yury-s yury-s commented Jul 8, 2026

Copy link
Copy Markdown
Member

Summary

  • Roll WebKit to r2328, which fixes CacheStorage disk persistence in persistent contexts. The Playwright patch added httpRequestHeaderFields to ResourceResponseData but never to its persistence encoder, so persisted responses failed to decode and cache.match() returned null on disk-backed (persistent) contexts — even immediately after cache.put(). Browser fix: microsoft/playwright-browsers#2404.
  • Add a persistent-context regression test (fixed by the roll).
  • Add an ephemeral-context test, marked expected-fail on WebKit: an in-memory CacheStorage entry is not persisted across reload, consistent with Safari.

Fixes #41618

Roll WebKit to r2328, which fixes CacheStorage disk persistence in
persistent contexts (httpRequestHeaderFields was missing from the
ResourceResponseData persistence encoder, so persisted responses failed
to decode and cache.match() returned null).

Add a persistent-context regression test (fixed by the roll) and an
ephemeral-context test. The ephemeral case is marked as expected to fail
on WebKit: an in-memory CacheStorage entry is not persisted across
reload, consistent with Safari.

Fixes microsoft#41618
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.

[BUG] WebKit: Cache Storage entry silently lost across page.reload() (container survives, entry does not)

2 participants