Unreliable <input> value due to requestAnimationFrame

[evancz]

Context

By default we use requestAnimationFrame for all renders. This allows us to sync up with the natural refresh rate of the browser, which is particularly helpful for animations. It also means that DOM updates are made asynchronously.

Problem

If you type really fast, you can actually change the value of an <input> before Elm has a chance to process things. This can lead to dropped keystrokes right now.

Reports

• Jumping cursor on fast typing - https://github.com/elm-lang/html/issues/105
• Filtering content in Elm does not work - https://github.com/elm-lang/html/issues/42
• Dropping characters with fast Japanese typing - https://github.com/elm-lang/html/issues/62

Possible Solution

It may make sense to have a special kind of on primitive that forces a synchronous render. This could also be useful for capabilities that are only available on the event cycle of a user interaction (e.g. https://github.com/elm-lang/html/issues/130)