Re: [ResourceTiming] Notification of new entries (prior to completion)

Thanks, I've carried the discussion to 
https://github.com/w3c/performance-timeline/issues/13

- Nic
http://nicj.net/
@NicJ

On 6/2/2015 1:57 PM, Philippe Le Hegaret wrote:
> We touched on this early on [1] and the conclusion at the time was to 
> get the notification once the object was fully populated, ie NT would 
> come after some of the RT notifications. Ilya and Nat seemed to have 
> reached the same conclusion 20 days ago.
>
> You definitively want to come on
>  https://github.com/w3c/performance-timeline/issues/13
>
> Philippe
>
> [1] http://www.w3.org/2015/02/25-webperf-minutes.html#item05
>
> On 06/02/2015 12:23 PM, Nic Jansma wrote:
>> Hi all,
>>
>> I can't remember if we've discussed this before or not, but I would like
>> to see if there's a way we could allow consumers of RT to get notified
>> of new entries prior to their completion (eg before responseEnd is
>> set).  Maybe as an optional argument to the PerformanceObserver 
>> interface?
>>
>> Ideally, I would like to be notified of new entries as soon as startTime
>> is known.
>>
>> One use case is to allow pages to monitor for new outgoing network
>> requests, which would also give you the ability to know how many
>> networking requests are in-flight.  You could theoretically build a
>> "busy" indicator with this.
>>
>> Specifically, what we want, is to be able to better monitor when all of
>> the resources triggered by a SPA soft navigation have completed.  The
>> body 'onload' event is no longer relevant for SPA apps.  Today we're
>> doing this by monitoring for changes to the DOM via MutationObserver and
>> hooking into onload/onerror events, which is not efficient.  We also
>> cannot monitor all types of resources in this way (eg fonts).
>>
>> Thoughts?
>>
>> -- 
>> - Nic
>> http://nicj.net/
>> @NicJ
>>
>