Particularly the custom CSS is likely to be nontrivial to setup again.
That said, browser.storage.sync is a pain in the ass, since it's limited to 8k record+id payloads (up to a total of 100k total). For oversized CSS strings, I guess we could either bundle a compression library, or split them overly long strings (or even both)? (We could also decide we don't care)
I think we also need to handle some some sort of migration from browser.storage.local to browser.storage.sync to avoid losing existing settings after the change.
Particularly the custom CSS is likely to be nontrivial to setup again.
That said, browser.storage.sync is a pain in the ass, since it's limited to 8k record+id payloads (up to a total of 100k total). For oversized CSS strings, I guess we could either bundle a compression library, or split them overly long strings (or even both)? (We could also decide we don't care)
I think we also need to handle some some sort of migration from browser.storage.local to browser.storage.sync to avoid losing existing settings after the change.