Getting Google to Work with Opera
The real shame is that almost every problem in Google’s services results in Google’s stuff being coded specifically for the mistakes other browsers have. Yes, Google needs its stuff to work more importanly in IE and Firefox, but coding for quirks of those browsers means your stuff is always going to have problems with alternative browsers and future browsers, especially if you have zero fallbacks for standards-compliant browsers.
a description of what the script does
warns the user to Mask as IE
simply makes the “browser not compatible” notification to go way
simply overrides bad browser sniffing
many issues related to bad object detection
Apparently, before being acquired by Google, Writely was a model of browser compatibility, and since Google picked it up, not so much. Shame.
In this thread’s case, the severe shortness of a script that fixes all functionality issues with Google docs, Google spreadsheets, Picasa, and Google calendar should be telling. That Google, one of the biggest companies around can’t find the time to test in Opera is shocking; that one man working alone can write an 140 line (including comments) script consisting of a handful of simple fixes should reflect far, far worse on Google than it does on Opera. Especially when you consider that they somehow find the time to work past IE innumerable flaws.
It’s not like Google doesn’t care. According to Opera Watch, some of their teams work hard with Opera to make sure things work. Problem is, then you have Google Page Creator, “which flooded the code with a enormous amount of browser quirks usage, or using Mozilla or IE’s bugs as features”.
(via Download Squad)