Bug 127504 - Loads started soon after main frame completion should be considered part of the main load
Summary: Loads started soon after main frame completion should be considered part of t...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-23 12:19 PST by Antti Koivisto
Modified: 2014-01-23 13:19 PST (History)
2 users (show)

See Also:


Attachments
patch (4.17 KB, patch)
2014-01-23 12:29 PST, Antti Koivisto
kling: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Antti Koivisto 2014-01-23 12:19:14 PST
ProgressTracker currently decides that main load is complete when the main frame stops loading. However it is common that timers and onload events trigger more loads immediately (for example by inserting iframes) and loading continues visually. These should be considered as part of the main load for paint throttling and speculative tiling coverage purposes.
Comment 1 Antti Koivisto 2014-01-23 12:29:32 PST
Created attachment 222015 [details]
patch
Comment 2 Andreas Kling 2014-01-23 13:12:46 PST
Comment on attachment 222015 [details]
patch

r=me, but please switch this over to using monotonically increasing time instead of WTF::currentTime().
Comment 3 Antti Koivisto 2014-01-23 13:19:56 PST
https://trac.webkit.org/r162637