Has there been a follow-up to the CSP issue in Firefox where extensions might interfere with each other?
https://www.reddit.com/r/firefox/comments/btvixo/firefox_bug_causes_addons_ublock_origin_https/
I was planning to use uBO, uM, and CanvasBlocker in unison. For CB, I think I can uncheck "block data URL", but will there still be issues when uBO and uM are used together? And what could be a possible workaround?
Posted Oct 23, 2019, 11:30 AM UTC
2414
No change - https://bugzilla.mozilla.org/show_bug.cgi?id=1462989
That's unfortunate. What would you suggest for users that use both uBO and uM?
Make CSP injections via uBO only, so to avoid triggering the issue.
So that would mean disabling inline JS blocking and service worker blocking on uM? Leaving uM and uBO to be usable conflict-free after that?
Yes, to summarise -- Just avoid blocking first-party css, script and don't use forbid web-workers switch via uMatrix and the issue will not trigger.
I'm using uBO with HTTPS Everywhere and Canvas Blocker. I have never noticed any issues. Should I remove some of them? Are there actually issues I don't know about?
This is one - https://github.com/kkapsner/CanvasBlocker/issues/214