Content Size Policy (name subject to change) |
||||||
Issue description(See http://www.chromium.org/blink#launch-process for an overview) Change description: This feature will allow authors to specify the maximum amount of content a given frame can load. Changes to API surface: TODO Links: Public standards discussion: TODO Support in other browsers: Internet Explorer: None Firefox: None Safari: None *Make sure to fill in any labels with a -?, including all OSes this change affects. Feel free to leave other labels at the defaults.
,
Sep 22 2016
bump milestone as work has paused.
,
Oct 19 2016
Removing myself as owner for now, not in my queue currently.
,
Nov 3 2016
Fixed the empty status.
,
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 13
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by bugdroid1@chromium.org
, Aug 2 2016