Android Community Forums - View Single Post - Browser AJAX Is Crippled For Rich Text Editing...Why?
View Single Post
  #1  
Old 11-16-2008, 03:41 PM
XerxesQados XerxesQados is offline
XerxesQados is completely purple. All over his body.
Smoke signaler
 
Join Date: Nov 2008
Posts: 30
XerxesQados is on a distinguished road
Default Browser AJAX Is Crippled For Rich Text Editing...Why?

I decided to check out Google Docs on my G1 to see if it was a viable solution to the "no office suite" problem. Apparently, it defaulted to the mobile version of the site, which allowed you to read all your documents but make no changes.

I was all prepared to ask how one could force the browser to go to the normal, functional version of Docs as opposed to the mobile version, but then I went to Zhura (which is a Google Docs-like service for screenplays and scripts, complete with Gears support) and discovered why. I went to edit a script and the entire page displayed flawlessly. However, no matter how many times I tapped on or trackballed in the direction of the big text box, it would not select.

I have to wonder, what's the big issue with rich text boxes on the web with the Android Browser? Are they really that big of a drain on resources? If the browser can stream all the interfaces and gets 72/100 on Acid3 (which is a ridiculously higher score than the Docs-compatible IE8, and IE7's score isn't even legible), I don't see why it can't do Google Docs and other sites' rich text boxes.
Reply With Quote
Ads