- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 28 Feb 2007 03:01:55 +0000 (UTC)
On Tue, 27 Feb 2007, Anne van Kesteren wrote: > > > > The "onmessage" (previously "onevent") attribute is intended to > > address this. Does it not? > > As I understand it 'message' is only dispatched when the Event field is > not set to something else. However, I suppose if you want full control > you can use the slightly more complicated DOM APIs. Right. > There's one problem with 'message' though. It conflicts with cross > document messaging. Now it's possible that they both dispatch and > implement a different interface but it might be confusing to authors. Fixed. (Merged them.) > The example that contains the following: > > load > Target: #image1 > > should probably be clarified to see that an event does actually dispatch. > Since Event defaults to 'message'. Fixed the example. > Editorial: in the "Message events" section the definition "message" is > not marked up with <code>. And the "onmessage" event handler points > doesn't point to it. Is that still there? I couldn't find it. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 27 February 2007 19:01:55 UTC