Implement Memory Pressure API |
||||||
Issue descriptionFeature description: API to to expose the memory pressure signal received by the system to web applications. Eng owners: fmeawad@google.com, panicker@google.com Design doc: https://docs.google.com/document/d/1tNZP12J6J-ZynaI8A4gfvPxH8QlyS55dZ8IpFqby0V8/edit Links: https://github.com/WICG/memory-pressure/blob/master/explainer.md
,
Apr 17 2017
,
Apr 18 2017
Reminder that if this has privacy/security/etc impacts it should also have a corresponding type=launch issue. For more details see bit.ly/2ncKZfp
,
Jun 5 2017
We've decided to punt on this based on initial work & prototyping. (google corp doc) https://docs.google.com/document/d/1HAlKYh4ZwxO3M6XNHlUI59cS8gpQbSDVfKCrH0ZCE_w/edit
,
Sep 12 2017
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues. We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate. For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit For any questions, please contact owencm, sshruthi, larforge
,
Sep 18 2017
,
Jan 4 2018
Shubhie, should we close this?
,
Apr 30 2018
Ping, is there still plans to implement this?
,
Apr 30 2018
Marking WontFix as per #4. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mlamouri@chromium.org
, Apr 6 2017