New issue
Advanced search Search tips

Issue 808086 link

Starred by 1 user
Status: Archived
Owner:
dproy@chromium.org
Closed: Sep 28
Cc:
sullivan@google.com
tdres...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Design and Implement Time to Interactive Metric with OOPIF turned on

Project Member Reported by dproy@chromium.org, Feb 1 2018 
It is not clear what the definition of TTI should be with OOPIF turned on. Few thoughts: 

- We should probably report it as a separate metric than current TTI.
- If we only take the long tasks in the main frame into account, TTI will be trivially gameable because developers can put all their content in an iframe.

Comment 1 by maxlg@chromium.org, May 16 2018 

ping. Any update here?

Comment 2 by dproy@google.com, May 16 2018 

No update as of now.

Comment 3 by npm@chromium.org, Sep 25

Owner: dproy@chromium.org
Status: Assigned (was: Available)
Site Isolation is now on. Are we still planning to update some definitions or should we WontFix?

Comment 4 by dproy@chromium.org, Sep 26 

+tdresser for prioritization here.

Comment 5 by tdres...@chromium.org, Sep 27

Cc: sullivan@google.com
This is quite low priority.

Annie, any thoughts on what we should do with bugs we kinda might want to get around to sometime?

We could track it in the backlog, but close the bug?

Comment 6 by sullivan@chromium.org, Sep 28 

Yeah, tracking it in the backlog but archiving the bug sounds good to me.

Comment 7 by sullivan@chromium.org, Sep 28

Status: Archived (was: Assigned)
(Archiving this to test changes to the backlog script)
►

Sign in to add a comment