New issue
Advanced search Search tips

Issue 738493 link

Starred by 2 users

Issue metadata

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

Blocked on:
issue 785349



Sign in to add a comment

Implement Long Tasks V2 (cover bug)

Project Member Reported by panicker@chromium.org, Jun 30 2017

Issue description

Cover bug for implementation of Long Tasks V2.
Will track specific tasks with separate bugs.

 
Blockedon: 738495
Cc: maxlg@chromium.org
Cc: panicker@chromium.org
Shubhie, can you file bugs for the other long tasks V2 work?

It doesn't look like exposing:
- Style/Layout
- V8 compile ( issue 738495 )
- V8 parse
- V8 CallFunction

is covered by any bugs.

Comment 4 by maxlg@chromium.org, Aug 1 2017

Blockedon: -738495
Owner: npm@chromium.org
Do we have a bug for the CallFunction work?
If not, Nicolas, can you file one?

And can we block this bug on the bug for CallFunction?

Comment 6 by npm@chromium.org, Nov 15 2017

Blockedon: 785349
Status: Assigned (was: Available)

Comment 8 by maxlg@google.com, Jan 29 2018

 Issue 773460  has been merged into this issue.

Comment 9 by dproy@chromium.org, May 9 2018

ping from bug triage. 
@npm: Should we start moving the LongTaskV2 to experimental? I remember there was some issues around the top level events, has we resolved it?

Comment 11 by npm@chromium.org, May 9 2018

Today we met with a couple of Akamai folks. I think the priority here is to first improve spec language and try to push for other browser vendors to launch LongTasks as well. Regarding task attribution, I have a proposal to improve task types, but from the talk today it seems that that is not the higher priority. Figuring out how to better blame third parties without leaking sensitive information seemed to be the bigger concern.
Labels: -Type-Bug Type-Feature

Sign in to add a comment