- From: Philip Jägenstedt <notifications@github.com>
- Date: Tue, 26 Sep 2017 01:44:55 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 26 September 2017 08:45:18 UTC
> The problem is unrelated to hierarchy restrictions. It is more about that whether a `<dialog>` can go fullscreen. If a `<dialog>` itself can go fullscreen, then HTML spec removing it from top layer may pose unexpected result in various algorithms when the `<dialog>` is in fullscreen. Right, not having to worry about such interaction would be good. In https://github.com/whatwg/fullscreen/pull/91#issuecomment-303340846 I added use counters to answer this question, and we have numbers from the stable channel now: https://www.chromestatus.com/metrics/feature/timeline/popularity/1998 https://www.chromestatus.com/metrics/feature/timeline/popularity/1999 In other words, it essentially never happens, and I would happily add that restriction to Blink. If we do that, I think that simplified this issue somewhat. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fullscreen/pull/102#issuecomment-332129719
Received on Tuesday, 26 September 2017 08:45:18 UTC