LGTM3
On Sat, Oct 9, 2021, 01:49 Alex Russell wrote:
> Thanks for clarifying that you're thinking about this problem, Nicolás.
> Looking forward to seeing more of that land in future intents.
>
> LGTM2
>
> On Thursday, October 7, 2021 at 5:44:37 PM UTC-7 Chris Harrelson wrote:
>
>> LGTM1
>>
>> O
Thanks for clarifying that you're thinking about this problem, Nicolás.
Looking forward to seeing more of that land in future intents.
LGTM2
On Thursday, October 7, 2021 at 5:44:37 PM UTC-7 Chris Harrelson wrote:
> LGTM1
>
> On Thu, Oct 7, 2021 at 1:15 PM Nicolás Peña wrote:
>
>> We do want to
LGTM1
On Thu, Oct 7, 2021 at 1:15 PM Nicolás Peña wrote:
> We do want to make it easier to track asynchronous work, and I think this
> will require something such as `measureUntil`. Once we implement that, it
> would be plausible to extend EventTiming to include that
> developer-annotated async
We do want to make it easier to track asynchronous work, and I think this
will require something such as `measureUntil`. Once we implement that, it
would be plausible to extend EventTiming to include that
developer-annotated async duration. It would also make it possible to
annotate any User Timing
So this design looks pretty good in terms of auto-generating a uniform ID
for pre-baked events, but I'm curious about how it will interact with
asynchronous tasks generated from within task callbacks, and how a
user-timing mark from within one of these scopes might inherit the
interactionID?
On Thursday, October 7, 2021 at 1:58:59 AM UTC-4 Yoav Weiss wrote:
> On Mon, Oct 4, 2021 at 7:13 PM Nicolás Peña wrote:
>
>> Contact emails
>>
>> n...@chromium.org, hbs...@chromium.org
>>
>> Explainer
>>
>> https://gist.github.com/npm1/9c2b95ece116d9bcb4bc224155e23777
>>
>> Specification
>>
>>
On Mon, Oct 4, 2021 at 7:13 PM Nicolás Peña wrote:
> Contact emails
>
> n...@chromium.org, hbs...@chromium.org
>
> Explainer
>
> https://gist.github.com/npm1/9c2b95ece116d9bcb4bc224155e23777
>
> Specification
>
>
> https://wicg.github.io/event-timing/#dom-performanceeventtiming-interactionid
>
>
On Mon, Oct 4, 2021 at 1:19 PM Michal Mocny wrote:
>
>
> On Mon, Oct 4, 2021 at 1:13 PM Nicolás Peña wrote:
>
>> Contact emails
>>
>> n...@chromium.org, hbs...@chromium.org
>>
>> Explainer
>>
>> https://gist.github.com/npm1/9c2b95ece116d9bcb4bc224155e23777
>>
>> Specification
>>
>>
>> https://wi
On Mon, Oct 4, 2021 at 1:13 PM Nicolás Peña wrote:
> Contact emails
>
> n...@chromium.org, hbs...@chromium.org
>
> Explainer
>
> https://gist.github.com/npm1/9c2b95ece116d9bcb4bc224155e23777
>
> Specification
>
>
> https://wicg.github.io/event-timing/#dom-performanceeventtiming-interactionid
>
>
Contact emails
n...@chromium.org, hbs...@chromium.org
Explainer
https://gist.github.com/npm1/9c2b95ece116d9bcb4bc224155e23777
Specification
https://wicg.github.io/event-timing/#dom-performanceeventtiming-interactionid
Summary
Developers currently use the Event Timing API to gather performanc
10 matches
Mail list logo