Minutes Telecon 2015-11-11
- Resolved: Publish new WD for Device Adaptation.
- MaRakow, TabAtkins, and fantasai got a chance to speak and come to a consensus on how to fold the change in approach to snap points into the existing WD. This change-over will occur over the next several weeks.
- Once the new version is ready, the group will publish a last version of the old approach right before publishing the new approach, both as WDs. This allows a good record of how the spec progressed without sending the wrong signal about the direction of the spec to implementors.
- There was support for the proposal of 2D rotation transform function for polar coordinates, though it was thought they should be named polar-angle and reverse-polar-angle or polar-reverse-angle to explicitly link them with the polar properties. An additional question was raised about how it would interact with animation, but it was decided that that interaction was dependent on if it’s a computed value or a specified value.
- Resolved: Accept the proposal for a 2D rotation transform function for polar coordinates and make it clear if it’s a computed value or a specified value and make a note on the implication of that decision on animations.
- Resolved: Accept the polar-origin changes.
- The polar-origin proposal lead to a conversation about adding a center value to fixed and absolute positioning. The conversation will continue on the mailing list. However, if this change ends up happening, it may negate the need for polar-origin.
- There wasn’t telecon time for a full conversation on the mailing list conversations around page floats, but it was suggested that the interested parties get on a separate call to work through the mailing list topics. johanneswilm and Florian will work on organizing a call.
- Resolved: Line-grid will restart in the case of orthogonal flows between parent and child.
- Resolved: Add JIS-B4 and JIS-B5 to paged media.
- Florian will summarize other page sizes that could be added to the spec in an e-mail.
Full Minutes
Minutes Telecon 2015-10-21
- Anyone with items to discuss at TPAC is asked to please put them on the agenda ASAP.
- The Japanese Industry meet-up is still short on details, but Florian is speaking with them tomorrow, so hopefully the details are forthcoming.
- Jihye brought her proposal for a polar orientation property to the working group for their feedback. The group felt that the effects of the property could be achieved by the rotate property either as it stands or with additional keywords aimed at handling polar cases easier.
- Florian also expressed a concern that the proposed behaviors in polar orientation may not be enough to solve common use cases and requested an issue be added that there may need to be more keywords.
- Resolved: Publish CR for Writing Modes.
- Everyone agreed that the spec text for
word-break: break-all needed re-working, though there wasn’t a clear decision on the right direction. Koji and fantasai will come up with a proposed change to the spec referencing UAX14 and see what the group thinks of it.
- The working group is in favor of any changes to the default TR stylesheet that brings it closer to the stylesheet that the CSS working group is already using.
- The Will Change and Variables specs have received resolutions for publication, but have not actually been published.
- Bert will look into where these specs are in the pipeline.
- There are also specs with last publication date of more than 6 months ago. This issue will be discussed at TPAC.
- Resolved: Publish Cascade 4 as CR
Full Minutes
Minutes Telecon 2015-10-07
- Everyone was reminded to add items to the wiki for TPAC conversation.
- The Houdini task force will meet on the Thursday of TPAC. They may also hold a breakout session on the plenary day depending on if there are proposals for specific topics and/or meet on Friday if they need more time.
- Resolved: Adopt Section 3 of the Snapshot.
- Resolved: Publish Snapshot.
- Florian and fantasai agreed that the spec should say something along the lines of the UA must provide a smart behavior and should match platform with ‘be smart’ defined as ‘provide a good experience’. They will work on solidifying the wording.
- Resolved: In
pre-wrap, disallow wrapping before the first space.
- The right people weren’t on the call for a resolution regarding the behavior of
scrollLeft in RTL or vertical-rl mode, but webkit plans to change to be more consistent with the proposal.
- Using
start and end for positioning needs a consistent decision between all 2d positioning, not just for floats. It was added to the TPAC agenda.
- There was a strong feeling from Rossen that there wasn’t a need to make Grid and Flexbox consistent in their
auto value for alignment. The spec will be left as-is for now and fantasai will look for more feedback, especially from authors.
- Resolved: Issue #19 for Framentation is out of scope.
- Resolved: Take Roc’s suggested wording about keeping inline blocks non-fragmented (Issue #21 for Framentation)
- Resolved: Each fragmentainer must contain at least some content or fragment of content.
- Issue #24 for Framentation, adding
force to the page, column, and region keywords, still needs to be discussed either on a call or at TPAC.
Full Minutes
Minutes Telecon 2015-09-30
- Tuesday afternoon is the best option for a joint meeting with WebApps during TPAC.
- The Sydney F2F dates are January 30th and 31st for Houdini, February 1st to 3rd for CSS, February 4th to 6th for SVG.
- Jihye reviewed her proposal for
polar-anchor (available here). Generally there was agreement that this was useful and the right direction for this property. There was concern that the property could still cause overflow even though this was designed to prevent it. auto seemed like it could be what prevents the overflow, but was under-specified in this proposal and needed to be fleshed out more.
- Resolved: Add
polar-anchor with issues for better specifying auto and percentages.
- dbaron has made the edits to Animations to revert the change to
animation-timing-function.
- TabAtkins will make the proposed changes to the computed values of
translate, rotate, and scale (available here) to the Transforms spec.
- The group will let fantasai and Richard Ishida come to a solution regarding
ruby-merge.
- There was a proposal to add
:focus-ring to allow authors to only style the focus ring when the browser would normally trigger a focus ring as a way to narrow-down the more generic :focus pseudo-class. There were concerns that this would have negative accessibility implications, but it was argued those implications exist within :focus and should be addressed there- this makes the problem no worse than what already exists. The name seemed problematic to some people so it may need bikeshedding later.
- Resolved: Add
:focus-ring to Selectors 4 or 5.
- The example in this e-mail the stacking context would happen at the 49% keyframe.
Full Minutes
Minutes Telecon 2015-09-23
- Resolved: Extend
resize to img, object, iframe, canvas, video, svg in level 4 of CSS UI.
- Resolved: Add normative prose in level 3 of CSS UI that a UI may extend
resize as described for level 4.
- Anyone involved in Houdini was asked to put their name on the wiki saying if they are available to attend a meeting at TPAC and, if so, what days they would be available.
- Resolved: Describe
sideways as what sideways-right used to do. State that for legacy compat UA may support sideways-right value that does the same thing and computes to sideways.
- Resolved: Moving a float to the next fragmentainer does not move in-flow content that comes after the float. (However, per CSS2.1, subsequent floats do move down.)
- Resolved: Clarify in Backgrounds level 3 you can’t make the border boundry solid black.
- The group needs to hear from TabAtkins about Chrome’s current timeline for the change in control characters. Depending on what TabAtkins says, if some browsers are still planning on releasing the change in December, the publicity campaign for this breaking change needs to begin ASAP for the web developers to have time to react.
- Spec authors were reminded that they need to post notifications to www-style when their spec is published (full publication rules are here).
Full Minutes
First Public Working Draft of CSS Basic User Interface Module Level 4
The CSS Working Group has published the First Public Working Draft of CSS Basic User Interface Module Level 4. This specification describes user interface related properties and values to style HTML and XML (including XHTML).
Changes since level 3 of the same document include specification of the user-select and appearance properties, the addition of a fade value to the text-overflow property, and additional controls over the text insertion caret.
Significant changes since level 3 are listed in the change section.
As always, please send feedback to the (archived) public mailing list www-style@w3.org
with the spec code ([css-ui-4]) and your comment topic in the subject line.
(Alternatively, you can email the editors and ask them to forward your comment.)
First Public Working Draft of Text Level 4
The CSS Working Group has published a First Public Working Draft of CSS Text Module Level 4. This module defines additional properties for text manipulation.
The main work on CSS Text is still being done in Level 3. So until that work stabilizes, CSS Text Level 4 is a diff spec containing only new and/or deferred material. This includes:
- A shorthand version of white-space property that expands to new properties controlling whitespace collapsing and trimming.
- New properties for controlling line breaks, including forced line breaks, balancing line lengths, and hints for where to avoid line breaks where possible.
- Hyphenation properties, a character-based text-align value, and the text-spacing property deferred from the last module level.
We’re looking for review on all aspects of the draft.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-text-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 Inline Layout Updated
The CSS Working Group has published an updated Working Draft of CSS Inline Layout Module Level 3. This module covers inline vertical alignment and special typographic effects
for initial letters, such as drop caps.
Changes since the previous Working Draft include:
We’re actively looking for review on all aspects of the draft, and in particular need help with handling non-Western scripts.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-inline]) 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 Layout Level 1 Updated
The CSS Working Group has published an updated Working Draft of CSS Grid Layout Level 1. This module defines a new type of layout manager, the grid, which makes it extremely easy to specify complex, responsive 2-dimensional layouts for a page or components.
The editors consider this draft to be the final design draft. There are a few open issues left, but these are mostly fixes and clarifications to the algorithms–the main one of which is ensuring the flexbox and grid flexing and fragmentation algorithms are in sync. There’s also one on visibility: collapse, which might be nice to solve, but might get pushed to Level 2. We will be updating the spec as we work through these, but don’t expect to make any significant changes to any existing features–unless someone sends a comment that requires such a change.
Your feedback is still welcome on the featureset and syntax. However because we’re hoping to prepare the final draft the week after TPAC, we would greatly prefer to receive said comments in time for discussion at the the CSSWG F2F–which begins on the 25th of October 2015.
We are looking especially for
- Feedback on anything you think is badly designed.
- Suggestions of use cases that are important to consider.
- Help with examples, figures, and making the spec generally more readable and understandable.
Changes since the last Working Draft are listed in the Changes section.
As always, please send feedback to the (archived) public mailing list www-style@w3.org with the spec code ([css-grid-layout]) and your comment topic in the subject line. Alternatively, you can email one of the editors and ask them to forward your comment, post something on your own blog and send us a link, or leave a comment here.
Minutes Telecon 2015-09-16
- There were several announcements regarding TPAC
- Everyone was requested to add items to the TPAC agenda so that scheduling can be handled in advance.
- Anyone planning on attending the Japanese Industry Meet-Up on the Sunday before TPAC was asked to please add their name to the wiki as well as any topics they’d like discussed. The start time and agenda will be announced shortly after a venue is decided upon.
- Lastly, anyone looking to attend the Monday evening developer meet-up at TPAC was reminded to sign up.
- Apple and Microsoft are still reviewing the prefixing policy language in the Snapshot 2015 so it couldn’t be finalized. Apple had some preliminary feedback that lead to further conversation about the word ‘unstable’ in section 3.2.3. Market Pressure and De Facto Standards.
- fantasai will further clarify the word ‘unstable’ and perhaps use an alternate word.
- The feedback also lead to a conversation about doing a better job making the case as to why the prefix policy change is good for implementors.
- Florian will write up a note with the rational which he summarized in the call by saying: “vendors can remove the prefixed version once the bugs are ironed out because there will be no risk to compat by removing the prefix because everyone also used the unprefixed version.”
- Resolved: Replaced sizing remains physical in Writing Modes. Add an appendix about the consideration of the security and privacy concerns.
- The authors of Writing Modes plan to ask for a new CR publication as soon as next week so if there are any outstanding issues, please add them now.
- Resolved: Add the form feed character (U+000C) and make sure all CSS specs align on the definition of white space.
- The group agreed that they wanted cases like Florian’s to be able to use a prefixed property in a spec example for what behavior should look like when implemented however the ability to do this is a W3C level decision so plh will discuss it with the appropriate parties.
Full Minutes
![[Photo: group photo of the CSS working group in Lyon, France]](/web/20151113175807im_/https://www.w3.org/Style/CSS/csswg-2010.jpg)
Contact: