In <485ceea9$> EMB wrote:
> Freesias wrote:
>> On Sat, 21 Jun 2008 18:26:48 +1200, sam wrote:
>>
>>>> All Web Applications should be browser agnostic, and should conform
>>>> to the published W3C standards.
>>>>
>>>>
>>> An intranet isn't the web
>>
>> If it uses a web browser, and if the pages are served from a web
>> server, then the application should conform to all published W3C
>> standards.
>
> Why?
I came across this blog entry just yesterday:
Apple's MobileMe drops support for IE 6
http://www.37signals.com/svn/posts/1...drops-support-
for-ie-6
Hardly shocking that Apple wouldn't support an old version of IE, but
the comments are more interesting.
~~~~~~
Lazlo 10 Jun 08
On the open web, IE is a ?web browser?. On tens of thousands of
intranets, IE is a ?web browser? and an application platform.
With Microsoft?s hearty encouragement, enterprise customers have spent
billions of dollars developing applications for that platform. Because
most of these applications were designed during the IE6 era (which
lasted over five years), and were written for a captive audience that
was guaranteed to have IE6 , they frequently rely on behaviors specific
to IE6 . Web-focused developers will sneer at this, but application
development isn?t web development. If you?re writing Mac applications,
you don?t ignore all the Mac-specific features and APIs available to you
on the off chance you might want to do a Windows version someday.
Along comes IE7 . It can?t peacefully coexist with IE6 so enterprise
customers have two options: stick with IE6 , or test/fix every app that
relies on IE to ensure that it works under IE7 . And the latter path
requires another choice: you either limit the fixes to stuff that works
in both IE6 and IE7 , or you get to deploy all the application changes
simultaneously, while deploying IE7 to every single desktop in the
entire organization at the exact same time. And if anything mission-
critical breaks as a result, you get to back it all out again. Every
last application, every last desktop.
Not a lot of orgs have hundreds of thousands/millions of dollars to burn
on development and QA just so they can have the exact same business
functionality on a slightly more up-to-date platform.
~~~~~~
Anonymous Coward 13 Jun 08
I can?t believe I work for one of the large corporations who are still
using IE6 (as standard), because some apps are not compatible with IE7 . ?
The crazy thing is, I can?t believe the software policy is to support a
particular browser (IE6) rather than web standards themselves.
When we finally upgrade to IE7 the software policy will be to support
IE7 . ? The problem will start all over again when IE8 is released ?
most likely breaking support for some sites written specifically for IE7 .
~~~~~~
--
Roger Johnstone, Invercargill, New Zealand ->
http://roger.geek.nz