I have a few different divs with text fields sliding in/out and have never had any issues with them. How are you calling up the sliding code to bring the div in? Does it seem like the sliding code is triggered when clicking on the field, or does it feel more like a bug in Safari? Do you have a URL we could check it out at? -=R
On 9/3/07 8:41 AM, "Tobias Kask" <[EMAIL PROTECTED]> wrote: > I've found another issue (that might not be new for you though): > I'm using javascript (mootools) to make a div slide onto the screen when the > user clicks a button. This div contains, among other things, a text field > input. However, when the user clicks this input field the iPhone automatically > slides back the div, leaving a text marker floating in the middle of the > screen where the text area was supposed to be. Keyboard input in this state > does nothing. > > Has anyone seen anything similar? Any ideas on how to work around this? > > regards, > Tobias Kask > > > On 9/3/07, nroose < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > wrote: >> >> I have noticed a bug on the iPhone. It occurs when a web page has a >> select field with the "multiple" attribute set and the first option is >> not supposed to be selected by default, and the iPhone selects it by >> default anyway. >> >> Here is the page: http://208.187.217.149/ims.htm >> <http://208.187.217.149/ims.htm> >> >> Here is the code: >> >> <html><title>iPhone Multi-select bug test<body> >> This page is for testing of the iPhone multi-select bug. The first >> two entries are set to be unselected. The third is set to be >> selected. iPhone selects the first and third. >> <form> >> <select name=x multiple> >> <option value='notselected1'>Not Selected 1</option> >> <option value='notselected2'>Not Selected 2</option> >> <option value='selected' selected>Selected</option> >> </select> >> </form> >> </body> >> </html> >> >> Perhaps this is not important to most web sites, since the multiple >> attribute is not used often, but it does matter to me. I thought >> perhaps I could put a disabled option first, and that would help, but >> apparently that is another iPhone bug - the disabled option is not >> disabled. >> >> >> >> >> >> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
