Minutes Telecon 2017-07-19
- Resolved: Request updated PR for writing modes
- Resolved: Publish an updated WD of css-align
- Resolved: Drop
inline-list-item
- Resolved: Publish new WD of css-display
- Resolved: Accept this edit and close issue 1552 as resolved
- Resolved: Make the change to page up and down to put in intended direction and endpoint class
- Resolved: Take home and end out of intended direction class
- Resolved: Updated CR for scroll snap
- Resolved: Make the changes listed in issue 1436 in css2.1 and position
- Resolved: Accept the change in issue 1578:
object-fit: scale-down should become a flag
- The group discussed issue 1611: Should last-baseline’s fallback alignment be safe or unsafe?
- TabAtkins introduced the issue and indicated that they were leaning toward safe since it allows all the content to be reached.
- However, it was discovered on the call that the usual fallback is unsafe so using safe would cause unexpected behavior.
- There was value in both arguments, so discussion will continue on github in hopes of reaching a resolution next week.
Full Minutes
Minutes Telecon 2017-07-12
- Anyone with interest was asked to respond to the request for review from the TTML working group.
- fantasai will reply to Chris shortly in order to resolve if Writing Modes needs one more CR cycle.
- gregwhitworth began reviewing all the Flexbox tests to establish coverage.
- The group discussed how to continue moving CSS2 publications forward:
- Though the group recorded several resolutions in February to change the CSS2 publication process (recorded here) the new process still hadn’t been fully implemented. This has lead to there being greater confusion as to what is the most up to date and possibly new work occurring in more than one place.
- There was some concern that this new process was either not the best way forward or not well understood, so there will be a conversation at the Paris F2F to revisit the original decision.
- In order to reduce confusion as to what is currently out there, Bert will look through css-testing and make sure that any changes there are merged into css22 before deleting css-testing as well as css-source (which is currently empty).
- There were three items listed in github for the group to choose from to resolve the compatible alignments not always being compatible issue.
- Exclude items with
align-self: stretch and a specified height constraint (min-height/height/max-height) from align-content: last baseline alignment.
- Exclude items with
align-self: stretch whose specified height constraint gets triggered such that it no longer sizes as stretch.
- Treat items with
align-self: stretch and align-content: last baseline as having an end fallback alignment instead of a start fallback alignment.
- Resolved: Option 3 from issue.
Full Minutes
Minutes Telecon 2017-07-05
- Resolved: New WD of Motion Path
- Conversation around alias “nowrap” as “no-wrap” started with the three options the topic had previously narrowed down to:
- No change at all
- Add dashed version as a parse-time alias
- Add dashed version as a new values that behaves the same as nowrap
- The group was divided on if the change was a good idea so conversation mostly focused on option 1 vs either 2 or 3. There was very little interest to implement the change quickly or at all from vendors so it was decided to close this for now and let the advocates see if they can convince anyone else of the need.
- Resolved: No change for issue about adding no-wrap
- The group did some on the call test cases that showed there wasn’t currently any interop on computed value of a negative calc unit. birtles brought up some concerns around Animations that needed further consideration before a decision is reached. Discussion will continue on github.
- Resolved: trim white space before / after property value in a declaration.
- Resolved: New Values boilerplate language accepted.
- There was no one strongly championing the gradients with a single color stop proposal, so it will stay out of the spec until it finds an advocate.
Full Minutes
Minutes Telecon 2017-06-28
- Rossen will confirm if Writing Modes needs a CR publication before the PR request.
- Variables needs to republished after the tests are approved.
- Resolved: make “disc” not overridable.
- Resolved: adopt inset as the new positioning property name that’s used for shorthand
- fremy will create a poll with a description and diagrams to evaluate if inset is preferable over some of the other top options.
- Resolved: leave behavior as-is and not accept ‘legacy’ values for ‘place-items’.
- Resolved: accept the proposal that margin and position properties will return the specified values.
- Resolved: the baseline alignment in block direction of tables is not defined. Also add a note prompting implementors to bring back ideas if they have any.
- Resolved: leave the ‘left’ and ‘right’ values to fallback to start.
- Resolved: remove left and right from align-self and align-content in align L3.
- birtles gave a brief introduction to issue 1301 (reconsider name of
frames() timing function) in hopes of getting more discussion before next week’s call.
Full Minutes
Minutes Telecon 2017-06-21
- The open Values & Units topics will be prepared for discussion next week.
- There were three proposed options for issue 1317(Make selection change behavior configurable):
- no change
- change from current and make it so clicking in
user-select:none undoes current section
- have two values, one for each behavior
- Resolved: option 1: no change and add perhaps a non-normative note explaining adding this on the root isn’t a great pattern
- Resolved:
line-break: break-all on its own has the effect of allowing breaks everywhere
- This change will be put in L3 of CSS Text.
- Resolved: Columns do not clip by default
- Resolved: Columns are properties applied to block containers only.
- Those arguing in favor of the proposed alias of “nowrap” as “no-wrap” did so for author usability. However, the argument against the alias is that it adds weight to the API and sets a precedent for doing this again in the future. The two sides couldn’t agree within the time of the call so the topic was deferred back to github.
Full Minutes
First Public WD CSS Overflow L4
The CSS WG has published an First Public Working Draft of the CSS Overflow Module Level 4.
CSS Overflow Level 4 builds upon Level 3 of the same specification, and adds:
- A way to control the amount of space reserved for scrollbars
- The ability to request that content that does not fit inside an element be fragmented (in the sense of the CSS Fragmentation Module)
The first of these two is a fairly self contained feature, and we encourage potential implementors or anyone interested to review it in details.
The second one is more far reaching, but also less mature, and with significant issues still open. Design level reviews are very much appreciated.
Significant changes since level 3 are listed in the change section.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-overflow-4]) 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 2017-05-31
- ChrisL will review the pending changes from gregwhitworth to Variables.
- Resolved: Add gsnedders as editor to CSS2.2
- Resolved: Blocks are turned into inline-blocks. (In reference to issue #1341: Does inlinification really need recursion?)
- Resolved: We are provisionally going with option b (inline-block -> block; inline flow-root -> flow-root). (In reference to issue #1246: Blockification doesn’t seem backwards-compatible for inline-blocks)
- TabAtkins will open a new issue to decide if you maintain separate computed values for just this one case or the whole possible space of values. Depending on that discussion the previous resolution may need to be revisited.
- Resolved: Define this (propagation of text-decoration with
display:contents) as a box-tree concept.
- Resolved: Let’s try it out, go forward with the diff. (In reference to issue #1118: Should anonymous boxes always inherit through the box tree?)
Full Minutes
Last Call for Comments on Media Queries Level 4
The CSS WG has published its hopefully last Working Draft of Media Queries Level 4.
Media Queries allow authors to test and query values or features of the user agent or display device, independent of the document being rendered. They are used in the CSS @media rule to conditionally apply styles to a document, and in various other contexts and languages, such as HTML and Javascript.
Level 4 extends and supersedes the features defined in Media Queries Level 3. It brings significant improvements on the syntax, and a shift from using media types to finer-grained media features.
This is the last call for comments, as we plan to request a transition to CR at the end of June unless issues are brought up or anyone specifically requests more time for review.
Significant changes since Media Queries 3 are listed in the Changes section.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([mediaqueries-4]) 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 2017-05-17
- Resolved: Request PR for Writing Modes.
- Those who had done a review generally thought the proposal for the interaction of the ‘inherit’ keyword and ::first-line (comment here) sounded sane, but conversation will continue on github to handle specifics and get more opinions.
- Resolved: Close issue (any-hover can’t be used to detect mixed hover and non-hover capable pointers) no change.
- Resolved: Mark the various hover and pointer things as at-risk.
- Resolved: Push scripting media query values to L5.
- Resolved: New WD of media queries 4.
- Resolved: Change the title to subsequent. (In reference to better terminology for ~ sibling combinator: GitHub issue)
- Resolved: Request PR on Selectors 3.
- Resolved: Accept the spec text proposed here (Should negative scroll-padding be allowed?)
- There will be a request for publication of Scroll Snap next week.
- Resolved: FPWD of Overflow 4
Full Minutes
Minutes Telecon 2017-05-03
- Moving specs toward REC:
- Writing Modes: fantasai will confirm that the proposed edits are okay.
- Fonts: Myles has finished changing the test font.
- Values & Units: fantasai will confirm the DoC is ready for republication.
- Transforms: Rossen will ask Bogden to help smfr with edits.
- Resolved: FPWD of Logical Properties with a short name of css-logical
- There was a lot of browser interest in achieving compatibility on scrollbar styling since it’s used widely enough that it can’t be removed. smfr had an explainer of the implementation that the Edge folks will review to see what additional information would be needed to make a compat spec, which would likely be added to CSS UI4. Anything extending beyond compat will be deferred until working group members have a better understanding of what’s out there now.
- The issue on defining/standardizing
line-height: normal (issue here) needs to be resolved before the issue on avoiding accidental double spacing (issue here) can be resolved. myles will write a test font to help make the test cases for line-height: normal more robust.
- fremy will file a bug on the appropriate browsers for the flex-shrinking propagating back down the flex chain issue (issue here)
- Resolved: Move gradient midpoint to Images L3.
- Resolved: Add the x unit to
resolution type in Values & Units 4.
- Resolved: Revert the edit to image-set in CSS Images.
Full Minutes
![[Photo: group photo of the CSS working group in Lyon, France]](/Style/CSS/csswg-2010.jpg)
Contact: