CSS WG Blog front page
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. This 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.)
Introducing CSS Values and Units Level 4
The CSS Working Group has published a First Public Working Draft of CSS Values and Units Level 4. This CSS module describes the common values and units that CSS properties accept and the syntax used for describing them in CSS property definitions.
Additions since Level 3 consist of:
Please review the draft and 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-values-4]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Values and Units L3 Updated CR
The CSS Working Group has published an updated Candidate Recommendation of CSS Values and Units Level 3. This CSS module describes the common values and units that CSS properties accept and the syntax used for describing them in CSS property definitions.
Changes since the 2016 Candidate Recommendation include
- Removing consideration of scrollbars in defining viewport units (due to lack of implementation)
- Defining empty
ur()s as representing an invalid URL
- Defining special handling of fragment-only relative
url()s because apparently browser engines can’t properly handle updating the computed values of relative url()s when the page’s URL is changed.
- Defined when range-checking of calc() is performed.
- Various other fixes and clarifications.
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-values-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
New Working Draft of CSS Box Model Level 3
The CSS WG has published two back-to-back Working Drafts of the CSS Box Model Module Level 3. The first publication archives Bert and Anton’s changes to that spec since the 2007 draft for archaeological purposes. (Note: It is still dangerously out-of-date, please continue to reference CSS2.) The second publication cuts the module down to a subset of CSS2 Chapter 8.
The scope of this module is now just the margin and padding properties. We have dropped all of the spec content that discusses box generation (moved to the CSS Display Module) or the Flow Layout model (will become its own module based on the prose in CSS2—which has been maintained—rather than what was in earlier publications—which was not). The remaining content, which discusses the box model (margin/padding/border/content areas) has been synced to CSS2. See Introduction. There are no non-editorial changes since CSS Level 2, other than adapting the prose slightly to account for vertical writing modes.
A future revision of this module might include the border styling properties (currently defined in CSS Backgrounds and Borders); whether or not to move them is currently open question, thoughts on this idea welcome.
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-box-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Grid Level 2 Updated: Subgrid Specification Completed
The CSS Working Group has published an updated Working Draft of CSS Grid Layout Level 2. This draft contains the “subgrid” feature that was cut from the Level 1 CR last year, along with a few other minor things.
At this point there are no further issues open against the subgrid feature, so we’re asking for everyone to conduct their final reviews against the feature. Changes since the last Working Draft are listed in the Changes section.
For the next update of this draft, we’ll be incorporating the full text of the CSS Grid Level 1 specification along with the spec text for a few small feature requests (which depend on incorporating the L1 prose):
Once that text is incorporated, the Level 2 spec will be feature complete, and we’ll start preparing it for Candidate Recommendation.
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-grid-2]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updated WD of CSS Inline Layout Level 3
The CSS Working Group has published an updated Working Draft of CSS Inline Layout Level 3. This module describes the css features relating to inline box layout in the block-axis dimension, particularly vertical alignment within a line and initial letter styling (drop caps, etc.).
This update includes a pile of improvements to the specification for initial letter styling as well as the outline of a property to control the height of the background/border areas of an inline box. Changes since the last Working Draft are listed in the Changes section.
There are still a lot of open issues, including more precise definition of the initial letters’ layout model as well as several property/value naming issues. The CSSWG welcomes feedback on these issues and on the draft in general.
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-inline-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Overflow 3 Draft Updated
The CSS Working Group has published an updated Working Draft of CSS Overflow level 3. This modules contains the features of CSS relating to handling the display of excessive amount of content in an element.
In addition to bug fixes and refinements accumulated since last publication, this draft introduces:
- Flow relative longhands to the overflow property: inline-overflow and block-overflow
- The line-clamp property (and its longhands), to provide a standard and improved replacement for the proprietary -webkit-line-clamp property.
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-overflow-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 2018-07-25
- fantasai requested assistance from experts for issue #698 (cursive shaping breaks needs better scoping). Myles offered to review and Rossen will ask a font expert from Microsoft to review.
- Resolved: No to renaming
hyphenate-character and add normative text describing how UIs are allowed to truncate additional characters (Issue #2809)
- Resolved: Change the
initial-letter value to initial-letters (Issue #862)
- A new github issue will be opened to try and find a new name for
initial-letters as the current name makes it seem like a selector. (Issue #2950)
- Resolved: No change is needed (Issue #2703: Initial letter, sizing, and overflow)
- Resolved: Accept the changes as stated in the issue (Issue #2375: Degenerate polygons with positive shape-margin)
- Issue summary:
- Zero-area shapes still have edges and those edges impact float layout.
- Zero-area shapes can be expanded by shape-margin values.
- Zero-area shapes will not affect floated elements that are block adjacent — there is no minimum of 1 pixel area applied to the shape.
- Limit the inset rectangle to a minimum of zero width/zero height, using rules similar to how border-radius values that add to greater than 100% are adjusted.
- Resolved: Accept florian’s proposal (Issue #285: Readonly form control and user-select)
- Proposal (to be word-smithed into a PR for review): an editable element is either an editing host or a form control with normally mutable textual content such as textarea, even if this form control is in non mutable state.
- Resolved: Defer this issue (#528: May want different properties for font matching and variation value) to next level.
Full Meeting Minutes
Archives
Browse by date:
Browse by category:
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: