Minutes Telecon 2019-05-15
- Resolved: Mark this as at risk and optional, remove profile (Issue #3925: Rescope :has to static CSS rather than .querySelector)
- Issue #3659 (lazyload) appeared to be duplicated by issue #1603 (Define crossorigin, preload and async URL modifiers) and will be closed unless there’s feedback to differentiate the two issues.
- Resolved: Republish CR of Values 3
- Anyone planning to attend should add their name to the wikis for CSS and Houdini
Full Meeting Minutes
CSS Easing Functions (Timing Functions) Level 1 Candidate Recommendation
The CSS Working Group has published a Candidate Recommendation and invites
implementations of CSS Easing Functions Module Level 1. Easing functions allow specifying the rate of change of some value according some measure of progress; for example, the rate of change in a CSS property value over time in an animation or transition effect.
This module extracts out these “timing functions” from earlier drafts of CSS Transitions for easier re-use across CSS and SVG modules. It also adds some additional options to the steps() function.
There are no significant changes since the previous Working Draft.
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-easing]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Up-to-date Working Draft of CSS Lists Level 3
The CSS Working Group has published an updated Working Draft of CSS Lists Level 3. The Lists module covers list-styling options such as changing counter styles and marker position as well as automatic counters and numbering. Level 3 introduces:
This is a significant and overdue redraft of Level 3: some experimental features were dropped and the whole draft has been streamlined and tightened up, shifting the draft from “please don’t try to implement this” to “pretty reliable”. However, there are still some open issues against Chapter 4 (Automatic Numbering with Counters), and we recommend continuing to use CSS2.1 as the definitive reference for those features until Level 3 has been fully synchronized with it. Changes since the last Working Draft 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 ([css-lists-3]) 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-04-24
- Resolved: Leave inverted colors as is, add webkit UA stylesheet as an example implementation for MQ L5 (close no change) (Issue #3858)
- Resolved: Add inversion rule to the UA stylesheet (Issue #3858)
- The authors were asked to revisit and update the security and privacy section for Media Queries levels 4 and 5.
- Resolved: Add the original list of colors from TabAtkins and fantasai as well as ones by smfr and ActiveText (Issue #3804) [List: Canvas, Text, LinkText, VisitedText, Highlight, HighlightText, GrayText, ButtonFace, ButtonText, ActiveText, Field, FieldText]
- There are use cases to support solving issue #3667 (Need a way to return the max value of a counter within a scope). Google is looking more to see if they’re interested in implementation a solution.
- Resolved: Publish new WD of Lists
- Resolved: Add fantasai as editor CSS Lists L3
- The original use counter for issue #3814 (Figure out what to do with non-standard CSSStyleSheet methods in WebKit / Blink) was too high for the methods to be dropped, however the data will be looked at more closely to ensure it’s not erroneously high.
- Resolved: Non-initial custom properties should be exposed on computed style objects, open a new issue about defining order (Issue #1316)
- The group was actioned to review and give feedback on the request from WHATWG around lazyload.
Full Meeting Minutes
Minutes Telecon 2019-04-17
- Resolved: Do a CSS parse on parameter for
element.pseudo() (Issue #3603: Should Element.pseudo(“unknown”) be an error or return null?)
- Resolved: Set minimum number of parenthesis to 32 (Issue #3462: Minimum nested pairs of parentheses in calc to 32)
- Resolved: Raise the number of expressions that must be handled to 32 (Issue #3462)
- Resolved: Start a new Color-Adjust draft (Issue #3807: Holistic review/proposal of color-modifying things)
- Rossen and Rune will be editors
- Resolved: Add the color-scheme property and meta with updated grammar and no ‘only’ property to Color Adjust spec instead of supported-color-scheme (Issue #3807)
- Resolved: Add forced-colors MQ to MQ spec (Issue #3807)
- Resolved: Add forced-color-adjust property as an opt to into new spec (Issue #3807)
- Resolved: Move print-color-adjust property into the new spec (Issue #3807)
Full Meeting Minutes
Minutes Telecon 2019-04-10
- Resolved: unicode-bidi / direction apply to
::marker (Issue #3809)
- Resolved: Apply counter-set after counter-increment (Issue #3810)
- Resolved: Implicit list-item counter is not reflected in computed style (Issue #3769)
- Resolved: Add
:picture-in-picture and :fullscreen to Selectors 4 (Issue #3796)
- The spec for
:picture-in-picture needs a permanent location that Selectors 4 can reference.
- Resolved: Do not propagate any style from display:none HTML or Body (Issue #3779)
- Resolved: Add
::marker to interface CSSPseudoElement (Issue #3769)
- Resolved: The ‘content’ property should apply to
::marker (Issue #3499)
Full Meeting Minutes
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
![[Photo: group photo of the CSS working group in Lyon, France]](/Style/CSS/csswg-2010.jpg)
Contact: