- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 May 2019 14:45:31 +0000
- To: public-css-archive@w3.org
> it shouldn't affect anything as long as at least one descendant of the element is rendered @FremyCompany, I agree that in ideal world it should be so, but in the same time try to avoid introducing complex heuristics. If it would be easier for implementers to always treat elements with `display:contents` as kind of offscreen-rendered element rather then switch between treating them as rendered or non-rendered depending on other conditions, I would rather go with this. At least, it's easier to remove the otherwise tabbable element from the tab sequence if authors want to (`tabindex="-1"`) than the other way around. And since the HTML definition of focusability is based on the "being rendered" concept, and the latter refers back to CSS box tree, I'd like to double-check that current CSS definition can't justify the understanding of "being (not) rendered" that I don't agree with:) -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2632#issuecomment-495661191 using your GitHub account
Received on Friday, 24 May 2019 14:45:32 UTC