- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jan 2022 17:00:53 +0000
- To: public-css-archive@w3.org
> If modal dialogs reset `pointer-events`, then I guess they should escape ancestor inertness? Since inertness sets `pointer-events: none`. However, https://html.spec.whatwg.org/multipage/interaction.html#inert says Why would it? We clarified that even though inertness behaves like `pointer-events: none`, it doesn't change the computed value, so they're not necessarily related. We should probably fix up the previous resolution of course. Regarding these two tests: > 2. What happens when the ancestor is replaced content or display: table-column? See the following tests: > > * [modal-dialog-in-replaced-renderer.html](https://github.com/web-platform-tests/wpt/blob/5874448f80/html/semantics/interactive-elements/the-dialog-element/modal-dialog-in-replaced-renderer.html) > * [modal-dialog-in-table-column.html](https://github.com/web-platform-tests/wpt/blob/5874448f80139811704f009a2d5c232f2647db98/html/semantics/interactive-elements/the-dialog-element/modal-dialog-in-table-column.html) I think consensus was that Gecko and WebKit have the preferred behavior since it's similar to how `display: none` suppresses descendant boxes. Perhaps we can resolve on that? -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6939#issuecomment-1016671534 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 January 2022 17:00:55 UTC