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.
<rdar://problem/12354161>
Created attachment 241313 [details] Don't track subresources after main frame loaded, expect for those started by user interaction.
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.
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>
All reviewed patches have been landed. Closing bug.