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
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.
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:
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.)
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, and hopefully transition to CR in the next six months.
As always, please send feedback to the (archived) public mailing list firstname.lastname@example.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 email@example.com 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
- 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.
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 firstname.lastname@example.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
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.
Minutes Telecon 2014-07-30
- The main remaining issue for Animations from the previous telecon revolved around computing values in keyframes. dbaron and sylvaing took turns explaining the issues and complexities when there are multiple properties with a different number of values. The group came to two conclusions for handling missing values; interpolate what the value should be from the given values or use a value from the non-animated state. No definitive conclusion was reached, but the leaning was toward interpolation. Discussion will continue on the mailing list with an e-mail summary from sylvaing.
- Resolved: Floats are passed up through Ruby to the containing block
- Resolved: Publish a new working draft for Ruby
- leaverou presented her findings from a poll seeking to rename
gray() to a less confusing name. The poll gave clear results in favor of
rgba(), however the working group had a concern that this would be confusing for new authors. Discussion continued after the call on IRC to try and find a non-confusing and author friendly solution.
- Resolved: Accept
rgb() with single values and
rgba() with 2 values and keep exploring other potential values
Minutes Telecon 2014-07-16
- Bert brought the proposed errata to CSS2.1 that he wrote after last week’s conversation about canvas background to the group. He was given two edits to make in order to make the errata more accurately reflect the group’s thinking. fantasai will update the test suite to reflect the change.
- Resolved: Accept proposal for error handling rules in grid layout
- TabAtkins updated the group on where his thinking has evolved to after discussions on the very active thread. TabAtkins also will re-write a new proposal and send it to the list for further review.
- TabAtkins addressed the changes he’s made to his color classes proposal since he presented his ideas from the wiki last week. Leaverou had some concerns about his attempt to address the various types of color syntax and will write up her concerns and post them on the mailing list. The plan to remove the RGBcolor name from DOM Level 2 ran into some objections and will be addressed in the thread.
- Several resolutions were recorded for open issues in Animations. They were:
- Resolved: Defer new timing keywords for bounce animations to level 2
- Resolved: Defer a new
steps() timing function to level 2
- Resolved: Accept the edit proposed in this e-mail
- Resolved: Inserting an
@keyframe rule if it wasn’t there starts an animation.
- Resolved: Begin work on Level 2 of Animations
Minutes Telecon 2014-07-09
- Bert informed the group that he has begun the wiki for the next F2F and encouraged people to add their names if they know they’ll be attending.
- There was general support for TabAtkins’s proposal to expose some color parsing and he’ll add it to Color 4.
- It was agreed that the issue raised by gregwhitworth regarding the sixing of controls was a bug in implementations, not an issue with the Sizing spec.
- fantasai updated the group on her status with Ruby and will wait on feedback from Kawabata and more conversations with Boris.
- fantasai outlined her current proposal for simplifying grid layout error handling. There was general approval from the group and she will seek a resolution next week after Rossen has had time to review the proposal in more detail.
- At Rossen’s request, fantasai also gave an update on Flexbox and said she was close to a complete Disposition of Comments with only a few complex issues that still need to be solved.
- In conversation about justification issues in Korean vs. Japanese documents, the group felt that authors should be encouraged to language-tag their work to help avoid problems with the behavior of auto. However, since many documents aren’t language tagged, everyone also felt a solution did need to be developed. Suggestions included:
- Re-instituting the inter-character property
- Accepting that using auto limits some features and thus encouraging language-tagging
- Creating a way to auto-detect the dominant script
- The discussion will head back to the mailing list for further feedback and hopefully a good compromise on default behavior.
- Everyone agreed that the current behavior of
display: none and
visibility: hidden is correct and should be written into a spec. SimonSapin will come up with proposed text for an errata to CSS2.1 that the group can ratify.
Browse by date:
Browse by category: