- From: <bugzilla@jessica.w3.org>
- Date: Wed, 01 Oct 2014 06:36:50 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23887 --- Comment #122 from Hayato Ito <hayato@chromium.org> --- (In reply to Olli Pettay from comment #121) > Sure. Could it be just OLDER-SHADOW-ROOT? I meant we might want to update the following sentence in the algorithm, as an example: > Let SHADOW-POOL-HOST be the shadow insertion point into which CURRENT shadow root is projected. Because the spec doesn't define what '*projected*' means for a shadow root, I think we cay say, instead, if we want to make it more explicit: > Let SHADOW-POOL-HOST be the shadow insertion point in the younger shadow tree relative to the shadow tree whose root is CURRENT shadow root. We can update other sentences where *projected* is used, in a similar way. BTW, I don't have much worry about optimizing (and correcting?) the proposed algorithm as long as the result will be an equivalent because now I understand the intention of the proposal and it's feasibility. Rather, I'd like to hear early feedbacks from developers, especially polymer developers and users, to know use cases where the difference of resulting event path between the current one and the proposed one matters. I have no idea when it matters. I appreciate any feedbacks and opinions so that we can decide. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 1 October 2014 06:36:52 UTC