15938 2012-02-08 22:02:31 +0000 Attaching events to content flows 2012-04-11 21:10:57 +0000 1 1 1 Unclassified CSS Regions unspecified PC All RESOLVED FIXED cssom P2 normal --- 1 vhardy vhardy christian.cantrell eoconnor mihnea rcaliman stearns public-css-bugzilla oldest_to_newest 63905 0 vhardy 2012-02-08 22:02:31 +0000 (Some feedback on regions for those interested…) I've written a little framework for dividing content up into "pages" (regions) using the CSSOM APIs. I'm happy with the way it turned out, but the way I had to go about doing it was more complicate than what I was hoping for. In fact, I tried every other method I could think of for detecting overflow before finally resorting to attaching webkitRegionLayoutUpdate events to regions. From Christian Cantrell (Adobe): ==== [...] something that should work is attaching the webkitRegionLayoutUpdate event listener to the flow itself rather than individual regions. For instance: var storyFlow = document.webkitGetFlowByName('story'); storyFlow.addEventListener('webkitRegionLayoutUpdate', function(e) { if (storyFlow.overflow) { // add another region } }); This would be a great way to know if additional regions were needed, however it wouldn't be enough to tell whether regions needed to be taken away. In that case, the flow would need an additional property like emptyRegions. Something like this would be nice: var storyFlow = document.webkitGetFlowByName('story'); storyFlow.addEventListener('webkitRegionLayoutUpdate', function(e) { if (storyFlow.overflow) { // add another region } else if (storyFlow. emptyRegions.length > 0) { for (var i = 0; i < storyFlow.emptyRegions.length; ++i) { document.getElementById('pageContainer').removeChild(storyFlow.emptyRegions[i]); } } }); 65478 1 vhardy 2012-03-13 22:53:04 +0000 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. 65957 2 vhardy 2012-03-22 17:07:54 +0000 (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) 66113 3 rcaliman 2012-03-27 13:52:36 +0000 (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. 66115 4 vhardy 2012-03-27 14:12:25 +0000 (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 66117 5 rcaliman 2012-03-27 14:18:20 +0000 (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. 66143 6 vhardy 2012-03-27 20:52:08 +0000 https://dvcs.w3.org/hg/csswg/rev/614c5fe1f9ad