Re: [frame-timing] Processing model proposal

cc: hixie, annevk, zcorpan

I didn't know that processing model existed, thanks.

How about the following as an update:

https://docs.google.com/a/chromium.org/document/d/1SukXPZVUmDb8srqzAGI6Muu55aue9UUhY6XC4SFQFBs/edit?usp=sharing

And then I would replace the whole
  5.1.1  PerformanceRenderTiming Processing Model
section of the Frame Timing processing model with a link to
https://html.spec.whatwg.org/multipage/webappapis.html#processing-model-9

In a similar vein, this model doesn't seem to specify an event processing
loop for compositing. I think we should keep that part in the Frame-Timing
doc for the moment,  but reach out to WHATWG and see if it makes sense to
add another loop type to this model.

Thoughts? Comments?
Thanks!
-Mike

On Mon, Mar 23, 2015 at 2:21 PM, James Robinson <jamesr@chromium.org> wrote:

> I believe that this should be covered by the HTML specification's
> processing model: (i.e.
> https://html.spec.whatwg.org/multipage/webappapis.html#processing-model-9)
> and any hooks that you need to wire up the frame-timing data should be
> provided by HTML's definition of the processing model.  Please don't
> attempt to define the processing model in yet another spec.
>
> - James
>
> On Fri, Mar 20, 2015 at 12:59 PM, Michael Blain <mpb@chromium.org> wrote:
>
>> Hi Web Perf,
>>
>> I'm trying to write up the processing model for the frame-timing spec.
>>
>> Here's what we have currently. Would love to hear thoughts/comments?
>>
>>
>> https://docs.google.com/document/d/1Li_R8v4po9QwjLxNrrD0CCfgYqk4wWA1Ge6pX4jokfQ/edit?usp=sharing
>>
>> This would go in a new section of  http://w3c.github.io/frame-timing/
>>
>> Thanks!
>> -Mike
>>
>
>