- From: freshp86 <notifications@github.com>
- Date: Tue, 03 Apr 2018 17:24:09 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 4 April 2018 00:24:33 UTC
Think of Web components (aka custom elements). An element that wraps a `dialog` is added to the DOM. The element along with its `::backdrop` are rendered when `showModal()` is called. For example see [here](https://freshp86.github.io/chromium-webui/demo.html) (which is a copy of actual code from Chromium). As a developer, a custom element is though of as a black box with a public API. Having to treat the `::backdrop` as anything other than a child of the custom element is inconvenient, and I don't think is the suggested route anyway. FWIW `dialog::backdrop` is already a thing, so I don't think arguing whether the existence of it is justified as opposed to just having a global `::backdrop` needs to be had in this discussion. -- 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/issues/124#issuecomment-378440469
Received on Wednesday, 4 April 2018 00:24:33 UTC