You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I've found that when I attempt to extend one of these "nested" selectors, it fails to compute correctly:
.foobar:extend(.testComponent-child) {}
I'm not sure if this is expected of the language, or not, but wanted to toss it out there to see if I should be doing something differently. I'd like to be able to extend these selectors without removing the convenience that "&" gives me when defining the selectors.
I often write "nested" selectors using the & to reference the base piece of the class (similar to BEM, SUIT, etc):
However, I've found that when I attempt to extend one of these "nested" selectors, it fails to compute correctly:
I'm not sure if this is expected of the language, or not, but wanted to toss it out there to see if I should be doing something differently. I'd like to be able to extend these selectors without removing the convenience that "&" gives me when defining the selectors.
I've put together a simple CodePen showing the issue here: https://codepen.io/joshlasdin/pen/GEYmzV
Thanks!
The text was updated successfully, but these errors were encountered: