Closed
Bug 230712
Opened 22 years ago
Closed 22 years ago
location information gets cleared if domain not found and command-r is then used
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 191145
People
(Reporter: jon, Assigned: mikepinkerton)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040107 Camino/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040107 Camino/0.7+
location information gets cleared if domain not found and command-r is then used
Reproducible: Always
Steps to Reproduce:
1. type a valid url into the location bar, however, use a domain which won't be
found.
2. a message will come up saying "domain could not be found. Please check the
name and try again."
3. click ok
4. then hit command-r (reload) and the location bar will clear out.
Actual Results:
the location field is cleared out.
Expected Results:
it should attempt to reload the domain. this would be the same behavior as
clicking the reload button in the UI.
Clicking the reload button also doesn't reload the page.
Camino just told you that the domain could not be found. So hitting reload has
no function what so ever, since the domain wasn't there. In stead camino tells
you to check the name and try again, but since you didn't why would camino tell
you the same thing again?
Perhaps Camino is to harsh and should allow the user to hit reload every time!
But I don't know.
Reporter | ||
Comment 2•22 years ago
|
||
I don't think it should clear the value of the location field.
The reason is that clearing it out prevents you from being able to fix things
like a small typo mistake in the URI.
Assignee | ||
Comment 3•22 years ago
|
||
this is a dupe of another bug, i'm certain.
Reporter | ||
Comment 4•22 years ago
|
||
found the duplicate...would be nice to have a fix made. =)
*** This bug has been marked as a duplicate of 191145 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•