Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

matches() does not work with pseudo-elements #4

Closed
topaxi opened this issue Jun 24, 2015 · 7 comments
Closed

matches() does not work with pseudo-elements #4

topaxi opened this issue Jun 24, 2015 · 7 comments
Labels

Comments

@topaxi
Copy link

topaxi commented Jun 24, 2015

Input:

.foo:matches(:hover, :focus)::before {
  color: red;
}

Expected:

.foo:hover::before, .foo:focus::before {
  color: red;
}

Actual:

.foo:hover ::before, .foo:focus ::before {
  color: red;
}

This just stopped working, I'm not sure which version update caused this (using cssnext, happens on http://cssnext.io/playground/ too).

@TrySound
Copy link
Member

@topaxi Double colon.

@topaxi
Copy link
Author

topaxi commented Jun 24, 2015

@TrySound double colon what?

@TrySound
Copy link
Member

@topaxi In example. Input and output are different.

@TrySound
Copy link
Member

@topaxi Sorry. Playground uses postcss-pseudo-elements.

@topaxi
Copy link
Author

topaxi commented Jun 24, 2015

@TrySound yes, this is the expected output for cssnext, ofc. this transformer should retain the double colon, doesn't really matter in this example though, the problem is the whitespace. Fixed the expected/actual.

@MoOx MoOx added the bug label Jun 29, 2015
@MoOx MoOx closed this as completed in 3883f71 Jun 29, 2015
@topaxi
Copy link
Author

topaxi commented Jun 29, 2015

Works, thx 👍

@stevenvachon
Copy link

The spec says that :matches() does not support pseudo-elements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants