Closed
Bug 16704
Opened 25 years ago
Closed 25 years ago
[DOGFOOD] go-back broken
Categories
(SeaMonkey :: UI Design, defect, P2)
Tracking
(Not tracked)
M11
People
(Reporter: warrensomebody, Assigned: radha)
References
()
Details
(Whiteboard: [PDT+])
I've noticed that the go-back button gets confused (or history gets confused or
something) from time to time. I notice this quite often. Start on the
mozilla.org page, then go to the travelocity home page, above. If you click on
the Find/Book A Flight button, then go back (try this several times), sometimes
you'll end up back at the mozilla.org page instead of the travelocity home
page. If you go forward at this point, you'll be able to jump from
www.mozilla.org to the travelocity login page, without the travelocity home
page inbetween.
Reporter | ||
Updated•25 years ago
|
Summary: go-back broken → [dogfood] go-back broken
Comment 1•25 years ago
|
||
Reproduced with 1999-10-17-08-M11 on WinNT 4.0sp3
Comments: I've seen this many times before but didn't know how to
characterise it. The same double-go-back can bee seen in some
circumstances moving among bugzilla pages. Comparing bugzilla and
travelocity the common element that comes to mind is HTTP 301 and/or
302 response codes. If the history-stack code is remembering that
the browser took two steps forward, but elides the intermediate page
from the stack, two steps back would be one step too far.
Component: Browser-General → XPApps
Priority: P3 → P2
Summary: [dogfood] go-back broken → [DOGFOOD] go-back broken
Target Milestone: M11
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Assignee | ||
Comment 3•25 years ago
|
||
This is a dup of 16782 ( the post data problem) instead of 17430.
*** This bug has been marked as a duplicate of 16782 ***
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•