Manuel Strehl
Manuel Strehl
Sass allows variables to be marked with the [`!default` flag](http://sass-lang.com/documentation/file.SASS_REFERENCE.html#variable_defaults_default), which makes it easy to overwrite them when embedding the library. The second commit in this PR marks all of...
There is [postcss/postcss-selector-matches](https://github.com/postcss/postcss-selector-matches/blob/master/src/) that acts on `:matches()` selectors. It's much too sophisticated for what is needed here, but might be a good starting point. It might be a bit tricky...
Cf. https://web.dev/more-capable-form-controls/ , https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/formdata_event We should fire it [here](https://github.com/hyperform/hyperform/blob/ec790c62ca7cb517da638e6d02a0477e3f98c010/src/tools/catch_submit.js#L32) to be on par with native submits.
Cf. https://funwithforms.com/posts/submit-vs-requestsubmit/ and https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/requestSubmit. Polyfilling is useful, since it’s currently not supported in IE11 and Safari.
A freak bug, where `hyperform` was embedded in a module, and the JS file containing it was loaded again and again. Everytime `hyperform(window)` runs in the module, Hyperform cannot detect,...
Currently, `fieldset` has no `checkValidity` and related. That’s according to the [spec](https://developer.mozilla.org/en-US/docs/Web/API/HTMLFieldSetElement#Methods), which assigns them trivial return values. However, this sounds like tremendously useful methods to have. Think partially revealed...
Apparently, Chrome adds new form features, especially tailored for custom elements. The most promising to polyfill might be the `formdata` event. See https://web.dev/more-capable-form-controls
`console.log(element.validity)` should print an object with `badInput`, `valueMissing`, ... keys.
Work through the tests here: https://quirksmode.org/dom/forms/ and check, if we have to polyfill/fix/unify something.
Example: In `src/tools/format_dates.js` we call ``` return (date.toLocaleTimeString || date.toTimeString).call(date); ``` There we should perhaps add our knowledge of the requested locale from `hyperform.setLanguage()` calls. ``` date.toLocaleTimeString(get_current_language()) ``` with `get_current_language()`...