Use containers name instead of numbers in import / export
See original GitHub issueDescribe the Bug/Feature
I’m using Cookie-AutoDelete along with containerise. Containerise’s main feature is automatically reopening tabs in their proper container, according to a CSV table. I use Cookie-AutoDelete’s containers support to have essentially cookies separated between containers.
Some days ago, a certain Firefox / extension update restored my containers to Firefox’ defaults (unreproducible + don’t know who to blame = haven’t reported a bug). Yet, it seems both extensions (CAD & Containerise) have kept their settings while I’ve had backups of them.
The problem I’ve encountered when trying to restore the settings, was that CAD’s export had keys such as:
"firefox-container-14": [
...
],
Because I’ve had to recreate the containers (using “multi-account-containers”), CAD’s export was essentially useless because the “new” containers had different IDs.
Ideally, since I use both extensions, I could write a script that’d sync both extensions’ settings but that’s impossible since CAD’s importer (I assume) isn’t capable of referring to containers by name and not ID.
I assume implementing this will be a little bit difficult because we’d probably want keep backwards compatibility? On a second thought, I think, it’s a matter of:
if (key starts with firefox-container-) and (a container matches the key's id):
// import cookie settings for this container (according to id)
else if (a container named "key" exists):
// import cookie settings for this container (according to name)
end if
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:5 (2 by maintainers)
Top GitHub Comments
Good idea. I’ll need to look into it further.
What about a mapping option? User requests import and is met with a screen to map containers themselves. Gets around IDs, colors, spellings, etc