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
Continuing the discussion from the last teleconf. Currently, Google Chrome and Microsoft Edge have persistent IDs, while Firefox is randomly generating an ID when the extension is loading. From the last meeting notes it seems that the majority of this group prefers unique persistent global IDs.
I'm not sure how important it is to have the ID persistent across browsers (?), however it seems to make sense to have a persistent ID, for native and cross-extension messaging, in the same browser, at least.
On the other hand, if an extension has web accessible resources this makes the extension easily detectable for websites, if the browserext:// URL is predictable due to a static extension ID. One solution could be to use URLs like browserext://<extension_id>.<random_token>/<path> where random_tokenis generated when the extension is loaded.
Continuing the discussion from the last teleconf. Currently, Google Chrome and Microsoft Edge have persistent IDs, while Firefox is randomly generating an ID when the extension is loading. From the last meeting notes it seems that the majority of this group prefers unique persistent global IDs.
I'm not sure how important it is to have the ID persistent across browsers (?), however it seems to make sense to have a persistent ID, for native and cross-extension messaging, in the same browser, at least.
On the other hand, if an extension has web accessible resources this makes the extension easily detectable for websites, if the
browserext://URL is predictable due to a static extension ID. One solution could be to use URLs likebrowserext://<extension_id>.<random_token>/<path>whererandom_tokenis generated when the extension is loaded.