On Thu, 30 Aug 2012 00:16:56 +0200, Boris Zbarsky wrote:
On 8/29/12 6:11 PM, Ian Hickson wrote:
Documents that are
aborted do not need to work, they were aborted precisely because they
don't need to work and are no longer needed.
Or because once again some ad was taking forever to load and t
On 8/29/12 6:11 PM, Ian Hickson wrote:
Documents that are
aborted do not need to work, they were aborted precisely because they
don't need to work and are no longer needed.
Or because once again some ad was taking forever to load and the web
page developer is doing all their stuff from onload,
On Fri, 15 Jun 2012, Henri Sivonen wrote:
> On Tue, Jun 12, 2012 at 1:46 AM, Ian Hickson wrote:
> > When a document is aborted the state is more or less left exactly as
> > it was when it was aborted. This includes the readiness state. It also
> > means no events fire (e.g. no 'load', 'unload',
On Tue, Jun 12, 2012 at 1:46 AM, Ian Hickson wrote:
> When a document is aborted the state is more or less left exactly as it
> was when it was aborted. This includes the readiness state. It also means
> no events fire (e.g. no 'load', 'unload', or 'error' events), a number of
> scripts just get a
On Fri, 30 Mar 2012, Henri Sivonen wrote:
> On Fri, Jan 13, 2012 at 2:26 AM, Ian Hickson wrote:
> > Jonas is correct. Since there was no interop here I figured we might
> > as well go with what made sense.
>
> I'm somewhat unhappy about fixing IE-introduced APIs to "make sense"
> like this. The
On Mon, Apr 23, 2012 at 4:55 AM, Henri Sivonen wrote:
> On Mon, Jun 20, 2011 at 3:10 PM, Jonas Sicking wrote:
>> On Mon, Jun 20, 2011 at 4:26 AM, Henri Sivonen wrote:
>>> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1039
>>>
>>> It says "complete" in Firefox, "loading" in Chrome a
On Mon, Jun 20, 2011 at 3:10 PM, Jonas Sicking wrote:
> On Mon, Jun 20, 2011 at 4:26 AM, Henri Sivonen wrote:
>> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1039
>>
>> It says "complete" in Firefox, "loading" in Chrome and Opera and
>> "uninitialized" in IE. The spec requires "com
On Tue, Apr 3, 2012 at 4:39 AM, Henri Sivonen wrote:
> On Mon, Apr 2, 2012 at 11:29 AM, Jonas Sicking wrote:
>> Everyone returning the same thing isn't the only goal. First of all
>> what's the purpose of all browsers doing the same thing if that same
>> thing isn't useful?
>
> No one is worse of
On Mon, Apr 2, 2012 at 11:29 AM, Jonas Sicking wrote:
> Everyone returning the same thing isn't the only goal. First of all
> what's the purpose of all browsers doing the same thing if that same
> thing isn't useful?
No one is worse off and stuff works even if an author somewhere relies
on a craz
On Mon, Apr 2, 2012 at 12:12 AM, Henri Sivonen wrote:
> On Fri, Mar 30, 2012 at 8:26 PM, Jonas Sicking wrote:
>> On Friday, March 30, 2012, Henri Sivonen wrote:
>>>
>>> On Fri, Jan 13, 2012 at 2:26 AM, Ian Hickson wrote:
>>> > Jonas is correct. Since there was no interop here I figured we might
On Mon, Apr 2, 2012 at 10:12 AM, Henri Sivonen wrote:
> Gratuitously changing features introduced by IE does not help authors
> one day have to
...when they have to...
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Fri, Mar 30, 2012 at 8:26 PM, Jonas Sicking wrote:
> On Friday, March 30, 2012, Henri Sivonen wrote:
>>
>> On Fri, Jan 13, 2012 at 2:26 AM, Ian Hickson wrote:
>> > Jonas is correct. Since there was no interop here I figured we might as
>> > well go with what made sense.
>>
>> I'm somewhat unha
On Friday, March 30, 2012, Henri Sivonen wrote:
> On Fri, Jan 13, 2012 at 2:26 AM, Ian Hickson >
> wrote:
> > Jonas is correct. Since there was no interop here I figured we might as
> > well go with what made sense.
>
> I'm somewhat unhappy about fixing IE-introduced APIs to "make sense"
> like th
On Fri, Jan 13, 2012 at 2:26 AM, Ian Hickson wrote:
> Jonas is correct. Since there was no interop here I figured we might as
> well go with what made sense.
I'm somewhat unhappy about fixing IE-introduced APIs to "make sense"
like this. The implementation in Gecko isn't particularly good. When
t
On Mon, 20 Jun 2011, Henri Sivonen wrote:
>
> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1039
>
> It says "complete" in Firefox, "loading" in Chrome and Opera and
> "uninitialized" in IE. The spec requires "complete". readyState is
> originally an IE API. Why doesn't the spec re
On Mon, Jun 20, 2011 at 4:26 AM, Henri Sivonen wrote:
> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1039
>
> It says "complete" in Firefox, "loading" in Chrome and Opera and
> "uninitialized" in IE. The spec requires "complete". readyState is
> originally an IE API. Why doesn't the
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1039
It says "complete" in Firefox, "loading" in Chrome and Opera and
"uninitialized" in IE. The spec requires "complete". readyState is
originally an IE API. Why doesn't the spec require "uninitialized"?
(The implementation in Gecko is
17 matches
Mail list logo
