W3C home > Mailing lists > Public > public-webapi@w3.org > January 2007

Re: capturing load events

From: Shadow2531 <shadow2531@gmail.com>
Date: Mon, 1 Jan 2007 20:16:29 -0500
Message-ID: <6b9c91b20701011716x929a8al3076578d7c0a94b8@mail.gmail.com>
To: public-webapi@w3.org

On 1/1/07, Shadow2531 <shadow2531@gmail.com> wrote:
> Reference for TC: <http://lists.w3.org/Archives/Public/public-webapi/2006Dec/0127>
> So, it seems that:
> win cap (1) ([object HTMLImageElement])
> doc cap (1) ([object HTMLImageElement])
> win cap (1) ([object HTMLDocument])
> doc t+b (2) ([object HTMLDocument])
> win t+b (2) ([object HTMLDocument])
>
> is the way to go because it doesn't break the 'false' behavior and it
> allows 'true' to work as mosts sites intend. (Opera can produce that
> with the body -> document target fixes.)

Actually, "allows 'true' to work as mosts sites intend", would be an
error on my part as most sites intend 'true' to work like 'false'.

So, even if that was the right way to go, " win cap (1) ([object
HTMLImageElement])" should not be there if we consider  what sites
expect. It is not there in the Minefield/3.0a2pre btw. Also, the win
cap (1) ([object HTMLDocument]) has 2 for the phase as if 'false' was
used for the event listener.  (That basically makes 'true' do the same
as 'false' for window and 'load' in Minefield/3.0a2pre).

I also see that document.addEventListener doesn't work in
Minefield/3.0a2pre with 'false' .

So, assuming document.addEventListener with 'false' worked in
Minefield/3.0a2pre, the result would look like this:

doc cap (1) ([object HTMLImageElement])
win cap (2) ([object HTMLDocument])
doc t+b (2) ([object HTMLDocument])
win t+b (2) ([object HTMLDocument])

That result would be more like what sites expect even if it doesn't seem right.

-- 
burnout426
Received on Tuesday, 2 January 2007 01:16:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:56 GMT