Bugzilla

I know this is a very contentious issue. However please do consider that the current approach for tracking protection makes it *impossible* for us to implement Livemarks in a sane manner. I really don't understand this desire for keeping this feature that randomly breaks extensions enabled.

Please see https://bugzilla.mozilla.org/show_bug.cgi?id=1502987#c3 for a description of our problem.

I implemented a _very_ targeted fix that allows XHR/fetch to bypass tracking protection for URLs the extension has access to.

I would like to point out that it's possible to bypass tracking protection by hacking your own Cookie header:  https://github.com/evilpie/livemarks/commit/ff996813a6601e0585c5c24d176badc3940ac30e. I am however rejecting this approach as too insane. And we really don't want all users to have to accept a new permission that we really shouldn't have to use anyway.

I know this is a very contentious issue. However please do consider that the current approach for tracking protection makes it *impossible* for us to implement Livemarks in a sane manner. I really don't understand this desire for keeping this feature that randomly breaks extensions enabled.

Please see https://bugzilla.mozilla.org/show_bug.cgi?id=1502987#c3 for a description of our problem.

I implemented a _very_ targeted fix that allows XHR/fetch to bypass tracking protection for URLs the extension has access to.

I would like to point out that it's possible to bypass tracking protection by hacking your own Cookie header:  https://github.com/evilpie/livemarks/commit/ff996813a6601e0585c5c24d176badc3940ac30e. I am however rejecting this approach as too well hacky. And we really don't want all users to have to accept a new permission that we really shouldn't have to use anyway.