Skip to content
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.

Custom Selectors sometimes generate REALLY unexpected output #178

Closed
awayken opened this issue Jul 2, 2015 · 5 comments
Closed

Custom Selectors sometimes generate REALLY unexpected output #178

awayken opened this issue Jul 2, 2015 · 5 comments

Comments

@awayken
Copy link

awayken commented Jul 2, 2015

I don't really know to explain this one except by example. It may be related to #177, which I just submitted, but it also might be unrelated.

Input:

@custom-selector :--buttons button, input[type="button"];
@custom-selector :--hovers :hover, .hover;

:--buttons:--hovers {
    background: color(#ff9800 shade(20%));
}

button:--hovers,
input[type="button"]:--hover {
    background: color(#ff9800 shade(20%));
}

Output:

:hover:--hovers,
.hover:--hovers {
    background: rgb(204, 122, 0);
}

:hover,
.hover
input[type="button"]:hover,

input[type="button"].hover {
    background: rgb(204, 122, 0);
}
@topaxi
Copy link

topaxi commented Jul 2, 2015

Duplicate of #163 and csstools/postcss-custom-selectors#19 and #177

@awayken
Copy link
Author

awayken commented Jul 2, 2015

@topaxi Since this ticket (and #177) do seem related to the postcss issue, do we keep them open until that task is completed and we can test that these examples work as expected? Or do we close these as duplicates?

@topaxi
Copy link

topaxi commented Jul 2, 2015

@awayken that is up to the maintainers of cssnext i guess :)

@awayken
Copy link
Author

awayken commented Jul 2, 2015

@topaxi All right. I'll leave my tickets as submitted for now, and I'll subscribe to the postcss ticket to get updates on progress.

@MoOx
Copy link
Owner

MoOx commented Jul 3, 2015

Please follow #163.

@MoOx MoOx closed this as completed Jul 3, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants