Feedback

[twikito]

Feedback

[Twikito]

@LeaVerou Thanks so much for your feedback! 🙏

This library was initially thought for me to avoid writing always the same thing, and an excellent sandbox to improve my JS skills, and for my students for a first approach on writing interactible web pages without writing JavaScript.

Since your feedback, I've been focusing on improving the documentation, and I hope I've succeeded on this.
Please, tell me what you think of this new version of the documentation, hoping it will help you understand more easily what this library is about and how to use it.

About the API improvements, I think you're right on most of the suggestion. I will surely take care of more improvements and features.

Still, I have some questions:

Why do I need to run JS for a purely HTML API? This excludes a bunch of designers who aren't comfortable with JS. Just make the attributes work, automatically, at least for the bundle version. Use Mutation Observers to pick up new ones too. Provide manual control for people with demanding use cases.

What did you have in mind mentioning Mutation Observers?

All of these demos are very component-y. It would be nice to provide some declarative HTML syntax to turn them into a web component without writing JS!

Did you mean give the user the possibility to automatically create a reusable named component?

It would be nice if there was a way to make data-toggle-target relative to the current element, to avoid having to generate ids for repeated elements. Perhaps by the selector using & or :scope to represent the current element?

Yes, it could be great to give the parent or ancestor selector missing in CSS, but I don't really know how to do that the right way. Although, it will be probably possible in the next few months… hopefully.

Again, thanks very much for your feedback!

[LeaVerou]

What did you have in mind mentioning Mutation Observers?

Mutation observers can help you observe changes to the HTML, so your syntax can be reactive to changes, without user code needing to be tightly coupled to it. E.g. they change the value of an ETS attribute and you just pick up the change with no further action required

Did you mean give the user the possibility to automatically create a reusable named component?

Yes, an actual custom element. E.g. <my-fancy-switch>.