If you preventDefault() in touch event listeners, e.g. so that you can have custom handling of gestures without screen moving around or resizing, the keyboard cannot be activated any more by setting focus() to some input element. What is that obsession in iPhone Safari with protecting keyboard, of all things, from application access, so that only a physical tap (synthesized click events don't work) can set focus and activate keyboard? The software on the server, which provided the application in the first place, is already handling whatever keyboard input comes in or making up its own if it wishes to do so, anyway.
Further, how exactly does the restricting of focus() and kbd activation to mouse listener but not allowing it to touch event listener, make system safer at all? What kind of scenario one would have to contrive to make such design flaw (and hoops it forces developers to jump through) look like a "feature"? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
