Minutes Telecon 2019-10-16
- Resolved: Pseudo elements are targeted via a parent plus a pseudo selector (Issue #4301: Dependency on CSSPseudoElement)
- Resolved: intrinsic-size is the name of the new property and value set is ‘auto’, ‘legacy’ and a length (Issue #4229: Proposal: content-size CSS property)
- There is ongoing discussion on github for how to resolve issue #4411 with several proposed solutions. The proposals are:
- Define that a subgrid subsets its parent grid’s template based on what part of it is covered, and ensures that its edges provide the requisite -start/-end lines at its edges. (This makes templates more of a “thing”, rather than a mere translation into line names that can subsequently be forgotten.)
- Define that the grid-*-start property searches the implicit lines before the first line instead of the lines after the last line if a specified line name is missing, similar to how span foo searches in opposite directions based on whether its a grid-*-start or grid-*-end value.
- Define that, while implicit lines have most names in the infinite space of possible names, only lines before the first line also have names ending in -start, and only lines after the last line have names ending in -end.
- Anyone interested should add their thoughts to the github issue.
- Resolved: Serialize the subgrid template rows and columns to only include line names defined for the subgrid locally and not include names that came from the parent grid (Issue #4362: `grid-template-rows/columns` Computed / Resolved Values for ‘subgrid’ values)
- Resolved: Space before a line break is removed even if reordered to the middle of line by bidi reordering (Issue #4308: Define break at space to remove a space explicitly)
- Florian will get i18n feedback for issue #4283 (Need additional value of word-break for Korean) to see if the property has use cases outside of Hangul, but the group was generally inclined to add a property to support this use case.
- Resolved: We are redefining the size property in @page to be called page-size. Also defining that size in the page context parses into page-size. The size property is a shorthand for width and height (Issue #820: Adding a ‘size’ shorthand for ‘width’/’height’)
Full Meeting Minutes
CSS Multiple-column Layout Level 1 updated Working Draft
Today I have published a new Working Draft of CSS Multiple-column Layout Level 1. This WD includes a number of changes and clarifications based on discussion and resolutions made since the last publication in May 2018.
Significant updates
You can find the significant changes from the May 2018 draft in the changes section of the draft. In particular I would appreciate a review of the changes to the section, The Multi-column Model. This section has undergone a significant rewrite, based on input from Morten Stenshorne and help from fantasai.
Additional changes include:
- Defining a spanner as an out-of-flow element, which leaves a forced break. This edit based on the resolution of 28 Feb 2019.
- Moving the definition of
column-gap to the Box Alignment specification, as column-gap is defined there for other layout methods.
- Properly defined how the margins on spanners collapse, resolved 22 October 2018.
- Several editorial changes to improve the clarity and readability of the specification. This work was informed in part by a specification reading workshop I held with members of Fronteers.
What’s next for multicol?
Over the past year I have begun sorting through the test suite for the specification, and inlining the tests in the specification. I intend to continue this work, with the aim of creating a complete test suite for multicol before taking it back to CR.
We have an outstanding issue (4036) about the behavior of the column-fill property, and whether it should behave in the same way in continuous media such as a web page, and paged media such as a printed webpage or book. I would appreciate comments on that issue.
Please review the specification and raise any additional issues on GitHub prefixing your issue title with [css-multicol].
PR of CSS Containment Module Level 1; FPWD of Level 2
The CSS WG has published a Proposed Recommendation 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 document is intended to become a W3C Recommendation. This document will remain a Proposed Recommendation at least until 13 November 2019 in order to ensure the opportunity for wide review. The W3C Membership and other interested parties are invited to review the document and send comments. Advisory Committee Representatives should consult their WBS questionnaires.
Changes since the last Candidate Recommendation are listed in the Changes section.
A disposition of comments and implementation report are available.
The CSS WG has also published a First Public Wording Draft of the CSS Containment Module Level 2. This is initially identical to level 1 discussed above, except that it retains an at-risk feature that was dropped from level 1 during the CR period: style containment. This extends the concept—and benefits—of containment to features like the counter-increment property or content: open-quote, which can otherwise have effects on more than just an element and its descendants.
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.)
Minutes Telecon 2019-10-09
- Resolved: Close this issue (Issue #4357: Propagation from body to document element is annoying) no change
- The group continued the conversation started at TPAC about the proposal for device-pixel-border-box (Issue #3554)
- The name ‘device-pixel-border-box’ will need to be bikeshedded since it’s not referring to the border-box but instead the content-box.
- Making the value optional could lead to too inconsistent of results to be worth doing. This will be split into a separate issue.
- The object will be a width and height not a rectangle since there’s no need for a top left setting.
- The discussion as to if there is a new API required if this is added to resizeObserver will be split into a separate issue.
- Resolved: Add API to get content box height and width in device pixel sizes to resize observer. Only return when requested and applies to all element.
- Resolved: If there is a language for which you do not know the breaking rules. Rather then treating as unbreakable you treat it as breakable anywhere similar to
overflow:anywhere (Issue #4284: Allow breaking anywhere when dictionary is missing for SEA scripts)
- Resolved: Accept Mat’s proposal which is that resolved value unwraps repeat notations and does not insert track sizes for subgrid (Issue #4362: `grid-template-rows/columns` Computed / Resolved Values for ‘subgrid’ values)
- fantasai plans to request CR for Grid 2 during next week’s call.
Full Meeting Minutes
Minutes Telecon 2019-10-02
- The charter has the proposed changes edited in and is ready to be announced.
- Issue #4357 (propagation from body to document element is annoying) will be covered next week, but in advance browsers are requested to review to see if they intend to make the change that’s being questioned.
- Resolved: Accept the proposed changes: We move where simplification occurs from being consequence of serialization to happening on the underlying value (Issue #2245: Actually describe how/whether computed math functions are simplified from specified ones)
- Resolved: Accept proposal in favor of serializing with the calc expression (Issue #3757: Support
number (and therefore calc) as a ratio)
- Resolved: Allow percentages inside the scale (Issue #3399: Have scale function accept percentage value)
- mwoodrow will create proposed spec text for issue #3322 (Should the overflow area take scroll position into account) based on how Gecko has written their code.
- Resolved: Close Issue #3084 (Interpolation of perspective) no change
- Resolved: 0 is allowed with 1px being the render time clamp (Issue #413: Zero value in
perspective() function)
Full Meeting Minutes
Minutes Telecon 2019-09-04
- fantasai introduced the proposed process changes that will be presented formally at TPAC. There is a presentation, mailing list, and GitHub repo for this. The goal of this new process is to make it easier to keep CR and REC level specs up to date by reducing the steps needed for Director approval and changing patent review triggers.
- Resolved: Add navigation controls media query to MQ 5 (Issue #4187)
- The group was leaning against issue #4162 (Expose User Preference Media Queries as HTTP Client Hint or HTTP Header) because the general feeling is that is would not have a significant benefit and may be another vector for fingerprinting. These concerns will be added to GitHub and discussion will continue there.
- The main part of issue #4123 (It should be detectable whether an element ellipsized the text) can be closed, though there is a sub-issue on some APIs not reporting subpixels which will need to be addressed still.
- Resolved: No change re computed value of list-style-type (Issue #4210: Compute non-existent `list-style-type`
counter-style to `decimal`?)
- Resolved: Do not add table-cell/table-caption as display-outside values at this time (Issue #3940: Make `table-caption` and `table-cell`
display-outside values)
- Anyone unable to attend a call next week due to travel to Japan should say so early on so a determination can be made if there are enough people to get quorum next week or if the call should be canceled.
Full Meeting Minutes
Minutes Telecon 2019-08-28
- The group continued discussing the proposal to add system-ui-serif, system-ui-monospaced, and system-ui-rounded (Issue #4107).
- The main focus was if there is a valid use case to support these new values instead of having Apple expose these as named fonts.
- The primary use case is for web apps where they want it to look as native as possible including using the same fonts as the system uses.
- There was disagreement in the group as to if this is really useful since not all systems have fonts that map to these three values.
- If this proposal is accepted, the group also discussed how to handle fallbacks. The two options are to fallback to a regular system font or to allow these values to be a part of a font family so authors can control the fallback.
- Discussion will continue on github to try and reach a consensus.
- Issue #3440 (When to/not to include preserved trailing spaces) has clearly defined proposals and PRs and anyone with an interest was requested to review them and weigh in on github.
- Having sizing available for aspect-ratio only boxes (Issue #4228: aspect-ratio-only boxes should be able to size to grid container) was a desired behavior. However there were concerns about this adding significant complexity to the layout algorithm for implementors, especially when there are nested grids or when subgrid is introduced. Comments on github are welcomed, especially from implementors of layout to see how large of a concern the algorithm changes present.
- The group’s direction was to not simplify values when aspect-ratio is number/number (Issue #3757: Support
number (and therefore calc) as a ratio). There wasn’t time to discuss other problematic cases (such as negative numbers and 0 in the denominator) so discussion will continue on github.
Full Meeting Minutes
Minutes Telecon 2019-08-21
- Charter issue #219 needs to be resolved before the charter goes for approval since no one is happy with the current horizontal review text
- The implementation report has been updated. Implementors are requested to review to see if any of the changes are small bug fixes that can be addressed quickly and easily
- The unintentionally dropped text about sizing orthogonal flows (Issue #4220) was edited back into the spec for review.
- Resolved: Republish Writing Modes L3 with added/missing section for orthogonal writing modes provided no issues raised before Friday
- Resolved: Loading images are not invalid but treated similarly as explained in Image Values (Issue #1984: Specify fallback behavior when replaced or background image content not available)
- Resolved: Republish CR of CSS Images 3
- Resolved: background-color computes to the system background-color for all values but the alpha channel (Issue #4175: background-color in forced color modes needs more than a simple unset)
- TabAtkins briefly introduced the proposal for content-size so that people could review in advance of a longer discussion. Comments can also be added to github issue #4229
- myles introduced the proposal to add system-ui-serif, system-ui-monospaced, and system-ui-rounded in order to reference the new fonts introduced in iOS and macOS (Issue #4107)
- The fallbacks need to be clearly defined for these values
- Environmental variables should also be investigated as a possible solution to this use case
- There wasn’t time for a full conversation so this will be discussed on next week’s call
Full Meeting Minutes
Updated WD of CSS Lists Level 3
The CSS Working Group has published an updated Working Draft of CSS Lists Level 3. This module contains CSS features related to list markers and counters: styling them, positioning them, and manipulating their value.
This update contains a major clean-up of the “Automatic Numbering with Counters” section, including fixing various sync errors against CSS2.1. It should now be usable as a reference for implementation. Remaining work includes more precise definitions for marker layout and better integration with HTML list numbering, particularly reversed lists. See notes and open issues.
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-08-14
- Apple will look into dates and locations for the second F2F in 2020. If anyone has conflicts please add them to the wiki so they can be factored into date selection.
- Resolved: No limit. If past what the UA can render it’s clipped (Issue #4059: Limits on text-underline-offset to preserve semantic meaning)
- Resolved: No change to the current spec, use thickness (Issue #4138: Rename `text-decoration-thickness` to `text-decoration-weight`?)
- Myles will review issue #1984 (Specify fallback behavior when replaced or background image content not available) for next week’s call.
- Resolved: Update note saying this is not for implementation and will be dropped (Issue #4164: Should the values of image-orientation include the
angle variants?)
- After issue #1984 is resolved there will be a call for republication of CSS Images.
- It seems like browsers function interoperably in issue #4181 (Should automatic list-item increment adjust for ol[reversed]?) after the initial value is determined so the group was leaning toward UA magic to handle this.
- Resolved: Update to match 2.1 and make counter(name, none) invalid (Issue #4163: counter(name, none) should be invalid)
- Resolved: Republish Lists 3 with open issue on ol[reversed] and reversed counter.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: