3 ms·
The reason chrome was not supported earlier is probably because OWA possibly used some arcane and non-standard IE features that were lacking in chrome. Also AFA
by barista 14y ago
The reason chrome was not supported earlier is probably because OWA possibly used some arcane and non-standard IE features that were lacking in chrome. Also AFAIK it never blocked the OWA outright (by redirecting to some other url instead)
- CurtHagenlocher 14y agoMy specific recollection is this: On Ubuntu at home, I used Chrome for most things. But I specifically installed Firefox to be able to use the "better" version of OWA. OWA would still work on Chrome, but it would automatically downgrade to the less-capable version. Presumably, Chrome and Firefox were similar enough that the same code should have worked with both.
- disgruntledphd2 14y agoAdditionally, for years and years (until maybe two years ago) they did the same in Firefox, where you always got the less capable version that had no means to delete multiple emails at one. Man, that was annoying. That being said, screw you Google, this is not OK. Maybe its business, but its not right. Time to start destroying my Google profile with Ghostery et al.
- aphexairlines 14y agoOWA specifically redirects Chrome for Linux to an older, static-html version. You have to spoof Firefox for Linux or spoof Chrome for Windows in order to get the rich client UI.