Merged
Conversation
Contributor
|
Hey :) |
This was referenced Feb 15, 2026
vringar
force-pushed
the
firefox_137
branch
2 times, most recently
from
f54292b to
da69a69
Compare
Firefox 137 no longer creates webappsstore.sqlite in fresh profiles. localStorage has migrated to storage/ls-archive.sqlite, and storage.sqlite is now the QuotaManager metadata database. Replace webappsstore.sqlite with storage.sqlite in the dump_profile sanity check and test assertions, and regenerate the test seed profile with Firefox 137.
vringar
approved these changes
Feb 16, 2026
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
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.
Do verify that a profile action was successful, we now check the QuotaManagers storage.sqlite DB source for association.
With LocalStorage now apparently being delegated into various per-origin DBs as explained here our old file was only generated/present for legacy reasons.
AI found this bug as a description for the new storage engine, but that would mean the legacy setup was present/supported for ~7 years before removal