- From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Apr 2016 19:08:48 +0000
- To: public-media-capture-logs@w3.org
I'd be happy to help with the process of moving the HTMLIFrameElement extension into the HTML spec. This generally is beneficial, as it gives authors and implementers of tools like conformance checkers a more centralized view of relevant content attributes. (Implementers of browsers are not really affected, as if they're implementing media capture, they'll see this spec.) We're working on similar moves for a few other specs which have to patch attributes onto HTML elements, like referrer policy and subresource integrity. How I would envision this working, concretely, is that the definition of "allowed to access user media" moves to the intro section of "Obtaining local multimedia content", where it would say something like > Every browsing context has an allowed to access user media flag. This specification does not detail how such or when this flag is set. or similar. Then, HTML can define that all non-nested browsing contexts have the flag set, and can define the the iframe content attribute and IDL attribute to control the flag for nested browsing contexts. How does this sound? I'd be happy to work on a pull request for HTML you could review to see the impact. I think this is a much nicer modularity boundary than the current approach, separating the host environment stuff (like extensions to HTMLIFrameElement and the content attribute) from the core media-capture--related concepts (like "allowed to access user media"). -- GitHub Notification of comment by domenic Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/353#issuecomment-215851094 using your GitHub account
Received on Friday, 29 April 2016 19:08:50 UTC