UnCSS ignoring complex selectors

[addyosmani]

Hey @giakki :)

Over in Web Starter Kit our basic layout uses a selector that looks like .app-bar.open ~ main. Unfortunately, this gets skipped by UnCSS, leaving us with a broken menu during our build, meaning we need to add an ignore in place to get this working.

Would it be possible to get some further testing done on why UnCSS is unable to handle such selectors correctly?

[giakki]

Oh no, not that again ;)

I'll look into it. Do you know if this also happens with just .app-bar.open, or .open ~ main?
Thanks!

[addyosmani]

We ran into it with .open ~main too if I remember correctly. Hope it doesn't cause too much trouble :)

[giakki]

Added a test.
Seems like updating the dependencies was enough.

Let me know if this was resolved!

[giakki]

Update: I had to unpublish v0.8.2 because of some weird dependency issues. I'll let you know asap!

[seriema]

Maybe related, but my CSS keeps these selectors even though there are no buttons or input elements on my page:

button::-moz-focus-inner,
input::-moz-focus-inner { ... }

[ben-eb]

@giakki It might be worth having a look at the ignore behaviour, such that it could test selectors such as button::-moz-focus-inner against just having a button element in the HTML code, rather than allowing the rule to pass. Imagine this should be a separate ticket though. 😄

[letsila]

Hi !

Combining tow classes selectors like so .first-class.second-class is still skipped. I have tried to ignore them but still doesn't work. The selectors are vanished by uncss.