W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2013

Re: [whatwg] seamless iframes and event propagation

From: Dimitri Glazkov <dglazkov@chromium.org>
Date: Wed, 23 Jan 2013 09:57:29 -0800
Message-ID: <CADh5Ky2rU+845oFpfTTxAC+QouhVcMBfk--y3Gb_2WzXdZwPFw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: whatwg <whatwg@lists.whatwg.org>, Hayato Ito <hayato@chromium.org>
On Fri, Jan 11, 2013 at 3:54 PM, Dimitri Glazkov <dglazkov@chromium.org> wrote:
> On Fri, Jan 11, 2013 at 11:56 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> I want you to create a list :-)

Apologies for such a long delay. Dog-ate-homework, etc. Here's what
WebKit does. If interface isn't mentioned, then there's nothing
special going on there.

Legend:
* N -- no change
* L -- computed lazily from target
* R - computed when retargeting
* X - influenced by shadow DOM changes in event dispatch process

Event:
type - N
target - R
currentTarget - R
eventPhase - X
bubbles - N
cancelable - N
timeStamp - N
defaultPrevented - N
srcElement == target - R
returnValue - N
cancelBubble - N
clipboardData - N

UIEvent:
view - N
detail - N
keyCode - N
charCode - N
layerX - L
layerY - L
pageX - N
pageY - N
which - N

MouseEvent:
screenX - N
screenY - N
clientX - N
clientY - N
x - N
y - N
offsetX - L
offsetY - L
ctrlKey - N
shiftKey - N
altKey - N
metaKey - N
button - N
relatedTarget - R
fromElement - L
toElement - L
dataTransfer - N

We currently don't seem to be doing anything with Touch events, but we
probably should.

Touch (proposed):
clientX  - N
clientY - N
screenX - N
screenY - N
pageX - N
pageY - N
target - R
identifier - N

:DG<
Received on Wednesday, 23 January 2013 17:57:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:12 GMT