5 ms·

Firefox FTW. I was relieved to find this was a Chrome-only problem.

• deleted 6mo ago
  [deleted]
• lxgr 6mo ago
  Turns out Firefox has a similar issue, despite mitigations :( https://bugzilla.mozilla.org/show_bug.cgi?id=1372288 https://bugzilla.mozilla.org/show_bug.cgi?id=1372288
  • eipi10_hn 6mo ago
    This only happens if the extension puts their `moz-extension://` links into the DOM. It's different to chrome case where extensions can be detected regardless of being activated on that site or not.
    • lxgr 6mo ago
      As I understand it, an extension could also leak its links via its own backend, e.g. to advertisers, who could then detect it even though no user-observable DOM modification is happening. Much better than static global IDs, but still not ideal.
      • eipi10_hn 6mo ago
        Yeah, anything happening in backend depends totally on the extensions. Unless I need something, I rarely use extensions that are closed-source or open-source but has some sending data in their features.