Closed
Bug 210866
Opened 22 years ago
Closed 22 years ago
error pages issues, can't go back, address bar goes to horrible long string....
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 157004
People
(Reporter: irchs, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030626 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030626 Mozilla Firebird/0.6
When you visit a non-existent domain, such as www.wraaaaaaaaaaaa.com with
Firebird with the following setting enabled:
browser.xul.error_pages.enabled ENABLED
You get a nice error message within a page like IE does. But, once you have got
this page, the back button becomes disabled, and when you refresh the page, the
last page you visited comes up. Also, it would be nice if the address that
failed remained in the address bar, instead of the garbled nonsense that looks a
little like this:
chrome://global/content/netError.xhtml?e=dnsNotFound&u=http%3A//www.wraaaaaaaa.com/&d=www.wraaaaaaaa.com%20could%20not%20be%20found.%20Please%20check%20the%20name%20and%20try%20again.
Obviously that can't be refreshed :) If the domain was down for a bit say, it
would be nice to refresh every few seconds until it came back up :)
Reproducible: Always
Steps to Reproduce:
1. browser.xul.error_pages.enabled to enabled
2. Go to www.wraaaaaaaa.com
Actual Results:
Back button was disabled, URL in address bar becomes garbled mess that can't be
refreshed to try the address again.
Expected Results:
I should be able to press back and go to the page I was browsing before hand,
and I should have been able to refresh and the page. It would also have been
nice if the browser could keep the URL that failed in the address bar.
Comment 1•22 years ago
|
||
this is a duplicate of bug 157004
Comment 2•22 years ago
|
||
*** This bug has been marked as a duplicate of 157004 ***
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
•