W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

Re: [csswg-drafts] [css-display][css-aam][selectors-4] How elements with `display:contents` get focused?

From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
Date: Fri, 01 Jun 2018 13:34:14 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-393881997-1527860053-sysbot+gh@w3.org>
> A display: contents element isn't visible. It isn't interactive. It's nothing at all. It just has contents that might be visible and/or interactive.

I guess this is 100% true from the (current) implementer's perspective, but not from the user's. If something is _nothing at all,_ it can't have any visible/interactive parts _at all._ If the user sees and interacts with something, it can't be _nothing_ — it actually _is_ the visible and interactive element that can only be _partially hidden._ Even if its main part is hidden, the one that gets the focus outline. That's why it's OK for me if such element can't be styled _directly_ on focus — it's really nothing to be styled _directly_ — but it's not OK to have no focus state for it (that I could use to style its visible descendants) at all.

> But zero fragments is a very different case. Where is that outline supposed to go???

With all due respect, I can't agree with treating the _visible part_ of the `display: contents` element as "zero fragments". I think of `::selection` as the closest existing thing. At least, the text content of the `display: contents` element can be selected, and these _non-zero_ selected _fragments_ can be styled somehow. So I suggested a new pseudo-element (something like old Mozilla's `::-moz-focus-inner`, maybe?) that would span all these fragments, so you would be able to apply the outline to it. But I could live without it, as long the element itself stays focusable in principle.

Maybe it would be better to make this pseudo-element proposal a separate issue, and focus on the focusability of the `display: contents` element itself here?

GitHub Notification of comment by SelenIT
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2632#issuecomment-393881997 using your GitHub account
Received on Friday, 1 June 2018 13:34:16 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:31 UTC