[Webkit-unassigned] [Bug 13892] Page reload behavior different from Gecko

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Sep 11 02:22:39 PDT 2007


------- Comment #18 from mrowe at apple.com  2007-09-11 02:22 PDT -------
In my testing, Camino *does* jump back to the top of both
http://news.bbc.co.uk/1/hi/scotland/edinburgh_and_east/6988616.stm and
http://bugs.webkit.org/show_bug.cgi?id=13892 when refreshing.  I'm pretty sure
that it's dependent of the timing of layout + painting in relation to the
loading of the data for the page.  If the page is first displayed before enough
content to reach the old scroll position has been loaded, then you see the page
scrolled to the top, and then to the correct position once things are done
loading.  It may just be that my network connection has slightly higher
latency, so Camino decides to render the partial content when less data has
been received.  Either way, as far as I can tell WebKit and Gecko behave very
similarly on this point.

As mentioned, restoration of the scroll position is a different issue than the
original bug report.  The original bug report addresses what reload means in
terms of which resources should be fetched from the network or cache.  I would
much prefer that this is split off into a new bug report before it gets too
cluttered with information about a different issue.  Putting everything that is
in some way related to reloading in this bug would make it nearly impossible to
decide when this bug can be marked as resolved.

Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list