W3C home > Mailing lists > Public > www-style@w3.org > June 2012

Re: [css3-regions][cssom] Bubbling for the regionLayoutUpdate event

From: Andrei Bucur <abucur@adobe.com>
Date: Mon, 11 Jun 2012 14:05:22 +0100
To: Alan Stearns <stearns@adobe.com>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <CBFBC670.3521A%abucur@adobe.com>
I don't think it is that easy :). The bubbling phase is described in
http://www.w3.org/TR/DOM-Level-3-Events/#bubble-phase :

"The bubble phase: the event object propagates through the target's
ancestors in reverse order, starting with the target's parent and ending
with the defaultView. This phase is also known as the bubbling phase.
Event listeners registered for this phase must handle the event after it
has reached its target."

The Regions spec doesn't explicitly defines a "parent" or the position in
the DOM hierarchy for the NamedFlow objects. I suppose there should be a
special chapter about this so there won't be any confusions when


On 6/9/12 6:21 PM, "Alan Stearns" <stearns@adobe.com> wrote:

>On 6/8/12 4:51 AM, "Andrei Bucur" <abucur@adobe.com> wrote:
>>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?
>Since you can determine the NamedFlow from the event target, it could be
>useful in the case of multiple named flows to have a single listener on
>the document. Would it be sufficient to add a line to the description of
>this event saying that it bubbles up to the document?
Received on Monday, 11 June 2012 13:06:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:17 UTC