12.3. Changes from November 29^th 2011 version

• Modified region styling examples to use element selector instead of of pseudo-code selectors (this had been omitted in the previous pass at removing pseudo-code from the examples).
• Removed divs with class set to "issue moved", "issue stale" and "issue resolved" since these divs where not displayed.
• Minor updates to the alternate stylesheet.
• Removed "This section is normative" paragraphs since in CSS specifications, sections are normative unless otherwise specified.
• Removed "This section is informative" paragraphs since in CSS specifications notes are always informative.
• Reworded the text about flow-into: <ident> and removed obsolete text about the interaction with the ‘content’ property.
• Removed "this section is non-normative" from the "Regions Concepts" section.
• In the section on region breaks, removed descriptions of break values normatively defined in external specifications. Removed the section about split boxes and replaced with paragraph referencing the page breaking behavior. Removed the discussion about how the ‘overflow’ property applies to content flown in regions from the break section, since this is covered in the section on ‘region-overflow’ already. See mailing list feedback.
• Clarified that @region style rules only apply to the ‘portion’ of an element that falls into the corresponding region and added an issue that the model for ‘partial’ styling needs to be defined. See mailing list feedback.
• Clarified that the NodeList returned by getRegionsByContentNode is live.
• Added a name property to the NamedFlow interface. Added a NamedFlowCollection interface and added a getNamedFlows method on the Document interface, as per Bug 15828.
• Modified wording about containing block resolution for absolutely positioned elements in a named flow.
• Modified initial examples as per Bug 15131
• Multiple editorial changes following mailing list review comments
• Fixed DOM references to now point to the DOM TR
• Fixed Web IDL issues as reported in Issue 15931
• Added text to explain support for multi-column elements as required by Issue 15191 and Action 375.
• Renamed ‘regionOverflow’ to ‘regionOverset’ to avoid confusion between fitting a flow in regions and the concept of visual overflow that the word ‘overflow’ (and the property) carry.
• Reworked the partial document interface following the Issue 14948 on getFlowByName.
• Updated the object model section as proposed on the wiki and in particular:
  • introduced a Region interface to replace the supplemental Element interface
  • Added a ‘flowFrom’ attribute on the Region interface
  • NamedFlow.getRegions() was added
  • Renamed getContentNode to getContent and getRegionsByContentNode to getRegionsByContent as per Isseu 15879
  • NamedFlow now returns static lists (see Issue 16286)
• Modified region layout event to be dispatched on NamedFlow instead of region as before. Was requested by Issue 15938 and required in the general effort to have the DOM APIs work with non-element regions.
• Changed paragraph on pseudo-elements to disallow ‘flow-into’ on all pseudo-elements because moving a ‘::before’ element (for a example) to a named flow does not seem useful and causes specification and implementation complexity.
• Added section about getClientRects(), getBoundingClientRect(), offsetWidth, offsetHeight, offsetTop and offsetLeft.
• Added ‘Regions visual formatting details’ section to better describe the model for resolving auto sizing on regions.
• Reworked the initial specification example.
• Changed break and region-overflow properties to apply to visual media instead of paged.
• Added opacity to region styling.
• Added possibility of ::before content contributing to overflow.
• Added CSSRegionStyleRule

12.4. Changes from June 09^th 2011 version

• Editorial changes (typos, rephrasings).
• Made ‘content-order’ a <integer> and not a <float> following a working group resolution
• Added Alex Mogilevsky as an editor
• Flow names became <ident> instead of <string> following a working group resolution
• Removed issue about possibly altering the DOM Events model for region events following a working group resolution
• Made the "relation to document events" section informative following a working group resolution
• Removed issue in section "The NamedFlow interface" following the working group's resolution to have both NamedFlow and the Element interface extension
• Following a working group resolution:
  • Turned the first issue in the "Extensions to the Element interface" into a note explaining that the NamedFlow interface can be used when regions are pseudo-elements.
  • Added NamedFlowUpdate
