Minutes Telecon 2020-04-01
- The definition of forced-color-adjust did not allow a granular enough level of control (Issue #4176: Cascade within forced-colors MQ). The need was to allow it to be set on a specific property or maybe even declaration. On call the suggestion was to leverage the ! syntax and create a value like !override-color-adjust to have the override set without having to create a new property that overrides existing properties. This idea was widely supported and is the direction the group wanted to move in. There were two seemingly good ways to specify the behavior of the ! syntax and discussion will continue on the github issue to work out which is better between the two. Options:
- color: blue ! override always beats color: red, even if red would normally win the cascade.
- color blue ! override and color: red cascade normally, and if red wins in the cascade, then there’s no longer an override and the blue just gets ignored.
- Resolved: Select Option B [Based on its resulting computed color value, the [computed|used] background-color of an element is forced by matching all channels other than alpha to the appropriate forced background color; which should be the corresponding system background color if color is a system color, and Canvas otherwise.] (Issue #4175: background-color in forced color modes needs more than a simple unset)
- Resolved: Publish updated WD of css-color-adjust-1
- There were three potential solutions for issue #4891 (Should collapsible space after inside ::marker be preserved?):
- Keep white-space: pre. Firefox is correct, changing Chromium will be trivial.
- Keep white-space: pre but add some magic that if a text ::marker has a trailing space and is followed by collapsible spaces, then these collapsible spaces are removed, even if the ::marker space is not collapsible. This will keep Chromium’s behavior but implementing this magic would be annoying.
- Say that inside markers don’t get assigned white-space: pre in UA origin. This is close to what Chromium does right now. But I guess doing this properly would need pseudo-classes like ::marker:inside and ::marker:outside, even if just for internal use, but that would create a circularity if in the future we allow setting list-style-position in the ::marker itself.
- On the call the group was inclined toward option 3 but needed to define how to do it before resolving as there were concerns about doing it with a pseudo-class. After the call discussion continued and those conversations lead to support of option 2 by using
::marker { text-space-trim: discard-after; } to achieve the behavior without magic.
Full Meeting Minutes
Minutes Telecon 2020-03-25
- Resolved: All boxes can participate in baseline alignment. If they don’t have a baseline one is synthesized (Issue #4675: Do grid items that have “no baseline set” participate in baseline alignment?)
- Resolved: Keep the two interfaces the same as each other (WICG Constructable Stylesheets Issue #45: Decide whether to change from FrozenArray to ObservableArray for adoptedStyleSheets)
- Though the group agreed that the interfaces should be the same, it has not yet been agreed what the same thing should be. There were three options listed during the call:
- Both .sS and .aSS use StyleSheetList; ShadowRoot gains methods to mutate .aSS
- Both .sS and .aSS use a readonly ObservableArray; ShadowRoot gains methods to mutate .aSS
- .sS is upgraded to a readonly ObservablyArray; .aSS is an ObservableArray
- Discussion focused around options 2 and 3; there wasn’t much discussion around option 1.
- Some group members will reach out to TC39 about adding .item to arrays which closes the gap between options 2 and 3. Additionally there was interest in possibly creating a usage counter for .item to see if there’s any option to remove it.
- The final decision needs to be based around the decision of how to handle the race conditions inherit in “assignment”.
Full Meeting Minutes
Minutes Telecon 2020-03-18
- When fantasai was editing in the resolution for issue #4175 she discovered a complication in how to handle elements which are not supposed to be forced to CanvasText such as buttons and inputs. She proposed if the UA stylesheet has a background-color rule we revert the author level. AmeliaBR had a second possible solution which could address the potential to have a color mismatch when there’s an element inside a button. In her proposal after reverting the rules then you would go through and then do a pass to figure out the background. To help the group decide some examples will be created and AmeliaBR will write up spec text for her proposal.
- Resolved: Option 3- Rewrite all author rules for affected properties to specify ‘revert’ instead (Issue #4020: User origin !important vs. forced colors mode)
- Resolved: Allow sink of 0 for initial letters (Issue #3698: initial-letter should allow zero sink?)
- Resolved: Close as won’t fix for lack of ideas on how to properly fix it. If someone comes up with a workable idea we can re-open (Issue #2108: ‘border’ shorthand resets ‘border-image’ but can’t set it)
- The request to get the physical size for an image in issue #4005 (physical, rather than logical, dimensions – for images) made sense to the group, however more fleshed out use case from the original reporter would help the group figure out how best to change the spec.
- The proposal for issue #4541 (Let offsetWidth / offsetHeight report actual size?) was no change and to keep the Chrome/Safari behavior, however before the group can decide more test cases were necessary, including against vendors that do printing such as Prince.
Full Meeting Minutes
Minutes Telecon 2020-03-11
- The April meeting will be held as a virtual F2F instead of in Cork. Exact details are still being discussed on the private mailing list and members are encouraged to add their thoughts in that thread.
- Resolved: @import doesn’t parse in constructable stylesheets and as a result throw syntax errors (WICG Constructable Stylesheets Issue #119: Add a note about the reasoning to forbid `insertRule(@import)`, or remove the condition?)
- There was concern that not supporting @import will lock in that lack of support. Discussion will happen on getting CSS Modules to resolve the @import module graph question that had blocked @import support.
- chrishtr introduced the re-written proposal (Issue #4843) for subtree-visibility which is created to allow authors to control element subtree visibility and provide rendering performance hints to the UA. He requested full review of the proposal so the spec can move toward implementation.
- Resolved: No change [to transform serialization] (Issue #3305: Is it necessary to serialize all 3 components of translate given the 3rd component is 0px)
- Resolved: We define this [rule serialization] in CSSOM to match browser compat as much as it exists. (Issue #4828: Serialization of rules)
- Resolved: Allow transitions on ::marker and allow animations with animations happening and animation rules applying the style (Issue #4814: Animations on ::marker?)
- The group will wait and see the results of Chrome’s experiment on changing to Firefox’s behavior for auto-disabling native appearance prior to changing spec text (Issue #4777: Auto-disable native appearance when cascaded value has author origin).
Full Meeting Minutes
Minutes Telecon 2020-03-04
- Resolved: Add three issues to the ED [Draft needs a security and privacy section. Add an issue for if there should be more than binary values. Add to the draft that this is still under discussion and maybe not ready to ship] (Issue #2370: Adding prefers-reduced-data as part of MQ5 FPWD)
- Resolved: Name this page-orientation with values rotate-left and rotate-right (Issue #4491: Add orientation descriptor)
- Resolved: min() and max() get simplified by simple unit values of the same unit we reduce to one instance of each. We also reorder the arguments in the same way that sums reorder. Review math functions for consistency (Issue #4550: Specify simplification of min() and max() more explicitly)
- Originally the group was looking to amend the algorithm for selecting first available font to check for the 0 glyph, if not there check for .notdef glyph, else use 0.5em (Issue #4796: Reconsider the definition of “first available font”). Upon discussion it became clear that using 0.5em was problematic for looking for a font file so discussion will continue in the issue.
- Group members should update their Cork F2F travel plans/availability on the wiki so that a determination can be made on if the F2F will proceed as planned or if there’s a need to develop a backup plan.
Full Meeting Minutes
Minutes Telecon 2020-02-19
- The group wasn’t certain if the best way to solve for increasing the pointer target size (Issue #4708: Increase pointer target size independently of element layout) was to allow set sizes as suggested in the issue or to expose a fixed set of values and let the user agent do the math. astearns will reach out to the original poster to get feedback on the two options.
- Resolved: Close no change to normative text but add a note about needing implementation experience (WICG Constructable Stylesheets Issue #120: Consider disallowing duplicate stylesheets)
- Resolved: Disallow @import in all constructable stylesheet APIs with a note that we’re doing it to match current state of modules and this might relax in future (WICG Constructable Stylesheets Issue #119: Add a note about the reasoning to forbid `insertRule(@import)`, or remove the condition?)
- Resolved: Change the new property to be ‘all’ not ‘always’ (Issue #4277: Consider adding an `all` value to `text-decoration-skip-ink`)
- Resolved: Line-height returns ‘normal’ in gCS for normal and all other give absolute length (Issue #3749: A question for the procedure to compute the resolved value of “line-height”)
- More research needs to be done to see exactly what value is being overwritten on the iframe to solve issue #4772 (`color-scheme` should affect embedded iframes)
Full Meeting Minutes
Minutes Telecon 2020-02-12
- Resolved: Remove @viewport, retire the spec, move the meta tag to a new spec (CSS Viewport) (Issue #4766: Remove @viewport)
- Resolved: Move layout/visual viewport spec into CSS Viewport spec
- smfr will be added as an editor to the new CSS Viewport spec
- Resolved: Accept proposal as phrased in comment from florian [When calculating the size of the containing box, including when computing its intrinsic size, it must be treated as having no contents.] (Issue #4741: It should be clearer that size containment inhibits effects of contents on intrinsic sizes)
- fantasai will draft up proposed text for issue #4720 (Clarify ::selection background-color in presence of fill/stroke) creating a keyword so that the UA can set that keyword and it’s only used if both color and background-color compute to the keyword.
- Resolved: Syntax order is physical for intrinsic-size (Issue #4531: intrinsic-size lost the thread)
- Resolved: Switch initial keyword [of intrinsic-size] from ‘none’ to ‘auto’
- Resolved: Add clarifying text that all system values are reflecting the browser settings (Issue #4533: Clarify to what extent new system color are about system settings versus browser settings)
- Resolved: Accept proposed definition [do not apply forced colors to SVG text, and only apply forced-color-adjust: auto; to foreignObject SVG elements.] (Issue #3855: Define what happens to SVG in forced colors mode)
Full Meeting Minutes
Minutes Telecon 2020-01-15
- Any items for the F2F agenda need to be added soon so that people can review and come prepared. The Summer F2F timing will be added to the agenda.
- Resolved: Remove hyphen from rec2020/rec-2020 in all contexts; everything else (P3/display-P3) stays as is (Issue #4535: color-gamut Keywords)
- Resolved: Whatever highlight being applied uses colors from before even if came from pseudo element like ::first-letter/::first-line (Issue #4625: Original color of highlight pseudo inside ::first-letter/::first-line)
- Adding an inactive-selection media query wouldn’t solve the original use case for ::inactive-selection/::active-selection (Issue #4579), though there may still be use cases for the media query. fantasai will revisit having a selector on the element as well as the other proposals within github to see what works better for the use cases.
- The group was leaning toward adding a contain-intrinsic-size property to address issue #4531 (intrinsic-size lost the thread), but wasn’t quite ready to resolve. TabAtkins will write up proposed spec text and dbaron will add some past examples to the issue. This will be added to the F2F agenda for resolution.
- Resolved: Specify Firefox’s behavior [Give max-content contribution of replaced only-aspect-ratio elements ICB width and then ratio height] (Issue #4218: max-content contribution of replaced only-ar elements might be improvable)
- The group agreed that on issue #4444 (Table row resolved width and height) there needed to have round trip for block axis. Once there is spec text the group will review and resolve.
- Resolved: Add an ‘always’ value to ‘text-decoration-skip-ink’ (Issue #4277: Consider adding an `all` value to `text-decoration-skip-ink`)
- For issue #3728 (Should mention the possibility to ignore custom cursors that go outside of the viewport) Firefox has been invalidating images that are too large for a custom cursor. Chrome will add its approach to the issue so the group can decide if the spec should change.
Full Meeting Minutes
Minutes Telecon 2020-01-08
- Members should tag any github issues that are for F2F discussion. A private wiki page will be made by fantasai to coordinate travel.
- Any group member with items that should be added to the list of topics to cover with Open Type should reach out to Chris.
- Resolved: Add lab keyword to color() function (Issue #4649: Should the color() function accept ‘lab’ as a color gamut keyword)
- The quick answer to Issue #4647 (Do gradients/animations using lab/lch colors interpolate in the Lab colorspace?) is yes. Going deeper into the issue the group decided that for transitions and gradients there should be a smart default that, if the colors use the same space, they’re interpolated in that space. If they’re not in the space they’ll interpolate in Lab space. Gradients will have the ability to select a different space for interpolation.
- Chris will add additional spec details to clarify how displays should render colors in wider color spaces in order to resolve Issue #4646 (Should lab() colors which are outside the sRGB gamut be rendered on capable displays?)
- After looking into issue #4622 more (gray() function produces a warm, D50 white) it’s not really a concern so Chris will close it no change
- Resolved: Drop gray() function (Issue #4621: Better name for gray()?)
- Resolved: Update WD of css-color-4
- Resolved: Close no change (Issue #4626: Layering of highlight pseudo backgrounds)
- fantasai introduced Issue #4579 (::selection vs ::inactive-selection) however there wasn’t time to resolve during the call.
Full Meeting Minutes
CSS UI 4 Updated
The CSS WG has published an updated Working Draft of the CSS Basic User Interface Module Level 4.
This specification describes user interface related properties and values to style HTML and XML (including XHTML). It includes and extends user interface related features from the properties and values of previous CSS levels. It uses various properties and values to style basic user interface elements in a document.
Alongside with a number of smaller bug fixes and tweaks, the main change in this new revision is that the definition of the appearance property has been significantly reworked to make the design compatible with existing web content. Further tweaks are expected, but this is a significant step forward since the last publication.
Significant changes 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-ui-4]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: