Minutes Telecon 2019-03-27
- There were no objections to moving Easing Functions to CR, however the editors were not on the call so resolution will be called for next week.
- Scrollbars was not quite ready for CR. There are still some open issues that need to be resolved and myles said he has some more to file. However, work is definitely progressing toward a CR.
- Houdini will request a room to meet on the Friday of TPAC.
- Resolved: Return ‘normal’ for line-height (Issue #3749: A question for the procedure to compute the resolved value of “line-height”)
- Resolved: Republish Selectors Nonelement as a Note and we are abandoning this work
- Resolved: For SVG Transform attribute there is no requirement for space or comma between transform functions (Issue #3719: SVG transform attributes: transforms don’t need to be separated)
- Resolved: Defer complex selectors for all of these selectors [:nth-child()/:nth-of-type()/:is()/:where()/:not()/:has()] and have a note in the current level mentioning this is an enhancement we’ll get to in the next level (Issue #3760: Defer complex selectors inside :nth-child() etc. to L5)
- florian introduced his proposal (Issue #3685) to be able to reuse the title of the document inline such as making it always present in the header or footer. There was concern about if using title was the best way to solve the use case, but there wasn’t enough time on the call to dive deeper.
Full Meeting Minutes
Minutes Telecon 2019-03-20
- The queue of PRs that need review has gotten long so group members were asked to review PRs and reduce the queue.
- The CSSWG has requested to meet on Monday and Tuesday of TPAC. An email will be sent to determine if a Houdini meeting should also be scheduled.
- Resolved: Accept the edits for Issue #3740 (Clarify that scroll-padding and scroll-snap-type on root propagate to viewport)
- Resolved: Accept adding
-webkit-discard value to continue properties to represent line-clamp that only applies to webkit flex boxes and make it shorthand expansion for -webkit-line-clamp (Issue #2847: Convert -webkit-line-clamp alias requirement into a spec issue)
- Resolved: Accept the edits in Issue #2905 (Allowing (or not) alternate ellipsis behavior for block-overflow)
- There was no agreement about changing the used value for line-height:normal to return the keyword ‘normal’ instead of a value (Issue #3749: A question for the procedure to compute the used value of “line-height”). Chromium returns the keyword but Webkit and Firefox return a value. The value returned may not be correct because
line-height:normal calculates per fragment of the element and any value returned would not be able to capture the multiple possible values of ‘normal’. Given that Webkit and Firefox return the value the concern is that there is content on the web depending on this value. People planned to look more into the possible implications of the proposed change. Discussion will continue on the github issue and this will be added to next week’s agenda to try and reach a conclusion.
Full Meeting Minutes
Minutes Telecon 2019-03-13
- Resolved: Publish updated CR for Scroll Snap
- Resolved: Void the previous resolution and close no change (Issue #3675: Font-family name matching requires full Unicode case comparison)
- Resolved: Make the same result for min content sizing apply to automatic minimums (Issue #2674: Resolving percentage heights of grid items during min-content sizing)
- Resolved: Change the algorithm take baseline from the first grid content instead of synthesize from first row (Issue #3645: Unintentional change to grid container baseline?)
- Resolved: Go with fantasai proposal (option a) for initial value of counter increment (Issue #3686: Initial value of counter-increment needs to be something different from none)
- Resolved: Accept the change in Issue #3649 (refer to columns not tracks)
- There is still concern that the proposed solution for issue #337 (Segment Break Transformation Rules for East Asian Width property of A) relies on a unicode property that the unicode consortium isn’t particularly maintaining. The counter argument is that the subset of properties this proposal creates will continue to be correct, even if the definition changes. A few working group members will reach out to unicode contacts to garner more feedback to lead to a decision.
Full Meeting Minutes
Minutes Telecon 2019-02-20
- Resolved: Publish new working draft of Pseudo L4
- The group discussed Issue #3605 (Specify better handling of text shadows for
::selection) but could not resolve if text shadows should be painted during ::selection. The argument for painting was that the author has already indicated that they want the text shadow. However, the argument against is that when styling the ::selection the author would not be thinking about text shadow that’s only set in one place. Discussion will continue at the F2F.
- Resolved: Trailing spaces should be counted for max-content but not min-content (Issue #3440)
- Resolved: When preserved trailing spaces hang they do it using allow-end rather than force-end (Issue #3440)
- Resolved: Include space in empty explicit grid tracks in the scrollable overflow area (Issue #3638)
- While discussing issue #3638 the group also discovered that there may be a chance to have Grid align closer to author expectations around including padding in scrollable area. A separate issue will be filed to cover that topic.
Full Meeting Minutes
Updated CR of CSS Contain
(This should have been published much earlier. Apologies for the belated announcement).
The CSS WG has published a Candidate Recommendation and invites implementations of the CSS Containment Module Level 1.
This CSS module describes the contain property, which indicates that the element’s subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
This is a minor update, driven by implementation experience and testing, focused on bug fixing and clarifications. Barring anything unexpected, the CSS-WG expects little to no change after this. People who intend to review this specification but have not yet had the chance to do so are strongly encouraged to look at it as soon as possible, as implementations are progressing, and growing usage in the wild will increasingly limit possible changes.
Significant changes are listed in the change section. A comprehensive test suite for the full specification was developed. A Disposition of Comments is also available.
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-contain]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updated CR of CSS Scroll Snapping Level 1
The CSS Working Group has published an updated Candidate Recommendation of CSS Scroll Snapping Module Level 1. This module contains features to control panning and scrolling behavior with “snap positions”.
The Changes are just fixing some errors in the previous draft. See also Disposition of Comments.
Please send any further 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-scroll-snap-1]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updated <‘property’> notation in Value Definition Syntax
The CSSWG just published updates to CSS Values and Units Level 3 and CSS Values and Units Level 4 redefining the <'property'> notation, which represents the value space of a property for re-use in other syntax definitions, to exclude any top-level #-multiplier. (See §2 Value Definition Syntax.)
The reason for this change it to make it easier to define syntax for list-valued properties and shorthands: for example, previously <'background-clip'> would represent [ border-box | padding-box | content-box ]# (a list of keywords), which precluded re-using it in defining the background shorthand syntax. Now that the top-level #-mark is ignored when importing syntaxes this way, shorthands of list-valued properties and other patterns which extend an existing value set become much easier to describe.
The full list of changes since the previous CR update can be found in the Changes section, and a Disposition of Comments is also available. (There were no substantive changes to Level 4 other than copying over the Level 3 changes.)
Please send any 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-values]) 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 2019-01-30
- Progress is being made on Issue #3440 (When to/not to include preserved trailing spaces). fantasai needs some more clarification on comments from xidorn and will then put together a proposal for working group review.
- Originally the pseudo element object was hung off the window to allow for future use in multiple element views. However many other decisions made by the group have made multiple element views hard anyway, so using element will not make it any harder in the future and will be clear to authors now.
- Resolved: Add
Element.pseudo(type) (Issue #3541)
- Resolved: Specify the current behavior and use the currentColor name (Issue #2850)
- Resolved: Specify stroke-color and fill-color are accepted in highlight styles (Issue #2362)
- Resolved: Add stroke-width to the set of properties (Issue #2362)
- There is a desire to create a standard set of principles for the list of highlight properties instead of evaluating properties one by one, however there’s also a need to make sure these can fully replace the prefixed properties.
- fantasai is looking for feedback on issue #3540 (Mark unimplemented CSSPseudoElement features at-risk) prior to next week’s call
Full Meeting Minutes
Minutes Telecon 2019-01-23
- Resolved: Change syntax to specify behavior implemented in majority of browsers (Issue #3182)
- Resolved: Defer the remaining syntax issue with a note we may address in future spec (Issue #2757)
- TabAtkins will compile a disposition of comments and request publication for CSS Syntax on next week’s call.
- Instead of solving for the handful of properties in Issue #3414 (CSS properties should apply to some SVG elements as well) the group will aim for a general solution to update all ‘applies to’ lines to have information about how they interact with SVG elements. In order to do this, interested individuals will work on a new language to use for applying to SVG elements as well as to make it clearer what the current general text around ‘elements’ really means. Once this is agreed to by the group one large PR will be drafted to make this change to all specs simultaneously. The goal is to have a first draft of the new language for discussion at the next F2F.
- Resolved: Amend the previous resolution to include form feeds so they’re processed same as lone CRs (Issue #855)
- People continue to think on issue #2950 (Better name for initial-letters property) so it will be added to the F2F agenda. On the call today one suggestion was line-span, but there were concerns that could be misinterpreted.
- There was concern that the approach taken to resolve on Issue #3329 (Which box information should we pass to the callback) was too broad and could be confusing since the data returned here would not be returned in other similar calls. Discussion will continue at the F2F.
- Resolved: Define repeat interpolation using the more restrictive rule in Issue #3503 [require that the first arg is a number, and identical between start/end; different values, or keyword values, both go discrete]
- Resolved: Do not allow quirks in ‘inset’ shorthand (Issue #3525)
- Resolved: Close this issue (Issue #3519: border-block/border-inline syntax) and add a note to the spec saying this is an intentional restriction
Full Meeting Minutes
Minutes Telecon 2019-01-16
- The group affirmed that Houdini Task Force didn’t need a separate day to meet at the next F2F.
- There are many tests that have been submitted, but not reviewed. This frustration is shared by several people, but no solution was immediately forthcoming. Some people expressed that if they are needed to review an email prompt may be more effective then a github mention.
- Resolved: Add CSS Transforms to the 2018 Snapshot
- Resolved: Move Grid from stable to rough interop in 2018 Snapshot
- Resolved: Once these edits have been completed republish 2018 Snapshot
- The resolution to Issue #2850 (How should a selected spelling error be painted?) is related to the decision on cascading / inheritance model for
::selection (Issue #2474) so that will be reviewed further to see if it helps in reaching a resolution.
- Resolved: Add a
.element property that brings pseudos back to their element (Issue #2816)
- Resolved: Make all the types include the
:: prefix for consistency (Issue #2815)
- Resolved: Rename letter and line to
::first-letter and ::first-line (Issue #2815)
- Resolved: Accept and add the
:placeholder-select pseudo class and add a note for ::placeholder that we’re interested in working on it (Issue #2517)
- Resolved: Add stroke-color, stroke-width, fill-color and paint-order (Issue #2362)
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: