Preact: Use of onInput in docs

[jakearchibald]

https://preactjs.com/guide/linked-state#linked-state-to-the-rescue

onInput is used to update state, but https://facebook.github.io/react/docs/forms.html recommends avoiding onInput and using onChange instead. Might be worth changing to onChange or adding a note to explain why onInput should be used despite React's advice.

[developit]

Good point, it's definitely a little under-explained. onInput is used because preact doesn't change the behavior of the DOM onchange event like React does. Instead, it encourages using the existing browser events under their existing names.

[pl12133]

A footnote in the "Differences to React" section might help clarify this. https://github.com/pl12133/preact-www/commit/ffa906b704cf52ee39d3a3d705d3188b0cf39de7

[developit]

@pl12133's change is published, but I think it might be worth adding a blurb to the Linked State page abount onInput as well.

[rubencodes]

Not sure I entirely understand—is this is a breaking change when switching from React? (e.g. if a user relies on behavior of onChange events, does this break?) If so would kindly suggest also adding a line about this under the Switching to Preact page :)

[developit]

Only if you're switching from React to Preact itself.
If you're using preact-compat, onChange behaves the same as React's.

[danedavid]

What should be done here ? Update the Switching to Preact page ?

[marvinhagemeister]

I think we can safely close this. On https://preactjs.com/guide/differences-to-react we have a section about relying on native events and not using an abstraction like react does.

[dandv]

@marvinhagemeister: which section is that? The "Synthetic Events" bullet under "What's missing?"?

I think that should be expanded upon, at least to recommend using onInput instead of onChange.