You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2023. It is now read-only.
I originally thought that swapping context ids would allow for different cookie locations. This may still be the case, but looking at the browser cookie api, values are still being stored into firefox-default, rather than the respective cookie stores.
WebExtensions have been pretty powerful, but also have some issues:
Everything is async, which is easy to write, but doesn't allow for communication between the extension and the native app. Things like preventing events aren't possible with async. Same with reading settings. With native settings, I can keep it in memory, read it synchronously, and act. With extensions, they get suspended, they have to read asynchronously, and they have their own storage which I need to sync
And with web extensions in general, getting messages to send has been the biggest pain so far
contextId:
I originally thought that swapping context ids would allow for different cookie locations. This may still be the case, but looking at the browser cookie api, values are still being stored into firefox-default, rather than the respective cookie stores.
https://bugzilla.mozilla.org/show_bug.cgi?id=1643688
The text was updated successfully, but these errors were encountered: