- From: David Levin <levin@chromium.org>
- Date: Tue, 24 Feb 2009 21:34:19 -0800
- To: public-webapps@w3.org
- Message-ID: <b902e34a0902242134i5837169if0e7789a65dd3b86@mail.gmail.com>
Just to round out the thread :), I fixed my test for IE and found that IE7 also throws an exception in this case. On Tue, Feb 24, 2009 at 2:23 PM, David Levin <levin@chromium.org> wrote: > I just got a Firefox nightly and found that it does throw in this case, so > the behavior changed from FF 3. > Also, I noticed that my test in IE didn't quite work. > > Dave > > > On Tue, Feb 24, 2009 at 11:51 AM, David Levin <levin@chromium.org> wrote: > >> Regarding the http redirect security violation steps, the spec ( >> http://dev.w3.org/2006/webapi/XMLHttpRequest/) says "If async is set to >> false raise a NETWORK_ERR exception and terminate the overall algorithm." >> I tried out IE7, Firefox 3, and WebKit nightlies and none of them seem to >> throw an exception in this case. >> >> Won't implementing the spec introduce a significant incompatibility? Or >> did I miss something? >> >> Thanks, >> Dave >> >> PS I'm asking because I doing a change in WebKit in this area. >> >> >
Received on Wednesday, 25 February 2009 16:26:55 UTC