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</code> is live.
Added text to explain support for multi-column elements as required by
Issue
15191 and Action 375.
Renamed ‘regionOverflow
```
href="#dom-region-regionoverset">regionOverset</a>’ 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)
</ul>
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.
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
</ul>
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.
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.
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.
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).