March 20th, 2011, 03:23 PM
|
#1 (permalink)
|
|
New Member
Thread Author (OP)
Join Date: Feb 2011
Location: P-Burgh
Posts: 10
Device(s): Le Sigh, Moto Droid » Droid Inc » Fascinate » Evo 4G » Epic 4G (stoked)
Carrier: Not Provided
Thanks: 2
Thanked 1 Time in 1 Post
|
Potential Google Body/Browser Workaround
Hey guys 2 day owner, TnT user, love it entirely except for the viewing angles. (Would an anti-glare screen protector help?)
Anyway, I digress...last night I tried navigating to Google Body on the web, and was informed that a WebGL browser was necessary to do so. I proceed to the Market and download Firefox at this point and then install the add-on "Phoney," which allows one to change their UA String to "Firefox Desktop." So I navigate back to Google Body and it actually loaded, well kind of. The menu bars displayed and the model partially rendered but after that Firefox derped so hard I had to call OSHA. My system rebooted and I tried again, same result.
So here is where I am at with this...
1. Firefox Mobile derps...a lot, usually not this hard though.
2. Does this mean that a stronger browser made to "look" like Firefox could potentially run Google Body?
3. Does anyone know of any browsers with a "Firefox UA String?"
|
|
|
Last edited by RedBear'n; March 20th, 2011 at 03:26 PM.
|
|
