Minutes Telecon 2013-02-28
- Resolved: Add Dael to CSSWG.
- Resolved: Accept jdaggett’s font resource error handling proposal.
- Discussed interaction of Media Queries and
@page ‘size‘, and similar situation with @viewport sizing.
- Resolved: Accept Simon’s fix to page names so they work on first page of document
- Discussed painting order of page-margin boxes.
- Resolved: Add
@page OM to css3-page, exact OM API TBD.
- Discussed editorship of GCPM.
- Discussed fallback behavior with variables.
- Resolved: Publish WD of Variables with Simon Sapin’s issues noted.
Full minutes
Minutes Telecon 2013-02-20
Animations
- Resolved: Add Rossen as editor to Animations
- Resolved: Øyvind’s clarification accepted.
- Discussed reversing timing functions. See follow-up thread.
- Discussed trigger for starting animations. It’s not onload, but unclear what it is.
- Resolved:
@keyframe rules cascade.
- Resolved: Keep
pseudoElement on animation events. Mark at-risk. Revisit in a few months if it’s a web-compat problem.
Publications and Stage Transitions
- Resolved: New WD for CSS3 Paged Media
- Resolved: Allow pseudo-class combinations for @page selectors
- Resolved: Publish css-print with fantasai as editor, updated changes section.
- Resolved: Send CSS Conditional Rules Level 3 to CR.
- Resolved: Publish new WD of Counter Styles Level 3 to take comments on new
width feature. Expect LC in a few weeks.
Miscellaneous
- Resolved: Add percentages to
column-gap, not to column-width (use column-count for that, it’s better).
- Resolved: Push font load events out to separate spec.
- Goodbye to Sylvain! Leaving role as MSFT CSSWG rep to go to Adobe…
Full minutes
Minutes Tucson F2F: Backgrounds and Borders, Placeholder Styling, Variables, Conditional Rules
Backgrounds and Borders
- Need more tests.
- Resolved: Drop
space from border-image-repeat since not implemented.
- Resolved: Move
box-decoration-break from CSS3 Backgrounds to CSS3 Fragmentation.
Full minutes
Placeholder Styling
Discussed use cases and rationale for ::placeholder pseudo-element vs. :placeholder pseudo-class. Need for pseudo-element seems to be largely driven by the need to style the text color with opacity so as to make it “fade” regardless of the input’s color scheme. Pseudo-class allows styling the entire input element in response to the placeholder’s visibility.
Options considered included:
- Pseudo-class vs. pseudo-element vs. both vs. reusing
::value pseudo-element.
- Reusing SVG’s
fill-opacity to address fading.
Resolved: :placeholder-shown pseudo-class and ::placeholder pseudo-element adopted.
Full minutes: Part I, Part II
Counter Styles
- Resolved: Remove the example about simulating zero-filled counter styles and add a feature for filled counter styles.
- Resolved: 2-byte minimum for counters.
- Resolved: If current value + increment is outside of the range, then do not increment. (Not allowed to overflow the integer.)
- Resolved: Current spec is OK for fallback cycle detection per counter value (rather than per counter style).
- Resolved: Keep
ethiopic-numeric in spec, but mark at risk.
Full minutes
variables
- Resolved:
var- prefix is lowercase and case-sensitive.
- Resolved: Publish Cascading Variables as Last call.
- Resolved: Accept CDO/CDC at top level in variables per dbaron’s message.
- Resolved: Can’t put unmatched brackets, braces, parens, or badstring/baduri tokens in variables. (No change.)
Full minutes: Part I, Part II
Conditional Rules
- Resolved:
@supports is not affected by limitations imposed by user prefs or system limitations.
- Resolved: Not adding
@supports all.
- Reviewed some other issues in Disposition of Comments.
Full minutes
Minutes Tucson F2F: Transitions and Animations
Transitions and Animations
- Resolved: Defer keypath syntax to next level of Transitions.
- Resolved: No slash in transition shorthand.
- Resolved: Do whatever we did for Animations for Transitions wrt init*Event methods.
- Resolved: Computed interpolated value of repeatable lists is least common multiple of the interpolated lists’ lengths.
- Resolved: Computed interpolated value of repeatable lists is least common multiple of the interpolated lists’ lengths.
- Resolved: Publish updated WD of Transitions with those edits.
- Discussed editorial work for animatability propdef lines.
- Discussed interaction and cascading order of transitions and animations.
Full minutes: Part I, Part II
Minutes Tucson F2F: Paged Media, Flexbox, Regions, Top Layer Positioning
Paged Media Level 4
Full minutes
Flexbox
- Resolved: Zero-length boxes stay at end of earlier line unless line is already overflowing, in which case they wrap. (Issue 1)
- Resolved: Flex line’s cross size is floored at zero. (Issue 2)
- Opened issue on percentage margins on flex items. (Issue 16)
- Resolved: Flex items’ cross size to be definite when stretched to fit definite size. (Issue 3)
- Resolved: Defer additional spacing controls to Level 2 (Issue 4)
- Resolved: Proposed handling of stretched items with intrinsic aspect ratio is accepted. (Issue 8)
- Resolved: Tab’s message is adopted as WG response for Issue 9.
- Resolved: Flex items can have negative outer size; no clamping to zero. (Issue 10)
- Resolved:
:first-line/::first-letter don’t apply to flex containers. Could revisit later if this is in high demand. (Issue 13)
- Resolved: (Issue 15)
- Resolved:
overflow applies to flex containers
Full minutes
Regions
- Regions polyfill (limited functionality, limited perf) available for experimentation.
- Discussed use of Web Components for region-based templating and linking them to the document via CSS.
Full minutes
Top Layer Positioning
Discussed top layer positioning (as used for fullscreen) and how it can be accessed via CSS. Seems that nobody’s really clear on exactly how it’s supposed to work wrt positioning and scrolling behavior [?] and more investigation is needed on what the “magic” requirements of HTML5 actually should be.
Full minutes
Minutes Tucson F2F: Text Decoration, Writing Modes, Text, Fonts
Text Decoration
- Resolved: Don’t drop
text-underline-position.
- Resolved: Not (currently at least) doing the
@pattern proposal.
- Other issues awaiting i18n input. See Disposition of Comments.
Full minutes
Writing Modes
Full minutes
Fonts
- Reviewed updated wording for case-sensitivity of font name matching.
- Discussed use of OpenType language tags.
- Discussed use of OpenType script tags.
- Discussed italic synthesis in vertical writing -> open issue.
- Resolved: Publish updated WD of CSS3 Fonts.
- Plan for 6-week LC after this next WD cycle.
Full minutes: Part I, Part II
Text
- Discussed interaction of word-break and line-break.
- Wordsmithed line-break definitions
- Resolved: Strike the two sentences “Support for this property is optional. It is recommended for UAs that wish to support CJK typography and strongly recommended for UAs in the Japanese market.”
- Resolved: (1) do language-specific justification; (2) and there are 4 values to
text-justify: none, auto, distribute and inter-word; (3) auto includes inter-ideographic behavior
- Plan to drop min/max values from letter-spacing, only have one value for tracking.
- Need some plan to resolve conflict between
- Having ability to turn off letterspacing from justification. (Needed for German)
- Having ability to combine tracking and letterspacing. (Useful in CJK, possibly needed by legacy Japanese docs using
text-justify: ideographic; letter-spacing: 0.)
- Plan to defer
text-align: <string> to L4.
Full minutes
Minutes Tucson F2F: Multi-col, Sizing, Fragmentation
Multi-col
- Blocked on testcases and a couple spec issues.
- Resolved: Column rules are painted in the inline content layer, but below all inline content inside the multicol. [But see follow-up.]
- Resolved:
- Remove lines 3-10 of pseudo-algorithm in multicol
- Remove concept of available width and have pseudo-algorithm depend on used width (whose calculation is defined elsewhere by container layout modules)
- State that intrinsic sizes of multi-col elements is undefined in this level.
- Add note pointing to where they will be defined (Sizing).
Full minutes: Part I, Part II
Intrinsic Sizing
Discussed conflicting definitions of intrinsic sizing in CSS3 Box and CSS3 Sizing. There are two conflicting principles:
- interop/deterministic layout
- allowing as high fidelity layout as possible
Bert and fantasai will incorporate appropriate text in CSS3 Sizing, defining the baseline and ideal layouts and discussing the principles outlined above.
Full minutes
Fragmentation of Rotated Boxes
- Discussed various options for fragmenting transformed boxes.
- Resolved: Transformation is applied independently to each fragment. Because nothing really gives you the expected results, and this is the simplest to define and implement.
- Authors should beware of combining transforms and printing. It’s unlikely to work well for anything more noticeable than subtle.
Full minutes
Minutes Tucson F2F: Syntax and Administrivia
Case-sensitivity
- Resolved: User-defined things continue to be matched case-sensitively. CSS-defined things continue to be matched ASCII-case-insensitively, even when defined to exist through UA stylesheet rules or equivalent (e.g. @counter-style rule); such identifiers are effectively ASCII-lower-cased on parse.
- Resolved: Font-family names are matched Unicode CI against the font, using C+F casefolding rules with no normalization or locale-specific mappings.
- We expect CSS-defined syntax to remain ASCII-only. (User-defined idents of course can span most of Unicode.)
Full minutes
CSS3 Syntax
- Resolved: Closing brackets in the wrong places are just invalid tokens in the context they’re in; they don’t get special handling. [Update CSS3 Syntax to match 2.1.]
- Discussed non-use of grammar productions in CSS3 Syntax, specifically potential concerns for:
- Inadvertent incompatibility with various parser architectures.
- Understandability of spec to authors or others who want a high-level view of the syntactic structure.
- Hooking syntax defined by other modules into the CSS general syntax.
- Reviewed current list of differences from CSS2.1 syntax.
- Resolved: Add tokens for all the multi-character attribute selector operators to css3-syntax. [Match CSS2.1 / Selectors Level 3]
Full minutes: Part I, Part II
CSS2.1
- Resolved: Develop text for CSS2.1 PER as open editor’s draft (while continuing to maintain errata). Publish PER when we’re done & have updated implementation report.
Full minutes
F2F Scheduling
- Resolved: Meet at TPAC, possibly TPAC-adjacent.
- Resolved: Summer meeting in Europe week of 9th September. Tentatively scheduled for Mozilla in Paris, other options on the table.
- Resolved: June 5-7 at Mozilla Japan in Tokyo
Full minutes: Part I, Part II
Minutes Telecon 2013-01-30
- Resolved: Viewport units in case of
overflow:auto are sized as if scrollbar is *not* present (even if they are).
- Discussed status/publication of CSS3 Box module.
- Resolved: keep compositing/blending of backgrounds the compositing spec for now.
- Discussed WebKit’s
overflow: overlay value. No consensus to add it; see minutes for considerations.
- Resolved:
non-ascii starts at 0x80.
- Discussed some other differences between CSS2.1 syntax and CSS3 Syntax drafts.
- Resolved: Allow
@page selectors to be comma-separated lists
Full minutes
Minutes Telecon 2013-01-23
- Discussed fontloader interface and callbacks
- Resolved: Add SVG attributes as CSS properties that apply only to SVG layout:
cx, cy, dx, dy, fx, fy, height, width, offset, r, rx, ry, x, x1, x2, y, y1, y2 and maybe d
- Discussed styling of placeholder text for input elements
- Discussed updating CSS3 Box WD. Concern with republishing is the out-of-dateness / incompleteness of much of the (editor’s) draft.
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: