| Previous revision |
— | spec:css3-regions:older-changelogs [2014/12/09 15:48] (current) – external edit 127.0.0.1 |
---|
| <html> |
| <h3 id="changes_from_November_29_2011"><span class=secno>12.3. |
| </span>Changes from <a |
| href="http://www.w3.org/TR/2011/WD-css3-regions-20111129/">November |
| 29<sup>th</sup> 2011</a> version</h3> |
| |
| <ul> |
| <li>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). |
| |
| <li>Removed divs with class set to "issue moved", "issue stale" and "issue |
| resolved" since these divs where not displayed. |
| |
| <li>Minor updates to the alternate stylesheet. |
| |
| <li>Removed "This section is normative" paragraphs since in CSS |
| specifications, sections are normative unless otherwise specified. |
| |
| <li>Removed "This section is informative" paragraphs since in CSS |
| specifications notes are always informative. |
| |
| <li>Reworded the text about flow-into: <ident> and removed obsolete |
| text about the interaction with the ‘<code |
| class=property>content</code>’ property. |
| |
| <li>Removed "this section is non-normative" from the "Regions Concepts" |
| section. |
| |
| <li>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 ‘<code |
| class=property>overflow</code>’ property applies to content flown in |
| regions from the break section, since this is covered in the section on |
| ‘<code class=property>region-overflow</code>’ already. See <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Dec/0477.html">mailing |
| list feedback.</a> |
| |
| <li>Clarified that @region style rules only apply to the ‘<code |
| class=property>portion</code>’ of an element that falls into the |
| corresponding region and added an issue that the model for ‘<code |
| class=property>partial</code>’ styling needs to be defined. See <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Dec/0480.html">mailing |
| list feedback</a>. |
| |
| <li>Clarified that the <code>NodeList</code> returned by |
| <code>getRegionsByContentNode</code> is live. |
| |
| <li>Added a name property to the <a |
| href="#dom-named-flow"><code>NamedFlow</code></a> interface. Added a <a |
| href="#dom-named-flow-collection"><code>NamedFlowCollection</code></a> |
| interface and added a <code>getNamedFlows</code> method on the |
| <code>Document</code> interface, as per <a |
| href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15828">Bug |
| 15828</a>. |
| |
| <li>Modified wording about containing block resolution for absolutely |
| positioned elements in a named flow. |
| |
| <li>Modified initial examples as per <a |
| href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15131">Bug 15131</a> |
| |
| <li>Multiple editorial changes following <a |
| href="http://lists.w3.org/Archives/Public/www-style/2012Feb/0001.html">mailing |
| list review comments</a> |
| |
| <li>Fixed DOM references to now point to the DOM TR |
| |
| <li>Fixed Web IDL issues as reported in <a |
| href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15931">Issue |
| 15931</a> |
| |
| <li>Added text to explain support for multi-column elements as required by |
| <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15191">Issue |
| 15191</a> and <a |
| href="http://www.w3.org/Style/CSS/Tracker/actions/375">Action 375</a>. |
| |
| <li>Renamed ‘<code class=property>regionOverflow</code>’ to ‘<a |
| href="#dom-region-regionoverset"><code |
| class=property>regionOverset</code></a>’ to avoid confusion between |
| fitting a flow in regions and the concept of visual overflow that the |
| word ‘<code class=property>overflow</code>’ (and the property) carry. |
| |
| <li>Reworked the partial document interface following the <a |
| href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=14948">Issue |
| 14948</a> on <code>getFlowByName</code>. |
| |
| <li>Updated the object model section as proposed on the <a |
| href="http://wiki.csswg.org/spec/css3-regions/css-om">wiki</a> and in |
| particular: |
| <ul> |
| <li>introduced a <a href="#css-region"><code>Region</code></a> interface |
| to replace the supplemental Element interface |
| |
| <li>Added a ‘<code class=property>flowFrom</code>’ attribute on the |
| Region interface |
| |
| <li>NamedFlow.getRegions() was added |
| |
| <li>Renamed getContentNode to getContent and getRegionsByContentNode to |
| getRegionsByContent as per <a |
| href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15879">Isseu |
| 15879</a> |
| |
| <li>NamedFlow now returns static lists (see <a |
| href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16286">Issue |
| 16286</a>) |
| </ul> |
| |
| <li>Modified region layout event to be dispatched on <a |
| href="#dom-named-flow"><code>NamedFlow</code></a> instead of region as |
| before. Was requested by <a |
| href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15938">Issue |
| 15938</a> and required in the general effort to have the DOM APIs work |
| with non-element regions. |
| |
| <li>Changed paragraph on pseudo-elements to disallow ‘<a |
| href="#flow-into"><code class=property>flow-into</code></a>’ on all |
| pseudo-elements because moving a ‘<code class=css>::before</code>’ |
| element (for a example) to a named flow does not seem useful and causes |
| specification and implementation complexity. |
| |
| <li>Added section about getClientRects(), getBoundingClientRect(), |
| offsetWidth, offsetHeight, offsetTop and offsetLeft. |
| |
| <li>Added ‘<code class=css>Regions visual formatting details</code>’ |
| section to better describe the model for resolving auto sizing on |
| regions. |
| |
| <li>Reworked the initial specification example. |
| |
| <li>Changed break and region-overflow properties to apply to visual media |
| instead of paged. |
| |
| <li>Added opacity to region styling. |
| |
| <li>Added possibility of ::before content contributing to overflow. |
| |
| <li>Added CSSRegionStyleRule |
| </ul> |
| |
| <h3 id="changes_from_June_09_2011"><span class=secno>12.4. </span>Changes |
| from <a href="http://www.w3.org/TR/2011/WD-css3-regions-20110609/">June |
| 09<sup>th</sup> 2011</a> version</h3> |
| |
| <ul> |
| <li>Editorial changes (typos, rephrasings). |
| |
| <li>Made ‘<code class=property>content-order</code>’ a <integer> |
| and not a <float> following a working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0329.html">resolution</a> |
| |
| <li>Added Alex Mogilevsky as an editor |
| |
| <li>Flow names became <ident> instead of <string> following a |
| working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">resolution</a> |
| |
| <li>Removed issue about possibly altering the DOM Events model for region |
| events following a working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">resolution</a> |
| |
| <li>Made the "relation to document events" section informative following a |
| working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">resolution</a> |
| |
| <li>Removed issue in section "The NamedFlow interface" following the |
| working group's <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">resolution</a> |
| to have both NamedFlow and the Element interface extension |
| |
| <li>Following a working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">resolution</a>: |
| |
| <ul> |
| <li>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. |
| |
| <li>Added NamedFlowUpdate |
| </ul> |
| |
| <li>Excluded ‘<code class=property>none</code>’, ‘<code |
| class=property>inherit</code>’ and ‘<code |
| class=property>initial</code>’ from the possible identifier names on |
| the flow property following <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0583.html">discussion</a> |
| on the mailing list. |
| |
| <li>Simplified integration discussion on multi-column layout and just |
| state that since column boxes are not addressable by selectors, they |
| cannot be regions. |
| |
| <li>Added specification of how the ‘<a href="#flow-into"><code |
| class=property>flow-into</code></a>’ property interacts with object, |
| embed and iframe elements. |
| |
| <li>Excluded ‘<code class=property>default</code>’ from the possible |
| identifier names on the flow property because it <a |
| href="http://www.w3.org/TR/2006/WD-css3-values-20060919/#keywords">may |
| get reserved</a>. |
| |
| <li>Added to the definition of ‘<code class=property>auto</code>’ on |
| ‘<code class=property>region-overflow</code>’ specifying that region |
| breaks must be ignored. |
| |
| <li>Renamed ‘<code class=css>Document.flowWithName</code>’ to ‘<code |
| class=css>Document.getFlowByName</code>’ since it is not a property. |
| |
| <li>Added a note that a ‘<a href="#dom-named-flow"><code |
| class=property>NamedFlow</code></a>’ instance is live. |
| |
| <li>Added an ‘<code class=property>undefined</code>’ string value to |
| the regionOverflow property on the Element interface extension. |
| |
| <li>Renamed NamedFlowEvent to regionLayoutUpdate to avoid having ‘<code |
| class=property>Event</code>’ in the event name. |
| |
| <li>Added description for special behavior of iframe/object/embed as flow |
| source |
| |
| <li>Removed issue on copying content to a named flow instead of moving |
| elements to named flow following working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0069.html">resolution</a>. |
| |
| <li>Removed issue on content:flow-from v.s., flow-from property following |
| working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0069.html">resolution</a>. |
| |
| <li>Renamed ‘<code class=property>flow</code>’ to ‘<a |
| href="#flow-into"><code class=property>flow-into</code></a>’ following |
| working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0069.html">resolution</a>. |
| |
| <li>Updated the css3-grid-align example following working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0069.html">resolution</a> |
| that it should use <div> instead of grid-cell pseudo elements that |
| were removed from the CSS Grid Layout specification. |
| |
| <li>Renamed ‘<code class=property>from-flow</code>’ to ‘<a |
| href="#flow-from"><code class=property>flow-from</code></a>’ following |
| a working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0069.html">resolution</a>. |
| |
| <li>Limited the applicability of ‘<code class=css>content: |
| flow-from()</code>’ to block container box and added a note that this |
| might be expanded in the future, following a working group <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0069.html">resolution</a>. |
| |
| <li>Removed issue about API to find which region displays an element in a |
| named flow since <a |
| href="http://www.w3.org/Style/CSS/Tracker/actions/350">ACTION-350</a> was |
| created to add this API. |
| |
| <li>In the ‘<code class=property>flow</code>’ property description, |
| removed the required wrapper anonymous block as agreed on <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0161.html">mailing |
| list discussion</a>. |
| |
| <li>Reworded the paragraph on how regions create a new stacking context, |
| as per the <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0025.html">mailing |
| list discussion</a>. |
| |
| <li>Reworked the "CSS regions Model" section to now be "CSS regions |
| Layout". Moved the definition of a region as the first sub-section. |
| |
| <li>Removed the "Visual Formatting Model and Flows" section to match the |
| new Regions Model (now CSS regions Layout) section. |
| |
| <li>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. |
| |
| <li>Added note about why regions create a new stacking context following |
| the discussion on the <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jul/0158.html">mailing |
| list</a>. |
| |
| <li>Removed sentence about content:none making elements disconnected |
| following the discussion on the <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jul/0158.html">mailing |
| list</a>. |
| |
| <li>Removed sentence about content:none making elements disconnected |
| following the discussion on the <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jul/0158.html">mailing |
| list</a>. |
| |
| <li>Added the ::region-before and a ::region-after pseudo-elements. |
| |
| <li>Added note of caution when using selectors and the ‘<a |
| href="#flow-into"><code class=property>flow-into</code></a>’ property |
| following a <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Jul/0191.html">mailing |
| list discussion</a>. |
| |
| <li>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. |
| |
| <li>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. |
| |
| <li>Added a note that regions establish a new block formatting context. |
| |
| <li>Renamed content-order to region-order. |
| |
| <li>Added a note about overflowing content in regions (e.g., for content |
| with borders). |
| |
| <li>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. |
| |
| <li>Replaced ‘<code class=css>content:flow-from(<ident>)</code>’ |
| with ‘<code class=css>flow-from: <ident></code>’ following a <a |
| href="http://krijnhoetmer.nl/irc-logs/css/20110824">working group |
| resolution</a>. |
| |
| <li>Added more specific wording about auto width and auto height, |
| following <a |
| href="http://www.w3.org/Style/CSS/Tracker/actions/351">ACTION 351</a>. |
| |
| <li>Reworked section on region markers to now use ‘<code |
| class=css>::before</code>’ and ‘<code class=css>::after</code>’ and |
| explain how ‘<code class=css>display:run-in</code>’ works with |
| regions. |
| |
| <li>Modified the @region style rule to remove the ::region-lines |
| pseudo-selector. |
| |
| <li>Removed the ‘<code class=property>region-order</code>’ property |
| following implementation feedback. |
| |
| <li>Specified that region-overflow does not influence a region's size. |
| |
| <li>Specified that the flow's writing mode is defined by the first |
| region's writing mode following <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0306.html">mailing |
| list discussion</a>. |
| |
| <li>Made iframe, object and embed support of flow-into optional following |
| <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Sep/0073.html">mailing |
| list discussion</a>. |
| |
| <li>Clarified that flow content following the last break in the last |
| region is not rendered, following <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Oct/0167.html">mailing |
| list discussions.</a> |
| |
| <li>Modified the rule for computing the width and height of a region when |
| they are set to auto, following <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Oct/0216.html">a |
| mailing list discussion.</a> |
| |
| <li>Added ‘<code class=property>auto</code>’ to the list of invalid |
| flow identifiers. |
| |
| <li>Made ‘<code class=property>none</code>’ the initial value for |
| ‘<a href="#flow-into"><code class=property>flow-into</code></a>’ and |
| aligned with ‘<a href="#flow-from"><code |
| class=property>flow-from</code></a>’, as explained in this <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Oct/0576.html">email</a>. |
| Also allowed the ‘<code class=property>inherit</code>’ value on ‘<a |
| href="#flow-from"><code class=property>flow-from</code></a>’ and ‘<a |
| href="#flow-into"><code class=property>flow-into</code></a>’ (same |
| email). |
| |
| <li>Added note about nested region styling following <a |
| href="http://lists.w3.org/Archives/Public/www-style/2011Oct/0650.html">a |
| mailing list discussion</a>. |
| |
| <li>Added additional DOM interface following <a |
| href="http://www.w3.org/Style/CSS/Tracker/actions/350">Action 350</a>. |
| |
| <li>Clarified that a region becomes a region only if its ‘<code |
| class=property>content</code>’ property computes to normal, following |
| the resolution of <a |
| href="http://wiki.csswg.org/spec/css3-regions#issue-22content-vs-flow-from-precedence">Issue |
| 22</a>. |
| |
| <li>Removed text about special iframe behavior as a result of <a |
| href="http://www.w3.org/Style/CSS/Tracker/actions/376">ACTION 376</a>. |
| |
| <li>Made the selectors explicit in the initial section code examples, |
| following discussion in <a |
| href="http://krijnhoetmer.nl/irc-logs/css/20111030">San Jose, October |
| 2011</a> face to face meeting. |
| |
| <li>Added section on use cases following <a |
| href="http://www.w3.org/Style/CSS/Tracker/actions/377">ACTION-377</a>. |
| </ul> |
| </html> |