Minutes Sophia-Antipolis F2F Part I 2014-09-08: CSS3 Text, Display Module, Backgrounds, Line Grid, CSS UI, Geometry Working Draft
CSS3 Text
- Resolved: Make control characters visible. (This will be consistent with Unicode, but will break backwards-compatibility on the Web.)
- Resolved: Text shaping MUST be broken across inline element boundaries when:
- A: one of margin/border/padding are non-zero
- B: vertical-align is not
baseline
- C: it is a bidi isolation boundary
- Text shaping MUST NOT be broken across inline element boundaries when there is no change in formatting.
- Text shaping SHOULD NOT be broken across inline element boundaries otherwise, if it is reasonable and possible for that case given the limitations of the font technology.
- See original e-mail for further details
- Resolved: No change for issue 59
Full Minutes || Spec Referenced
Display Module
- Plan to defer longhands of
display to the next level; this will allow restricting combinations of display-inside and display-outside that are difficult to implement at this time.
- Discussed open issues with
box-suppress, including details that need to be defined for the hide value and how this interacts with visibility and speak. This section needs more work.
Full Minutes || Spec Referenced
Backgrounds
- Resolved: Accepted Bert’s proposed wording for CSS2.1 erratum on interaction of
display: none and the root background
Full Minutes || Spec Referenced
Line Grid
- Resolved: Publish a working draft of line grid
Full Minutes || Spec Referenced
CSS UI
- Resolved: Add
caret-color to css3-ui
- A desire to color the background/foreground of selected text lead to a conversation about bringing
::selection back and potential issues with exposing security-sensitive items (such as spell-check)
- Resolved: Add
::selection to Pseudo-elements 4.
- Resolved: Outline corners follow border-radius (no additional outline-radius property needed)
Full Minutes || Spec Referenced
Geometry Working Draft
Full Minutes || Spec Referenced
CSS Regions draft updated
The CSS Working Group has published an updated Working Draft of CSS Regions Level 1. CSS Regions gives the ability to say, “Display this content (a named flow) over there (a region chain).”
The changes from the last public working draft are only in the introduction. You may have looked into CSS Regions in the past and thought to yourself, “Magazine-style layout isn’t relevant to me.” If you have, please take a look at the new intro which now shows much more basic examples and motivations for the feature.
Please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-regions]) and your comment topic in the subject line.
(Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2014-10-08
- Resolved: Unclosed URLs at the end of file should auto-close
- Resolved: Change the values and units to make invalid empty URL fail to resolve automatically
- Resolved: Remove the old text that negates the entire media query if an unrecognized media value or feature appears
- MaRakow reported that now that there’s interest in Snappoints, he’ll begin working on the open issues.
- Resolved: Accept Pseudo Elements 4 as an official ED, add TabAtkins as an editor, and remove the bits that aren’t in Selectors 3
- Everyone was reminded to register for TPAC if they haven’t.
- Fantasai requested that people look over the Flexbox spec and have any questions ready so they can move to CR either at or shortly after TPAC.
Full Minutes
Minutes Telecon 2014-10-01
- Resolved: Publish new working draft for Regions
- Everyone was reminded to come up with topics for TPAC and to register (if they haven’t already)
- Resolved: Change the behavior of
setProperty() according to last week’s proposal following Rossen’s approval
- Resolved: Allow empty string in
media-query
- Resolved:
animation-fill-mode applies whenever it’s updated
- zcorpan will reply to this e-mail to elaborate, but the group believes that the iframes issue is addressed by HTML.
- The group was okay with all of Bert’s notes except it was suggested to move DOMMatrix into being an old version of Geometry Interfaces instead of making it a note.
Full Minutes
CSS Display Level 3 Updated
About a fortnight ago, the CSS WG published an updated Working Draft of the CSS Display Level 3. This module describes how the CSS formatting box tree is generated from the document element tree and defines properties (like the display property) that control the types of boxes thus generated.
Significant changes since CSS2.1 include:
- Splitting
display into display-inside and display-outside to independently control the layout mode inside the box and its role in the parent formatting context, respectively.
- Adding an independent “noneness” switch that does not overwrite the box type declaration. (This will make it way more straightforward to dynamically show/hide content.)
- Reintroducing
display: run-in, but with more reasonable behavior than was in CSS2.1 before it was dropped.
- Adding a
display: contents value that eliminates the element’s own box and brings its children up to act as children of its parent box.
- Adding a handy glossary of key terms from CSS2.1 chapter 9.
Significant changes since the previous draft are listed in the Changes section.
We have a couple of key issues open that we would particularly like feedback on:
- Naming of the box-hiding-and-showing property. Please send us suggestions for improvement! (Or comments on what you like about the current name. We’re pretty unsure atm, but want it to be easily understandable.)
- Run-in model: we’re looking for comments on how best to handle out-of-flow elements between run-ins that form a sequence.
- Interaction of
display: contents and counter numbering: specifically, comments from implementers about the implementability of various options, and comments from authors about how they’d expect the numbering to behave.
- Figuring out an ideal interaction for the new show/hide switch and its equivalent (the
speak property) from CSS Speech. (Likely we’ll make speak: auto depend on the value of box-suppress, but we’re open to other considerations.)
Our plan going forward is to resolve all the open issues (obviously), defer the longhands of display to another level[1], and hopefully transition to CR in the next six months.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-display]) and your comment topic in the subject line. Alternatively, you can email the editors and ask them to forward your comment, or post a comment here.
CSS Flexbox Level 1 Revision 1 Update, Call for Comments
The CSS Working Group has published another Last Call of CSS Flexible Box Layout Level 1 in response to feedback on the recent changes. Flexbox is a new layout model for CSS: the contents of a flex container can be laid out in any direction, can be reordered, can be aligned and justified within their container, and can “flex” their sizes and positions to respond to the available space. This is an update to fix various problems, particularly in the layout algorithm, found through implementation review and experience during the Candidate Recommendation phase. As before, the CSSWG is not revoking the call for implementations: we’re just issuing an LCWD to process the changes.
To help with review and with correctly updating implementations, exact diffs since the original Candidate Recommendation, and their justifications, are available in the Changes section. A Disposition of Comments is also available. The Last Call comment period ends 25 October 2014: please either send comments by then, or request an extension; we plan to process them during TPAC.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-flexbox]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2014-09-24
- The group was very interested in meeting with the digital publications working group at TPAC. dauwhe will suggest the Monday breakout time to the dpub group. Rossen will also investigate a joint meeting with the user interface task force.
- TabAtkins came to the group asking for approval to bring some items he had been working on in Images 4 up to Images 3 since he felt they were already stable items and therefore should be in the spec that’s closer to REC.
- Resolved: Allow nearest neighbor for image rendering in both directions but allow browsers to do prettier in the down directions.
- Resolved: Include image rendering in Images 3
- Resolved: Close the issue (regarding guessing resolution from file size in Images 3) with no change because we’ll fix it later in harmony with HTML
- TabAtkins will send an e-mail to the list regarding the details of his plan for lifting restrictions on nesting with image set.
- Resolved: Have image set in Images 3
- Resolved: Move crossfade to Images 3
- Resolved: Remove special case from
::first-letter
- There was support for altering the property to override an important style in CSSOM to conform with author expectations, however there was some concern about possible breakage. We will revisit the issue after there has been time to write tests to confirm there’s no compatibility issues.
Full Minutes
CSS Line Grid Draft Updated
The CSS Working Group has published an updated Working Draft of CSS Line Grid Level 1. CSS Line Grid defines features for aligning content to a baseline grid.
The changes from the first public working draft are mainly cleaning up and removing features for the first level of this specification:
- Added line-snapping examples
- Modified box-snap values
- Removed line-slack
- Removed grid offset
- Removed grid units
- Removed 2d box snapping
- Removed rounding functions
Please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-line-grid]) and your comment topic in the subject line.
(Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2014-08-20
- Resolved: New LCWD for Counter Styles
- Resolved: New CR for Backgrounds and Borders
- Resolved: New WD for Display Module
- Resolved: Adopt proposal to address overflow scroll positioning in Alignment
- The following comments for CSS Text were discussed:
- Resolved: Accept the proposed resolution for issue 4
- Resolved: Reject issue 51
- Resolved: Reject issue 65
- For issue 21, the group agreed with making the soft hyphen the only place you can break in a word as long as there’s an added contingency to handle words so long that one part still doesn’t fit on the line after the soft break.
- Issues 59 and 72 are both waiting on feedback from Microsoft and will be addressed at the next F2F at the latest.
- Resolved: Move the three documents (behavior extensions, hyperlinks, and marquee) to notes
Full Minutes
Minutes Telecon 2014-08-06
- Everyone was tasked with reading the new process for CR documents in order for the group to be able to discuss how to handle current CR documents in light of the new process.
- Resolved: John Daggett is reinstated as Font spec editor
- Many members of the group expressed a desire to have a more unified color class instead of the separation in TabAtkins’ proposal; something closer to what leaverou is trying to create. There was also concern expressed for how the proposal handled CMYK colors. TabAtkins requested that people type up their proposes and/or thoughts in e-mails so that he can respond in long form with his reasoning for separation.
- gregwhitworth will post examples to the mailing list in order to further conversation about brand color.
- There was some of skepticism about the value of the proposal for a transform shorthand, but most people wanted more time to consider it. Some others expressed a desire to focus attention on review of Transforms Level 1 before considering this proposal. TabAtkins will create a document that looks more like a spec proposal in order to aid conversation which will likely continue at the F2F in September.
- Everyone was reminded to register for the September F2F because if they don’t, they won’t have network access.
Full Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: