- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Dec 2014 04:06:43 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27222 --- Comment #9 from Hayato Ito <hayato@chromium.org> --- (In reply to Olli Pettay from comment #6) > (In reply to Hayato Ito from comment #5) > > I'm not a fan of using 'event path' here. An event path should not be > > abused. > No abusing here. Just being consistent how events propagate and you look > for the first title attribute in the propagation path starting from the event > target. > > > Using the ancestor chain in the composed tree should be enough, > > shouldn't it? > Well once the event propagation is fixed, event path and ancestor chain are > effectively the same. That's already effectively same. The difference is only the position of insertion points. Except for insertion points, nothing will change. > I don't see reason to special case <content> or <shadow>. The ordinal intended usage of shadow roots and insertion points are for composition. Using them beyond the original role sounds bad unless there is a strong reasonable demand from developers. >From my experience, unless there is a strong demand from developers, I suggest that we shouldn't let shadow roots nor insertion points to have a special *power* beyond the original role. That would cause the complexity both in the spec and the implementation. I've already encountered the difficult situation several times in implementation and I am not a fun of bringing the complexity by special cases. Just excluding them is a normal case for me. Including them is rather *special* case, from my experience. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 18 December 2014 04:06:45 UTC