Closed
Bug 269693
Opened 20 years ago
Closed 20 years ago
Back button disabled when there is an error page displayed
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 226401
People
(Reporter: spooky, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 I am using the option browser.xul.error_pages.enabled set to true. I am browsing and when I click or type an invalid address or any page that can not be displayed, I can not go back. The error page is displayed and the back button is inactive. Although I am able to go back from the mouse... and it jumps 2 pages back instead of one. The I click forward to return to original page. Sometimes it works just fine, sometimes is not working fine. Sometimes is working on new tabes. Sometimes is not working on new tabs. A Reproducible: Sometimes Steps to Reproduce: 1. Open browser, go to a page. 2. Type an invalid address. Error page opens. 3. Back button is disabled. You can not go back. You can go back from mouse's back button.
Comment 1•20 years ago
|
||
Confirmed for: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0 Reproducible: Sometimes Steps to Reproduce: 1. Open about:config. Toggle this option to true: browser.xul.error_pages.enabled 2. Open http://www.google.com 3. Open http://www.mozilla.org in the same tab 4. Open http://www.sahdasjdhajskdasdksakdaskjde.com (random URL ;) ) 5. Observe all kind of weird things happening to the function of the back button. It sometimes is dissabled, sometimes it will work correctly and sometimes it will go back two pages.
Comment 2•20 years ago
|
||
Duplicate of bug 226401?
Comment 3•20 years ago
|
||
(In reply to comment #2) > Duplicate of bug 226401? > Yes, it is. *** This bug has been marked as a duplicate of 226401 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•