RESOLVED FIXED 138582
Don't track sub-resources that are started after main frame progress has completed. 
https://bugs.webkit.org/show_bug.cgi?id=138582
Summary Don't track sub-resources that are started after main frame progress has comp...
Yongjun Zhang
Reported 2014-11-10 14:55:00 PST
After main frame progress has finished, start loading a sub-resource shouldn't affect UI process's view of page loading status (i.e., the page has already completed loading and the progress shouldn't change). To avoid confusing the UI, we should consider not to track sub-resources that are started after the main frame has finished loading, except for those loaded by user interaction.
Attachments
Don't track subresources after main frame loaded, expect for those started by user interaction. (6.78 KB, patch)
2014-11-10 15:22 PST, Yongjun Zhang 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Yongjun Zhang
Comment 1 2014-11-10 14:55:39 PST
<rdar://problem/12354161>
Yongjun Zhang
Comment 2 2014-11-10 15:22:27 PST
Created attachment 241313 [details] Don't track subresources after main frame loaded, expect for those started by user interaction.
David Kilzer (:ddkilzer)
Comment 3 2014-11-10 20:13:00 PST
<rdar://problem/12354161>
Sam Weinig
Comment 4 2014-11-19 16:27:06 PST
Comment on attachment 241313 [details] Don't track subresources after main frame loaded, expect for those started by user interaction. Would be great if you could add an API test for this.
WebKit Commit Bot
Comment 5 2014-11-19 21:45:47 PST
Comment on attachment 241313 [details] Don't track subresources after main frame loaded, expect for those started by user interaction. Clearing flags on attachment: 241313 Committed r176382: <http://trac.webkit.org/changeset/176382>
WebKit Commit Bot
Comment 6 2014-11-19 21:45:54 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.