[Webkit-unassigned] [Bug 127504] New: Loads started soon after main frame completion should be considered part of the main load

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 23 12:21:45 PST 2014


https://bugs.webkit.org/show_bug.cgi?id=127504

           Summary: Loads started soon after main frame completion should
                    be considered part of the main load
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Page Loading
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: koivisto at iki.fi


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.

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