Comma separated CSS selectors are exploded with commas
See original GitHub issueHi!
From version 2.3.0, any combined CSS selectors (with coma) are quite destroyed :p Input CSS:
.entity-enter-to,
.entity-leave {
opacity: 1;
}
Ponyfill’s output CSS copied from IE11 DOM:
.,e,n,t,i,t,y,-,e,n,t,e,r,-,t,o,,,
,.,e,n,t,i,t,y,-,l,e,a,v,e{opacity:1;}
If you have no idea where it comes from I can try to find more infos. (single selectors are fine)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why do CSS comma separated selectors break entire rule ...
It turns out this is actually intentional and defined in Selectors Level 3 (emphasis by me):. If just one of these selectors were...
Read more >What Is the Comma for in CSS Selectors? - ThoughtCo
CSS means cascading style sheets. The comma in a CSS selector separates multiple selectors within the same styles.
Read more >Multiple CSS selectors separated by commas don't work #3960
I think I was holding this selector wrong. TIL if any of the selectors are wrong in a comma separated list of selectors,...
Read more >CSS Selectors · WebPlatform Docs
A comma-separated list of selectors represents the union of all elements selected by each of the individual selectors in the list. (A comma...
Read more >Less Combinatorial Explosion Parent Selectors - Javatpoint
Combinatorial Explosion Parent Selectors. The & operator can be used to produce all possible permutation of selectors in a list separated by commas....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds good. Appreciate the effort, @rndmerle.
If for some reason you decide to dive back in and there is something I can do to help, give me a shout. I’ll close this issue for now, but I’m happy to reopen if/when necessary.
Apparently the IE11 support on Glitch is not yet available. Anyway, I spent some more hours trying to set-up a minimal reproduction repo but it’s even more complicated and inextricable than I thought.
I actually gave up 😦 The farthest I could go was to find it was related to
es.string.split
not being polyfilled whilees.regexp.exec
was. But it’s more complicated it seems.Considering the fact that I’ve an easy workaround, that it seems nobody else has this issue, and that even if I could coin the real cause it would still take hours to fix, I think it’s not reasonable to spend more time on this.