Minutes Telecon 2022-03-30
- Resolved: No change, work on more general solution to more openness across shadow boundaries (Issue #5984: CQ vs shadow boundaries)
- emilio will write up how he believes issue #3297 (The lh and rlh units are more complicated than what they seem) should be implemented. The group will see if implementers can agree to that proposal after it’s drafted.
- Resolved: Use CSSNumberish for “time” values in Web Animations API (Issue #7102: CSSNumberish Time values to represent types)
- Resolved: Use percentages for scroll-timeline values (Issue #7045: Percentages vs Pixels for Scroll Timeline Values)
- Resolved: Make cascade-dependent keywords revert/revert-layer disallowed in style() queries (Issue #7080: CSS-wide keywords in style())
- Resolved: Other css-wide keywords (initial, inherit, reset) are allowed (Issue #7080)
- There wasn’t time to resolve on issue #7142 (container ;/ style), but the group agreed to look at what WPT is testing now and add clarifications to the issue in order to hopefully resolve next week.
Full Meeting Minutes
CSS Text Level 4 Undiffed and Updated
The CSS Working Group has published an updated Working Draft of CSS Text Module Level 4. This CSS module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.
This update:
- Merges in the entire contents of CSS Text Level 3 so that it is no longer a diff spec.
- Adds percentage values to
letter-spacing and word-spacing, to allow for values relative to the font-size of the text to which they apply. (em values are resolved against the element on which they are declared, and inherit as absolute lengths.)
See Additions since Level 3 for a list of the new features since Level 4. Some of these features are more stable than others, and future work on this module will be refining their designs and definitions. You can see the current list of open issues in the CSSWG GitHub repo.
We encourage anyone with an interest in text and internationalization to review this 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-text-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 2022-03-16
- After last week’s conversation on issue #6773 (Make system colors fully resolve (but flag they were system colors) thus reversing the resolution of #3847), several people reread the original issue and conversation and contributed additional thoughts on github. There is still disagreement between what authors expect and what might be the best behavior for users so discussion will return to github.
- Resolved: Use HTML restrictions for custom idents (Issue #7129: Custom property names too permissive, require namespacing rules)
- Resolved: Illegal characters in an ident can be escaped (Issue #7129)
- Resolved: Invalid ident characters are treated as DELIM tokens (Issue #7129)
- Resolved: Republish css-text level 4 (Issue #6900: Republishing CSS Text 4)
- TabAtkins and fantasai will review the issue reported on issue #6777 (Column wrap intrinsic size algorithm can make inline min-content > max-content) and add comments or proposed changes to the issue.
- There were interesting use cases for issue #6641 (Custom properties on :root) as well as good arguments against special casing. Discussion will continue on the issue to formulate a concrete proposal.
Full Meeting Minutes
Minutes Telecon 2022-02-23
- Resolved: Start Scroll Snap 2 ED, with :snapped and snapping event model, with Adam Argyle as additional editor (Issue #6985: Proposing `:snapped`: exposing private snapped item browser state for developers and designers)
- Resolved: Accept current Tables 3 spec text regarding calculation of shared borders in collapsed-border mode between table and cells (Issue #6230: Collapsed table first row width quirk)
- The group will check for other compat concerns and look further into if Firefox would consider instead making NULL U+0000 visible and then resolve based on that discovery (Pull Request #6983: The web de-facto requires NULL U+0000 to not be visible)
- Resolved: Close no change (Issue #6376: Bikeshed the container property & at-rule names to avoid confusion with other usage of contain/container)
- Resolved: Restrict container-name to just idents (Issue #6405: container-name string vs ident)
Full Meeting Minutes
Minutes Telecon 2022-02-16
- Resolved: Will add this to the color-4 module, after forking to a new issue (Issue #6741: Support all existing (non-legacy?) formats in color()?)
- There is interest in exploring issue #7035 (color-interpolation inherited property to set default interpolation space) further to see if it can be solved with focused properties. Discussion will continue on github.
- There was still some concern about the effect of issue #6773 (Consider reversing the resolution of #3847) so the group will take a week to review and then revisit the issue next week.
- Resolved: Accept this as L2 Editor’s Draft. (Pull Request #6533: Some ideas for linear() easing)
- Resolved: Add Jake Archibald as editor/co-editor of that Editor’s Draft.
- Resolved: Will not add an inertness property for now. (Issue #7021: Should inertness be exposed as CSS property?)
- Examples will be added to issue #6981 (Outline rects of an inline) in order to understand the current state and determine a possible solution.
- Resolved: Keep style queries in level 3. (Issue #7020: Defer style queries to level 4?)
Full Meeting Minutes
Minutes Telecon 2022-02-09
- Resolved: When we select a container, we determine which container by looking at the actual queries and finding an appropriate container for the questions being asked (Issue #6644: Determine container type automatically from the query)
- Resolved: Remove the container-type syntax from the preamble of the @container rule (Issue #6393: Provide a syntax to query a specific container-type)
- Resolved: All queries in an @container rule are against the same container, which can answer them all (Issue #6876: Multiple container-query s with multiple containers)
- The group will continue discussing style containers in the draft for now and revisit the question of deferral (Issue #7020: Defer style queries to level 4?)
- Resolved: Accept what’s in the draft (Issue #2040: Problems with styling ::first-letter with punctuation)
- Resolved: Negative spread values on text-shadow are invalid (Issue #6971: Disallow negative spread values on text-shadow)
- Resolved: Add inset to text-shadow (Issue #6074: Add ‘inset’ keyword to text-shadow)
- Resolved: Text shadows start at outer (for outset) or inner (for inset) edge of stroke (Issue #6074)
Full Meeting Minutes
Minutes Telecon 2022-01-26
- There was some concern that the overall approach defined in pull request #6537 (Define how to compute the kind of widget to use for an element) defines things that should be defined in HTML. This is a larger conversation that will go back to the issue and may also want to engage with OpenUI.
- Resolved: Add `first-valid` and please add an issue to bikeshed the name once we better understand the scope (Issue #5055: Allow an inline way to do “first value that’s supported”)
- Resolved: Drop the function syntax for querying sizes, but keep the function syntax for querying styles (Issue #6870: Spec syntax for size queries)
- Issue #6794 (Change content-size suggestion to min-intrinsic instead of min-content?) needs some deep investigation of the spec to determine the right behavior. TabAtkins and fantasai will look into it further and add this back into the agenda when they have a proposal.
- Resolved: Reject the proposed change but clarify the specification; we invite Serifo to comment further if they have objections to this resolution (Issue #6822: Percentage height resolution of children of flex items with indefinite flex basis)
- TabAtkins introduced the proposal for a toggle switch and requested feedback and questions on the github proposal.
Full Meeting Minutes
Minutes Telecon 2022-01-19
- Resolved: Publish a Proposed Correction for Media Queries 3, along with any necessary antecedents as determined by florian/chris/fantasai (Issue #6962: REC update)
- Resolved: Put an issue in the draft saying we’d like to remove (Issue #6788: ‘input-security’ considered harmful)
- Resolved: Set visibility:hidden [typo: this should be visibility:visible] on modal dialogs (Issue #6939: How does top-layer interact with ancestors)
- New issues will be opened to resolve the modal pseudo-class and reparenting issues raised as a part of issue #6939
- Resolved: Close no-change (Issue #3936: How should selector supports test react to partially-implemented selectors?)
- Resolved: hyphenate-character is shippable; we’ll add it to the Snapshot 2022 list of exceptions (Issue #6887: Is hyphenate-character stable enough to ship?)
- Resolved: Make conditionText readonly (Issue #6819: Setting .conditionText interop is terrible)
- Resolved: Add an `at-rule` function with syntax `at-rule(@keyword)` or `at-rule(@keyword; descriptor: value)` (Issue #2463: Feature detection for descriptors)
- There were concerns about the parser complexity and inefficiency that would come from the proposal in issue #4431 (Make box-shadow a Shorthand Property). However, there was also strong support expressed for the properties. Discussion will continue in the issue.
Full Meeting Minutes Part I and Part II
Minutes Telecon 2022-01-12
- Next week’s meeting will be an extended session from 8-10amPT
- Resolved: Republish CSS Color 3 REC as editorial update (Issue #6910: CSS Color 3: Proposed Changes)
- There wasn’t a clear preference for issue #6870 (Spec syntax for size queries) on the call. People are encouraged to engage on the issue to reach a decision.
- Resolved: Boxes default to style containment, syntax of ‘container’ and @container preamble is name / type (Issue #6393: Provide a syntax to query a specific container-type)
- Resolved: Work on solving these use cases for an isVisible API and revisit in a future call (Issue #6850: add Element.isVisible[toDocument] to detect if element is visible in the document)
- Resolved: Add color-extract() to Color 5 and continue work (Issue #6937: color-extract() function to extract individual color components)
- Resolved: Close no change (Issue #6938: Make all color components in Relative Color Syntax optional)
Full Meeting Minutes
Minutes Telecon 2022-01-05
- Resolved: We will spec that grid, flex, and table fragmentation align globally before fragments are created (Issue #6812: Flexbox alignment and fragmentation)
- Resolved: We will not truncate margins at any break when aligning globally for fragmentation (Issue #6812)
- alisonmaher will reach out to print formatters to get feedback on the above resolutions. If they have a different opinion the group will revisit.
- Resolved: The mix interpolation function will only be used for top-level values with various discussed caveats. mix() is the name of the top level interpolation (Issue #6700: Validity of generic interpolation function mix())
- The general agreement from the github conversation for issue #6513 (getComputedStyle and fragmentation) was to select a simple value to return, create exceptions where compat demanded, and direct authors toward existing fragment-aware APIs if they need an accurate answer. On the call, there were concerns about breaking compat since these properties have existed for a while, even though there isn’t interoperability. Suggestions were to do a deeper dive into properties and specify a compat-friendly requirement or to specifically state browsers handle this differently and there is no interop. Discussion will continue on github to reach a decision.
- Resolved: When an inline box is split by a block box, offsetWidth and offsetHeight will include dimensions of block box (Issue #6588: Needs more details for offsetWidth and offsetHeight)
- Resolved: Property and fontface rules always work in an @container rule (Issue #6827: What happens to other @rules inside @container?)
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: