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.)
Candidate Recommendation of CSS Display Level 3
The CSS Working Group has published a Candidate Recommendation and invites implementations of the CSS Display Module Level 3. This module describes how the CSS formatting box tree is generated
from the document element tree and defines properties that control the types of boxes thus generated.
New features since Level 2 include:
The draft also features
Changes since the last Working Draft are listed in the Changes section. A Disposition of Comments is also available.
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-display]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updated CSS Cascading and Inheritance Levels 3 & 4
The CSS Working Group has published updated Candidate Recommendations of CSS Cascading and Inheritance Level 3 and CSS Cascading and Inheritance Level 4. This CSS module describes how to collate style rules and assign values to all properties on all elements by way of cascading (choosing a winning declaration among many) and inheritance (propagating values from parent to child).
These updates are largely about clarifications; however we also:
- Dropped the unimplemented/obsolete “override” origin (introduced by DOM2STYLE).
- Dropped the definition of scoped cascading from Level 3. (It remains in Level 4 for now.)
- Added definitions for how property aliasing works to Level 4.
- Defined the computation of styles on text nodes (exposed by the new
display: contents feature in CSS Display Module Level 3) in Level 4.
A full list of changes since the earlier publications are listed in the Changes sections: Level 3 Changes, Level 4 Changes. See also the Dispositions of Comments: Level 3 DoC, Level 4 DoC
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-cascade]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updated Draft of CSS Logical Properties and Values Level 1
The CSS Working Group has published an updated Working Draft of CSS Logical Properties and Values Level 1. This module introduces properties and values that control layout through
logical (writing-mode–relative), rather than physical, direction and dimension mappings.
The most significant open issue in the draft is the syntax for switching margin-style
shorthand parsing from physical to logical. The CSSWG would appreciate feedback and suggestions on this feature, see Issue 1282 and comment about constraints.
The other two open issues are about how logical longhands inherit (Issue 3029) and whether shorthands expand to all longhands or only either logical or physical (Issue 3030). Use cases that would tip the decision in one direction vs the other are particularly welcome (so far we have none, so the only consideration at the moment is implementation complexity).
We encourage everyone interested in this module to put some thought into these issues and to send any feedback for consideration. We hope to close off the issues by the end of October and transition the module to Candidate Recommendation shortly afterwards.
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-logical-1]) 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-08-22
- Resolved: Align grid layout static position as content box rather than padding (Issue #3020)
- Resolved: Drop section 5, backgrounds and borders, from logical properties. (Issue #3028)
- Resolved: Accept proposal [Have values that affect alignment compute in containing block. Values that affect alignment of content of a box of an element are computed in writing mode of element itself]. (Issue #3013)
- Resolved: The flow relative keyword values compute to themselves, not to physical equivalents. (Issue #2821)
- Resolved: Publish a new WD of logical properties.
- Resolved: Layout containment censors baselines and size containment does not (Issue #2995)
- Resolved: Publish Selectors 3 as PR
- Resolved: Accept the changeset [Change from an allow list to a disallow list for break-inside] (Issue #1904)
- Resolved: Specify 0 size elements are positioned as early as possible in the fragmentation flow (Issue #1529)
- The people on the call leaned toward browsers defaulting to on by default for text-decoration-skip-ink (Issue #2818), however some individuals that had previously been against on by default weren’t available for the call so discussion will continue on Github and this can be discussed on the next APAC timed call (5 Sept.)
- Resolved: Rename overflow to block-ellipsis. Rename auto to none. Rename ellipsis behavior to auto. (Issue #2561)
- Resolved: No change to spec, leave piece of text out [text: The ‘medium’ value is the user’s preferred font size and is used as the reference middle value.] (Issue #2430)
Full Meeting Minutes
Minutes Telecon 2018-08-15
- Though the group resolved on issue #2988 (‘overflow’ 2-value syntax is in wrong order) last week, the resolution is raising concerns and questions on github. Anyone interested should comment there.
- Interested members were requested to review the proposed changes to resolving line names in subgrids; Issue #2564
- The security and privacy index edits (Issue #620) are completed so CSS Cascade will be published based on the resolution made during the Sydney F2F (Resolution)
- Resolved: Cross-fade blends images in premultiplied space (Issue #2722)
- Instead of adding new properties to Ruby and Text Decor to handle TTML’s use case in issue #2998 the group thought it might be possible to handle using a special case for ::first-line. This proposal will be added to the github issue to see if this covers the entirety of the use case or if there’s more nuance that would still require additional properties.
- Resolved: Close this issue (#2947: Reconsider if ‘inline-block’ and ‘inline flow-root’ should be syntactically equivalent) no change.
- Resolved: Request CR transition for CSS Display
- Issue #3006 (Mixing baseline self-alignment with random content alignments) needs a better example before it can be discussed. Anyone with examples is invited to add them to the github issue.
- TabAtkins completed the proposal for issue #1425: Fully specify the “Overflow and Scroll Positions” section and those interested will review so a resolution can be reached.
- The proposal in issue #3012 is to change
:visited to remove all special casing and limit the use cases such that it stops being able to leak private information. This proposal would remove some current use cases for :visited so several working group members needed to discuss with their teams. Additionally, there were concerns about it violating the GDPR regulations so before resolving members will also consult with their legal teams.
Full Meeting Minutes
Updated CR of CSS Scroll Snapping Level 1
The CSS Working Group has published an updated Candidate Recommendation of CSS Scroll Snapping Module Level 1. his module contains features to control panning and scrolling behavior with “snap positions”.
The Changes include:
- Fixed scroll-snap-align shorthand to assign block-axis value first, inline-axis value second, accordingly to logical shorthand conventions. (It was backwards in the earlier publications.)
- Added an
auto value as the initial value of scroll-padding; UA heuristics must be mapped to this keyword so they can be overridden.
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-scroll-snap-1]) 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: