New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 667394 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 113048
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

remove chrome.csi API

Project Member Reported by bmcquade@chromium.org, Nov 21 2016

Issue description

Similar to bug 621512, which focuses on removing the chrome.loadTimes API, we should also remove the chrome.csi API. This API is non-standard, and even less intuitive than the chrome.loadTimes API. It also reports bad data, for instance, chrome.csi().onloadT reports not the onload time, but rather dom content loaded time. This is not documented anywhere, so any devs using onloadT for time to onload are getting bad data without realizing it.

We should deprecate this API and migrate developers to standard equivalent APIs.

As a first step, we should measure usage of this API. The API can be found here:

https://cs.chromium.org/chromium/src/chrome/renderer/loadtimes_extension_bindings.cc?q=getcsi&sq=package:chromium&l=60
 
Cc: igrigo...@chromium.org
Components: Blink>PerformanceAPIs
Cc: kouhei@chromium.org japhet@chromium.org kinuko@chromium.org
Issue 113048 has been merged into this issue.
Cc: panicker@chromium.org
Owner: ----
Status: Available (was: Assigned)
Haven't done anything here. Returning to the queue for now.
Mergedinto: 113048
Status: Duplicate (was: Available)

Sign in to add a comment