- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 20 Apr 2016 10:13:18 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc:
Received on Wednesday, 20 April 2016 17:13:47 UTC
I don't really understand the current specification. It acknowledges you can have multiple relative targets and it says they have to be calculated prior to dispatch, but it never explains how that is done. And then in the dispatch algorithm itself it only talks about "relative target" as if it is a single thing. It seems to me that if you can have multiple and if they need to be known prior to dispatch, we need to store them somewhere, just like we need to store the path. Now, a question I had is if we write down that computation, whether it can be simpler than what I have above. Because for each "get the parent" invocation, we now invoke "retargating", which ends up iterating over target's ancestors. Is there no better way to do that? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/485#issuecomment-212519197
Received on Wednesday, 20 April 2016 17:13:47 UTC