- From: Rossen Atanassov <notifications@github.com>
- Date: Tue, 26 Jul 2022 07:59:08 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 26 July 2022 14:59:24 UTC
Hi @michaelwasserman – @torgo and I are just reviewing this at [our f2f](https://github.com/w3ctag/meetings/tree/gh-pages/2022/07-London). It looks like [the issue raised](https://github.com/mozilla/standards-positions/issues/636#issuecomment-1132985573) by @annevk hasn't been adequately addressed. That seems to be a pretty common use case (where a malicious site might seek to take over a display and mimic the user's OS (or similar) in order to steal credentials. Also as we've been reviewing it seems to us like this is more than a small enhancement. This proposal extends several technologies that are not part of multiscreen: `user activation`, `Element.requestFullScreen` and `window.open`. Since the scope is a bit wider than a small enhancement on an existing API. Can we ask that you to fork the topic and file a new design review request for this? -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/602#issuecomment-1195596347 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/602/1195596347@github.com>
Received on Tuesday, 26 July 2022 14:59:24 UTC