Closed
Bug 298112
Opened 19 years ago
Closed 19 years ago
Failure to repaint with bfcache
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dpoon, Assigned: bryner)
References
Details
Attachments
(1 file)
653 bytes,
patch
|
darin.moz
:
review+
dbaron
:
superreview+
asa
:
approval1.8b3+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050617 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050617 Firefox/1.0+ With the fast back-forward cache enabled, pages don't repaint when going back. Reproducible: Always Steps to Reproduce: 1. In about:config, set browser.sessionhistory.max_viewers to 5 as suggested, and restart Deer Park. 2. View one page ("Page 1"). 3. Navigate to another page ("Page 2"). 4. Click the Back button. Actual Results: The address bar changes to that of Page 1, but the content window remains on Page 2. By using the keyboard to scroll, the newly revealed part repaints, resulting in a view that is partly Page 1 and partly Page 2. Using the build advertised on Asa's blog: http://weblogs.mozillazine.org/asa/archives/008353.html The 20050531 build does not have this problem. No extensions installed.
Comment 1•19 years ago
|
||
I just reported this on <http://weblogs.mozillazine.org/josh/archives/2005/06/firefox_mac_bui.html> It works fine with the normal 20050618-nightly, but not with Josh experimental build (see bug 282940).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•19 years ago
|
Blocks: blazinglyfastback
Assignee | ||
Comment 2•19 years ago
|
||
We put content viewer destruction off on a plevent, which means that the Hide() may not happen now until after we invalidate. Make the Hide() part synchronous so that the right things get painted. This is a regression from bug 294231.
Attachment #187070 -
Flags: superreview?(dbaron)
Attachment #187070 -
Flags: review?(dbaron)
Comment 3•19 years ago
|
||
Comment on attachment 187070 [details] [diff] [review] patch hiding the content viewer up front, while still deferring its destruction, seems reasonable to me. r=darin unfortunately, i don't know content viewer well enough, so i'd still recommend getting a review from dbaron, boris, or someone :)
Attachment #187070 -
Flags: review?(dbaron) → review+
Assignee | ||
Comment 4•19 years ago
|
||
Comment on attachment 187070 [details] [diff] [review] patch requesting approval, pretty safe fastback fix
Attachment #187070 -
Flags: approval1.8b3?
Attachment #187070 -
Flags: superreview?(dbaron) → superreview+
sr=dbaron, but maybe you should remove the Hide call from DocumentViewerImpl::Destroy?
Updated•19 years ago
|
Attachment #187070 -
Flags: approval1.8b3? → approval1.8b3+
Assignee | ||
Comment 6•19 years ago
|
||
Maybe... it's a good thing to make sure of though so I think I'll leave it for now (perhaps clean it up when we clean up docviewer teardown as described in bug 297991). Checked in.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
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
•