- From: <bugzilla@jessica.w3.org>
- Date: Fri, 09 Jan 2015 06:51:20 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21066 Koji Ishii <kojiishi@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kojiishi@gmail.com --- Comment #51 from Koji Ishii <kojiishi@gmail.com> --- (In reply to Hayato Ito from comment #49) > > However, event.path will become to includes Window object at the beginning > of that as a result. This is the only user visible change, I think. and change the type to an array of EventTarget, right? > We might have a plan B: > event.path API return EventTarget[] where Window object is removed from > the event path. > > If someone have a strong concern about the compatibility and prefer plan B, > please let me know that. I actually prefer this, not from the compatibility, but because I cannot see any useful cases of having window in event.path API. I think the Shadow DOM spec is fine either way, since it's talking about how the actual event path is, but when we add the API to the DOM spec, we could simply say "window object is not included in the returned array from the event.path property." Thoughts? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 9 January 2015 06:51:23 UTC