On Safari/node setInterval does indeed exhibit the same issue so this is
not a bug in Elms core. However Elm does have an opportunity to smooth this
inconsistency out.
What I have done so far to mitigate this issue is essentially what you
describe. I have experimented with a couple of different
I have been using Time.every for a project that requires ticks at a
constant interval. I found that different platforms drift by varying
amounts. Some platforms seem to oscillate around the desired 0 millisecond
drift. This is acceptable for my use case. However some platforms
constantly increa
You should read this article to see why existing solutions generally do not
work very
well: https://medium.engineering/why-contenteditable-is-terrible-122d8a40e480
I am pretty sure draft.js has a good underlying data model that copes with
mapping to the DOM well. Perhaps looking into how that w
I have just been thinking the exact same thing over the past couple of
days.
If you wanted to keep compatibility with older browsers this could also
just be a function that takes a value and a node style callback:
Elm.Main.ports.apiSession = function (value, cb) {
var sess = localStorage.get