• Excluded ‘none’, ‘inherit’ and ‘initial’ from the possible identifier names on the flow property following discussion on the mailing list.
• Simplified integration discussion on multi-column layout and just state that since column boxes are not addressable by selectors, they cannot be regions.
• Added specification of how the ‘flow-into’ property interacts with object, embed and iframe elements.
• Excluded ‘default’ from the possible identifier names on the flow property because it may get reserved.
• Added to the definition of ‘auto’ on ‘region-overflow’ specifying that region breaks must be ignored.
• Renamed ‘Document.flowWithName’ to ‘Document.getFlowByName’ since it is not a property.
• Added a note that a ‘NamedFlow’ instance is live.
• Added an ‘undefined’ string value to the regionOverflow property on the Element interface extension.
• Renamed NamedFlowEvent to regionLayoutUpdate to avoid having ‘Event’ in the event name.
• Added description for special behavior of iframe/object/embed as flow source
• Removed issue on copying content to a named flow instead of moving elements to named flow following working group resolution.
• Removed issue on content:flow-from v.s., flow-from property following working group resolution.
• Renamed ‘flow’ to ‘flow-into’ following working group resolution.
• Updated the css3-grid-align example following working group resolution that it should use <div> instead of grid-cell pseudo elements that were removed from the CSS Grid Layout specification.
• Renamed ‘from-flow’ to ‘flow-from’ following a working group resolution.
• Limited the applicability of ‘content: flow-from()’ to block container box and added a note that this might be expanded in the future, following a working group resolution.
• Removed issue about API to find which region displays an element in a named flow since ACTION-350 was created to add this API.
• In the ‘flow’ property description, removed the required wrapper anonymous block as agreed on mailing list discussion.
• Reworded the paragraph on how regions create a new stacking context, as per the mailing list discussion.
• Reworked the "CSS regions Model" section to now be "CSS regions Layout". Moved the definition of a region as the first sub-section.
• Removed the "Visual Formatting Model and Flows" section to match the new Regions Model (now CSS regions Layout) section.
• Moved the sections on allowed region breaks, forced region breaks and "best" regions breaks to follow the property definitions to follow the formatting of the paged media section in CSS 2.1.
• Added note about why regions create a new stacking context following the discussion on the mailing list.
• Removed sentence about content:none making elements disconnected following the discussion on the mailing list.
• Removed sentence about content:none making elements disconnected following the discussion on the mailing list.
• Added the ::region-before and a ::region-after pseudo-elements.
• Added note of caution when using selectors and the ‘flow-into’ property following a mailing list discussion.
• Removed sections about allowed, forced and best region breaks to align with the multi-column specification approach and until the group agrees on where and how the general issue of breaks (regions/pages/columns) should be addressed.
• Removed the section on Integration with other specifications since specifications that was superfluous especially since there is no specific integration with multi column, grid or template layout.
• Added a note that regions establish a new block formatting context.
• Renamed content-order to region-order.
• Added a note about overflowing content in regions (e.g., for content with borders).
• Added a note that a region cannot layout content it is part of (to avoid creating a circular dependency) in the flow-from description, specifying that if flow-from references the flow an element is part of, then the element does not format anything visually.
• Replaced ‘content:flow-from(<ident>)’ with ‘flow-from: <ident>’ following a working group resolution.
• Added more specific wording about auto width and auto height, following ACTION 351.
• Reworked section on region markers to now use ‘::before’ and ‘::after’ and explain how ‘display:run-in’ works with regions.
• Modified the @region style rule to remove the ::region-lines pseudo-selector.
• Removed the ‘region-order’ property following implementation feedback.
• Specified that region-overflow does not influence a region's size.
• Specified that the flow's writing mode is defined by the first region's writing mode following mailing list discussion.
• Made iframe, object and embed support of flow-into optional following mailing list discussion.
• Clarified that flow content following the last break in the last region is not rendered, following mailing list discussions.
• Modified the rule for computing the width and height of a region when they are set to auto, following a mailing list discussion.
• Added ‘auto’ to the list of invalid flow identifiers.
• Made ‘none’ the initial value for ‘flow-into’ and aligned with ‘flow-from’, as explained in this email. Also allowed the ‘inherit’ value on ‘flow-from’ and ‘flow-into’ (same email).
• Added note about nested region styling following a mailing list discussion.
• Added additional DOM interface following Action 350.
• Clarified that a region becomes a region only if its ‘content’ property computes to normal, following the resolution of Issue 22.
• Removed text about special iframe behavior as a result of ACTION 376.
• Made the selectors explicit in the initial section code examples, following discussion in San Jose, October 2011 face to face meeting.
• Added section on use cases following ACTION-377.