Minutes Telecon 2021-04-28
- Please start gathering thoughts and content for the 2021 snapshot on github in issue #6243.
- Resolved: No change to name; stay with size-adjust (Issue #6114: bikeshedding name of size-adjust descriptor)
- Resolved: Add from-font keyword to font-size-adjust [to Fonts 5] (Issue #5539: font-size-adjust: auto)
- fantasai will add details to issue #4818 (oblique angle for vertical text with text-combine-upright) about the difference in visual presentation this would introduce between regular italics and this property. Discussion will continue on GitHub
- The group will wait for more evidence of author demand before taking up issue #6104 (Consider ‘extends’ descriptor to reduce duplicate declarations)
- Resolved: Fonts with negative line gaps are clamp at 0 (Issue #5064: The web de-facto requires nonnegative line gap metrics in fonts)
- Resolved: Undo previous resolution. Treat replaced elements with an internal ruby display value as if they were inline at used value time (Issue #6000: Replaced annotation containers and base containers are nonsensical)
- Resolved: Close no change (Issue #6237: Add a :media pseudo-class, to match the set of elements matching the media pseudo-classes)
- Issue #6250 was filed to better define if Seek returns as playing or paused.
- Resolved: image-set should act like srcset attribute with applying resolution (Issue #6241: image-set() resolution should be applied on-top of, not instead-of the natural image resolution)
- Resolved: Switch to using 25AA (Issue #6200: counter-style square symbol (0x25FE) is bad)
- Issue #6175 (What is the migration path for Container Queries?) is reaching a conclusion to allow a user to test a container query property value pair. The final details will be worked out on GitHub.
Full Meeting Minutes
Minutes Telecon 2021-04-14
- @scope work will be done in the next level of CSS scoping; miriam will be added as an editor
- Resolved: Have display:math behave as mrow and ping accessibility groups to see if that’s an issue (Issue #5388: math/inline-math (whether display:math on a non-MathML context should be more inline or block))
- Resolved: We are interested in defining all the math display types necessary for MathML layout to not be element-dependent (Issue #5866: MathML individual display types)
- There were three possible paths forward in handling
display-legacy parsing (Issue #5575: Should display-legacy values be aliased at parse time?):
- Alias at parse time
- Define the new and old values as 2 independent values with same behavior so they always parse differently
- Do in between where some APIs return old and some return new if you specify new values
- Most of the debate was between options 1 and 3:
- Those arguing for option 1 believed it would be the easiest for authors to understand.
- The argument for option 3 is it allows newer APIs to return the new values but prevents changing the return of older APIs when a new value is used. This would prevent breakage when using scripts that do not accept the new values.
- More data about possible breakage will be added to the issue in order to further conversation.
Full Meeting Minutes
Minutes Telecon 2021-03-31
- Resolved: The return value of getComputedStyle to match Firefox behavior that first-line is ignored in getComputedStyle (Issue #1510: currentColor when fragments have different colors)
- Resolved: Clamp values between 0-100, all other values are invalid (Issue #6047: How should negative percentages behave in
color-mix()?)
- Resolved: Highlight color represents selected text color which is what you’d use for ::selection (Issue #6008: Consider clarifying Highlight system color, and maybe adding a new system color for control background)
- Resolved: Add keyword to represent selected item with name TBD (Issue #6008)
- There were some complex questions which need to be discussed in order to resolve issue #6069 (Interaction of flexbox minimum height and aspect-ratio minimum height) and the group ran out of time on the call to cover them all. Discussion will continue on github.
Full Meeting Minutes
Minutes Telecon 2021-03-24
- dbaron will be added as editor of Transforms 2
- Please indicate on the wiki if you’ll be able to attend any sessions for the virtual F2F
- Everyone is encouraged to help clear out the old PRs in the repo
- A decision on how to handle content-visibility:auto content for accessibility (Issue #5857) will wait until there is more feedback from the AT developers and accessibility teams.
- Resolved: Animation work is skipped in content-visibility subtrees when they’re not rendered. creating, taking, or ending animations. Animation is refreshed if recalculate (Issue #5611: content-visibility should pause CSS animations in subtree)
- Resolved: Custom highlights will always go below native highlights (Issue #4595: Position of the custom highlights relative to the built in ones)
- Resolved: Leave custom highlight properties in the api as currently written in spec (Issue #4591: Priority by number or some other method)
- No one is pushing for a fast solution for issue #4398 (Semantics of CSSPseudoElement : EventTarget) so people will continue to think on the best way to solve the issue.
- Resolved: Add sub-pseudo elements [to style punctuation before or after ::first-letter]. Bikeshed names (Issue #2040: Problems with styling ::first-letter with punctuation)
- Resolved: Add quirky hex color and quirky unitless lengths to Values & Units (Issue #6100: Upstream parser quirks to syntax)
- Resolved: Add a quirks mode flag to parsing algorithm and syntax which is passed to property specific parsers (Issue #6100)
Full Meeting Minutes
Minutes Telecon 2021-03-17
- Resolved: Republish WD of Cascade 5 and move open feature requests to L6
- A request for wide review of Cascade 5 will be sent in preparation for a CR request
- Resolved: Republish Sizing 3 WD
- In 2 weeks there will be a CR request for Sizing 3 WD. Everyone is encouraged to review the spec in advance of that in case there are uncaught issues with intrinsic sizing.
- Resolved: Reverse the resolution and drop advance-override (Issue #5983: advance-override details)
- Resolved: Add a size-adjust descriptor to @fontface, accepting a percent. Applies a scale factor. Impacts all associated metrics of the font, including the outline. Because it does not affect a computed fonts size it does not affect em [it does affect normal] (Issue #6075: Add glyph scaling override descriptor to @font-face)
- A new question will be opened for if we should deprecate font-size-adjust based on the above resolution
- There is a new proposal for addressing issue #5624 (Higher level custom properties that control multiple declarations) which would create a new type of custom property which creates a new cascade pass to resolve. Anyone with interest in this problem is asked to participate on the GitHub issue to reach a solution.
- Resolved: Remove color() function fallback (Issue #5931: Concerns about color() function fallback)
- It remains undecided if the content-visibility: auto subtree elements should be visible in the accessibility tree (Issue #5857). Exposing the content could mean a performance hit only for those using the accessibility tree and therefore be considered discriminatory. On the other hand, not exposing the content could lead to them not getting to some content which should have been reachable. Conversation will continue on GitHub.
Full Meeting Minutes
Minutes Telecon 2021-03-10
- Resolved: Publish updated WD of CSS Ruby
- Resolved: Add this defined hiding behavior to spec and ping engines to impl it (Issue #5927: visibility:collapse on ruby annotations)
- Resolved: Add accent-color to list of properties adjusted and have it adjusted to auto (Issue #5987: accent-color in Forced Colors Mode)
- There’s a need for real world examples and author feedback for issue #5911 (Scroll snap areas for fragmented boxes (like in css-multicol)). rachelandrew and fantasai will work together to create a blog post with examples to get author feedback.
- miriam presented the proposal for light-dom scoping (Issue #5809: Proposal for light-dom scoping/namespacing with re-designed `@scope` rule) which is explained in this slide deck.
- This approach creates a scope which is designed to prevent things from leaking out of the scope but allows the regular styles to go in.
- There were a lot of different opinions as to if the proposed handling for prioritization was robust enough to handle author need or if its simplicity paired well with newer models such as layers to cover more needs.
- The next step is for miriam to write up the proposal using more spec-like language and start creating separate issues for the concerns being raised so that this proposal can begin being refined.
Full Meeting Minutes
CSS Ruby Layout Level 1 Updated Working Draft
The CSS Working Group has published an updated Working Draft of CSS Ruby Layout Level 1. “Ruby”, a form of interlinear annotation, are short runs of text alongside the base text. They are typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This module describes the rendering model and formatting controls related to displaying ruby annotations in CSS.
Major changes include:
- Adding an
alternate keyword as the initial value of ruby-position.
- Renaming
ruby-merge: collapse to ruby-merge: merge.
- Defining
visibility: collapse to hide annotations explicitly.
- Redrafting key parts of the Ruby Layout section to more precisely define interlinear and inter-character layout and their interaction with
ruby-align.
- Adding additional figures and examples throughout.
The full list of changes since the April 2020 draft is available in the Changes section.
There are still a number of known issues open, most of which are about pinning down details in the layout rules. Issues are currently tracked in two places: a disposition of www-style comments and in CSSWG’s GitHub repo.
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-ruby]) 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 2021-03-03
- When adding a definition for advance-override (Issue #5983: advance-override details) there’s a need to consider where the adjustment should occur. There wasn’t clear consensus on where spacing should be added. It was suggested that this be considered at the same time as issue #6075 (Add glyph scaling override descriptor to @font-face)
- Resolved: Add back commas Issue #6066: Commas in color-mix()
- A separate issue will be opened to consider removing the “in” keyword from color-mix.
- Resolved: color-mix(metadata, color-option#{2}), where color-option = color && percentage? (Issue #6064: More clarity around the percentage in color-mix())
- Resolved: Negative percentages are invalid in color-mix() (Issue #6047: How should negative percentages behave in color-mix()?)
Full Meeting Minutes
Minutes Telecon 2021-02-24
- The disagreement about removing prefers-contrast: forced (Issue #5433: duplication of `forced-colors: active` and `prefers-contrast: forced`) was focused around users who have defined a color set which would not qualify as high or low for the forced-colors media query and therefore would not be detected if prefers-contrast: forced was removed.
- Firefox will gather data about the colors used so the group can monitor if the change would cause a negative impact in experience for these users.
- There was also disagreement as to if reduced visual complexity is necessary when there are forced colors. There was no data available about expectations and people had contrasting views on what is most likely.
- There was discussion on if the prefers-contrast MQ should be held back until the group decides how to handle the reduced complexity and forced color relationship. The group didn’t agree, though, so it will be opened as a separate issue.
- Resolved: Remove the forced value from prefers-contrast MQ (Issue #5433)
- Resolved: Bake the smoothing into non-integer changes in current pixelated value. Add a new value for nearest neighbor jaggedness (Issue #5837: image-rendering:pixelated should not force “nearest neighbor” (or similar) when the scale factor is far from an integer (e.g. 150%))
- Resolved: Republish CR-snapshot of Scroll Snap
- Resolved: Add an ‘alternate’ value which is the initial value (Issue #5971: Alternating sides for ruby-position)
Full Meeting Minutes
Minutes Telecon 2021-02-17
- The group didn’t agree on if the heuristic description for :focus-visible should be updated to detail interactions with the Shadow DOM (Issue #4893: :focus-visible and Shadow DOM). If it is updated, it wasn’t clear if the guidance should be to bubble :focus-visible to the host or not.
- Part of the conversation around issue #5885 (:focus-visible matches on initial programmatic focus) was about where the browser should be drawing a focus ring which is a discussion that should be held with the WHATWG. The discussion in the issue will be focused back to the pseudo class itself and if it’s specified correctly.
- Resolved: The stuff inside @page or @margin rule are descriptors but act like properties for behavior and cascade (Issue #5970: Should page descriptors support `!important`?)
- Issue #5970 still needs a resolution on how variables will be handled. The proposal on the call was for them to be accepted and to inherit from the root. There were concerns about inheriting from the root causing issues when interacting with media queries so discussion will continue on the github.
- The group was unsure if they should allow container queries to propagate (Issue #5913: :root/body viewport propagation and containment). There will be an effort to check current usage to verify that there’s no risk of breakage if it’s disallowed. Discussion will continue on github to see if there’s a way to allow propagation without running into a circularity problem.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: