Minutes Telecon 2015-04-22
- Everyone was encouraged to read the email from Florian outlining the different implementations and possible solutions for pre-wrap and white space processing. Discussion will continue on the mailing list and this will possibly become a F2F topic in May.
- Resolved: New Editor’s Draft for the next level of multi-column layout
- Resolved: Add just Florian as editor for this new editor’s draft for the time being
- The grammar for
media-condition will be changed to avoid requiring looking ahead by an unbounded amount.
- TabAtkins and Florian came up with the right behavior set for
@media not (unsupported-media-feature) vs @media not (unsupported+syntax), but it’s different from previous proposals, so they’ll contribute their new idea to the mailing list for further discussion/objections before hopefully getting resolution next week.
- TabAtkins and Florian came up with a proposal to address custom media queries before an
@import and will write the proposal for the mailing list.
- Resolved: Font MIME type registration is out-of-scope for CSSWG, FontsWG has a (partial) list, forwarding issue to them
- Resolved: Add that people may support larger Hebrew counters if they want
- Resolved: Re-publish Counter Styles CR with the above addition
- The addition of a
::flex-line pseudo-element might be good for a future level of flexbox, but not for the current level.
- Consensus was that renaming the global default was the least-bad option for dealing with the
cursor: default naming conflict and the name bikeshedding will happen on the mailing list.
Full Minutes
Minutes Telecon 2015-04-15
- Anyone planning on or interested in attending the CSS Houdini F2F in conjunction with the August F2F was asked to please contribute to the email thread planning dates.
- Resolved: Rename
fast and slow profiles to static and dynamic
- For now, conversation on the Selectors 4 matching algorithm will continue on the mailing list to allow more space to explain the complex algorithm and its relationship with the work being done on CSS Scoping.
- There was some disagreement as to if all
text-transform should be removed from a plain-text copy/paste or if there are some worth maintaining. People also disagreed on what behavior would be viewed as a bug by users. fantasai will reach out to the editing taskforce to get their feedback and use that to inform how the existing spec should be written and if there’s a need to create a spec to just address copy/paste issues.
- There was disagreement on the approach to and need for adopting user-select in CSS UI 4
- The
auto and none values for the appearance property in CSS UI 4 were agreed upon, but there was a lot of resistance to the button value. For now, Florian will move the button value to a note describing how the appearance property could later be extended if desired.
- Resolved: Accept
auto and none, do research on the rest.
Full Minutes
Minutes Telecon 2015-04-01
- The working group will request to meet on Monday and Tuesday during TPAC
- Resolved: New working draft of CSS 3 UI, accepting changes to
box-sizing
- Resolved: Then publish another working draft of CSS 3 UI.
- Resolved: Motion Path FPWD granted
- Resolved: Accept feedback coming from mailing-list as WG review of the WebVTT proposal
- A decision on the text change to Media Queries 4 will wait another week for Microsoft to continue reviewing.
- Discussion will also wait on changing required cursor image formats until next week to give Microsoft another week to review.
- Resolved: Add the
::marker { font-variant: tabular-nums; } rule to the default stylesheet
- Discussion of intrinsic sizes and multicolumn elements will continue on the mailing list and wait until next week when someone from Chrome is on the telecon.
- Resolved: Accept Myles’ proposal to make baseline of overflow non-visible inline blocks the higher of the actual baseline (at initial scroll position) and the margin-box bottom. Separately investigate whether to switch from margin-box bottom to padding-box bottom for sanity. (requries web-compat check)
Full Minutes
Minutes Telecon 2015-04-08
- There was disagreement as to if the specific order of state changes when loading fonts is needed to prevent bugs or if it’s an unnecessary step that slows performance. TabAtkins will gather more cases and the e-mails that led him to make the language more strict in order to further the conversation.
- Resolved: Change the appropriate sentence in Media Queries 4 to “User agents must re-evaluate media queries in response to changes in the user environment that they’re aware of”
- Resolved: Remove the timeout portions from the proposed font loading control spec.
- Resolved: Move Font Loading Control to the Font Loading spec.
- Resolved: We are recommending informatively
.cur support. Normatively must support PNG and SVG and saying should support animated formats too.
- Resolved: Accept fantasai’s proposal to add
text-combine-upright to ::marker.
Full Minutes
New Extended Units and Gradients Draft
The CSS Working Group is pleased to announce a new Editor’s Draft of CSS Expressive Generalizations and Gadgetry Level 1 (renaming suggestions welcome). This new module adds:
We are currently debating the publication of an FPWD. If you have comments, please contribute to the discussion on www-style!
Minutes Telecon 2015-03-25
- Everyone in the group was asked to respond to the e-mail from Bert regarding TPAC.
- There is a two week review period for the Round Displays document.
- Resolved: Publish Values and Units as CR
- Resolved: Publish Variables as CR
- The proposed cuts to what items are in Lists (available here) seemed sound, so the editors will make them and request publication once they’re done.
- Resolved: Publish Cascade Level 3 as CR
- Resolved: FPWD for Cascade Level 4
- Resolved: Publish Will Change as CR
- The box-sizing review period was extended for another week.
- Resolved: Create an ED for TabAtkins’ constructable stylesheets draft.
- Short name for now is cssom-construct
- Microsoft requested a week to review the proposal of changing ‘should’ to ‘must’ in the following sentence from Media Queries 3: “User agents should re-evaluate media queries in response to changes in the user environment”
- There were several different viewpoints on how to address page-specific properties outside of an
@page context, so discussion will continue on the mailing list.
Full Minutes
Minutes Sydney F2F Part II – 2015-02-09 PM: Sizing, Text, Writing Modes, Multi-line/Block-Ellipsis
Sizing
- Resolved: Add gregwhitworth as editor to Sizing
- Resolved: Auto margins assumed to be zero for intrinsic size computation
- The spec authors will work out a way to address the various ways percentages work.
Full Minutes || Spec Referenced
Text
- Resolved: Treat replaced elements as ideographic chars for line-breaking. Based on data, possible add an exception for
 .
