[Webkit-unassigned] [Bug 26409] [GTK] Glitches in new progress/load-status system

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 13 15:50:37 PDT 2009


Christian Dywan <christian at twotoasts.de> changed:

           What    |Removed                     |Added
                 CC|                            |christian at twotoasts.de

--- Comment #10 from Christian Dywan <christian at twotoasts.de>  2009-08-13 15:50:36 PDT ---
> - A weird 10% progress is reported for pages before the status even reaches
> PROVISIONAL. Not sure where this comes from, but it should either go away or
> come after PROVISIONAL or COMMITTED I think.

Arguably a provisional load is already doing *something*, this comes down to
what you perceive as progress. A user may be confused when he hits return and
the progress bar is empty because it takes ages to obtain a response from the
remote end. So I don't really think it's wrong.

> - FINISHED comes before 100% progress is reported. I believe the natural
> expectation would be to receive 100% while the status is still not finished,
> and *then* receive FINISHED.

The FrameLoadClientGtk relies on FrameLoader. And FrameLoader actually has
guards to catch this case, so it looks like a bug in WebCore. I mostly hacked
the Gtk bits so I can't easily say where to look.  I guess this needs some
looking at debugging output.

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

More information about the webkit-unassigned mailing list