Keep the toolbox worker out of Pad - #168
Merged
Merged
Conversation
DenisValeev
marked this pull request as ready for review
July 26, 2026 21:27
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
1 participant
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.
What changed
/padand/pad/*before anyrespondWithpath.Why
The root-scoped cache-first worker was crossing the application boundary and storing Pad HTML, hashed assets, and API responses. That allowed a pre-curriculum samples response to outlive a Pad deployment despite Pad's
no-storepolicy.Impact
Toolbox offline behavior is unchanged for its own apps. Pad now owns its own release and cache policy.
Validation
node --check service-worker.jsnpx playwright test tests/offline-manifest.spec.js— 2 passed