New issue
Advanced search Search tips

Issue 718486 link

Starred by 2 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 725567



Sign in to add a comment

[Buffer] Buffer Long Tasks that happen before onload

Project Member Reported by panicker@chromium.org, May 4 2017

Issue description

Update implementation per spec update:
https://github.com/w3c/performance-timeline/pull/76
 
Would this be a good first bug?
Yes, it's perfect :)
Cc: tdres...@chromium.org panicker@chromium.org
Owner: maxlg@chromium.org
Over to Max, we can discuss in our next 1-1.

Comment 4 by maxlg@chromium.org, May 17 2017

Thanks! I will take a look.

Comment 6 by maxlg@chromium.org, Jul 4 2017

Blocking: 725567

Comment 7 by maxlg@chromium.org, Jul 10 2017

Status: Started (was: Assigned)

Comment 8 by maxlg@chromium.org, Jul 10 2017

Blocking: -725567

Comment 9 by maxlg@chromium.org, Jul 10 2017

Blockedon: 725567

Comment 10 by maxlg@chromium.org, Oct 10 2017

Summary: [Buffer] Buffer Long Tasks that happen before onload (was: Buffer Long Tasks that happen before onload)
What's the current status of this change? Is it blocked on anything? I know there is some spec work happening around this, but I don't think it should block implementation?

Comment 12 by maxlg@chromium.org, Mar 22 2018

Yes, the spec is not finalized yet, as being discussed in this thread - https://github.com/w3c/performance-timeline/issues/81.

As the feature prototyped behind a flag, should we just implement the not-yet finalized proposal or wait till it finalize?
I think implementing the current proposal behind the flag would make sense.
Labels: -Type-Bug Type-Feature

Sign in to add a comment