184012 - blocked images are not blocked

Status: RESOLVED INVALID

(Core :: Graphics: Image Blocking, defect)

Description

[Michael K]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130

blocked images at this site are not blocked - even though Mozilla says they are.

Reproducible: Always

Steps to Reproduce:
1.set mozilla to "block images from this site".
2.
3.

Actual Results:  
images still appear.

Expected Results:  
blocked the images.

BTW there is BUG 183250, among others that ARE OPEN ON THIS SAME PROBLEM - Why
don't you Mozilla-ites purge the system if there are duplicate
bugs???????????????????

If they are open - fix them!  If they are duplicates, add relivant data from
newest to oldest, and DELETE newest.  If they are UNABLE TO BE CORRECTED, SAY SO!

Thanks.

Comment 1

[Matthias Versen [:Matti]]

.

Comment 2

[Sander]

If you do tools -> block images from server, all mail.com images will be
blocked. However, the mail.com page instead uses images stored at
http://img1.us4.outblaze.com/ - so those won't be blocked.
If on the other hand you right-click, block images from server and then reload
the page, you will notice that images are now indeed blocked.

-> INVALID

Comment 3

[Michael K]

Thanks - maybe a more novice like instructional approach on the blocked image
window pane (where the list of blocked images are displayed) may be added: 
"Confirm images are not on a remote server or you may need to right-click, block
images from server, and then reload the page."

Just a suggestion

THANKS

MRK

Comment 4

[Michael K]

OK, but you mean to select each individual inage an then block it manually.  A
slow workaround, I agree, but can't some kind of thing be done at the Mozilla
level to do the same thing?? - (we are lazy users)  

May I reopen just to get this question answered?

also - just a comment - anyone there have a mail.com account - there is ALWAYS a
pop-up that appears when you actually get to your message window, upper left. 
Here is the properties (!) of one of them - can it be just blocked or is it
bypassing Mozilla's built in pop-up blocker???
http://view.atdmt.com/AVE/iview/xctdvaws06900004ave/direct;wi.250;hi.250/01?click=http://oas-central.realmedia.com/RealMedia/ads/click_lx.ads/mail.com/popup/1253181503/x02/ExactAdv/ATT_IO738_0325_250/att.html/33663431626633303364663336656130?

Thanks
MRK

Comment 5

[Michael K]

OK, but you mean to select each individual inage an then block it manually.  A
slow workaround, I agree, but can't some kind of thing be done at the Mozilla
level to do the same thing?? - (we are lazy users)  

May I reopen just to get this question answered?

also - just a comment - anyone there have a mail.com account - there is ALWAYS a
pop-up that appears when you actually get to your message window, upper left. 
Here is the properties (!) of one of them - can it be just blocked or is it
bypassing Mozilla's built in pop-up blocker???
http://view.atdmt.com/AVE/iview/xctdvaws06900004ave/direct;wi.250;hi.250/01?click=http://oas-central.realmedia.com/RealMedia/ads/click_lx.ads/mail.com/popup/1253181503/x02/ExactAdv/ATT_IO738_0325_250/att.html/33663431626633303364663336656130?

Thanks
MRK

Comment 6

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Reassigning unconfirmed image blocking bugs to the new owner

Comment 7

[Michael K]

Any new information - In the latest Mozilla there is a pop up blocker feature,
but it seems to have too many options to make any sense - I just "prevent
scripts from opening new windows" and yet this STILL OPENS A NEW WINDOW.

Comment 8

[Andreas Kunz]

First, Michael, please read the bug submission guidelines on
http://www.mozilla.org/quality/bug-writing-guidelines.html.
Especially the part about severity might be interesting for you (also given the
other bugs you filed) as might be the fact that there should only be ONE problem
mentioned per bug report and that bugzilla is not a support system or helpdesk,
but a developers tool.

Blocked images ARE blocked, so this is not a bug.
-> INVALID

Re comment #4: You don't have to right-click every image you want to be blocked.
Mozilla currently blocks images per-server, so if you block an image from an
advertising server, you'll not see an image from that server again, wherever you
surf.
And many sites contain images from their own site, images you want to see
because they belong to the user interface or articles, and they contain ads from
ad servers. So Mozilla makes it possible to selectively block only the
advertising images which should make you happy. The trick is to find out which
images come from which server. Bug 93390 is about showing the name of the server
to make that easier.

Blocking ALL images on a page is more often a bad idea than not. And I rarely
encounter pages that contain images from more than 2 or 3 ad servers. And I have
already so many ad servers blocked that I don't see that many ads...

The popup things really don't belong in this bug.
But FYI: there are several bugs about how pages try to circumvent popup
blocking: bug 126224, bug 144726, bug 173016, bug 176079, bug 187255.
Websites will always search and find ways to still open a popup. As long as the
popup blocker blocks most popups I consider it doing its work. Just switch back
to IE after using Mozilla for some weeks and you'll see what I mean.

Comment 9

[Michael K]

Andreas, 
Regarding "First, Michael, please read the bug submission guidelines
on...Especially the part about severity might be interesting for you (also given
the other bugs you filed) .... bugzilla is not a support system or helpdesk,but
a developers tool."  

I am sorry - I am TRYING to HELP.  Since there is no evident helpdesk (am I
correct???) and I have no intention of spamming the system here, I am sorry I
seem annoying.but to me, and in my interpretation of the categories, severity
relates not only to the entire platform, but all the way down to the specific
effect on the little serf-peon using the tool.  Something that doesn't work as
described, or is confusing to implement(therefore non functional) is to me
severe.  I WILL redefine my opinions, and correct any future submissions
accordingly, but I wanted my rationalle to be made.  

"The popup things really don't belong in this bug."
I agree and I am wrong.  I apologise...

Thanks

Comment 10

[Andreas Kunz]

> Since there is no evident helpdesk (am I correct???)

That's exactly right. As you can read on the mozilla.org homepage: "Mozilla.org
provides binaries for testing and feedback." Mozilla is not an end user
distribution with full support. Try Netscape if you want support.

I acknowledge that you try to help, but be reminded that every minute a
developer has to explain in bugzilla how a feature works is a minute during that
he cannot make Mozilla better.


> Something that doesn't work as described, or is confusing to 
> implement(therefore non functional) is to me severe.

According to this definition every bug is 'severe' because it makes something
not work as expected.

In bugzilla bugs are classified in - if you want it like this - 'more severe' or
'less severe' named "blocker" down to "trivial".

As you can read on the bug submission page, "major" means: "a major feature is
broken" - which is a) not true in this case, nothing is broken here (ok, you
didn't know that, but it still costed time and nerves) and b) image blocking is
not exactly a major feature of Mozilla (as opposed to writing mails or something).
"critical" (which you used in bug 196938) means "Mozilla crashes, hangs or
causes you to loose data". Try to decide yourself if this was appropriate...