I won't be able to attend today's call, but I wanted to throw my support
behind the PerformanceObserver proposal. My single concern was resolved and
I believe the API addresses all the use cases I had planned.
Thanks!
Eli Perelman
Mozilla
On Wed, Feb 11, 2015 at 11:35 AM, Ilya Grigorik <igrigorik@google.com>
wrote:
> One more thing for the agenda: PerformanceObserver! :)
>
> See:
> https://lists.w3.org/Archives/Public/public-web-perf/2015Feb/0013.html
>
> On Tue, Feb 10, 2015 at 5:05 PM, Philippe Le Hegaret <plh@w3.org> wrote:
>
>> Let's schedule a call for tomorrow to move things forward.
>>
>> - Navigation Error Logging
>> 4 issues
>> https://github.com/w3c/navigation-error-logging/issues
>> https://lists.w3.org/Archives/Public/public-web-perf/2015Feb/0016.html
>>
>> - Server Timing
>> https://lists.w3.org/Archives/Public/public-web-perf/2015Feb/0009.html
>>
>> - User Timing
>> 2 issues
>> https://github.com/w3c/user-timing/issues
>>
>> - Navigation Timing 2
>> Any desire to implement
>> performance.getEntriesByType("navigation") ?
>>
>> - requestAnimationFrame
>> Next step for RAF given the lack of progress on PV2
>>
>> - Automatic publishing of Working Drafts in /TR
>>
>> --
>> Philippe
>>
>>
>>
>>
>