Add API to enable web developers to detect and diagnose memory regressions in their site |
|||
Issue descriptionExplainer: https://github.com/WICG/performance-memory/blob/master/explainer.md This includes specifying (or replacing) Chrome's currently non-standard performance.memory API. Some additional (google-internal) requirements from the GSuite team: https://docs.google.com/document/d/1nV8-Gk2zuiMg-Dk1jbbkvDPS7H8rb18wpRyBOYbrQIM/edit
,
Aug 24
Hi Erik, is there any update on this request? It came up today in a discussion with gsuite.
,
Aug 24
Spec has been very slower going through discussions with other vendors. I sent an i2i 2 days ago and will try to get an original trial up: https://bugs.chromium.org/p/chromium/issues/detail?id=876553#c2
,
Sep 21
We're blocking this on crbug.com/887967 - adding a CORS-only feature policy. This work is going to be on the backburner for the foreseeable future, the security / privacy concerns make it very difficult to expose more here.
,
Dec 7
,
Jan 11
@tdresser: any update on this? This is listed as a priority for GSuite. |
|||
►
Sign in to add a comment |
|||
Comment 1 by rbyers@chromium.org
, Jun 1 2018