RE: [minutes] Web Performance WG Teleconference #139 Agenda 2014-10-15

I provided feedback on the pull request, but for the sake of the list, I added the following to https://github.com/w3c/smoothness/pull/4


+1 This seems consistent with Resource Timing and Navigation Timing APIs.

Tobin

From: Ilya Grigorik [mailto:igrigorik@google.com]
Sent: Thursday, October 16, 2014 11:02 AM
To: Tobin Titus
Cc: public-web-perf; Philippe Le Hegaret
Subject: Re: [minutes] Web Performance WG Teleconference #139 Agenda 2014-10-15


On Wed, Oct 15, 2014 at 12:58 PM, Tobin Titus <tobint@microsoft.com<mailto:tobint@microsoft.com>> wrote:
Web Smoothness
- IE already exposes this information in ETW traces.
   Microsoft doesn't have any strong objections to exposing it in real-time through JavaScript.
- Some language could be tweaked:
   Would prefer not to use vendor-specific lingo such as "jank" in the spec
   Naming of the spec should better match what it is to prevent mischaracterization (aka, it doesn't make sites "smooth")
- Move over to Github with Philippe's help
- Move over conversation from Mozilla as well

How does everyone feel about renaming "Smoothness" to "Frame Timing" API?

I think it better captures the intent and addresses above concerns. Pull request: https://github.com/w3c/smoothness/pull/4


ig