345719 - Popup blocker fails two tests on PopupTest

Status: RESOLVED DUPLICATE of bug 246453

(Firefox :: General, defect)

Description

[Maury Markowitz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060721 Minefield/3.0a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060721 Minefield/3.0a1

Both of the URLs above:

http://popuptest.com/popuptest6.html
http://popuptest.com/popuptest8.html

fail to be blocked by Minefield (a1). The good news is that it passes all of the other tests.


Reproducible: Always




This is a great site for quick testing of the popup blocker. You may want to distribute this URL widely among the development team:

http://popuptest.com/?

Comment 1

[Ria Klaassen (not reading all bugmail)]

If you add 
#AdFloater { display: none !important}
#DropIn {display: none !important}
to userContent.css, they both stay away. The only advantage is, that it passes this test now :).

Comment 2

[Brian Polidoro]

The pop-up blocker blocks pop-up windows.  Neither of these are windows.  One is a span and the other is a div.  Both are part of the page. 

Comment 3

[Maury Markowitz]

Brian, don't take this the wrong way, but that's missing the forest for the trees.

"pop-up" is a generic term used to describe any annoying moving adware, of which there are many varieties. Some use JS to popup a dialog-like box, others use Flash or other plugins, and still others use DIV or SPANs to do basically the same thing. Users want them all blocked. Period.

Claiming this report is "invalid" based on what is essentially semantics seems rather suspect. Given that there appears to be a technological solution, blocking SPANs and DIVs that point to out-of-domain content, I think this should remain on the list somewhere.

Comment 4

[Brian Polidoro]

Well there's bug 217013 for one example.  But I suppose using bug 246453 is a better example because it leads to an open bug.

*** This bug has been marked as a duplicate of 246453 ***