- From: <bugzilla@jessica.w3.org>
- Date: Wed, 13 Jun 2012 12:04:39 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17090 --- Comment #4 from Hayato Ito <hayato@chromium.org> 2012-06-13 12:04:39 UTC --- I think we can change the current spec with a little modification for re-targeting event.target to support the new behavior. I've just done a tiny experiment using WebKit and that worked well. As for re-targeting event.relatedTarget, let me think further. Let me report the result later. (In reply to comment #3) > Okay. I am for it. Event dispatching returns to us. :) > I think that it must be useful for developers to know most *accurate* node as > event.target as long as it does not break encapsulation. > > Let me formulate which node event.target should be. > > (In reply to comment #2) > > I think we should break the encapsulation boundary symmetry here. > > > > Since the insertion point is specifically designed to be replaced by contents > > of a shadow host when rendering, we can justify saying that the insertion > > points do not retarget. > > > > Of course, this means we have to rethink the whole thing again :) Yikes! -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 13 June 2012 12:04:42 UTC