Manuel Strehl

Connected with #6, where we need that functionality anyway for clean radio button support.

But the value can be empty. The [WHATWG spec](https://html.spec.whatwg.org/multipage/input.html#radio-button-state-(type=radio)) actually loses some words about that. So basically, this: ```html Select one Maccharoni Cheese ``` is, from a validation point of...

Plans, yes. Time, no :cry:. The idea is to replace the ["High-Level API" document](http://hyperform.js.org/docs/high_level_api.html) with a more structured approach: Which configuration parameters are possible, which methods do `hyperform` and the...

Note to self: Don't forget to document the hooks infrastructure.

Thanks for the issue, and sorry for the delay in answering it! Yes, at the moment this is by design to keep as close to the spec as possible. (There's...

Hi Geoff, thank you for the feedback! I see the problem, but unfortunately that’s based on a misconception. The `valid`/`invalid` events are strictly per-element events. You see in the console,...

Let’s see... No, there is no internal bookkeeping of the state of single input elements, but you could create that quickly yourself (ES6 needed, though): // assuming `form` to be...

I'm not against such a feature (and implemented things like that myself several times), but what would be a rule that one could add, and that cannot be built with...

Most interestingly, Firebug and the JSBin console _do_ display the enumerables.

Reading that article was in fact one of several reasons why I started Hyperform :) If you take a look at the accompanying [CSS file](../blob/master/css/hyperform.css) it does something similar, but...