Minutes Telecon 2019-12-18
- Dates for the summer 2020 F2F will be finalized on the private list.
- Resolved: Publish a new WD of CSS UI L4
- The group discussed limiting the exposed fonts in order to limit fingerprinting vectors (Issue #4497: Limit local fonts to those selected by users in browser settings (or other browser chrome)) and was interested in creating possible spec text.
- Even though there are plenty of other vectors to fingerprint users, a majority of the group felt that it was worth the effort to chip away at the problem.
- There were different options as to what fonts to use; an intersection of OS fonts, a union of them, or somewhere in the middle where we accept that you’ll still be able to know basic information like OS from the font list.
- Though the spec shouldn’t list exact fonts, there was a desire to have an accompanying note-like document that does say fonts which are known to conform to the spec text.
- In the current GitHub there is a proposed way to still allow users to install and allow a font and that use case is important to support as this is a common need for users that consume content in a minority language.
- Though there’s a desire to ensure this text strongly protects users of browsers it may still need to be a SHOULD level requirement as there are other use cases where fingerprinting isn’t a concern such as PDF renderers
- Resolved: Reverse previous blockification requirement and require generating a block container (Issue #4448: How should spaces be treated in markers?)
- Resolved: Use white-space:pre as the value in UA stylesheet with text about possibly processing new lines (Issue #4448)
Full Meeting Minutes
Minutes Telecon 2019-12-11
- TabAtkins will review issue #4497 (Limit local fonts to those selected by users in browser settings (or other browser chrome)) with the security team before giving feedback
- There is a commit for issue #4482 (Switch advanced attr() to being var()-like) which needs review. Assuming no major changes are requested a resolution will be requested next week.
- The on call agreement for issue #4535 (color-gamut Keywords) is align the color function keywords with preexisting color gamut keywords however there weren’t the right people on the call to resolve on that proposal conclusively.
- In issue #4531 (intrinsic-size lost the thread) the proposal is to return to just having a property to set a size for an async-layout element when we’re not actually calculating the content’s size and omit the extra use cases discovered during the F2F since this use cases added significant complexity, made the original use case harder, and were achievable using other methods. After discussion there were two possible paths forward 1) rename the property and only solve the limited use case. 2) leave the property broad knowing that there will be additional use cases to solve in the future within a similar problem space. Additional use cases will be gathered in issue #4585 (Use cases for explicit intrinsic-size) until the January meeting at which point the group will decide between the two possible approaches.
- Issue #4491 (Add orientation descriptor) needs visual examples before the group can decide on the use case. It was generally agreed that four directions will be necessary rather then just portrait/landscape.
Full Meeting Minutes
Minutes Telecon 2019-12-04
- Resolved: Publish FPWD of resize-observer
- Resolved: Add Adam Argyle as an editor for Colors L5
- Resolved: Add the video prefix MQ and define how used in bi-plane and non-bi-plane environments (Issue #4471: Dealing with bi-plane (video/graphics) when reporting values)
- The parts of this issue related to CSSOM will be broken into a separate github issue.
- After the previous resolution is added, a request will be made to take Media Queries L5 to FPWD.
- Resolved: Serif, sanserif, and monospace must match, all other generics should match if appropriate. (Issue #4442: Don’t require browsers to always match every generic font family to a concrete font family)
- Resolved: Take Mats’ 3 part proposal leaving actual value of UA stylesheet in the air as a separate issue to be determined later (Issue #4448: How should spaces be treated in markers?)
- Add white-space as a property that applies to ::marker
- Add ::marker { white-space:pre } to the UA sheet
- Mention that an outside ::marker box has its display value blockified. (This makes it clear that if an author overrides white-space with say white-space:normal then any trailing space in an outside marker’s text is expected to be truncated as it normally would at the line end in a block.)
Full Meeting Minutes
CSS Containment Module Level 1 is a W3C Recommendation
The CSS WG has published the CSS Containment Module Level 1 as a W3C Recommendation
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 now a W3C Recommendation. As such, it has received the endorsement of W3C Members and the Director. W3C recommends the wide deployment of its Recommendations as standards for the Web. The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to W3C Recommendations.
Significant changes from earlier drafts are listed in the Changes section. A Disposition of comments since the Proposed Recommendation and Implementation Report are available.
If you find any error, please report them by either filing an issue in GitHub and including [css-contain-1] in the title of the issue (preferable), or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-contain-1]) and your comment topic in the subject line.
Further development will happen in the next level of this specification. To make comments about that draft, including suggestions for new features or other refinements, please either file an issue in GitHub and include [css-contain-2] in the title of the issue (preferable), or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-contain-2]) and your comment topic in the subject line.
Minutes Telecon 2019-11-20
- The next F2F is in about 2 months so anyone planning on going should make travel plans.
- There is an email on the private list to coordinate which calls need to be canceled around the end of year holidays. Another one will be sent to see if we need to cancel next week due to US Thanksgiving travel.
- Resolved: Remove implementation warning and add a note about possible changes to list of values for webcompat. Wording at editors discretion (Issue #1250: Remove warning about ‘appearance’)
- Resolved: All math functions aggressively simplify their calculations as far as possible for a given value-computation stage. (Issue #4399: What should non-calc() math functions serialize to when they’re fully resolved?)
- Resolved: If numeric simplification of a math function results in a single value, the serialization is that value wrapped in `calc()` (Issue #4399)
- Work will continue on defining how unit canonicalization works
- Resolved: Accept edits for Issue #4065 (Blockification section should use the computed value, not the box of the element)
- A separate issue will be opened to look and see if the same issue exists in the Houdini Layout API
- Resolved: Working group is fine with translate, rotate, and scale shipping (Issue #4515: The readiness of shipping individual transform properties – translate, rotate, scale)
- Resolved: Move the 3D Transforms to a level 3 of Transforms
- After the call there was IRC chat that concluded separating the individual properties from 3D Transforms would remove value from the individual properties and will likely need to be revisited.
Full Meeting Minutes
Minutes Telecon 2019-11-13
- Resolved: Publish new WD for Text 4
- Resolved: Republish Fonts 4
- Resolved: Pick option 2; effectively subset the grid area into the subgrid (Issue #4411: Subsetting grid-template-areas in subgrids)
- Resolved: Start L3 [of Grid] with all work that is in L2 but not about subgrid
- Resolved: Publish Grid L2 as CR
- The group was interested in seeing specific details for changing
attr() to be more var()-like (Issue #4482: Switch advanced attr() to being var()-like) so TabAtkins will write up spec text for review.
- Resolved: Give the 2nd option a chance and see if there are compat reasons to instead keep current behavior (Issue #4475: Resolved values of grid-template-rows/columns don’t round-trip)
- TabAtkins will look into what the Gecko and Chromium devtools expose about grid to see if something similar can be specified as a future enhancement.
- Resolved: Specify serialization as proposed in https://github.com/w3c/csswg-drafts/issues/4335#issuecomment-548962309 [When serializing either the specified or computed value of a
string value of ‘grid-template-areas’, each null cell token is serialized as a single “.” (U+002E FULL STOP), and consecutive cell tokens are separated by a single space (U+0020 SPACE), with all other white space elided.]
Full Meeting Minutes
CSS Text 3 Updated
The CSS Working Group has published an updated Working Draft of CSS Text Level 3. 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.
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 2019-11-06
- Resolved: Accept the change that astearns put into the ED, handling the case where margin = 0 for very small values of shape-margin (Issue #675: Calculation of corner radii by margin-box and border-radius)
- Resolved: The line ending trailing space is applied after bidi (Issue #4422: Bidi and pre-wrap end of line spaces)
- Resolved: Publish a new WD of text-3
- It was agreed that the spatial-navigation-action property will continue to behave as defined and does not inherit (Issue #4449: Proper definition of ‘spatial-navigation-action’ property). If there are use cases for the inheritance the group will re-look at this issue.
- Resolved: Publish WD of CSS-Nav-1
- Resolved: To remove the constructor and remove the language about how to populate the object into a different point in the spec (Issue #3946: ResizeObserverEntry either needs to have its JS constructor removed, or define how its members are initialized when constructed)
- Resolved: Add ui-sans-serif (Issue #4468: Add a ui-sans-serif keyword to go with ui-serif)
- Resolved: Add pointer-events to css-ui level 4 (Issue #4438: Spec the pointer-events property for non-SVG elements)
Full Meeting Minutes
Minutes Telecon 2019-10-30
- Resolved: We come up with a set of mandated color mappings for deprecated system colors, put in spec, and write tests for them (Issue #3873: Prevent fingerprinting with deprecated system colors)
- Resolved: Make system color keywords behave like currentColor and inherit as keywords (Issue #3847: Make system color keywords compute to themselves)
- Resolved: Rename text keyword to CanvasText (Issue #4465: Text system color conflicts with background-clip)
- Resolved: Publish a new WD for Colors 4
- Resolved: Specify that the PaintWorklet’s canvas-ish methods can take color keywords and do the right thing (Houdini Issue #921: Current Color as an input to paint worklets)
- Resolved: Fix Typed OM spec to ensure that currentcolor and system color keywords reify as CSSStyleValue, not CSSKeywordValue, until we have CSSColorValue for them to reify as (Houdini Issue #921)
- smfr introduced issue #236 (Provide a way to specify rastered content scale for transformed content) and there was interest in giving authors a way to pass more information and influence rasterization, but there wasn’t enough time on the call to create a solution.
Full Meeting Minutes
Minutes Telecon 2019-10-23
- The use case presented in issue #4329 (Add vhc value) to address the shifting viewports in mobile when the nav bar hides is one that the working group wants to address. However, there was concern that enough time hadn’t been spent on understanding all the possible cases that need to be addressed and the pros and cons of each potential solution. jensimmons will take the lead on making sure the necessary research is done to reach a resolution.
- There was support expressed for changing the semantics of having transform-style: preserve-3d on the root element such that it means that anything that’s preserved as 3-D up to the root element would be rendered in actual 3-D to address issue #4242 (Proposal new transform-style: detached) but there were people missing from the call so a resolution will be reached later.
- Resolved: For the individual transform properties if they spec a value that can be expressed as 2d we treat as 2d and serialize accordingly (Issue #3305: Is it necessary to serialize all 3 components of translate given the 3rd component is 0px)
- Resolved: Require transform functions to be downgraded to 2d if possible (Issue #3305)
- Resolved: We return the values the animation is working on while the animation is going and that includes the endpoints per the definition in web animations (Issue #3920: Serialization of individual transform when the animation is at 0% or 100%)
- Resolved: Reject this proposal (Issue #589: Let ‘transform-origin’ and ‘transform’ take comma-separated lists)
- Florian created examples and a PR to resolve issue #4422 (Bidi and pre-wrap end of line spaces). fantasai will make some changes to the PR and a call for resolution will happen next week.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: