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

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=13892


hyatt at apple.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Page refreshes cause FOUC   |Page reload behavior
                   |compared to a Gecko refresh |different from Gecko




------- Comment #2 from hyatt at apple.com  2007-05-27 15:21 PDT -------
This isn't really FOUC.  This is just normal page loading.  Gecko and WebKit
both look pretty ugly on a fresh load of the page.  Gecko doesn't look ugly on
refresh, but that's because its refresh is incomplete.  You have to hit
Shift+Reload to get a real refresh in Gecko.

The problem with Gecko's approach is that refreshes can be incomplete, and
people have to discover the secret Shift modifier key in order to get real
refreshes.  To avoid this problem we just treat all refreshes as full.  This
results in a slower refresh than Gecko, but also in a refresh that is never
incomplete or wrong.


------- Comment #3 from akwb at msn.com  2007-05-27 16:07 PDT -------
Thanks for your replies. Is it your view that although a "normal" refresh in
Gecko ends up loading items such as images from a the cache that in the vast
majority of refresh situations this wouldn't be an issue and would result in
much improved refresh performance (if only perceived)? It is my opinion that
the behaviour of refresh should be aimed at making the perceived speed of
Webkit greater than all others (a main Webkit goal) and loading items from
cache clearly aids this aim. I'm not sure really if the goal of Webkit is to be
the fastest rendering engine from a "statistical" or a "perceived" pov (both
would be nice!)?

I don't mind if this bug report turns into a bit of a scratch pad to help
improve the way Webkit refreshes/reloads pages. For example Opera allows for
the user to specify a time limit for caching different types of items
(images/documents). I actually much prefer the Gecko way of doing things to
either Opera or Webkit's ways. 

To sum up: I think the refresh behaviour should be the smoothest/least jarring
one and the user should have the option to perform a "complete" refresh by
holding down a modifier key (isn't this also the way IE does it? So the vast
majority of users are trained to already hold down a key to force a full
refresh).


-- 
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.