When you click back to a page that is cached, you shouldn't have the jarring effect of a paint, then a scroll - it should just appear at the right place
<rdar://problem/5204291>
When the page your going back to actually is in the cache, we're fine. The real bug here is when going back to a noncached page, and the page is reconstructed from cached resources. Our engine is so fast that sometimes these types of navigation might be confused for cached pages and therefore the jarring scroll change seems super bizzare. So basically I think the real issue is the jarring way in which scroll happens when you go back to a page that *isn't* cached. When the page goes through the loading mechanism the "normal way" and resources are pulled from the memory cache, disk cache, and even over the network, we do eventually restore the scroll position. Twice, in fact. At horrible times - after the first layout and after the load is complete. These are really silly times to be doing this. We should scroll to the position in the document the moment that position exists. Scrolling really has nothing to do with loading. Darin had this idea - and I think it's perfect with some small refinements - which is that the FrameLoader tells the FrameView "Hey, this is your cached scroll position. Scroll to this point the moment it actual exists in the document". Then when the load is complete, FrameLoader tells the view "Okay, we're done loading. So if you haven't already scrolled to that position, don't do it anymore" This should be reasonably easy to do.
*** Bug 75501 has been marked as a duplicate of this bug. ***