- From: Dimitri Glazkov <dglazkov@chromium.org>
- Date: Fri, 11 Jan 2013 11:31:02 -0800
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: Hayato Ito <hayato@chromium.org>, whatwg <whatwg@lists.whatwg.org>, Eric Seidel <eric@webkit.org>, Ian Hickson <ian@hixie.ch>, Adam Barth <w3c@adambarth.com>, Ojan Vafai <ojan@chromium.org>
On Fri, Jan 11, 2013 at 11:28 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Fri, Jan 11, 2013 at 8:16 PM, Dimitri Glazkov <dglazkov@chromium.org> wrote: >> On Fri, Jan 11, 2013 at 11:12 AM, Anne van Kesteren <annevk@annevk.nl> wrote: >>> Is that the case for all non-target/relatedTarget attributes that need >>> adjustment? That they do not actually need to be adjusted but are >>> calculated on getting based on the target and its conditions at the >>> time of getting? (E.g. for touch events, the new pointer events, >>> anything else?) >> >> That's been our implementation experience. It's neat that properties >> on event objects fall cleanly into two categories: >> >> 1) properties that inform the author about the actual event dispatch >> process (target, relatedTarget) >> 2) properties that inform the author about the specifics of the event. >> >> The #1 are the ones that need adjustment for encapsulation. The #2 are >> the ones that can be either computed on demand or don't need >> adjustment. > > I'd like to have the concrete list, because in the event model all > attributes are initialized before the event is dispatched and they do > not change. That's the way init*Event() and now event constructors > work. offset* (and a few others on MouseEvent) might be special > because they were added later on and were not really standardized (I > made an attempt in CSSOM View for MouseEvent extensions but did not > cover this peculiarity). Sure. Where are you seeing this list being mentioned? In Shadow DOM spec or in DOM Core spec? I am happy to help, just not sure what exactly I need to be doing :) :DG<
Received on Friday, 11 January 2013 19:31:27 UTC