Brian Blakely

It's rather bizarre, what I have been able to find is that this bug seemingly only manifests when the field is wrapped in a ``. The official demo doesn't use...

It actually does work with any input element.

Thank you for your appreciation! Since this is intended a polyfill, I'm not likely to add features that aren't available to the native input[type="date"] spec. I'm sorry!

That is an interesting idea, to support more input type values. Will think about doing that this week! Thank you for the suggestion!

Note that this requires some refactoring in order to match the standard behavior, so it probably won't release for a bit.

This isn't possible right now. It should be added, but in the meantime you'll need to change the display value yourself: ```javascript const val = input.value.split(`-`); input.setAttribute(`value`, `${val[1]}/${val[2]}/${val[0]}`); ```

There must be something else happening; I tested this suggestion. Would you kindly send a demonstration of the issue?

Glad that worked! "Manual" usage will still land at some point.

This PR seems a little bit big for the description. Was this intentional?

Started to test this (in case no one else is working on it), but I have a question. This is vendor-prefixed in Blink, but not Edge/Gecko/Webkit. As such, should there...