Bug 127504

Summary: Loads started soon after main frame completion should be considered part of the main load
Product: WebKit Reporter: Antti Koivisto <koivisto>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Severity: Normal CC: commit-queue, japhet
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Description Flags
patch kling: review+

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]
Comment 2 Andreas Kling 2014-01-23 13:12:46 PST
Comment on attachment 222015 [details]

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