Minutes and Resolutions Telecon 2011-04-20
Looks like I forgot to post these to the blog last month…
- Reviewed what’s left to move Namespaces to PR
- Resolved: Use Bugzilla to track CSS2.1 issues going forward. Discussion will remain on the mailing list, however, not in the bug tracker.
- Resolved: Don’t consider text-transform of accents for Text 3, but possibly for Text 4 if there’s more information showing it’s needed/possible.
- Discussed module naming. Plan is to publish Snapshots as Notes and push an announcement along with the CSS2.1 REC announcement explaining the move to year-based Snapshots for CSS overall, using independently levelled modules.
- Agreed on a clarification to transitions’ effect on shorthands.
- Resolved: Transforms create a pseudo-stacking context, not a full one. z-index doesn’t apply (unless the element is positioned, as usual).
- No dissent on adding disclosure triangle list style to CSS3 Lists. It was noted that it should respect the writing direction.
Full minutes
Angles in Gradients
Posting on behalf of Tab Atkins:
I’ve been pretty adamant for some time that gradients should use the math-y interpretation of angles, where 0deg is East and 90deg is North. In addition to matching what you learn in school about polar coordinates, it matches what tools like Photoshop expose. Other members of the WG, though, have been equally adamant that we should more closely match existing language conventions, particularly that bigger angles mean clockwise rotation.
The strength of my conviction has eroded over time. It really is true that every other use of angles uses them to represent clockwise rotations. In SVG, angles are present in transforms and the glyph-orientation properties, while in CSS they’re present in transforms, image-orientation, and the azimuth and elevation aural properties. In all of them (save elevation, which rotates in a different axis), the rotation is clockwise.
I also know that, as an author, there have been several places where SVG has annoyed me because it does two similar things in an inconsistent way (unfortunately, I don’t remember exactly what things annoyed me). I suspect these things were designed to be consistent with other tools that SVG wanted to align with. I, having never used these tools, don’t understand this and just see the self-inconsistency. I’d prefer to avoid a similar situation with CSS, where users that don’t remember their polar coordinates and never used gradients in Photoshop look at CSS gradients and just see that the angles are defined in a way that’s inconsistent with how they’re defined elsewhere. Plus, an argument can be made that actually respecting polar coordinates would involve clockwise rotation, as the angles should progress from the X-axis toward the Y-axis, which points downward on the screen.
So, we have three choices:
- A) Keep the angles as they are, with 0deg=East and 90deg=North (counter-clockwise)
- B) Switch to screen-coord polar, with 0deg=East and 90deg=South (clockwise)
- C) Switch to bearing angles (compass directions), with 0deg=North and 90deg=East (clockwise)
Except for ‘azimuth’ [which uses ‘0deg’ to indicate straight ahead], current properties are consistent with either B or C, as they just use the angles for rotation, not direction.
What do you think?
Post your response to www-style or CSS3.info.
Minutes and Resolutions Telecon 2011-05-11
- We’re missing AC reviews for CSS2.1. Reviews have been submitted by Microsoft, Mozilla, Opera, Nokia, and Apple. (Note: 2/5 comments suggest incorporating the resolution for issue 225.) All other W3C Members should ping their AC reps to send in a review.
- Resolved: Use plinss’s spec annotation system for CSS2.1 and future specs. (It annotates sections of the spec with test results and a link to the tests.)
- Resolved: Define cjk longhand list numbering up to 100,000 with fallback to cjk-decimal beyond, allow UAs to implement longhand beyond that limit, put definition for that in informative appendix.
- Resolved: Add new CSS3 width keywords as an appendix to CSS3 Writing Modes, add note that they might be moved/copied to a more appropriate spec later.
Full minutes
Minutes and Resolutions Telecon 2011-05-05
- Discussed charter
- Plan to trim down css3-images, will discuss on www-style
- Resolved: Publish CSS3 Lists WD
- Resolved: jdaggett, szilles as editors of css3-linebox
- Resolved: Publish CSS Snapshots once unprefixed legacy properties issue is noted
- Resolved: Remove phonemes property; include note to explain removal
- Resolved: Discussed CSS logo proposal
Full minutes
Minutes and Resolutions Telecon 2011-04-27
- Discussed draft charter.
- CSSOM and CSSOM Views was seen as very important, but needing another editor to help Anne, who is stretched thin.
- Discussed CSS Snapshots and prefixes, trying to word Sylvain’s suggestion that prefixes only be dropped after CR and once an implementation report is submitted (with testcases if necessary).
- Resolved: Publish updated Working Draft of CSS3 Writing Modes
- Long argument over Tab’s request to create a Variables/Mixins spec, ending with a homework assignment to create a requirements doc to frame the discussion, for continuation at the F2F.
Full minutes
New CSS Publications: CSS3 Fonts WD, CSS3 Text WD, CSS Grid Layout WD, CSS Multi-column Layout CR
The CSSWG recently published some updates to:
There’s also a new module in town, CSS Grid Layout [css3-grid-layout], which attempts to integrate a number of layout features into CSS.
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-04-13
- Resolved: June F2F move to Kyoto, Japan
- Resolved: Accept the new CSSWG site design from Divya Manian
- Resolved: EPUB should use prefixed versions of properties that aren’t yet in CR. No recommendations on what the prefixed property means.
Full minutes
Minutes and Resolutions Telecon 2011-04-06
- Decided on Japan for June F2F, exact location TBD next week.
- Resolved: Proposal accepted for CSS2.1 Issue 225 with “If the element has children” removed, pending Anton’s approval.
- Resolved: dsinger’s answer to Olaf adopted as official for CSS2.1 Issue 286. No change to the spec.
- Resolved: Publish updated WD of CSS3 Speech.
- Resolved: Publish updated WD of CSS3 Text.
- CSS Namespaces has the required test passes for PR, need to prepare a disposition of comments and implementation reports.
Full minutes
Minutes and Resolutions Telecon 2011-03-30
- Discussed location of June F2F. Most people seem to be OK with Kyoto/Osaka (in place of Tokyo), but we need a meeting room June 2-4. (Needed: space for ~25 people, projector, power, and wifi)
- Resolved: Updated proposal accepted for CSS2.1 Issue 203.
- CSS2.1 Issue 179 is closed with Bert’s latest edits and Anton’s approval.
- Resolved: For CSS2.1 Issue 192
If a shortened line box is too small to contain any content after the float, then that content the line box is shifted downward (and its width recomputed)
until either it some content fits or there are no more floats present. Any content in the current line before a floated box is reflowed in the first available same line on the other side of the float.
- Resolved: Not dropping :first-line :first-letter from CSS2.1. It may be underdefined, but it’s in CSS1 and CSS3 and we have a usable level of interop demonstrated in the test suite, so dropping it here doesn’t gain us anything.
- Resolved: Advance CSS2.1 to PR.
- Plan for errata is to maintain errata list after REC and occasionally publish updated RECs via PER phase.
Full minutes
Minutes and Resolutions Telecon 2011-03-23
Full minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: