- From: <bugzilla@jessica.w3.org>
- Date: Thu, 01 May 2014 16:40:15 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25458 --- Comment #28 from Dimitri Glazkov <dglazkov@chromium.org> --- (In reply to Anne from comment #27) > The way you want to define this is that events have an associated path and > an associated path object. Then at various points in the lifetime of the > event, you change the associated concepts as appropriate. E.g. initially, > when you create an event, its associated path is the empty list and its > associated path object is a new Array representing its associated path. > > Then during dispatch when the path is calculated you set a new path and a > new Array representing it. > > Event.prototype.path meanwhile returns the path object. The specification > algorithms use the path. Love it. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 1 May 2014 16:40:17 UTC