Bug in 0.17 - value function isn't setting inputs value as it did in 0.16 about html HOT 3 CLOSED

Am I right that it's only happening if the input is focused and not readonly?
Here is a modified example: https://gist.github.com/gdotdesign/f2dcb32b5b2843452876f89d5d303094

from html.

I missed the conversation about this on #elm-dev yesterday. The most likely reason I would need this (or some other equivalent) is to clear the value of an input after a form submit, for example If I had a chat app, and I had an input used to key the message, I'd need some way of clearing the input value after the message was submitted.
I think @rtfeldman suggestion would work good:

tl;dr value is innately buggy and should probably be replaced by defaultValue + setValue

I'm not sure I like removing the value function (attribute), as it reduces elm-html parity with html. Maybe keep value, with bold guidance to consider the alternative (whatever that might be).

From a perf stand point: I see how this might make perf testing look worse but I'm having a hard time seeing how this would result in perf issues in most real scenarios.. Might be short sighted on my part.

from html.

I did a fix for this in elm-lang/virtual-dom@4be12eb

from html.