- From: Hayato Ito <notifications@github.com>
- Date: Wed, 01 Jun 2016 16:53:14 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc:
Received on Wednesday, 1 June 2016 23:53:53 UTC
FYI. Blink does not construct such a list, as an optimization. As long as we can achieve the processing equivalence, it should be okay. Yeah, the spec is complicated, however, the basic idea does not change from my comment: https://github.com/w3c/webcomponents/issues/375#issuecomment-178989178. Hopefully, the example in the comment would be helpful. If we are to define the behavior of this example in a normative way, we have to use such a list in the spec for the purpose of the normative explanation. Ideally, we should have a spec which the UA can implement *literally*, but that can not be always easy.... :( --- 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/496#issuecomment-223158986
Received on Wednesday, 1 June 2016 23:53:53 UTC