- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Mar 2017 16:55:07 +0000
- To: public-css-archive@w3.org
Thanks for the clarification, Tab. I still think it's _slightly_ confusing to have one layout rule for "native" shadow DOM (e.g., videos and complex form widgets) and another rule for custom web component shadow DOM, but that's consistent with them being very different from a DOM scripting perspective. However, I would prefer to have a consistent rule for all the replaced elements with fallback content, whether that's an `<object>`, `<video>`, or a `<progress>`. `<canvas>` is the odd one out, because it's child content isn't ignored when the canvas is rendered (it's still part of the accessibility tree & tab order), so it could have special rules. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/540#issuecomment-287121520 using your GitHub account
Received on Thursday, 16 March 2017 16:55:13 UTC