Don't alert user about unregistered protocols for iframes

NEW
Unassigned

Status

()

Core
Networking
P5
normal
13 years ago
4 months ago

People

(Reporter: boogs, Unassigned)

Tracking

(Depends on: 1 bug, {testcase})

Trunk
x86
Windows XP
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-would-take], URL)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414

Hi,

I recently noticed that Mozilla, upon encountering an iframe where the src URL
uses an unknown protocol, pops up a window alerting the user that "... is not a
registered protocol".

Considering that the user did not type in the URL themselves, I think this
shouldn't be done - it's both annoying and confusing.


Reproducible: Always

Steps to Reproduce:
1. Go to example URL mentioned above, which has " ttp" instead of "http" as the
protocol for the embedded iframe

Actual Results:  
Mozilla pops up an alert notifying the user that "ttp is not a registered protocol".

Expected Results:  
Mozilla should silently ignore the error; another alternative would be to
display a "broken iframe" icon, similar to the one used for broken images, in
order to point out the error in an unobtrusive way.

Comment 1

13 years ago
This would be fixed with error pages being turned on.

Comment 2

13 years ago
(In reply to comment #1)
> This would be fixed with error pages being turned on.

See Bug 28586. Look for duplicates under the dependent bugs.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED

Comment 5

10 years ago
This bug still exists (Mac trunk)
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---

Comment 6

10 years ago
data:text/html,<iframe src="bogus:">
Assignee: general → nobody
Status: UNCONFIRMED → NEW
Component: General → Networking
Ever confirmed: true
Keywords: testcase
Product: Mozilla Application Suite → Core
QA Contact: general → networking
Version: unspecified → Trunk

Comment 7

7 years ago
See also bug 167475.
Whiteboard: [necko-would-take]
You need to log in before you can comment on or make changes to this bug.