- From: Brandon McConnell via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Jul 2023 15:07:28 +0000
- To: public-css-archive@w3.org
It is an interesting question @Que-tin poses. Many developers purposely use a `display: contents` wrapper intentionally to have its children act as children of the parents. Selectors (like `:nth-child`) won't pass that barrier, but maybe values/functions should, if that's not currently the spec? 🤷🏻♂️ Otherwise, adding a contents wrapper could instantly break the layout where it wouldn't have before. I would totally understand if making that change would bring a host of other undesirable side effects though. My initial thoughts were exactly @jonathantneal's, but I wonder if we should consider that a bit further before implementing. -- GitHub Notification of comment by brandonmcconnell Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4559#issuecomment-1644099822 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 July 2023 15:07:30 UTC