tag:blogger.com,1999:blog-3411749392293107623.post1849050971582674286..comments2013-04-13T13:01:23.167+01:00Comments on Mobile-Driven-Cerise: Dodgy double input fields on AndroidUnknownnoreply@blogger.comBlogger9125tag:blogger.com,1999:blog-3411749392293107623.post-46264587501832388652013-04-13T13:01:23.167+01:002013-04-13T13:01:23.167+01:00hi frd input {
-webkit-user-modify: read-write...hi frd input {<br /> -webkit-user-modify: read-write-plaintext-only;<br />}<br />coding working well scrolling not working <br />chrisjulhttps://www.blogger.com/profile/05399459463707837220noreply@blogger.comtag:blogger.com,1999:blog-3411749392293107623.post-63680713195087163392013-04-13T12:37:42.677+01:002013-04-13T12:37:42.677+01:00am also same problem am using type="number&qu...am also same problem am using type="number" text box overly plz help me send me the code to my mail id christopher.jul@gmail.comchrisjulhttps://www.blogger.com/profile/05399459463707837220noreply@blogger.comtag:blogger.com,1999:blog-3411749392293107623.post-72028610950267944892013-04-09T17:13:59.713+01:002013-04-09T17:13:59.713+01:00Thank you for the foot work. This lead me down the...Thank you for the foot work. This lead me down the right path. I was having a similar issue with a 2.3.4 Bionic device. In my particular case I had to find the "acceptable" div element (I'm using a template system with a bloated UI framework so there wasn't just 1 div).Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3411749392293107623.post-44457978761172695472012-11-14T20:58:36.876+00:002012-11-14T20:58:36.876+00:00Just found this bug today on Android 2.3.5 (i will...Just found this bug today on Android 2.3.5 (i will let you know if I found a fix) finger cross.Yeneneh Mulatuhttps://www.blogger.com/profile/06832845808581895073noreply@blogger.comtag:blogger.com,1999:blog-3411749392293107623.post-13010381217052369562012-07-19T12:36:55.987+01:002012-07-19T12:36:55.987+01:00first change your blog background for good readabi...first change your blog background for good readabilityAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3411749392293107623.post-12217629905178030702012-07-04T08:37:45.311+01:002012-07-04T08:37:45.311+01:00Awesome! Putting it in the container field didn...Awesome! Putting it in the container field didn't work for me, but applying it directly to the element worked well. It even got rid of an annoying bouncing effect that shows up when you type. THANKS!Johnhttps://www.blogger.com/profile/14773718035690264062noreply@blogger.comtag:blogger.com,1999:blog-3411749392293107623.post-73431251250579510952012-05-30T18:52:22.929+01:002012-05-30T18:52:22.929+01:00i have the same problem.. it seems that the proble...i have the same problem.. it seems that the problem is in the margin-top and bottom. but who can develop without those? i dont have a good solution yet.. hope it will come soonRemcohttps://www.blogger.com/profile/06097452197732893963noreply@blogger.comtag:blogger.com,1999:blog-3411749392293107623.post-38969375172533878232012-04-19T20:23:50.061+01:002012-04-19T20:23:50.061+01:00I tried this with my app, but it actually made the...I tried this with my app, but it actually made the problem worse.<br /><br />Earlier I was only seeing this on Android 4.0 browsers, but never on earlier androids. So my solution was to switch contentEditable divs instead of inputs for platforms that support contentEditable. That solution was a much better experience. But for pre ICS androids you have to use the input fields. I haven't figured out how to counter this on those platforms.Jasonhttps://www.blogger.com/profile/10425130813214963146noreply@blogger.comtag:blogger.com,1999:blog-3411749392293107623.post-32201259593775942612012-03-30T09:54:06.278+01:002012-03-30T09:54:06.278+01:00I couldn't get it to work. I still get the ove...I couldn't get it to work. I still get the overlay but only in the password input field, and not on the text input field and am running out of ideas.Defenderhttps://www.blogger.com/profile/02550598453779166304noreply@blogger.com