News for hackers. Stuff that matters.
Re:A JavaScript browser library fails due to an adblocker bl... by gorhill on Sunday July 09, 2017 @09:55AM (#14729744)
I'm puzzled. Content blocking extensions can't interfere with your extension's internals, and can't interfere with network requests made by another extension.

If your extension injects resources in the DOM, than a content blocker can interfere with the proper loading or rendering of these resources.

However I am very surprised about your statement that a content blocker extension intefered with your extension assets, my understanding is that should not be possible. You mind disclosing what is your extension?

Re:A JavaScript browser library fails due to an adblocker bl... by kevingadd on Sunday July 09, 2017 @10:25PM (#14732989)
Most Chrome extensions need to interact with content, so if you want to do that you have to run code inside the content context. Adblockers can intercept any requests you make, even if it's to extension content (i.e. not over the internet, not to an ad/tracking server). This goes so far that they will silently block attempts to open a popup window (in this case, in a click handler to open extension-specific UI for the user.)

The content was under chrome-extension:// and was just an html file. Incidentally I use ublock. I'd be happy to help you troubleshoot this if it's possible to fix the issue.

Re:A JavaScript browser library fails due to an adblocker bl... by nsgi on Sunday July 09, 2017 @05:36PM (#14731809)
You can't inject a content script into another extension's page but the last time I used it the webRequest API could intercept internal requests, including those from extensions. Although they're planning to crack down on e.g. extensions redirecting search requests from the new tab page and the omnibox.