- Renamed the
- The old
region-overflowproperty, which controlled the behaviour of the last region in the region-chain, was renamed to
region-fragmentto make it clear it doesn’t change overflow behavior, but rather fragmentation. Its functionality has not changed.
- Named flow events
- We refined the events generated by named flows, to make them more clear and give developers better control over the timing of their event handlers. Here’s what changed:
- • Added the
regionoversetchangeevent is dispatched if the value of the
regionOversetproperty changes for any of the regions in the region chain, including the case when regions are added or removed from the chain.
- Most uses of the
regionlayoutupdateevent were to track how the named flow fits in the region chain. This new event should be used for these cases now.
- • Added the
regionfragmentchangeevent is dispatched on any change to a named flow’s fragmentation through its region chain, including changes to any overset fragment. This event is not yet implemented in WebKit or Blink but we will be adding it in the future.
- • Removed the
regionlayoutupdateevent has been removed from the Regions spec and will be removed from WebKit and Blink around mid-August 2013.
- Make sure to update your code to use the new
regionoversetchangeevent instead of it.
- Defined offsetParent interaction
offsetParentalgorithm was updated for elements inside named flows so that, if no valid offset parent is found within the named flow, the body element is returned. This of course has a direct effect on all offset values:
All these changes (except for the removal of the
regionlayoutupdate event and the addition of the
regionfragmentchange event) are already available for you to test in WebKit Nightly and Chrome Canary.
For a complete list of all updates in this new version of the Regions working draft, please see the change log.