This is preview!
I have not needed the functionality offered by the input event in most of the pages I've written, so it's not likely to be a universal need.
> I thought that this is exactly the kind of thing jQuery did - take something that was awkward and unwieldy and turn it into something much easier to work with
True, but that is also what jQuery UI and jQuery plugins do in general.
Wholeheartedly agree. For sure my biggest pet peeve of all web forms. Quite a different approach than the topic of this thread (and I don't mean to OT), but I feel like we've got a pretty good solution for this particular concern in our Mask widget, currently in development as part of jQuery UI:> such as the problem where so many (inc high profile) sites automatically move focus to the next field after you complete the current, but if you made a mistake then you can't shift+tab back into it.
I am not a fan at all of UI ideas like three fields for phone number where it automatically tries to advance the focus as you are typing, they end in sorrow regardless of the underlying browser technology. It's just a bad idea no matter what.
ondrop, or handling
valueproperty. I'd also expect it to break in Opera 10.x and lower for cut & paste. It also prevents shift+cursor key text selection.
Me either. Unfortunately, though, we don't get to decide on the behaviour of these sites. I've never been a fan of mask-as-you-type inputs either, to be honest, they break Ctrl+Z/Undo and come with a whole host of accessibility issues that never seem to get worked around. Much better to have a good validation plugin and, if you really want it, mask-on-blur.I am not a fan at all of UI ideas like three fields for phone number where it automatically tries to advance the focus as you are typing, they end in sorrow regardless of the underlying browser technology. It's just a bad idea no matter what.