use <auto-tune> instead of <autotune>

[Kilian]

Sorry for a pretty bike-shedding ticket, but a small improvement would be to use <auto-tune> instead of <autotune>. The latter is an unknown html element and thus invalid, but the former is a custom element, so compliant :)

[dvdsgl]

Interesting! Would you mind making a PR?

[dvdsgl]

Maybe autotune-experiments>? I don't want to hyphenate "autotune."

[Kilian]

PR is no problem! autotune-experiments is pretty long though? A somewhat default for custom elements is to prepend them with x- to work around this, that would make it <x-autotune> (e.g. https://x-tag.github.io/) or maybe <autotune-block>? Your call ;)

[Kilian]

Additionally, maybe prefix the autotune attributes (autotune and autotune-class) with data- to make them custom attributes.

Edit: You already do! Then just lead with that in the README.

[dvdsgl]

What is the consequence of using invalid tags? I don't like that we're doing it but it's so easy to read!

x-autotune looks great.

[Kilian]

No real consequences. Validators and strict parsers will complain, browsers will happily accept unknown elements. Same for attributes.

But, with custom element you could add more behaviour directly to the element using the custom elements api, potentially offloading a bunch of your code to browser native stuff. With custom attributes, you can use browser api's like dataset to make your live as a developer easier.

one PR for x-autotune coming up :)