Minutes and Resolutions Hamburg F2F May 2012: Miscellaneous
Administrative and Testing
- The CSSWG is getting overloaded; discussed ways of scaling the WG resolution process to handle the higher flux of issues. Some ideas, no conclusions.
- Tentatively scheduling F2Fs in Tucson next February and Tokyo in May.
- Resolved: Send Style Attributes spec to PR once implementation reports are published on www.w3.org.
- Håkon encourages people to review the new tests in the multi-col test suite.
- Discussed separating the test approval process from the test review process, as we did for 2.1
Full minutes
XSL:FO and CSS3 Layout
- Liam Quin presented an overview of XSL:FO and proposed folding the remainder of the XSL:FO WG into CSS
- Bert Bos presented on a collection of various layout challenges and how they can or cannot be solved with proposals in the CSSWG
- Steve Zilles started a discussion on harmonizing the divergent CSS3 layout proposals
Full minutes
Spec Editing
- vhardy showed off a tool to help editors synchronize specs with Bugzilla
- plinss explained plans to host test-annotated /TR specs
Full minutes
Minutes and Resolutions Hamburg F2F May 2012: Text Layout and Typography
CSS3 Text
- Resolved: Pending Jonathan Kew’s okay, keep
text-transform:capitalize word-boundary rules undefined, with only an informative reference to UAX29.
- Resolved: Disallow combinations of values in
text-transform for this level.
- Resolved: Changing currentColor to resolve at used-time is okay with the SVGWG; we’re just waiting on Color to be errata’d.
- Resolved: The behavior of
letter-spacing at element boundaries is kept as-is in the draft. A note should be added about using padding to put extra spacing on either side of an element, for the use-cases in which that is important.
- Resolved: Remove the
avoid value from text-wrap.
- Resolved: Remove the longhands (
text-wrap, text-space-collapse) for white-space.
- Resolved: Change
overflow-wrap back to word-wrap. Allow CSS Property Aliasing (future spec) to define that it aliases to overflow-wrap. Next time Text revs, change the property name officially and talk about aliasing.
- Resolved: Drop the
full-size-kana value from text-transform in level 3.
- Resolved: Don’t change
nowrap keyword, even though it’s lack of a hyphen is confusing.
CSS3 Writing Modes
- Resolved: Nobody cares too strongly, so fantasai should decide whether to use
isolate bidi-override or isolate-override.
- Resolved: no UA dependent values for text-orientation
- Resolved: Put our own table of behaviors for
mixed-right and upright values in the Writing Modes spec until UTR50 stabilizes.
CSS3 Fonts
- Resolved: Fallback for font-variant-position occurs per run rather than per-glyph.
- Resolved: The
font-variant-position property is defined independent of the existing use of the font-size/vertical-align properties to synthesize subscripts/superscripts.
- Discussed small-caps fallback per-script rather than per-font, and using text-transform rules for synthesizing small-caps.
- Noted some proposed updates to prose for
font-family syntax to match CSS 2.1 errata.
Full minutes: Writing Modes and Text, Fonts
Minutes and Resolutions Hamburg F2F May 2012: Shaping and Paging Flows
Regions
Alan and Florian presented several ideas for generating styleable
pseudo-elements to hold content flows:
overflow: repeat, which would redirect overflow into creating a repetition of the element as it’s sibling. Individual repetitions can be targetted and styled with an ::nth-copy(An+B) pseudo-selector.
- A generic
::slot() pseudo element
- A Page Templates proposal
There was consensus to replace all the examples in Regions with some combination of the above techniques. There was also consensus that the proposals need to be developed further, and that overlap and interaction among them needs to be carefully considered.
Shapes and Exclusions
- Discussed how shapes/exclusions impact wrapping content. (It’s just like floats.)
- Discussed using background images to define shapes/exclusions
- Discussed concerns about mixing with absolute positioning and the resulting collision-prone layouts.
GCPM
- Reviewed some features in GCPM, including new float keywords,
columns() notation in float property, and float position snapping.
Fragmentation
- Resolved: The gap between a breakpoint and the end of the page does consume specified height. The box’s background and border are only drawn in that gap if
box-decoration-break is slice and the element has auto height.
- Resolved: Publish an updated Working Draft of CSS3 Fragmentation in a week after edits announced if there are no objections.
Full minutes: Regions, Shapes, and Exclusions, GCPM and Fragmentation
Minutes and Resolutions Hamburg F2F May 2012: Layout, Values and Units
Box Alignment
fantasai presented a proposal to converge all layout models on a single set of alignment properties.
- Resolved: fantasai to continue working on this proposal
- Resolved: flexbox alignment properties to be renamed to css3-align equivalents.
Grid Layout
- Resolved: rename the values of grid-flow so that row adds rows, column adds columns, and layer just stacks grid items on top of each other.
- Resolved: add row-gap and column-gap to the specification such that they provide uniform gutters
- Also discussed scoping of Grid Layout vs. Template, ways to remove overlap, and scoping things for Level 1 vs. higher. No conclusions.
Values and Units
- Resolved: Disallow values with commas in toggle() at this level. (LC Issue 12)
- Resolved: Won’t fix level-skipping in this level (except we’re renaming to toggle() because of it). (LC Issue 13)
- Resolved: Rename
cycle() to toggle(), leave behavior as is.
- Resolved: Fix error the UA stylesheet rule for
<ul>. (LC Issue 14)
- Resolved: Add a note to clarify computed style comparisons better. (LC Issue 15)
- Resolved: Reject deferring cycle() to L4. (LC Issue 16)
Full minutes: Box Alignment and Grid Layout, Values and Units
Minutes and Resolutions Hamburg F2F May 2012: Flexbox
Flexbox: Box Construction
- Resolved: Don’t create anonymous flexbox items that are only whitespace.
- Resolved: A flex item with
visibility: collapse stays in box tree, but has special layout: Do layout once normally, then collapse it to a strut of its line’s cross size and lay out again. (This keeps the cross-size stable if the flexbox has only one line.)
Flexbox: Flex Property
- Resolved: Give
flex the longhands flex-grow, flex-shrink, and flex-grow.
- Resolved:
box-sizing affects flex-basis
- Resolved: Use
flex-basis for sizing flex items, even inflexible ones.
- Resolved: Flex items are flexible by default.
- Resolved: On flex items, a
flex-basis of auto computes to the computed width or height (as appropriate); on elements that are not flex items, it always computes to auto.
Flexbox: Flex/Cross Sizing
- Resolved: Accept Alex’s new formulation for negative flexibility.
- Resolved: Negative flexibility is 1 by default.
- Resolved: Add new
auto keyword as the initial value of min-width and min-height. On CSS2.1 display types it computes to zero; on flex items it is treated as min-content.
- Resolved: For cross-sizing of a flex line, adopt proposal C.
Flexbox: Pagination
- Resolved:
break-before/after: always triggers a flex-line break, and all values that trigger fragmentation on an item in a row flexbox get propagated to the flex line.
- Resolved: Make page-breaking algorithms for flexbox informative, as an example; UAs can do better.
Flexbox: Terminology
- Resolved: Rename
display:flexbox to display:flex.
- Resolved: Change spec terminology from “flexbox” to “flex container”, and “flexbox item” to “flex item” to be more consistent with other specs.
Full minutes
CSS Regions Level 3 Updated
The CSS Working Group has published an updated Working Draft of CSS Regions.
CSS Regions allows you to collect content in a named flow, then flow this content through boxes in a region chain.
The most important change in this new draft is the ability for region boxes to automatically size to the fragment of content they receive. This is described in a new visual formatting section which explains the processing model that enables this new behavior. In particular the auto sizing processing model allows regions to have height:auto and size themselves to accomodate content between breaks. There is a thorough example that walks through the steps, and a quick summary on www-style.
Another big change is an updated and expanded CSSOM section. It incorporates extensive feedback from specification and implementation work.
The introductory example has been reworked to include a final region that sizes to accommodate the remainder of the flow content and use grid layout to position the various regions. The code for the example has been collected in one place to improve readability.
A new section describes how multicolumn properties interact with region chains.
There are too many other changes to list here, but you can look through the change list to see the record of every difference from the last working draft.
This new draft is still a work-in-progress, but many improvements have been made since the last official publication. All of the known needed work on outstanding issues is captured in the draft with links to the latest discussions.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css3-regions]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Exclusions and Shapes Level 3 Updated
The CSS Working Group has published an updated Working Draft of CSS Exclusions and Shapes.
CSS Exclusions and Shapes allows you to define non-rectangular shapes for wrapping content, for instance around the outside of floats. It also extends content wrapping functionality previously limited to floats: now any element can become an exclusion.
This new draft contains an update to the exclusions processing model, which describes how exclusions cause content to wrap around their shapes. Several updated examples show how the model works using varying positioning schemes such as floats and grid layout.
The draft also goes into much more detail on how floats work with all of the new capabilities. A new example using floats has been added, and a new section clarifies how floats and exclusions interoperate.
CSS Exclusions and Shapes is still a work-in-progress, but many other improvements have been made in this draft since the last official publication. All of the known needed work on outstanding issues is captured with links to the latest discussions.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css3-exclusions]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes and resolutions telcon 2012-05-02
The main topic of the telcon was the Disposition of Comments for the March draft of Values and Units.
- Resolved: Errata CSS 2.1 to disallow ‘inherit’ after comma in ‘font-family’
- Resolved: Include the sign in the NUMBER token in CSS 2.1.
- Resolved: The result or attr() is of integer type if all operands are integer and there is no division.
- Resolved: Allow attr() in calc() and disallow cycle().
- Resolved: cycle() is top-level only; when attr() is not at top level then the type of the fallback must match.
- Resolved: Drop minimum supported multipliers for repeated components from 30 to 20.
Full minutes
CSS Writing Modes Level 3 Updated
The CSS Working Group has published an updated Working Draft of CSS Writing Modes Level 3. This CSS module covers bidirectional text and vertical text layout.
The primary changes in this update are to integrate references to Unicode Technical Report #50 (which will define the default orientation of all Unicode characters) and to adjust the algorithm for auto sizing in orthogonal flows to account for the size of the containing block. Significant changes since the last Working Draft are listed in the Changes section.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css3-writing-modes]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS3 Media Queries reaches Proposed Recommendation
The CSS Working Group has published CSS Media Queries as a Proposed Recommendation. Media Queries allows authors to tailor the style that they want to apply to a document based on characteristics of the environment the document is being rendered in.
Changes since CR are corrections of errors in non normative text and clarifications, and are detailed in the Changes section. A Disposition of Comments is also available.
As always, please send feedback to the (archived) public mailing list www-style@w3.org (see instructions). When sending e-mail, please put the text [css3-mediaqueries] in the subject (alternatively you can email one of the editors and ask them to forward your comment).
![[Photo: group photo of the CSS working group in Lyon, France]](/Style/CSS/csswg-2010.jpg)
Contact: