Unkeyed input caution.

I find the following dev-mode warning puzzling: UNKEYED_INPUT: Unkeyed <input> detected. Consider adding a name, id, _key, or _ref attr to avoid accidental DOM recycling between different <input> types.

Could you offer a bit of background as to why this is (may be) an issue, please?

Particularly, I am finding it’s hard artificially come up with a key for all inputs, it’s unnatural to need to do so, and it’s extremely easy to forget to do so if you don’t need a key for other reasons (which, to date, I’ve never had). It seems like, on the surface, DOMVM should not try to recycle input elements if they are internally problematic.

[leeoniya]

one option would be to only show the warning for inputs/textareas/selects whose vnodes do not explicitly set the value or checked. this would make the warnings less chatty. you could still run into the focus problem, but at least you won’t have a wrong untracked value transfered into a recycled input, which is far more serious,

maybe.

[leeoniya]

I still don’t like “recycling” to refer to this mechanism

js is filled with reinvented terminology for old shit rather than adopting what already existed. polyfills? they’re called “shims” literally everywhere else.

i added the rest of the input family to the warning list in https://github.com/leeoniya/domvm/commit/69ed88538db9dae47524d1a578f85602f5b80cc1