RESOLVED FIXED 127504
Loads started soon after main frame completion should be considered part of the main load 
https://bugs.webkit.org/show_bug.cgi?id=127504
Summary Loads started soon after main frame completion should be considered part of t...
Antti Koivisto
Reported 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.
Attachments
patch (4.17 KB, patch)
2014-01-23 12:29 PST, Antti Koivisto 		kling: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Antti Koivisto
Comment 1 2014-01-23 12:29:32 PST
Created attachment 222015 [details] patch
Andreas Kling
Comment 2 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().
Antti Koivisto
Comment 3 2014-01-23 13:19:56 PST
https://trac.webkit.org/r162637
Note You need to log in before you can comment on or make changes to this bug.