W3C home > Mailing lists > Public > public-webapi@w3.org > December 2006

Re: capturing load events

From: Shadow2531 <shadow2531@gmail.com>
Date: Fri, 29 Dec 2006 02:16:33 -0500
Message-ID: <6b9c91b20612282316k21fa6a2dq97e497710368309d@mail.gmail.com>
To: "Hallvord R. M. Steen" <hallvord@opera.com>
Cc: "Bjoern Hoehrmann" <derhoermi@gmx.net>, public-webapi@w3.org, "Joao Eiras" <joao.eiras@gmail.com>

On 12/28/06, Hallvord R. M. Steen <hallvord@opera.com> wrote:
> On Thu, 28 Dec 2006 16:33:43 +0100, Bjoern Hoehrmann <derhoermi@gmx.net>
> wrote:
> > It also means that a
> >
> >   window.addEventListener('load', func, true);
> >
> > listener would never be triggered. Presumably that should be changed
> > to say that it would be triggered only if the event's target is the
> > Document. Do you see any problem with that?
> No, I agree it should change.

Been following these discussions and the reports.

So far, this is what I get out of everything:

1. window.addEventListener("load", func, false) should fire only one
load event with the target being the document.

2. window.addEventListener("load", func, true) should do the exact
same thing as #1.

3. Opera will have to change addEventListener() when used on a window
object to make #2 work the same as #1. (but perhaps not for userJS

4. Opera changing #2 to work like #1 will break some pages that are
properly using 'true'. Hopefully, the list is small and this fixes
more pages than it breaks.

5. 'true' will just be a dummy value when used on a window object (and
in essence, just mapped to 'false') to make some current pages work
that should really be using 'false'.

6. Instead of window.addEventListener("load", func, true),
document.addEventListener("load", func, true) will need to be used if
you really want capturing for the document.

Are those the rules we're shooting for?

Received on Friday, 29 December 2006 07:19:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:22 UTC