- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Fri, 8 Jan 2016 13:55:17 +0100
- To: Hyojin Song <hyojin22.song@lge.com>
- Cc: www-style list <www-style@w3.org>, Tantek Celik <tantek@cs.stanford.edu>
On Fri, Jan 8, 2016 at 1:20 PM, Hyojin Song <hyojin22.song@lge.com> wrote: > I think some policy to properly handle the situation described above > should be specified in the fullscreen API spec in forms of notes or issues. > It can assure the consistent implementation among user agents in case > of malicious web page. Again, it really depends on what you're doing. If the user already opted into presentation mode, it might be okay to go fullscreen on the second screen for a particular element without user interaction. So again, what's needed is some elaboration on use cases and such. >> Note that the Fullscreen API is mostly focused on fullscreening an >> element. Is that what you want for presentation as well? > > Right. It's best option to use the existing :fullscreen pseudo-class, but > it would have some changes to support the second screen use cases. > How can we(SSP WG) discuss with this work? https://fullscreen.spec.whatwg.org/ has indications as to how to participate at the top. I recommend filing an issue on GitHub. -- https://annevankesteren.nl/
Received on Friday, 8 January 2016 12:55:44 UTC