- From: Brian Kardell via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Mar 2022 16:35:31 +0000
- To: public-css-archive@w3.org
I don't have very strong feelings about this, any of 1,2,3 seem totally usable to me, but... When you're looking at a range, inclusive or exclusive feels secondary to the selectors, which will in all probability look a lot more like @Rich-Harris's examples - as those get more complex than `.a` or `.b`, I wonder if it gets just a little harder to scan them if there is some 'noise' between them that is kind of secondary. It's pretty minor, probably, but because of this I sort of think I prefer them in the order they are listed, pretty much. -- GitHub Notification of comment by bkardell Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6577#issuecomment-1063119015 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 March 2022 16:35:32 UTC