Minutes and Resolutions 2010-01-20
- Reviewed status of action items and CSS2.1 test suite.
- Resolved: Fix grammar to allow spaces inside parentheses in calc(). [ISSUE-116]
- Resolved: Clamp calc() results outside property’s value range to within the range. Document that this requires all properties accepting calc() to define their range as closed (not open) intervals. [ISSUE-117]
- Resolved: min() and max() take one or more arguments ISSUE-112.
- Discussed dbaron’s email about calc() being overly-restrictive wrt units. Agreed that the output of calc() just needs to match the input of the property. WG seems interested in having value / value divisions, and in cases where this leads to division by zero, to have it fall back to inherit-or-initial as defined by the property’s default inheritance behavior. dbaron to write up a proposal. ISSUE-118.
- Resolved: Accept proposal to make transitioning ‘visibility’ values between 0 and 1 map to visible.
Full minutes
Minutes and Resolutions 2010-01-13
- Reviewed status of CSS2.1 test suite and next steps
- Resolved: Tab’s response to PFWG’s review of CSS3 Backgrounds and Borders is the CSSWG’s official response.
- Discussed px vs. pt thread; Tab to write a summary.
- Resolved: The UA may transform numeric values on input (e.g. limiting their precision or clamping them to a range), but anything the UA produces as output it must also accept as input.
- Resolved: Publish css-style-attr Last Call Working Draft with 3-week comment period.
Full minutes
Minutes and Resolutions 2009-12-16
Full minutes
Minutes and Resolutions 2009-12-09
- Discussed various problems with color correction.
- CSS3 Color is still waiting for dbaron to finish addressing all LC comments before CR or PR publication.
- Reviewed a message about selectors and security. Concluded that doing anything about it is outside the scope of CSS.
Full minutes
Two new Candidate Recommendations
Two CSS modules became Candidate Recommendation: CSS Backgrounds and Borders and CSS Multi-column Layout.
It is now time to see if the specifications can be implemented. Large parts of both modules have already been implemented experimentally in various browsers and other software. Over the next six months, the working group plans to develop a test suite and then use the results of testing to decide if the specifications are ready to become W3C Recommendations.
Feedback on the specifications, in particular experience with implementing them, can be sent to the mailing list <www-style@w3.org>. Please, include the short name of the specification between square brackets [] in the subject of any message you send. That is:
[css3-multicol]
or
[css3-background]
Selectors is a Proposed Recommendation
Many thanks to all who helped with comments, tests, and implementations!
The Selectors specification was just advanced to Proposed Recommendation
by the W3C Director. That means that the specification has successfully
passed public review and has been sufficiently implemented to no longer
need a status as Candidate Recommendation (which is also known as “call
for implementations”).
Currently, the W3C members are reviewing the specification one last
time. Of course, we think we have done our job well and they won’t find
anything wrong. They have a little over a month for that task.
However, the specification will not immediately become a W3C
Recommendation at the end of the review period. That is because
Selectors has normative references in its bibliography to
CSS 2.1 and to
the CSS Namespaces
module, and so it was decided that those have to
become Recommendations first. That ensures that W3C Recommendations are
as stable as possible, by only depending on other Recommendations.
A bit of history: Selectors became Candidate Recommendation already in
2001, but a couple of proposed features (‘:contains’, ‘::selection’)
were never implemented and turned out to be difficult enough that we
abandoned them for now. To fix the draft with respect to those problems,
a new working draft was made in 2005, which was updated one last time
earlier this year.
You can see the last changes we made to the specification in the
disposition of comments. Nothing major changed, but a number of
descriptions were improved.
The CSS Validator supports Selectors level 3
The CSS Validator implements the latest Selectors. To check a style sheet, it is enough to choose “CSS level 3” as the profile in the Web interface.
Minutes and Resolutions 2009-12-02
- Mozilla and WebKit have both implemented
pointer-events applied to HTML (not just SVG). Only two values are supported: auto and none.
- fantasai sent and Tab will send comments on Doug’s Spec Conventions proposal. There were no other comments at this point.
- Resolved: Publish CSS3 Color as CR or PR without proposed
color-correction addition.
- Reviewed implementation status for CSS Namespaces based on Chris’s report. Only one test does not have two passes.
- Resolved: Add
start and end values to float (CSS3 Box Model)
- Resolved: Publish Snapshot as CR along with CSS3 Color CR or PR.
- Resolved: Snapshot will replace /TR/css3-roadmap, and will also be the target of /TR/CSS3 and /TR/CSS, pending the Director’s approval.
Full minutes
Minutes and Resolutions 2009-11-18
- Resolved: Accepted fantasai’s proposed text for requiring that the the area outside the border edge, considering the border-radius curve and not considering border-image, does not accept mouse events on behalf of the element.
- Resolved: Not adding
background-opacity; considering functionality for future specs, but probably not in that form. (See previous discussions on targetting filters.)
- Resolved: Rejected proposal to allow extra slashes in border-image shorthand.
- Noted:
box-break: continuous | each-box will be renamed box-decoration-break: slice | clone unless there is consensus on a better proposal.
- Resolved: Publish new Working Drafts of Transitions and 2D Transforms.
Full minutes
Minutes and resolutions 2009-11-25
The CSS WG looked, among other things, at the stability of the Backgrounds and Borders module and an issue with replaced elements and ‘run-in’ in CSS 2.1.
- Resolved: The WG will request Candidate Recommendation status for Backgrounds and Borders.
- Resolved: There is no ambiguity that an image can be ‘run-in’. No additional text is needed.
There was also news about Selectors: after seeing the number of implementations, the Director agreed to give the specification Proposed Recommendation status. The review period will start in a few days.
Full minutes
Minutes and Resolutions November F2F TPAC Santa Clara
Drop Shadows and Filter Effects
- Discussed drop shadows and what inner shadow is.
(Tab: the shadow is cast by a negative of the alpha channel, then clipped
to the actual alpha channel
)
- Discussed applying effects like drop shadows and opacity to different
parts of the box. (fantasai: The pieces we’d need to address, in various
combinations: background layers, border (one piece), content (one piece)
)
Only adjacent layers would need to be composited together. Drop shadows
would then paint immediately below the composited layer.
See also fantasai’s message on this topic.
- It seems likely the SVG
filters spec and the filter property would be able to
address these use cases, particularly if parametrized canned filters were
added for commonly desired effects and CSS targets were added e.g. as
described by roc.
- This topic will be further discussed with the SVGWG possibly on the
public-fx@w3.org
mailing list.
Full minutes
Media Queries for HTML5 Video
It is proposed to add media queries to <video> and then
to also define queries for the user’s special needs. These new media queries
will go into a new media queries module.
Full minutes
CSS2.1 Test Suite Status
Reviewed status of CSS2.1 test suite. Still on track wrt
roadmap.
fantasai has a rough coverage report, but is missing many of Microsoft’s tests
because they don’t have the right metadata. (Microsoft’s management is preventing
Arron from correcting the tests.)
Full minutes
Selectors
Full minutes
CSS3 Color
- Resolved: Drop section 3.1.1 from CSS3 Color.
- Resolved: Add
color-correction property with
values default and srgb where default
is UA-defined and srgb corrects untagged images to sRGB.
- See also David
Baron’s follow-up message proposing something different.
Full minutes
display: run-in
Worked through issues summarized in Bert’s email
- Resolved: Accepted proposal at the bottom of this email.
- Resolved: Add “The content of replaced elements is not considered in the
CSS rendering model.” to the definition of “replaced element”.
- Filed CSS2.1 Issue 142.
- Resolved: Run-ins inherit from their document parent,
not their sibling. It is explicitly undefined in 2.1 what happens with
parent/sibling ::first-lines and run-ins.
Full minutes
Size to Fit for text
Reviewed examples of copyfitting by changing the font size and various past
proposals for addressing some of the use cases. Intentions can be split into:
- Size each line of text individually until it fills the line box.
- Size up the entire paragraph as one unit until the longest line fills its
line box.
dbaron proposes a copyfit property to trigger these behaviors. An alternate
proposal is to incorporate this into text-justify.
Related behaviors were mentioned: specifically, triggering justification on
the last line only if it’s longer than a certain threshold; and specifying
a minimum length for the last line, which would trigger whole-paragraph
justification if the last line were not long enough.
Conclusion is to add some notes to css3-text and leave it for the next active
editor to deal with.
Full minutes
CSS3 Multicol
Full minutes
Grid, Flexbox, and Template Layout Interactions
- Discussed interaction of layout models.
- Discussed triggering fallback based on UA support.
- Resolved: Remove note about interaction between grid and tables.
- It’s not clear how to make progress on these drafts.
Full minutes
font-variant and font feature support in CSS
John Daggett proposes adding subproperties to font-variant
for allowing access to the more common OpenType features. font-variant
would become a shorthand for font-variant-ligatures,
font-variant-alternates, font-variant-caps,
font-variant-numeric, font-variant-position.
There some concern about fallback behavior for subscript and superscript
features, and winding up with either a complete loss of semantics or a
double-sub/superscript rendering.
John notes that OpenType has language-sensitive rendering, and proposes
allowing an explicit choice of typographic language different from the content
language.
There’s concern about exposing alternate glyphs from a generic mechanism
such as font-variant, because the choices are very font-specific. Proposals
include dealing with it in @font-face; and pairing the glyph set number with
the font name so that it only triggers on that font name.
Otherwise the WG is mostly in agreement and pressures jdaggett into putting
his proposal in the editor’s draft. 🙂
Full minutes
text-overflow: ellipsis
Resolved: Only horizontal overflow triggers for
text-overflow: ellipsis. Add a new keyword for handling ellipsis due to
vertical overflow (where the ellipsis appears on the last line only).
Discussed other issues with text-overflow, including:
- Interaction with
overflow, whether it prevents overflow, whether
it requires overflow: hidden, what happens with overflow: scroll,
how that makes sense with floats, etc.
- Where and how the ellipsis is drawn, how it interacts with
surrounding text
- What happens with overflowing blocks in the vertical ellipsis case
- Whether the ellipsis is an indication of content you can’t see or
content you can’t reach
- What happens when you scroll, does the ellipsis get drawn on the
other side, too? both sides?
- Interaction with bidi, whether the ellipsis causes logical clipping
in place of visual clipping
- Whether the behavior you want for ellipsizing text you can scroll to
is different from the behavior for ellipsizing text you can’t get to,
and other potential reasons for different behaviors
Apparently some of these questions were
resolved over lunch.
Full minutes
Transitions, Transforms, and Animations
- Apple would like a few sample tests in an appropriate format
to begin writing test suites. dbaron offered to help with that.
- Reviewed behavior of inherited properties and how inherited
transitions don’t trigger new transitions.
- Discussed effects of batched layout updates and flushing on
transitions, and the resulting unpredictability in behavior.
- Expecting another WD soon, then LC afterward for Transitions
and possibly for 2D Transformations; 3D Transforms and
Animations both need more work.
Full minutes
Administrative
- Reviewed our Last Call comments for
MathML for CSS.
Bert didn’t find much to comment on. Stretchable characters is something
we might need to look at in the future. John Daggett has some comments on
font variations vs. Unicode codepoints.
- Discussed modularization and profiles; the questions raised are all
answered by the Snapshot.
The only complaint was that it’s not visible enough, which will be solved
when the Snapshot enters CR.
- Next F2F scheduled for March 29-31 hosted by Apple in Cupertino.
Full minutes
Addendum
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: