chrome.storage.sync: support syncing to self-hosted

NEW
Unassigned

Status

()

Toolkit
WebExtensions: General
P5
normal
7 months ago
5 months ago

People

(Reporter: glasserc, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [storage]triaged)

(Reporter)

Description

7 months ago
Right now there are a bunch of places in the chrome.storage.sync code where we assume we're syncing to our "official" FxA servers. It would be good to loosen these assumptions and be more accepting of people who want to sync to their own services. I don't think all the requirements are clear yet. In particular, how do we handle crypto?

Updated

7 months ago
Component: WebExtensions: Untriaged → WebExtensions: General
Priority: -- → P5
Whiteboard: [storage]triaged
You need to log in before you can comment on or make changes to this bug.