Bug with data-toggle-class-on-target

[twikito]

Bug with data-toggle-class-on-target

[Twikito]

Hey @jenstornell 👋

Well, I understand what happens here. When you set data-toggle-is-active on a trigger, I do not toggle but add classes. So here, you will have the two classes flex hidden on the first panel, and so, when you click on another trigger, those two classes are toggled, so removed, and the default display value is kept. Logical.

Actually, that's why I said in the documentation:

In this case, you should add the specified class name on each element, even if the script will check that for you.

In your example, I guess you should only toggle the flex class, so set data-toggle-class-on-target="flex", and it works.

But well… your example makes me think. Maybe I should really toogle classes instead of adding them for triggers that are active by default.
What do you think?

[Twikito]

Hey @jenstornell 👋

I thought about this a little bit longer, and it came to me that since we are now able to toggle as many classes as we want, the adding instead of toggling classes on active by default triggers doesn't make sence anymore.

I will change that behaviour.

[Twikito]

Hey @jenstornell 👋

It's now fixed! Using data-toggle-is-active attribute to set a trigger and its targets as active by default will toggle them once on initialization as a consequence.

More information here: https://github.com/Twikito/easy-toggle-state/releases/tag/v1.15.0