Minutes and Resolutions Telecon 2011-09-07
- CSS3 Fonts will not be officially updated until jdaggett finishes more edits
- Discussion of default text orientation of characters, conclusion that there should be a clearer distinction between the determination phase and the fixup phase.
- Tentative Conclusion: No change to CSS3 Text wrt cpsp OT feature
- Resolved: UAs may do better than the Unicode minimum for text-transform casing.
Full minutes
New CSS Module: Conditional Rules Level 3
Posting on behalf of L. David Baron:
CSS Conditional Rules Level 3 has been published as the first public working draft of the CSS Conditional Rules Module. To quote from its introduction:
CSS 2.1 defines one type of conditional group rule, the @media rule, and allows only rulesets (not other @-rules) inside of it. The @media rule provides the ability to have media-specific style rules, which is also provided by style sheet linking features such as @import and <link>. The restrictions on the contents of @media rules made them less useful; they have forced authors using CSS features involving media-specific style sheets to use separate style sheets for each medium.
This specification extends the rules for the contents of conditional group rules to allow other @-rules, which enables authors to combine CSS features involving @-rules with media specific style sheets within a single style sheet.
This specification also defines additional types of conditional group rules, @supports and @document, to address author and user requirements.
The @supports rule allows CSS to be conditioned on implementation support for CSS properties and values. This rule makes it much easier for authors to use new CSS features and provide good fallback for implementations that do not support those features. This is particularly important for CSS features that provide new layout mechanisms, and for other cases where a set of related styles needs to be conditioned on propertysupport.
The @document rule allows CSS to be conditioned on the page to which the style sheet is being applied. This allows users to apply styles to a particular page or group of pages, which greatly increases the power of user style sheets.
The CSS working group welcomes comments on this specification. The preferred place for them is the www-style mailing list. Please start the subject line of your message with the spec code[css3-conditional] and include a summary of your comment.
-David
Minutes and Resolutions Telecon 2011-08-31
- Resolved: Publish a new WD of CSS3 Values and Units.
- Resolved: Publish FPWD of Selectors 4 with the REC of Selectors 3 (ETA end of September).
- Resolved: The editor of a spec is responsible for posting to the blog, www-style, etc. when something is published.
- Also discussed: spec markup for testing, CSS2.1 issue tracking, blog transition to WordPress, plinss’s new test tracking system which is up for pre-alpha testing, some additional administrivia.
Full minutes
Minutes and Resolutions Telecon 2011-08-24
- Resolved: Publish CSS3 Text and CSS3 Writing Modes as WDs with updates mentioned in minutes.
- Deferred Selectors 4 publication until Selectors 3 hits REC in a couple weeks.
- Resolved: Use
flow-from property to enable regions, mark interaction wit content and display as an issue.
- Resolved: CSS Regions has a region break like multicol and start on css3 pagination module and Mozilla/Adobe/MS would sort out the editorship of that spec.
- Resolved: TabAtkins to create a proposal for printing backgrounds by default.
Full minutes
Last Call for Comments on CSS Speech
The Cascading Style Sheets (CSS) Working Group has published a Last Call Working Draft of the CSS Speech Module. The CSS Speech module defines aural CSS properties that enable authors to declaratively control the rendering of documents via speech synthesis. The feature set exposed by this specification is designed to complement the model described by the Speech Synthesis Markup Language (SSML) Version 1.1.
Comments are welcome through 30 September 2011. As always, send feedback to www-style with the spec code [css3-speech] and your comment topic in the subject line.
Minutes and Resolutions Telecon 2011-08-17
- Resolved: Put ltr | rtl keywords back into image(), mark as at-risk.
- Discussed having a switch to have author request background printing.
Full minutes
CSSOM Updates
On 12 July 2011 Anne van Kesteren pushed out a First Public Working Draft of the CSS Object Model [cssom] specification. The primary goal of the spec is to standardize various un(der)specified-but-implemented APIs for interacting with CSS style sheets and drive the Web platform towards interoperability in this area.
A second goal for the CSSOM effort is to provide better APIs for interacting with style sheets. To that end, Daniel Glazman has put out a call for suggestions to find out what problems the CSSOM APIs most need to solve.
Anne also published an update to the CSSOM View Module [cssom-view]. The main thing holding this module back is the lack of feedback, particularly from implementers, so please send comments!
As always, send feedback to www-style with the appropriate [spec-code] and your comment topic in the subject line.
Updated CSS Drafts: Images, Regions, Writing Modes
Going backwards in time as I try to catch up…
CSS Images [css3-image]
On 12 July 2011, the CSSWG published an updated Working Draft of the CSS Image Values and Replaced Content Module Level 3. Among other significant changes, this publication switches the linear-gradient() angles to bearing angles (compass directions) with 0deg pointing up due to overwhelming feedback that this made more sense.
Next up, Tab is planning to change the syntax for keywords to make them less confusable. If you have good suggestions, send them over to www-style.
CSS Regions [css3-regions]
On 9 June 2011, the CSSWG published aa First Public Working Draft of the CSS Regions Module. This module defines linked flows between different regions (boxes) on the page. CSS Regions is still in the early stages, so expect lots of changes as we figure out the right way to do things. You can check out the latest in the unofficial editor’s draft.
CSS Writing Modes [css3-writing-modes]
On 31 May 2011, we also published an updated Working Draft of the CSS Writing Modes Module Level 3. Most of the changes were detail-oriented as we dive into the ambiguous nitty-gritty of how to typeset vertical text.
As always, send feedback to www-style with the appropriate [spec-code] and your comment topic in the subject line.
Minutes and Resolutions Telecon 2011-08-10
- Resolved: Add logical keywords to gradients.
- Resolved: Publish next CSS3 Images WD with
to <keyword> syntax for gradients.
- Resolved: No change to how repeating gradients are handled (using
repeat-* functions).
- Resolved: Publish updated WD of CSS3 Images with these changes.
- Resolved: Publish LCWD of CSS Speech, comment period to end September 30th.
- Discussed editing of CSS3 Values and Units module.
- Resolved: Assign HTMLWG request for block-in-inline anonymous box pseudo as an issue to the CSS3 Box module.
- Discussion of
flow-from syntax for CSS Regions and which property it belongs in.
Full minutes
Minutes and Resolutions Telecon 2011-08-03
We worked through the items on the CSSWG’s HTML5 LC review wiki page.
- Resolved: Send comment that pseudo-selectors section should have normative references to Selectors 3 / CSS3 UI.
- Resolved: HTML5 should update to and reference Selectors 4 for
:ltr and :rtl. See also switching to :dir().
- Action: Peter to write up selectors coordination issue wrt
::cue et al.
- Resolved: Issue about lack of
disabled attribute in <link> is not a CSSWG comment.
- Action: Peter to write comment on referencing CSSWG editors’ drafts.
- Resolved: No CSSWG comment on case-insensitive attribute values.
- Resolved: No comment on
video { object-fit: contain; }.
- Resolved:
font-size: xxx-large is not a CSSWG comment to HTML
- Resolved: Bert sends attribute value normalization comment on his own; not a CSSWG comment
- Resolved: Bert sends white space parsing issue on his own
- Resolved: No comment on
<details> markup.
- CSSWG needs to do some work to make
<details> usable, see e.g. visual collapsing and markers.
- Resolved:
<iframe seamless> definition has some problems that need fixing.
- Action: Tab to write up a comment on
<iframe seamless>
- Resolved: Adopt Bert’s comment on normativeness of Chapter 10 as CSSWG comment.
- Resolved: No CSSWG comment on HTML namespaces.
Full minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: