- From: <bugzilla@jessica.w3.org>
- Date: Wed, 27 Apr 2016 16:55:54 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25554 Travis Leithead [MSFT] <travil@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |travil@microsoft.com Resolution|--- |WONTFIX --- Comment #1 from Travis Leithead [MSFT] <travil@microsoft.com> --- HTML5.1 Bugzilla Bug Triage: Won't Fix While media manipulation could be abused by JavaScript in the way you describe it seems like it would be a conflict of interest for the site. In other words, why would the site that owns both the media element creation (and it's attributes) have dueling JavaScript that did something it didn't like? Naturally, as other libraries are often included in a page that could do bad things, there is a risk, but that is the risk taken whenever external code is loaded into the context of a page (and not done through an iframe). Furthermore, similar ideas are currently being discussed in the "interventions" spec, which aims to track what browsers are doing to mitigate these types of issues, and come to a mutual agreement on what may be standardized. I'd encourage you to participate there: https://github.com/WICG/interventions If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks! -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 27 April 2016 16:55:59 UTC