Closed Bug 160548 Opened 22 years ago Closed 22 years ago

network error pages losing previous page in history

Categories

(Core :: DOM: Navigation, defect)

defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 157004

People

(Reporter: jmd, Assigned: adamlock)

References

Details

Steps to reproduce:
  Linux 2002073108.
  I enabled error pages (bug 28586)
  I was reading an article as the first item in session history.
  I middle-clicked to paste in something I wanted to search for.
  Got the malformed URL error page.
  Wanted to go back to page with info on it that I still needed.
  Observe back button and menu item greyed out.

Luckily, the old page was still at the bottom of the 'Go' menu, and selecting it
worked properly. The item was still bulleted as if I was there currently.

Expected: back button and menu item are enabled. Go menu shows previous sites,
but none are bulleted.
I wanted to repeat what I've said in bug 157004:

IMHO, while the error page URL should not be in the history, the *original* URL
that caused the error *should* be in history. This should take care of
"advancing" correctly and this should make it possible to come back later to a
page that fails to load and to try loading it again. This also should work in a
way such that pressing "reload" on an error page would re-try the original page.

P.S. BTW, what I describe is the behaviour that you get when using a proxy
(Squid, for example) that would just report all the errors as the error page
(but will still keep the original URL). It works really nice with history,
"reload", etc and I think Mozilla should act the same way.
Workaround for this bug: Hit reload.

BTW, the behavior described by Aleksey in comment 1 was also described by mpt
when he filed bug 28586: "for example, after browsing elsewhere for 
a while I can use the Back menu to come back to the error page, and then click 
Reload to have another go at connecting"
Blocks: errorpages
Yes, that would make much more sense... whose bright idea was it to go through
all this trouble removing the pages from history in the first place? Doesn't IE
store it in session history? It should be in global too, actually.

If I learn about site foo.com, it's down today, and I want to retry tomarrow, I
should be able to find it in my history.
> Doesn't IE store it in session history?

Yes, it does.
OS: Linux → All
Hardware: PC → All
Dupe of bug 157004

*** This bug has been marked as a duplicate of 157004 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
adamlock, I do not think that this is a dup. This one is about the _previous_
URL being overwritten, while that one is about the url with the error being
overwritten... afaict.

can you please clarify and reopen if necessary?
The issue is that the url shouldn't be seen and shouldn't interfere with session
history or the back/forward buttons. These are all things that I intend to fix
in bug 157004 so therefore it doesn't need another open bug.
*** Bug 254288 has been marked as a duplicate of this bug. ***
No longer blocks: errorpages
You need to log in before you can comment on or make changes to this bug.