Welcome to WebmasterWorld Guest from 54.211.120.181

Forum Moderators: incrediBILL

Message Too Old, No Replies

Issue with iPod Touch browser

     
5:44 pm on Nov 2, 2011 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Feb 27, 2003
posts:746
votes: 0


I recently updated the presentation of some custom forums on my site, so that now they are using HTML5 as well as taking advantage of drop shadow and curved border css effects. Since making this change, however, a number of users accessing the forums from their iPod are complaining that typing in the textarea lags very badly, whereas it hadn't before I made the change.

There is no javascript applied to the textarea. It's not rich editor or anything special. Just a vanilla html textarea. I didn't actually make any change to it at all--as I said, I just changed the overall layout to HTML5 with some CSS3 effects.

The user agent of the affected iPods: Mozilla/5.0 (iPod; U; CPU iPhone OS 4_2_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8C148 Safari/6533.18.5


Any ideas? It seems like it's obviously a browser bug, but it's a bug I'd like to avoid triggering!
8:47 pm on Nov 2, 2011 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member lucy24 is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:Apr 9, 2011
posts:13266
votes: 363


Preliminary question: did you run the new html and css through the "mobileOK" validator? Some of what they tell you will be over the top (in particular, the iPad will take anything you throw at it and come back for more) but it gives a useful starting point.

[validator.w3.org...]
5:42 pm on Nov 4, 2011 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Feb 27, 2003
posts:746
votes: 0


Thanks, I wasn't aware of that validator. I changed from serving HTML5 to <!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.2//EN" "http://www.openmobilealliance.org/tech/DTD/xhtml-mobile12.dtd"> and users are reporting that it's functioning better now. I guess this device doesn't play nice with HTML5.