- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Dec 2013 07:24:43 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23887 --- Comment #21 from Steve Orvell <sorvell@chromium.org> --- (In reply to Olli Pettay from comment #20) > (In reply to Steve Orvell from comment #15) > > I'm not quite sure I follow this. Is SH2 a child of IP1? If so, it's > > fallback content in the insertion point and would only render if Child was > > not selected by IP1 so I'm not quite sure how the resulting event flow could > > occur. > > What has rendering to do with this all. We're talking about event dispatch ;) Yeah, that's fair. The key bit is that SH2 and Child1 cannot co-exist in the event path. If the fallback content is not used, I think the event path is: Child->IP1->SR1->SH1 If an event is fired on the fallback content: (some distributed child of SH2)->IP2->SR2->SH2->IP1->SR1->SH1 Given this, I believe the event should never be able to bubble to the same insertion point more than once. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 3 December 2013 07:24:48 UTC