-
-
Notifications
You must be signed in to change notification settings - Fork 188
Playground sometimes gets confused #165
Comments
In the first tab I got this console warning: Warning: The selector ':--fizzbuzz' is undefined in CSS! But even if I repaste the same snippet, it's compiled wrong and a new warning appears, works fine in a fresh tab though... |
It might be related to the plugin. Maybe a memory issue. This is weird. |
Yeah, maybe I shouldn't browse with nightlies... I'll try to use a plain stable Firefox with a new profile for the playground for the next days and report if I can reproduce this. |
Okay I reproduced this now with the following code: @custom-selector :--foo .foo;
:--foo {
color: bar;
} After that, I type a new @custom-selector :--foo .foo;
@custom-selector :--bar .bar;
:--foo {
color: bar;
} If I now use Input: @custom-selector :--foo .foo;
@custom-selector :--bar .bar;
:--foo :--bar {
color: bar;
} Output: .foo {
color: bar;
} Tested in Firefox 38 and a completely new profile (no addons etc.) |
Mh weird, I'll try on other machines later this day. I can still reproduce this on my notebook on either Firefox or Chrome. Note: I can't reproduce this if I copy&paste the second custom-selector, if there is some debouncing, maybe I'm typing slower than you..? |
Ok I totally reproduced it. It seems the module that handle custom selectors have a weird memory management. |
Closing since the appropriate issue is opened on the right module csstools/postcss-custom-selectors#19 |
I'm not really sure when it happens, but sometimes the playground does weird things.
All I can say, I'm deleting the initial stuff and pasting in the new css.
Here side by side comparison:

Tested in Firefox 41.0a1
The text was updated successfully, but these errors were encountered: