Support

Winden values ​​with ! + other bugs

Publish date: 04/27/2024 •  Bug • Winden •  thiago souza

Hey guys,
 
  Winden is not working with negative or inverse values ​​when using “!”
 
 Ex: hover:!bg-black.  Winden does not recognize this markup if CDN cache is active, so it is not generating the markup.
 
 Autocomplete does not recognize group-hover: nor rounded, you have to type completely.
 
 Sometimes when selecting a class with autocomplete it doesn’t work, it crashes and sometimes overloads the browser, this didn’t happen before, it started after this last update.
 
 -950 color variations are not recognized.
 
 
 Using winden in this new look of the classes that shows the classes separated in a box at first seems to be good, but compared to the old format that only showed the text and autocomplete working today I see that before it is more productive, it is faster to add, editing and deleting classes, in this new format it seems to take longer, as you need to click on classes to remove or click to edit, autocomplete does not seem to work very well, when editing classes with hover: it adds hover: 2x.  Would it be possible to add an option to return to the old format of writing classes?

 

 

 

 

 

 

Uploaded files:

  • support says:

    Thanks for reaching us :
    1. The important ! class should be !hover:bg-black instead of hover:!bg-black

    2. Group Hover we will see what is the issue as this is already have been worked on with latest update. Maybe there are some places remaining.

    3. Are you using only tailwind classes, or there are more classes from builder as well?Which builder are you using? We didn’t have any lag issues when we tested, maybe we missed some specific cases, can you provide a login so that we can test further?

    4. Can you please more about negative classes, -950 color variation, is it s a custom class/color ?

    5. The new Winden UI with tags options allowed us to use plain classes natively in the builder without any hack, so I’m afraid we will get back to the old hacky method. But We will try to improve this one to whatever possible.

    Regards,
    Mohammad Arshad
    DPlugins Support

  • thiago souza says:

    Hi, Arshad,

    1. The important thing!, it must be hover:!class, I have used this method before and so much so that in the bricks editor it works correctly, but on the front it is not displayed, which leads me to believe that it is not generating the correct class.

    3. I went back to Swiss knife and the browser stopped crashing, I’m using Bricks and I use Firefox.

    4. this 950 is the color variations, before tailwind had up to 900 now it has 950, this 950 variation does not appear in autocomplete.

    5. This new format is not bad, I just think that just typing as before is much more practical, but that depends on taste, so it’s not a complaint, it’s just an option for the end user.

    Thank you very much for your attention.

  • support says:

    Can you please check with the Winden 2.0.4, if the above issue is solved ?

    Regards,
    Mohammad arshad
    DPlugins Support

  • thiago souza says:

    Hi Arshad,
    It was corrected, yes, it was updated with a new option that appears more buggy.
    But it was corrected, yes,

    Thank you for your attention,

    • support says:

      Can you please explain what buggy thing you faced now, because we are going to release a new update, and if it is related to our plugin, then we would like to solve that….

      Regards,
      Mohammad Arshad
      DPlugins Support

      • thiago souza says:

        A copy and paste button was added, I don’t know why as it is used it generates copies of these buttons below the painclass text box.
        I’ll try to edit this post with an image to make it clearer what I’m talking about.

  • thiago souza says:

    I edited this call and added an image to make it clearer.

    Grateful for the attention,

Leave a Reply