Anticipated Chromium change would first issue deprecation warnings when the newly disallowed behavior is seen. New behavior (without any deprecation warning) will be behind a RuntimeEnabled flag (probably one distinct from MediaSourceExperimental, since bug 623698 will likely use MediaSourceExperimental).
Later, in M54/M55, the new behavior will be exposed on stable without any deprecation warning.
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
Comment 1 by wolenetz@chromium.org
, Jun 27 2016