Closed
Bug 662200
Opened 14 years ago
Closed 14 years ago
nsISHistory::requestedIndex is not reset after page reload through nsSHistory::Reload
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
FIXED
mozilla8
People
(Reporter: khuey, Assigned: khuey)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(1 file)
1.10 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
Start on page A, navigate to page B, then page C. Click back. Refresh (what is now page B). The navigation buttons will be greyed out when they should not be.
Comment 1•14 years ago
|
||
I couldn't reproduce on a few sites I tried. Can you try a more detailed str?
Assignee | ||
Comment 2•14 years ago
|
||
Are you trying a build with the patch from bug 622315?
Comment 3•14 years ago
|
||
Ah, nope.
Assignee | ||
Comment 4•14 years ago
|
||
Yeah, this is a regression from that. I backed it out since I didn't have any clue how to fix this.
![]() |
||
Comment 5•14 years ago
|
||
So the issue, presumably, is that nothing actually resets the requested index when the navigation completes?
![]() |
||
Comment 6•14 years ago
|
||
Should we be comparing requested index to current index as well, not just to -1?
Assignee | ||
Comment 7•14 years ago
|
||
This fixes this behavior for me and passes the tests in docshell/
I'm going to try to write a mochitest for this behavior.
Attachment #537785 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 8•14 years ago
|
||
(In reply to comment #5)
> So the issue, presumably, is that nothing actually resets the requested
> index when the navigation completes?
Yes, this is correct. The attached patch does that.
(In reply to comment #6)
> Should we be comparing requested index to current index as well, not just to
> -1?
I don't think so. I think we should avoid navigating whenever there is a pending navigation.
Assignee | ||
Updated•14 years ago
|
Summary: Back and then reload results in grayed out navigation buttons → nsISHistory::requestedIndex is not reset after page reload.
![]() |
||
Comment 9•14 years ago
|
||
Comment on attachment 537785 [details] [diff] [review]
Patch
Hrm... Changing this stuff is scary as hell, but ok...
Attachment #537785 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 10•14 years ago
|
||
Yeah, I'm terrified too :-)
Assignee | ||
Comment 11•14 years ago
|
||
So, fun thing, this only occurs if the reload is triggered through nsSHistory. If the reload goes through nsDocShell we do an internal load and never muck with history.
Summary: nsISHistory::requestedIndex is not reset after page reload. → nsISHistory::requestedIndex is not reset after page reload through nsSHistory::Reload
Assignee | ||
Comment 12•14 years ago
|
||
Patch:
http://hg.mozilla.org/projects/cedar/rev/580ddd2f1267
Regression test:
http://hg.mozilla.org/projects/cedar/rev/ea5ed0f2a952
Whiteboard: fixed-in-cedar
Comment 13•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/580ddd2f1267
http://hg.mozilla.org/mozilla-central/rev/ea5ed0f2a952
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: fixed-in-cedar
Target Milestone: --- → mozilla7
Assignee | ||
Comment 14•14 years ago
|
||
This was backed out of Aurora to fix Bug 670318.
http://hg.mozilla.org/releases/mozilla-aurora/rev/cd5b516e9a39
http://hg.mozilla.org/releases/mozilla-aurora/rev/5cf936e830cf
Target Milestone: mozilla7 → mozilla8
You need to log in
before you can comment on or make changes to this bug.
Description
•