W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2008

RE: <Further LC Followup from IE> RE: Potential bugs identified in XHR LC Test Suite

From: Zhenbin Xu <Zhenbin.Xu@microsoft.com>
Date: Thu, 19 Jun 2008 14:19:10 -0700
To: Ian Hickson <ian@hixie.ch>
CC: Sunava Dutta <sunavad@windows.microsoft.com>, Web API public <public-webapi@w3.org>, IE8 Core AJAX SWAT Team <ieajax@microsoft.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <72F767ADE7C63540BE69CD2722A41F440E9C93E11F@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>

I think we are now off track.

Nonetheless we should realize that customer cannot
write an interoperable page with my fictional home grown browser if it doesn't exist
or doesn't have the needed feature when the page was written.  I doubt customers
would write against particular browser if equal efforts can results in interoperable
solutions run on top multiple browsers.  Now that the solutions are in place, they
deserve our consideration.

I would argue it is important to think about customer's migration path when we design
new feature or standardizing existing ones.  Otherwise we would be painting customers
into corner and blaming them for their dilemma.

> -----Original Message-----
> From: Ian Hickson [mailto:ian@hixie.ch]
> Sent: Wednesday, June 18, 2008 9:48 PM
> To: Zhenbin Xu
> Cc: Sunava Dutta; Web API public; IE8 Core AJAX SWAT Team; public-
> webapps@w3.org
> Subject: RE: <Further LC Followup from IE> RE: Potential bugs
> identified in XHR LC Test Suite
> On Wed, 18 Jun 2008, Zhenbin Xu wrote:
> >
> > In the case there isn't clear technical differences, I don't think we
> > should pick the right solution based on implementer's cost. Rather We
> > should base it on customer impact. A bank with 6000 applications
> built
> > on top of IE's current APIs simply would not be happy if some
> > applications cannot run due to changes in some underlying object
> model.
> > And this is not IE's problem alone since the bank simply cannot
> upgrade
> > or change the browser, if all other browsers result in the same
> > breakage.
> For non-Web HTML pages like in this example, solutions like IE's "IE7
> mode" are fine. IMHO we should be concentrating on pages on the Web,
> not
> on browser-specific pages -- interoperability isn't relevant when the
> page isn't intended to run on multiple browsers.
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.
> fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._
> ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-
> .;.'
Received on Thursday, 19 June 2008 21:19:41 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:10 UTC