Switching between the Kinto and Rust extension storage engines doesn't work
Categories
(Firefox :: Sync, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox78 | --- | verified |
People
(Reporter: lina, Assigned: lina)
References
Details
Attachments
(2 files)
STR:
- Flip the
webextensions.storage.sync.kinto
tofalse
(it's true by default) to switch to the Rust engine. - Open the Browser Console.
- Call
Weave.Service.engineManager.switchAlternatives()
to ensure the pref flip takes effect. - Type
String(Weave.Service.engineManager.get('extension-storage')._sync)
to check the source code.
Expected: The source of this function, indicating it's using the Rust sync engine.
Actual: This, so it's still using Kinto! 😱
(If you then sync and check about:sync-log
, you'll notice log lines for Syncing extension settings for <add-on name>
, which is also from Kinto).
Comment 1•3 years ago
|
||
I think markh said in the demo that it requires restarting after flipping the pref to take effect, no?
Assignee | ||
Comment 2•3 years ago
|
||
Alternative engines are registered using the lowercased version of
the keys in the modules object. But extension-storage
is hyphenated,
so we need to use Extension-Storage
(not ExtensionStorage
) as the
key name, to match the name of the engine and its collection.
Without the hyphen, we'll register the alternative as
extensionstorage
, so it'll never be used because everything else
expects the engine to be called extension-storage
.
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Hmm, I think you do have to restart for the WebExtension API, but there might be another issue on the Sync side—we weren't registering the alternative under the right name (extension-storage
vs. extensionstorage
), so, even if you flipped the pref and restarted, it would still use Kinto.
Pushed by kcambridge@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f350b8dff15d Correctly register `Extension-Storage` engine alternatives. r=tcsc
Comment 5•3 years ago
|
||
bugherder |
Comment 6•3 years ago
|
||
Verified as fixed in FF78.0b6. I will attach postfix screenshot
Updated•3 years ago
|
Comment 7•3 years ago
|
||
Description
•