support for /deep/ and ::shadow
See original GitHub issueWith custom elements landed in Chrome beta and shadow dom in Chrome stable, the need for ::shadow
and /deep/
syntax is becoming real. I don’t like the /deep/
syntax, it’s ugly as sin, but also rather important for overriding styling inside a shadow dom element, and right now less crashes when it encounters it, so: feature request for ::shadow and /deep/ support =)
Issue Analytics
- State:
- Created 9 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
What's the substitute for ::shadow and /deep/? - Stack Overflow
For something to replace ::shadow and deep that works now, use a style element inside your shadow root, with something like @import url(...
Read more >8 Benefits of Shadow Work and How to Start Practicing It
It takes training, self-awareness, guidance, and courage to help you face your shadow self in a healthy way. This is exactly why shadow...
Read more >Shadow Work Prompts Journal | Self Help Therapy Journal ...
A perfect journal for self-reflection and personal growth, filled with daily deep questions to ponder. Helpful. Report.
Read more >Shadow Work: Benefits, How To, Practices, & Dangers
Proponents of shadow work say it can help heal generational trauma, allow people to rethink the messages they send children in their life,...
Read more >Difference Between Shallow and Deep Foundation
Sources of main differences between deep and shallow footings are ... lateral support and resists uplift, is effective when foundation at shallow depth...
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 FreeTop 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
Top GitHub Comments
::shadow
is already supported (as well as any other::identifier
and:identifier(identifier)
stuff)./deep/
support may be too early since it’s actually a combinator and most likely they will change it to something like>>
or>>>
(for example earlier^
and^^
support has been added and now where are these draft combinators? Gone 😃. And meanwhile it’s always possible to generate whatever selector characters by escaping:I guess there’s nothing wrong with supporting a draft CSS feature in Less but not when the feature changes too often (yet).
Yes,
^^
is the old syntax and we don’t need to support it anymore (and^
too if I’m not mistaken).