- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 May 2018 08:11:01 +0000
- To: public-css-archive@w3.org
Considering the selector in the test from the @dbaron's comment above: if there were classes instead of type selectors there
```css
.h3 ~ :matches(.h1 ~ p.test):matches(.h2 ~ p.test) { ... }
```
then it would be expanded as
```css
.h1 ~ .h2 ~ .h3 ~ p.test,
.h1 ~ .h3 ~ .h2 ~ p.test,
.h2 ~ .h1 ~ .h3 ~ p.test,
.h2 ~ .h3 ~ .h1 ~ p.test,
.h3 ~ .h1 ~ .h2 ~ p.test,
.h3 ~ .h2 ~ .h1 ~ p.test,
.h1.h2 ~ .h3 ~ p.test,
.h1.h3 ~ .h2 ~ p.test,
.h2.h3 ~ .h1 ~ p.test,
.h1 ~ .h2.h3 ~ p.test,
.h2 ~ .h1.h3 ~ p.test,
.h3 ~ .h1.h2 ~ p.test,
.h1.h2.h3 ~ p.test { /* p.test preceded by all .h1, .h2, and .h3 in any possible order */ }
```
With type selectors (as in the original example) only the first 6 combinations make sense, so the equivalent expanded result can be shorter.
--
GitHub Notification of comment by SelenIT
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1027#issuecomment-391259738 using your GitHub account
Received on Wednesday, 23 May 2018 08:11:03 UTC