486492 - Exceptions -- Images: Sites listed with "status" BLOCK, not always blocked

Status: RESOLVED INCOMPLETE

(Firefox :: Settings UI, defect)

Description

[Chris Markis]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729)

I have listed as many "advertisers" as I can catch in the "Exceptions -- Images" marked as "BLOCK", yet many of them are still getting through.  Some of them are downright un-acceptable in my viewpoint.  Yet I have no way to "block" them with your product.

Reproducible: Always

Steps to Reproduce:
1.  Place "ad" sites in Exceptions -- Images" with "BLOCK", yet obnoxious ads still showing up from those sites.
2.
3.

Comment 1

[Chris Markis]

ad.yieldmanager.com
adq.nextag.com
doubleclick.net
doubleclick.com
2of7.com
adserver.yahoo.com
advertising.com
hitbox.com
atdmt.com

Comment 2

[Matthias Versen [:Matti]]

Example URL ?
Your steps to reproduce are incomplete, please post the complete steps.
That means every single step like 1) open http://www.example.com 2) right click on the top left image and select "block image" .......

BTW: You know about the adblockplus addon ?

Comment 3

[Tyler Downer [He/Him]]

This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.