Closed kheina closed 1 year ago
it looks like adding support on chrome is fairly straight forward, just needed to add logic to retry the various elements injected into the twitter page (request hijacking, toasts div, stylesheet for toasts).
firefox on the other hand appears to have additional isolation between extensions that chrome doesn't have. it seems like chrome routes requests made by content scripts through the web page's own XMLHttpRequest.prototype
, which allows blue blocker to see these requests and parse them. firefox, however, does not.
this is backed up by the xhr list in the developer console literally being empty while running old twitter:
unless there's another way to read requests from other addon's content scripts, old twitter will need to send content payloads to blue blocker for parsing in order for blue blocker to work
it seems like I was mistaken, blue blocker also doesn't work on chrome with old twitter. the requests I'm seeing are those made by the new twitter code running behind the old twitter extension. it appears any requests made by content scripts that are not owned by your extension are invisible to other extensions
closing this in favor of #185, so that people aren't confused by my investigatory comments
from an email I received: