Generating wrong css for :after :before pseudo selectors
See original GitHub issue val reactTreeView = style(
&.before.after(
content := "g"
)
)
producing
.ReactTreeView_DefaultStyle-0001::after::before {
content: g;
}
adding ::
instead of :
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
CSS :before and :after not working? [duplicate] - Stack Overflow
I am trying to use :before and :after with list but it is not working. I am sure it's a simple mistake but...
Read more >7 Practical Uses for the ::before and ::after Pseudo-Elements ...
The core idea is to create a gradient over the image and use the CSS z-index property with a negative value. The negative...
Read more >before - CSS: Cascading Style Sheets - MDN Web Docs
In this example we will create a simple to-do list using pseudo-elements. This method can often be used to add small touches to...
Read more >CSS ::after / ::before applying to the wrong element
I'm trying to apply a floating shadow to the .gb-button element, by using the ::after pseudoelement, however no matter what I do the ......
Read more >Diving into the ::before and ::after Pseudo-Elements
In CSS, ::before and ::after are keywords you can add to a selector to create pseudo-elements. The pseudo-elements are inserted into the element ......
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 Free
Top 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
So according to the CSS3 spec we’re doing the right thing. I think this is fine. IE8 will be forgotten long enough 😀
If this becomes a big deal, reopen and we can discuss what to do. Else I’m happy to leave this as is.
@cretz Moving to #50 as we’ve moved off the original issue topic.