- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Jun 2019 10:20:47 +0000
- To: public-css-archive@w3.org
I'd like to note that we have had multiple discussions on this topic both in other issues and outside of github in the past few weeks, and I have come to revise my opinion here a bit. I think it wouldn't make no sense to decide that `display:contents` do not render outlines, since they do not have boxes on which the outline drawing request can be stored. In the end, what I think really matters is that when a `display:contents` link gets keyboard-focused, an outline is drawn around the boxes it's associated with, but that can be achieved by "manually giving a default `auto` outline to the boxed descendants of an un-boxed focused element" rather than having an element without a box draw an multipart outline. Both options are possible, really, and I'd be fine with both of these ways of doing things, but my understanding of the current consensus from people invovled in this issue is that, implementation-wise, not drawing an outline for a `display:contents` element makes more a lot more sense, and I'm inclined to believe it. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3323#issuecomment-498200225 using your GitHub account
Received on Monday, 3 June 2019 10:20:48 UTC