W3C home > Mailing lists > Public > public-css-bugzilla@w3.org > March 2012

[Bug 15938] Attaching events to content flows

From: <bugzilla@jessica.w3.org>
Date: Tue, 27 Mar 2012 14:18:21 +0000
To: public-css-bugzilla@w3.org
Message-Id: <E1SCXE5-0001it-4o@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15938

--- Comment #5 from Razvan Caliman <rcaliman@adobe.com> 2012-03-27 14:18:20 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > (In reply to comment #1)
> > > > So the proposal is:
> > > > 
> > > > a. Have NamedFlow implement the EventTarget interface
> > > > b. Have NamedFlow dispatch a region layout update event
> > > > (http://dev.w3.org/csswg/css3-regions/#region-flow-layout-events)
> > > > c. Add an emptyRegions member to the NamedFlow interface.
> > > 
> > > - For a. and b., make sure the bubbling is consistent with other EventTargets
> > > that are not DOM nodes.
> > > - For c., suggests having a property for the last non empty region index (-1 if
> > > empty flow or if no region at all)
> > 
> > For c., if you're suggesting collecting empty regions, why not collect all
> > regions for a flow? 
> > Then, the developer could iterate through them and check the regionOverflow
> > property.
> 
> Here, the goal is to help the developer get to the index of the last empty
> region easily. There is already a proposal (on NamedFlow), to help the
> developers iterate, see:
> 
> http://wiki.csswg.org/spec/css3-regions/css-om

Noted. Thanks for the clarification!
I missed the getRegions method.

-- 
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 Tuesday, 27 March 2012 14:18:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 14:18:32 GMT