-
Notifications
You must be signed in to change notification settings - Fork 50
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
CSS element > element selector is ignored #30
Comments
This occurs the same with the following .jewel.checkbox > input[type="checkbox"] { but seems the same as before |
What do you mean by ignored? Is it not in the output .css file or is it not taking effect? |
It's not in final App.css, if I change to for example .jewel.textfield .input {...} it appears. I'm for now using dot notation, but I think selectors [1] should be working right since are very needed in CSS. Right now I think we only support a subset of them. Thanks |
Are you sure your syntax is allowed? The documentation and examples seem to indicate that both sides have to be element names and not class names. |
Yes. That's allowed. I'm successfully using some CSS that looks like this:
However, this syntax does work for me when the namespace is: Carlos, can you confirm that this does not work? |
This seems to be working for me in the compiler test. Get the latest compiler and see if is better |
Hi, I tried but is not working for me. I'm sure I have the latest, since #31 is working now. I tried with something basic like Harbs proposed
And this is not in App.css btw, I was using
since the beginning. Maybe something around this is affecting this kind of rule. I'm trying to imagine what could be... |
I added the above to the compiler test case and it worked as expected. Post a test case or get the compiler's test case to fail. |
Maybe post the full css block? |
Hi, I think I see where is the problem. If I declare something in the final Application with or without a "dot" (i.e: .div or div), all goes ok. The problem is declaring in a library! when I tried to create that on a library, dot notation is ok but without dot (i.e: h1, div, span) all rules are always ignored in the final app css. Make this more sense now?, hope we could get to the end of this since is somehow blocking Thanks |
As I commented on #32 this fix solves all the problems. Thanks! |
Hi,
I'm finding another blocking problem with CSS compilation.
I have the following CSS rule:
.jewel.textfield > input {
...
}
this is ignored in the final App
(Note that other kind of selection like "> *" is working)
This is blocking and needed to continue with the theming effort, I'll try to use in the meanwhile a temporal selector to achieve the final results
The text was updated successfully, but these errors were encountered: