Minutes Telecon 2019-06-20
- Coming out of the F2F there is a push to get Writing Modes to REC status. Before next week’s telecon, there will be follow-up done to check into getting Mozilla to conform to a change in the spec.
- Resolved: Republish Display
- Resolved: Accept change in https://github.com/w3c/csswg-drafts/commit/5a43ab7210d08c9a012a7697eb39a382f8133079 (Issue #3694: How to distribute space using flex ratios when the sum is 0?)
- Resolved: Accept change in Issue #3693 (“Maximize Tracks” shouldn’t distribute equally for flexible tracks)
- Resolved: Accept proposal in Issue #3683 (Don’t expand flexible tracks under a min-content constraint)
- The group will wait a few more weeks to see if anyone has a concrete proposal to handle the concerns in issue #3880 (Combine forced-color-adjust and color-adjust properties somehow?). If there’s no proposal the group will close the issue no change.
- Resolved: Computed value of color-scheme will match its specified value (Issue #3848: Disallow repetition of color-scheme keywords?)
- Before deciding if multiple color-scheme
meta values should take the first or the last value (Issue #3846) TabAtkins will investigate if other metas do first or last. This will allow the group to see if this is something that can be standardized so authors don’t have to try and remember which metas behave which way.
- The group generally agreed that option/optgroup should be able to set counters (Issue #4004) though there were concerns about how it would interact with things like
display:none. TabAtkins and fantasai will come up with proposed spec text for the group to review and debate.
- The group would like `text` of `leading-trim` to be interoperable (Issue #3978) but there were concerns that browsers aren’t using the same tables for calculations so interoperability may not be possible. At a higher level there is a desire to make new font functions handled the same for all browsers and OSs even if older values cannot be. The group ran out of time so discussion will continue in the GitHub issue.
Full Meeting Minutes
Updated Working Draft of CSS Sizing Level 3
The CSS Working Group has published an updated Working Draft of CSS Sizing Level 3 . This module describes the various CSS sizing properties like width/height/etc. Level 3 extends them with keywords that represent content-based “intrinsic” sizes, allowing CSS to more easily describe boxes that fit their content or fit into a particular layout context. It also defines a lot of the key sizing terminology used throughout our layout specs.
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-sizing-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
First Public Working Draft of CSS Color Adjustment Level 1
The CSS Working Group has published a First Public Working Draft of CSS Color Adjustment Level 1. This module introduces a model for and controls over automatic color adjustment by the user agent to handle user preferences, such as “Dark Mode”, contrast adjustment, or forced-contrast color schemes.
This is a First Public Working Draft and the features herein are subject to change. Implementers should track open issues and ongoing discussions.
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-color-adjust-1]) 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-05-22
- The plan for issue #3731 (How should inline-axis intrinsic sizing work for ‘fit-content’ and ‘fit-content()’?) is to select option #2 (reverse-compute them on their own, where a box with max-content size S and width: P (a percentage, expressed so 1.0 is 100%) has a max-content contribution to its parent of S/P. This prevents overlap in block-like layout, but isn’t sufficient when there’s more than one thing per line.) but the appropriate people weren’t on the call to resolve.
- Resolved: The resolved value of min-size: auto is 0 when there is no box (Issue #3557)
- Resolved: Republish WD of css-sizing
- Resolved: Publish Media Queries 5 as FPWD, with a pending privacy & security section & the resolved edit re UA stylesheets
- Resolved: Publish css-overscroll-behavior-1 FPWD
- Resolved: Make spec match browsers on color hints / positions (Issue #3931)
- Resolved: Add `font-size: xxx-large` to Fonts level 4 (Issue #3907)
- Issue #3194 (Font fetching in anonymous mode makes it impossible to link to fonts behind authentication) needs further discussion on GitHub and those interested are encouraged to comment there.
- Some browsers have implemented the changes for
display:contents and those that have not are encouraged to do so.
- Resolved: No change to URL serialization for fragment-only URLS (Issue #3195)
Full Meeting Minutes
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
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: