Minutes Telecon 2018-12-19
- Resolved: text-decoration-fill and -stroke goes into Fill and Stroke spec. Shapes properties go into Shapes L2. Both with notes they’re at risk and looking for implementer interest. (SVG Issue #591)
- Resolved: Close this issue (Issue #3445: Non-existent line names in abspos grid items) and accept the clarification note.
- Resolved: Add a clarifying note to L3 and discuss a potential new value in L4 (Issue #3434: Prevent line breaking after explicit hyphens)
- There is disagreement to if the segment break transformation rules should be defined using East Asian Width or if there’s a different approach available.
- The argument to use East Asian Width is that currently line breaks are unusable and this moves toward addressing that even though it requires special casing some characters, like emoji. Additionally more characters can be added at a later date if a better system is found.
- The argument against is that since it is currently unused time should be taken to find the right solution and avoid risk that we’ll end up with a compatibility problem later.
- fantasai stated that there were two principles she’s like to solution to adhere to:
- We have defined rules all UAs must follow.
- We’re using unicode property of some kind and not having CSS spec create a custom list
- Discussion will continue on the issue and then on a telecon or F2F.
Full Meeting Minutes
Minutes Telecon 2018-12-12
- The group will have a call on 19 Dec, but not 26 Dec or 2 Jan.
- Resolved: Return computed value for
getComputedStyle() for these properties [grid-row-start/etc] (Issue #2681)
- Resolved: Fully specify the first 2 bullet points and leave it at that for this level (Issue #3201)
- Check interpolation type per track, rather than for the entire list, before falling back to discrete. I.e. a length-percentage track can animate between two values while an adjacent auto track flips discretely to min-content.
- Allow discrete interpolation of line name changes independently of track sizes.
- Resolved: Use the normalized value to serialize grid-template-areas (Issue #3261)
- The plan is to request republication of Grid next week so anyone interested in review should look over the spec.
- myles and anyone else interested will review issue #337 (Segment Break Transformation Rules for East Asian Width property of A) for discussion on next week’s call.
- Resolved: Publish a new WD of Text L3
- The proposal to add an @partial rule to serve as a way to overwrite a parts of an @rule (details here) was interesting to the group, but there needs to be more use cases to argue that there is a larger need that justifies this change. Either way, the original use case of being able to override some values on the
@font-feature-values
Full Meeting Minutes
Last Call for Comments on CSS Text Level 3
The CSS Working Group has published an updated Working Draft of CSS Text Level 3 and is issuing a Last Call for Comments prior to requesting a transition to Candidate Recommendation. CSS Text contains various typesetting properties not related to font selection, such as alignment, line breaking, white space collapsing, text justification, and other forms of text-level spacing adjustments.
This update completes the handling of all comments received during the 2013 Last Call period and up through today. A Disposition of Comments documents the comments and their resolutions. The CSSWG requests review of the draft and the changes. If no further comments are received, we expect to transition the draft to Candidate Recommendation in two weeks, thus the deadline for comments or requests for extended time to review is Wednesday 19 December 9:00am Pacific Standard Time.
Note that requests for new features are being deferred to Level 4. This is just a request for review of the existing features in Level 3. (Comments on Level 4 are of course also welcome; please file appropriately.)
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-text-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 2018-11-28
- This telecon was dedicated to beginning to work of a Line Layout task force that will work on developing a new line sizing model.
- The possibilities were gathered into potential spec text in order to create a starting point for discussion.
- Questions and concerns were gathered in Issue #3199
- A new issue will be opened to dive deeper into how to handle interactions with Ruby reserve.
- There was interest in making sure that the handling of Ruby reserve is well defined and not a mystery.
- Having a property to ensure there is enough space on the first or last line if the author thinks they might have a Ruby in their paragraph was also of interest to solve.
- There were two main models proposed, ‘better behavior’ and ‘box model behavior’
- Better behavior is “Line boxes are sized, and content positioned within them, as defined in [CSS2], except that positive half-leading is not applied to any box other than the root inline box.”
- Box model behavior is “Line boxes are sized to fit the root inline box and its half-leading, as well as the outer edges of any inline-level descendants in the same inline formatting context. Positive half-leading is not applied to any other inline box; negative half-leading is applied as negative margins to inline boxes whose block-axis margins, borders, and padding are zero.”
- The group didn’t think both were necessary. Of the two, the preference was to focus on the box model behavior.
- There was also ‘absolute behavior’ listed but it was captured to make sure the proposal listed all options and no one believed it was the right path forward.
- Similarly, there was no desire to add the ‘quirks’ behavior proposed.
line-height:normal compatibility needs to be addressed in this proposal. The current behavior works well so there’s an interest in making sure it stays.- fantasai will re-write the proposal with two options, ‘legacy’ and ‘normal’ where ‘legacy’ is the as-is behavior and ‘normal’ is the ‘box model behavior’ explained above.
- The box model behavior will be re-written to unconditionally have negative padding adjust the content box (An issue will be filed to track this)
- The normal property will apply to inline boxes (An issue will be filed to track this)
Full Meeting Minutes
Updated Working Draft of Selectors Level 4
The CSS Working Group has published an updated Working Draft of Selectors Level 4. Selectors are patterns that match against elements in a tree and are used as a core part of CSS and in DOM methods such as .querySelector(). This update adds, drops, and renames a number of selectors:
- zero-specificity pseudo-class named :where()
- :matches() renamed to :is()
- :blank defined to select empty user input elements
- :empty tentatively redefined to ignore whitespace-only text nodes
- :drop() dropped due to removal of support in HTML
- Added case-sensitive attribute value matching flag
s.
In addition, the specificity rules for :is() and :nth-child() were altered to use the most specific selector argument rather than the most specific selector that happened to match. See specificity rules in the spec and
and discussion leading up to this change in Issue 1027.
Changes since the February 2018 WD are all listed in the Changes section.
One major issue that’s open is redefining the way invalid selectors are handled within :is() and similar pseudo-classes to ignore unknown selectors rather than invalidating the entire style rule. See Issue 3264. Another series of open issues concerns the :visited pseudo-class and how to balance security concerns with usability requirements. Other remaining work is largely clarifications and better integration with the DOM and HTML specifications.
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 ([selectors-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 2018-11-21
- Resolved: Publish WD for Transforms
- There hasn’t been any recent work toward resolving the concerns that have been already raised about the Exclusions spec. (Issue #3308) Interest from web developers is still high so those interested in working on it will compile use cases and revisit the open concerns in light of the use cases.
- Resolved: Add ‘always’ and ‘all’ to break-before and break-after where always is on the nearest fragmentainer and all breaks across all fragmentainers. (Issue #3318)
- Resolved: Use media query style invalidation inside pseudo classes that accept selector lists (Issue #3264)
- Resolved: Kick the can down the road and think about this (Issue #3082: Reconsider removing selector list invalidation) for Selectors 5
- Resolved: Add
:defined to selectors L4 (Issue #2258)
- Resolved: Publish a new WD of Selectors 4
- The draft proposal for
line-box-contain (Issue #3199, Proposal) created a lot of interest, but time ran out on the call so those who wish to discuss further will organize a separate call to dive deeper into details.
Full Meeting Minutes
CSS Flexbox Level 1 Updated
The CSS Working Group has published an updated Working Draft of CSS Flexible Box Layout Level 1, which defines the flex layout model. The contents of a flex container can be laid out in any direction, can be reordered, can be aligned and justified within their container, and can “flex” their sizes and positions to respond to the available space. We expect this model to be particularly useful for UI layouts.
This update resolves the undefined behavior of block-axis percentage margins and padding and addresses issues found since the 19 October 2017 publication. Exact diff-marked changes, and their justifications, are available in the changes section and a disposition of comments is also available. There remains one significant issue open, pending a Web-compat investigation.
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-flexbox-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 2018-11-14
- Resolved: Rename
:matches() to :is() and deprecate :matches() in Safari and anywhere else using it (Issue #3258)
- There is a use counter running on
:blank (Issue #1967). The group will look at this in ~2 months once there’s data. If there’s no compat risk, Chrome is willing to change.
- Resolved: Add a Sensitive ‘s’ flag (Issue #2101)
:valid-within / :invalid-within pseudo-classes may need to move into Selectors 5 (Issue #3072). There’s also interest in investigating :has-child to see if that solves enough use cases to be worth doing.- There was disagreement on where backdrop filter should be able to be set (FXTF Issue #53: Backdrop filters should not use BackgroundImage). Isolating it would reduce likelihood that this is an expensive property to implement, but also reduces the potential functionality of the property. Discussion will continue in the github issue around potential use cases and this will be added to the next APAC agenda when dino can attend.
- Resolved: Publish a new WD of Filter Effects L1
- majidvp is working on trying to implement the propose change in issue #2988 (‘overflow’ 2-value syntax is in wrong order). In addition to this specific problem there’s a need to address the larger issue of logical and physical properties interacting with shorthands.
Full Meeting Minutes
Minutes Telecon 2018-11-07
- Resolved: Republish CR of Geometry API spec
- Resolved: Add jensimmons as co-editor of Sizing spec
- jensimmons requested review of her proposal to prevent overflow in a container with an explicit aspect ratio (Issue #3268)
- Resolved: FPWD for Shadow Parts spec
- Resolved:
optimizeQuality behaves the same as smooth (Issue #3283)
- Resolved: Serialize
grid-template-areas as simplified computed value for both specified and computed value (Issue #3261)
- Resolved: Define that margin collapsing between first or last child behaves same as between sibling children (Issue #3073)
- Resolved: Republish CR of Break L3.
- Resolved: FPWD of CSS Break L4
- The discussion on
:blank (Issue #1967) was reopened to confirm that the group no longer saw the compat risk that they originally sited when not making the change 3 years before. The members on the call generally believed someone needed to commit to implementing first or the decision should be reversed however there weren’t enough members on the call to decide on their path.
- New tags will be added to github to help indicate which agenda+ items should happen on an APAC time call and which should only happen during a normal timed call.
Full Meeting Minutes
Minutes Telecon 2018-10-17
- Resolved: Publish updated WD of Paged Media L3
- Resolved: Change cursor in vertical writing mode to a must (Issue #3196)
- Resolved: Accept this edit [A computed track list is a list alternating between line name sets and track sections, with the first and last items being line name sets.] (Issue #3154)
- Resolved: Content alignment and self alignment share a baseline (Issue #3200)
- There is a request for review of Issue #3071:
:valid-within / :invalid-within pseudo-classes
- During the discussion of Issue #3064 (Shouldn’t column-fill: auto take min-height into account?) there was interest in creating a general approach to handling heights so this topic will be added to the F2F agenda where it can be discussed with a whiteboard.
- The right people weren’t on the call to cover Issue #2386 (confirm browser support) so it will be added to the F2F agenda
- Resolved: Add drop and raise as keywords to initial-letters property (Issue #2955)
- Resolved: Order does not matter for the keyword in initial-letter property (Issue #2955)
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: