Comments on: Safari on the iPhone update fixes and breaks events

By: Adam McIntyre

Adam McIntyre — Fri, 03 Aug 2007 17:37:31 +0000

This is exactly the same behavior — and fix — given by IE 6′s (haven’t checked 7) onpaste event. It’s a really odd bug in implementation; how did this stuff make it through testing?

By: Joshua Giese

Joshua Giese — Fri, 03 Aug 2007 16:20:57 +0000

I hope that apple will fix this and some of the other stability issues in safari in their next release

By: justin

justin — Fri, 03 Aug 2007 13:17:43 +0000

Nice work around thanks.

By: Paolo Montrasio

Paolo Montrasio — Fri, 03 Aug 2007 09:14:34 +0000

No regression tests at Apple or an incomplete test suite. I’d like to bet on the latter and hope they read Ajaxian :-)

By: Michael Geary

Michael Geary — Fri, 03 Aug 2007 08:59:07 +0000

Some things never change. For 20 years, the classic cure-all for Windows timing problems has been the moral equivalent of setTimeout( fn, 0 ):

PostMessage( my_hwnd, MY_MESSAGE, 0, 0 );

By: arnaud

arnaud — Fri, 03 Aug 2007 08:20:03 +0000

Some time ago, I have also to use this trick on IE6.
The problem was not easily repoducible and occured only when the user was entering some text very quickly.
But it was the same issue: the text.value was not yet updated just after the last event.