Closed Bug 143750 Opened 22 years ago Closed 22 years ago

Annoying alerts for inline content <IFRAME>

Categories

(Core :: DOM: Navigation, defect)

x86
Linux
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 196120

People

(Reporter: trevin, Assigned: Matti)

References

()

Details

I have blocked several domains' http port using ipchains in order to reduce the clutter in sites that I visit. Under NS Communicator, this resulted in pages having a few broken-image icons lying around; I could navigate through the rest of the site without any problem. With mozilla, however, viewing the same site results in a pop-up alert telling me (for example): "The connection was refused when attempting to contact ad.doubleclick.net." I have to dismiss the dialog before proceeding on each page where this shows up. I'd like to suggest that alerts be disabled for inline images and other embedded content. At the very least, add an option for turning alerts off in this case.
Forgive me; I believe I was incorrect in my original assumption that mozilla was showing an alert for images. On inspection of the HTML source for the subject web site, it looks like it's trying to access ad.doubleclick.net in an IFRAME or LAYER besides (in addition to?) an IMG, and that's from a javascript segment. The alert is still annoying, though.
Component: Image Blocking → Browser-General
Summary: Annoying alerts for inline images → Annoying alerts for inline content
reassigning to corrected component.
Assignee: morse → Matti
QA Contact: tever → imajes-qa
This will be fixed with bug 132031 *** This bug has been marked as a duplicate of 132031 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
REOPEN: the "opup" mentioned here was a necko error, not a pop-up ad.
Status: RESOLVED → UNCONFIRMED
Component: Browser-General → Embedding: Docshell
Resolution: DUPLICATE → ---
Summary: Annoying alerts for inline content → Annoying alerts for inline content <IFRAME>
*** This bug has been marked as a duplicate of 196120 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
I know, I duped it to the wrong bug#. This should be a dupe of the error-pages bug but this is now fixed in a docshell.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.