Closed
Bug 303311
Opened 19 years ago
Closed 19 years ago
forward navigation does not change visible document until window resize
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: tuukka.tolvanen, Unassigned)
References
Details
firefox gtk2 trunk cvs 20050730
This bug is just a vague and probably redundant collection of hints, since I
can't reproduce the issue reliably. I think it appeared around when fastback
did, so I'll try blaming that.
Firefox sometimes (once a week or so) gets into a state where clicking on a link
seems to load the new page: url bar and window and tab title may get updated.
However, the content area keeps displaying the old document, scrollable and all.
Resizing the window causes the document to be changed to the newly loaded one.
E.g. reload does not do the trick.
Going back goes to the previous page (i.e. still visible page) ok. Going forward
after back shows a blank content area filled with the window background color.
Sometimes opening a link in a new tab and switching to it yields a blank content
area with the window background color. Tabbing into it turns it dark grey
(looked like text selection color, _maybe_). The content is one tab index only,
while the document that showed up after resize had several tabbable links.
Not every load does this, roughly almost every other load switches doc ok in the
broken state. Can fail, or succeed, with either POST or GET. The brokenness
applies to new windows as well.
The broken state might have been triggered last time by a bunch of quickly
consecutive externally triggered loads from thunderbird, but that might be
coincidence.
This could be somewhat the same as bug 301354, I can run in this state for a
long time without seeing any crashes. I vaguely recall that I might have seen a
tab in a state where the old page pixels are still displayed, but the doc
underneath for things like hover cursors and stuff is the old doc. Or the other
way around. Couldn't get it to this state just now, though. That might look like
the doc is click-dead because it doesn't respond to clicks where you'd expect.
Reporter | ||
Comment 1•19 years ago
|
||
I haven't seen this (using trunk) for quite a while, marking wfm. If someone is still seeing this issue, please reopen with version info.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•