W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2002

RE: Fixes needed (DOM L3 Events, CustomEvent)

From: Arnold, Curt <Curt.Arnold@hyprotech.com>
Date: Wed, 27 Mar 2002 16:56:55 -0700
Message-ID: <4D62A7266F41D611B92C00E018C1C19C0DD4DF@thor.aeathtl.com>
To: "'www-dom@w3.org'" <www-dom@w3.org>
Daniel Cazzulino wrote:

>2 - Interface CustomEvent: it says: "It is intented to be used by the DOM 
>implementation to access the underlying while ...". First, it should be
>"INTENDED", second, access the underlying WHAT?
>And regarding this interface, how is the DOM implementation supposed to
change the >currentTarget and phase attributes if they are readOnly in the
Event interface and >it doesn't have the CustomEvent methods? It seems to me
that all events must have >these two methods, or maybe the attributes should
be made read/write.

Definitely this section is filled with typos (how about the currentPahse
that appears later).

Current implementations of Events have private knowledge of how to change
the currentTarget and phase attributes of their events.  CustomEvent would
only be used when an event was not recognized as an internal event.

There are other missing pieces too, for example, there is no method for the
implementation to determine if stopPropagation() or preventDefault() was

In general, it is a dangerous thing to let anyone other than the
implementation write to currentTarget and eventPhase.  Though the prose says
that only the implementation should call it, there would be nothing
prohibiting a rouge script from holding on the the event and messing with
the phase and target at will.

It would seem a lot cleaner for CustomEvent to be part of the
implementation, created by DocumentEvent.createEvent("UserEvents") and allow
the caller to initialize it with an arbitrary object:

interface CustomEvent : Event {
    readonly attribute EventDetail detail;
    void initUserEvent(String eventTypeArg, boolean canBubbleArg,
		boolean cancelableArg, EventDetail detail);

Where EventDetail would be Object for most bindings.  Not quite as pretty to
use as adding your own event interface, but it should offer the same
capability with less issues.
Received on Wednesday, 27 March 2002 19:19:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:09 UTC