150325 - [RFE]Add ability to block images that are links to sites

Status: NEW

(Core :: Graphics: Image Blocking, enhancement)

Description

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

It would be nice to block images that are links to ad.doubleclick.net but not
hosted on ad.doubleclick.net.  Could this feature be added?

Comment 1

[Boris Zbarsky [:bzbarsky]]

This can already be done:

a[href*="ad.doubleclick.net"] img { display: none}

in userContent.css

Comment 2

[Arno Roefs]

Would be nice to be able to set this in the preferences in an easy way.

Comment 3

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

I cannot find that file anywhere on my hard drive.  Do I have to create it myself?

Comment 4

[Boris Zbarsky [:bzbarsky]]

Yeah, you want to take userContent-example.css, rename it to userContent.css and
then edit it.

Comment 5

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

I assume the fact that this isn't closed means that someone is working on adding
an option in the prefs page?

Comment 6

[Boris Zbarsky [:bzbarsky]]

That's what the "assigned" part means, yes.

Comment 7

[Michael Lefevre]

*** Bug 142054 has been marked as a duplicate of this bug. ***

Comment 8

[Stephen P. Morse]

I was going to ask for an example of this, but I see there is an example in the 
dup bug 142054.

Using that example, I go to http://www.wunderground.com/US/MA/Boston.html and I 
see the four boxes at the bottom.  I right-click on one of those boxes and I 
select block-images-from-this-site from the context menu.  Then I reload the 
page.  The box that I clicked on does not display.

So it seems to me that we have what you are asking for.  Therefore closing this 
out as WFM.  If I'm misinterpreting something here, then please reopen and give 
an explicit example (including URL and set of steps) for demonstrating the 
problem.

Comment 9

[Jesse Ruderman]

*** Bug 167630 has been marked as a duplicate of this bug. ***

Comment 10

[Kostub]

In this bug you want to block images depending on which site they link to and
not depending on which site they are hosted from. Even though you have given a
way to do this by modifying the userContent.css file, there is no UI component
in Mozilla which allows you to do it. When I right click on an image I would
like to see the option:
Block Images that Link to this server.

This would get rid of the problem at
http://www.wunderground.com/US/MA/Boston.html
Clicking each image and disabling it from the server works. But it does not
disable all images linking to server.as5000.com

Comment 11

[Asa Dotzler [:asa]]

*** Bug 176913 has been marked as a duplicate of this bug. ***

Comment 12

[Eli Dourado]

This bug should NOT be marked resolved.  Kostub is right on.  This should be an
option in the context menu whenever you right-click a linked image.

Comment 13

[Tom Everingham]

reopening per comment# 10

Comment 14

[Mitchell Stoltz (not reading bugmail)]

Mass reassigning of Image manager bugs to [e-mail], and futuring.
Most of these bugs are enhancement requests or are otherwise low priority at
this time.

Comment 15

[Michiel van Leeuwen (email: mvl+moz@)]

*** Bug 183250 has been marked as a duplicate of this bug. ***

Comment 16

[Mitchell Stoltz (not reading bugmail)]

Is adding this feature worth the added bloat and complexity? I'm not sure. AN
implementation would help, so if anyon'es interested in having a go at this, go
ahead. I won't be working on it anytime soon.

Comment 17

[Evert Verhellen]

I stumbled across this one as I asked on #mozillazine whether Mozilla is able to
block images that link to an external site. The discussion so far seems to
suggest having an external site list. I think this adds unnecessary complexity
to both the UI and to the way people will have to use this feature. Can't we
just have an additional image acceptance policy `Do not load any images that
link to an external site' instead? Doing so would provide a very effective
mechanism to work around the advertisement workaround widely in use today. The
availability of this feature would probably also obsolete bug 78104 which, in
essence, pursues a similar objective as this bug.