RE: Window Modes todo

Adding WWW-DOM to widen the audience a bit.

>>  Having the attributes not be read only and allowing their modification before the Event is dispatched seems better to me.  But changing this for DOM Events in general seems like a larger issue for discussion.

Note that this is how it works in IE at the moment. It may be possible to make a change here for DOM L3 events, but we should take care as this would be a substantial change.

-----Original Message-----
From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Cameron McCormack
Sent: Thursday, July 16, 2009 7:03 PM
To: Robin Berjon
Cc: public-webapps@w3.org
Subject: Re: Window Modes todo

Robin Berjon:
> To be honest, I'm not entirely certain of the value in enabling user
> script creation of these events — but I guess that's another matter.

Sure.

> What concerns me is that all the initFooEvent/NS that we have all over
> are all copied and pasted from one another, and it's not entirely
> clear to me that this is not cargo-culting as I can't seem to recall
> what motivation there is for all of that :)

Yeah it doesn’t seem particularly scalable.  And what happens when we want to add another attribute on to the Event interface that we want to allow initialisation of?  We won’t be able to just insert an argument in the middle of initUIEvent(), initMouseEvent(), etc.

Having the attributes not be read only and allowing their modification before the Event is dispatched seems better to me.  But changing this for DOM Events in general seems like a larger issue for discussion.

--
Cameron McCormack ≝ http://mcc.id.au/

Received on Monday, 27 July 2009 03:38:31 UTC