292460 - Highlight parse errors in navigation bar URLs

Status: RESOLVED EXPIRED

(Firefox :: Address Bar, enhancement)

Description

[Jim Walters]

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

When an invalid URL is entered in the navigation bar (for example,
"http://www.google. com") an Alert pops up and says the URL is not valid and
cannot be loaded. It may be helpful to indicate where the parse error is in the
navigationbar.

Reproducible: Always

Steps to Reproduce:
1. Navigate to "http://www.google. com"


Actual Results:  
Invalid URL alert displays. No indication of where the parse failed in the URL
displayed in the navigation bar.

Expected Results:  
Highlight, insofar as possible, where the parse error occurred.

Comment 1

[Nickolay_Ponomarev]

How do you define "parsing error"? The dialog doesn't indicate a parsing error
but a DNS error, i.e. that DNS lookup for "www.google" site failed.

Comment 2

[Jim Walters]

(In reply to comment #1)
> How do you define "parsing error"?

When I put in "www.google.c om" I get the alert "The URL is not valid and cannot
b e loaded". When I put in "www.googe.caom" I get the alert "www.google.caom
could not be found. Please check the name and try again." There seems to be a
difference.

Comment 3

[Nickolay_Ponomarev]

Hm, right. It's hard to type a malformed URL though, that's why I never noticed
this. Doesn't seem like something that's worth the effort of implementing it IMHO.

Comment 4

[Gervase Markham [:gerv]]

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/

Comment 5

[Gervase Markham [:gerv]]

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.