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
Minutes Telecon 2018-10-10
Full Meeting Minutes
CSS Easing Functions Level 1: Last Call for Comments
The CSS Working Group has published an updated Working Draft of CSS Easing Functions Level 1. This module extracts the easing functions from earlier drafts of CSS Transitions into their own module, to more easily reference them from both CSS Transitions and CSS Animations and any other modules that need them.
Changes since the last draft consist of removing the frames() notation in favor of the new jump-* keywords in steps(). Also the module has been renamed (from Timing to Easing), to reflect the possibility of reuse for progress of things over a basis other than time.
As there are no open issues other than some editorial work, and hardly any have been received since the FPWD in February, we expect to transition this module to Candidate Recommendation next month. Consider this the last call for comments. 🙂
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-timing]) 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-09-26
- Since
word-wrap:break-word cannot affect min-content due to web compat there is now a need to achieve that behavior through another method. Discussion is ongoing in github #2682 to determine the best approach and anyone interested is encouraged to participate.
- Resolved: Add
:blank for input selectors (Issue #1283)
- Resolved:
:empty does cover white space (Issue #1967)
- Resolved: Specificity of :host() is 1 pseudoclass + specificity of argument. (Not just specificity of argument.) (Issue #1915)
- Resolved: Accept the proposal from fantasai and Kobayashi-sensei [keep the full size of the larger glyph and trim smaller] (Issue #1668)
- Location is still unknown for the February F2F but there is work in progress to produce alternate locations.
Full Meeting Minutes
Updated Working Drafts of CSS Text Level 3 and CSS Text Level 4
The CSS Working Group has published updated Working Drafts of CSS Text Level 3 and CSS Text Level 4. This module 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.
CSS Text Level 3 is a fairly late-stage Working Draft. This update fixes a number of issues not addressed in and/or raised after the 22 August 2017 publication last year. The Disposition of Comments tracking issues raised and fixed since the 2013 Last Call Working Draft has been updated.
CSS Text Level 4 is still an early-stage exploratory Working Draft, currently maintained as a diff spec against Level 3. This update fixes some issues in the previous WD and adds the line-padding, text-group-align, and text-spacing: space-first features. The Changes section summarizes all changes since the First Public Working 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]) 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-09-19
- Resolved: Request publication of FPWD of scrollbars
- Resolved: Higher level properties a positive angle will be a forward leaning slant, lower level properties will be what is written by the author (Issue #3091)
- Resolved: Publish Fonts L4
- Resolved: Use ‘should’ in the patch (Issue #1746: box-decoration-break and multi-box inline elements)
- Resolved: Add florian as an editor to Text 3
- Resolved: Revert the previous resolution [break-word will no longer affect intrinsic sizing] (Issue #2951)
- Resolved: Make the normative change [to apply a min width to rendered tabs] (Issue #2883)
- Resolved: Publish a new working draft of Text 3
- Resolved: Publish a new WD for Text 4
- Resolved: text-overflow affects non-breakable portions of the block-overflow string (Issue #2882)
Full Meeting Minutes
Minutes Telecon 2018-09-12
- There were concerns that some portions of the HTML fieldset/legend spec were extending functionality instead of just defining what is needed for compat. This is an ideal topic to address during TPAC where conversation can happen with members of the WHATWG. Until then conversation will continue on github.(Issue #3094)
- A separate issue will be created for CSS2.1 to create a term that means “things that create a stacking context” and use that in the spec where appropriate. Once this is done other specs can use this term too. (Issue #2717)
- Resolved: Containment should apply to outer SVG but nothing else in SVG. (Issue #2987)
- Chris Harrelson is added as a co-editor to Filter Effects.
- As a part of the document being created to solve FXTF Issue #282 There needs to be details on blending added to the document about the visual effect of filter() on the document element. Also, the behavior on the root element needs to be considered in reference to the current behavior for iframes.
- Resolved: Disconnected elements don’t have stylesheets (Issue #3096)
- There is a use case to be able to set values on a disconnected element through different APIs; plinss will investigate current work on this use case and, if necessary, file an issue.
- Resolved: Add sentence “Authors should use pointer on links and may use on other interactive elements” To UI4. (Issue #1936)
- Group members are asked to begin to populate the topics list for the F2F.
Full Meeting Minutes
Updated Working Draft of CSS Box Alignment Level 3
The CSS Working Group has published an updated Working Draft of CSS Box Alignment Module Level 3. This module contains the features of CSS relating to the alignment of boxes within their containers in the various CSS box layout models: block layout, table layout, flex layout, and grid layout. It also includes the new cross-module gap properties (row-gap, column-gap, gap).
This update contains better and more thorough definitions of the effect of self-alignment on statically-positioned absolutely-positioned boxes
and of content-alignment on scroll containers. See specific changes.
One interesting and useful side-effect of these changes is that the internal padding of a scroll container will increase the scrollable area at the block-end and inline-end edges of a scroll container with non-normal content alignment, resolving a longstanding author request.
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-align-3]) 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 Lyon, France]](/Style/CSS/csswg-2010.jpg)
Contact: