- From: Alan Stearns <stearns@adobe.com>
- Date: Tue, 12 Jun 2012 16:42:43 -0700
- To: Alex Mogilevsky <alexmog@microsoft.com>, Andrei Bucur <abucur@adobe.com>, "www-style@w3.org" <www-style@w3.org>
On 6/11/12 3:16 PM, "Alex Mogilevsky" <alexmog@microsoft.com> wrote: >> On 6/8/12 4:51 AM, "Andrei Bucur" <abucur@adobe.com> wrote: >> >> >Hello! >> > >> >The Regions spec states that the regionLayoutUpdate event should be >> >bubbling. When this event was dispatched on the region this was very >> >easy to understand as they were DOM elements. Now, the NamedFlow object >> >is the target, which is not clearly positioned in the DOM hierarchy. >> >How is the bubbling supposed to behave for this event? Should it be >> >possible to listen for the event on the parent document and determine >> >the NamedFlow from the event target? >> > >> >Thanks! >> >Andrei. > >The way the event defined now (only on NamedFlow and never on region) it >doesn't make any sense to bubble. It was useful for setting one listener >on multiple regions, now the event on NamedFlow already is the single >object to connect one listener to. > >If the event is ever applies to individual regions again, it should >bubble again. Currently that functionality is removed due to insufficient >motivation. It may hypothetically help to optimize for incremental >updates in regions, but there is not enough evidence that it would in >fact make a difference. > >We should just make the event not bubble. > >Alex I agree. I've made that change. Thanks, Alan
Received on Tuesday, 12 June 2012 23:43:14 UTC