- From: Lea Verou <notifications@github.com>
- Date: Tue, 16 Feb 2021 03:30:32 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 16 February 2021 11:30:44 UTC
Hi @alice! 👋🏼 Looking at the explainer, I'm missing some examples of how this is supposed to be used. If it's used on `<body>`, wouldn't it make the entire subtree inert, *including the `<dialog>` itself*? There often is a natural container for all content that excludes dialogs, popups, etc, but not always, so libraries cannot depend on it, and would need to introduce their own wrapper element, which is fairly intrusive. I suppose this is why `<dialog>` in the spec isn't actually defined in terms of the `inert` attribute? Given that `inert` is currently a boolean attribute, it doesn't look like there's a way to override it on descendant subtrees. However, a way to do so could be quite useful to address the many cases where the inert subtree(s) contain the blocking elements or vice versa. Another example that comes to mind is UI to edit parts of an HTML page in place (e.g. a social media profile), by appending form elements within the elements being edited. One wants the parts of the page that are being edited to be inert, but the editing controls inside them to be interactive. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/610#issuecomment-779776894
Received on Tuesday, 16 February 2021 11:30:44 UTC