You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment: SeaMonkey 2.39, uBlock Origin 1.6.0 (self build from c7f1027 ), new profile
Steps to reproduce:
(shouldn't matter but I'm starting SeaMonkey from command line like: seamonkey -p. I have seen this issue starting SeaMonkey normally though.)
install uBlock Origin, restart SeaMonkey
set as home page, a page that contains an image that should be blocked (for this step, I put the following page up on my local test server and an image at the mentioned path: )
<!doctype html>
<img src="/banners/ads/advertisement.gif" />
<div>image blocked or allowed</div>
restart SeaMonkey
(if re-testing with the same profile, clear cache before restarting SeaMonkey again, to make sure nothing is loaded from cache)
Expected results: image is blocked
Actual results: image appears on screen (it loaded). The image does not get blocked until reloading the page.
(Un-checking "Hide placeholders of blocked elements" makes it easier to see what's going on, but is not necessary to reproduce the problem.)
IIUC this is not technically possible to fix in non-Gecko-based-browsers because there the browser doesn't load extensions until after firing the first network requests, making this moot. However, in Gecko-based browsers the extensions are loaded before any requests are fired, and can have control over these requests.
It is not reasonable to expect that uBlock Origin can finish initializing all its filters before the browser can fire requests, so I would suggest to fix the problem something like this: When "I am an advanced user" is checked, allow the user to choose whether "early" network requests (requests fired before uBlock Origin is finished loading) are allowed or blocked (default to allow, and this setting locked to allow if "I am an advanced user" is un-checked). (Also preferably blocking "early" requests would not be strict-blocked - that is, not blocked unless requested by a document loaded in a browser window/tab. But if top-level documents would have to be blocked as well, it wouldn't end to be a big deal.)