- It was agreed that the Text spec says that control characters should show, but everyone should coordinate when the change is made so that no one browser gets inundated with bug reports.
- Resolved: Everyone will go coordinate on September being when control characters (Unicode class Cc) become visible. Implementations should aim to have it in their codebases by June, ready to go out in the next release after the coordination date.
Full Minutes || Spec Referenced
Writing Modes
- Resolved: Keep sideways-left, mark as at-risk, possibly punt if it threatens CR-exit.
- GregWhitworth will look at what options are valid for where writing-modes should propagate from – if it can be from
body or if it has to come from root or if there are other approaches entirely.
- Resolved:
writing-mode: vertical-lr on the rt based on parent’s ‘display’ & ‘ruby-position’
- Resolved: Drop the values if the SVGWG drops the values/properties, otherwise keep them.
Full Minutes || Spec Referenced
Multi-line/Block-Ellipsis
- Resolved: Replace region-fragment with ‘fragmentation’, written by Florian, determine where it belongs.
- Resolved: Split fragmentation values of ‘overflow’ into a separate property. Further develop this in the overflow module.
- Resolved:
region-break gets folded into the new property, too.
- Resolved: Florian added as editor to Overflow.
Full Minutes || Spec Referenced
Minutes Sydney F2F Part I – 2015-02-09 AM: CSS2.1 Issues, Font Loading API, Selectors, Text Level 4
CSS2.1 Issues
- Resolved: Change the 3rd bullet point of margin collapsing (CSS 2.1 section 8.3.1): Bottom margin of last inflow child and the bottom margin of parent, no longer collapse if the parent has non-zero min-height and the bottom margin of the last inflow child collapses with the top margin of the parent. Exact changes pending more testing.
- Resolved: Backport
@charset parsing rules from CSS3 to CSS2.1. dbaron to propose errata; zcorpan to update tests.
Full Minutes || Spec Referenced
Font Loading API
- There needs to be more use cases for
font-face-set being constructible.
- TabAtkins will re-order the process of observing the rejection and the queuing.
Full Minutes || Spec Referenced
Selectors
- Florian brought back some documented need for a selector that propagates input states to the corresponding label.
- Resolved: Florian to work on a proposal for a selector that propagates input states to the corresponding label and/or other associated elements.
- TabAtkins brought back his previous idea of allowing
:has() with some previous-child and -parent combinators in fast profile. There were still a lot of concerns about the performance implications. dbaron will test to see what the effects would be so that a more informed decision can be made.
- fantasai brought her proposal to add
::marker to pseudo-elements spec, takes properties from color module and fonts module (color, font-*, and opacity)
- Resolved: Add
::marker with font properties and color to pseudo-elements spec (and still plan to do more later in the lists spec).
Full Minutes || Spec Referenced
Text Level 4
- fantasai and astearns brought the CSS Text Level 4 document that they’d created to the group.
- For their
text-wrap: balance proposal, there was some concern about the inheritance behavior. Instead, they will work on creating wrap-inside, wrap-before, and wrap-after properties.
- The
white-space properties were well received, though it was thought that discard would be a better word than consume.
- Resolved: Make css-text-4 an editor’s draft (currently a different spec)
- Resolved: fantasai and astearns to edit
Full Minutes || Spec Referenced
Minutes Telecon 2015-03-18
- The
continue property for region-fragment received the most attention for bikeshedding. One issue with continue is that it is a verb when almost all property names have been nouns or adjectives. Some people were inclined to return the name to fragmentation but most of the group felt that would have no context outside of the working group. It was suggested that there was likely vocabulary for this concept and that users of programs like inDesign or PhotoShop would likely have some suggestions.
- There was also clarification on the purpose of having the
region-fragment properties defined outside the overflow context. It was agreed thought they are similar, they’re not the same and therefore should be separate.
- TabAtkins brought up that the current behavior of
all isn’t viewed as particularly accessible since it removes the :focus outline on an element. Consensus was the old default that was removed from the spec would fix the problem. The spec authors will go back and see if there are any reasons that default was removed that need to be addressed and re-introduce next week for formal resolution.
- The Microsoft team will look into if Microsoft is open to submitting
.cur and .ico to the web consortium.
- Resolved: Add a note saying
.cur and .ico are the standards and they will be expected in new products. It’s an informative note. It will be up to the person writing the note as to what exactly goes inside.
- There were no objections to mandating PNG as a supported format of the
image CSS value, as well as SVG if the implementation supports SVG and saying for cursor that all non animated formats supported for image MUST be supported in cursor, and that all animated formats supported in image SHOULD be supported in cursor. However, Microsoft asked for a week to review, so formal resolution will be asked for on next week’s call.
- Most people seemed to agree that we should overflow the same way we’re doing other logical properties and whichever is declared later wins the cascade, but conversation will continue on the mailing list to suss out any added complications.
- For now, work on
trailing-spaces will be in CSS Text Level 4
Full Minutes
Minutes Telecon 2015-03-11
- Resolved: Don’t add a property to hide scrollbars at this time.
- Florian brought up the two different allowed implementations of pre-wrap in the CSS Text spec and his belief that it’s confusing to have two different behaviors and that neither of the spec’ed behaviors may meet author expectations. Everyone spent time with the examples and comparing them to text editors and word processing software to determine if there really is an expected behavior. None of the implementors had an interest in changing their version and the group wasn’t convinced this is necessary given that most editing on the web is done with custom code.
- Resolved: Add the
trailing-spaces value to text-decoration-skip.
- It was agreed that, though the proposal to create special word-break rules for Korean (available here) was possible, it wasn’t necessary as feedback from Koreans has been that the current default is acceptable behavior.
Full Minutes
![[Photo: group photo of the CSS working group in Lyon, France]](/web/20150426100623im_/http://www.w3.org/Style/CSS/csswg-2010.jpg)
Contact: