Minutes Telecon 2016-10-26
- Resolved: Rich text copy/paste is undefined in Text Level 3.
- Originally the group resolved that plain text copied to the clipboard must (or should) not be affected by text-transform in Text Level 3, but there was an objection from koji so the group will revisit next week.
- dbaron requested more time to look at absolutely positioned boxes in inline relatives being interoperable, so discussion will continue on github
- Resolved: 0px width float that is next to a line box does count as shortening a line box
- Resolved: Change “
baseline|last-baseline” to “[ first | last ]? baseline“
- Resolved: Match webkit/blink behavior for initial value of
mask-repeat and mask-position
- Resolved: ChrisL, TabAtkins, and shane as editors for Masking spec.
- Resolved: Add hoisting of listed properties other than overflow.
Full Minutes
Minutes Telecon 2016-10-19
- Most of the call was dedicated to discussing how to and if we should define the effect of text-transform on copy/paste (CSS Text Issue #108)
- As a general principle there was a desire to have copy/paste match what users are seeing when they copy, however several people believed that the actual use cases in this case overrode the principle.
- There were four main use cases that the group uncovered:
- Turning a heading into all caps
- Turning a first line into all caps
- Turning acronyms into small case when they’re all caps in the source
- A ruby use case around ruby where in Japanese “しゃ” reads “sha”, and “しや” reads “shiya”. If that’s your ruby, there can be a text-transform to turn one into the other, because at small sizes it is hard to tell apart and smaller letters are hard to read. But out of context, you don’t want to change the pronunciation.
- Though mostly in the above use cases preserving the text-transform would be the worse user experience, there are times where you would expect preservation
- Consistency between inner text, paste to plain text, and range to string was another thing to be considered in the decision.
- In a straw poll the group was about evenly split between copied plain text ignoring text-transform or leaving it up to UA for UX decision.
- Group members will look through browser bugs to try and determine user expectations.
- There was also a desire to conduct a through user survey, though no one was tasked with creating one.
- Resolved: White space property is applied to plain text paste output.
- Resolved: Don’t define interaction between hanging punctuation and kerning and leave it up to UA to decide how to adjust.
- fantasai will write up her proposal to address hanging-punctuation scrollable overflow for review as there wasn’t time on the call.
Full Minutes
Minutes Telecon 2016-10-12
- There is a move to finalize the April/Japan dates so anyone with conflicts should put them on the list.
- Resolved: Keep our should/must/may testing in place and put it into the web documentation.
- Resolved: We start the list of steps given at here keeping the test harness in working order as each step is done. We let gsnedders and those doing the work decide when to move steps.
- Resolved: Remove CSS grammar section in CSS 2.2 and have a pointer to CSS syntax.
- fantasai will write up proposed spec text for a definition of line-height calculations which will describe Blink and Gecko do.
- The minimum and preferred width of a multicol definition is in Syntax spec.
- Positioning boxes with
float:left; width:0px; will wait until next week to give people time to review the github comments.
Full Minutes
Minutes Telecon 2016-10-05
- TabAtkins summarized his proposal for creating overflow-gap: auto | stable | always. Rossen asked if making these optional values for auto on the overflow property would make more sense as it would avoid creating another property. This was considered and a few people originally expressed no preference, but the more it was discussed the more people felt this was the wrong approach. There still wasn’t agreement as to if this new property should be a longhand of the overflow: auto or if it should be completely separate.
- Resolved: We will work on a solution to accommodate issue 92
- Resolved: The normal value of align-self and justify-self preserves aspect of image but stretch causes it to stretch to fit containing block. Default value continues to be normal.
- Resolved: Accept the proposal for Text issue 96 (for linebreak transformation rules ambiguous characters are narrow unless it’s Chinese or Japanese or Yi in which case they are wide)
- Resolved: Make tab size animatable
- Resolved: Make tab size a number
- Resolved: Have tab-size account for letter spacing and word spacing
- Resolved: No change to the spec for Text issue 110
- Resolved: Capitalize only title cases lower case things, not upper case letters
- Resolved: text-align-last: justify will compute to center for CJK
Full Minutes
Minutes Telecon 2016-09-14
- Resolved: Don’t have the computed value dependency.
- The conversation around url parsing contradiction between 2.1 and Syntax needed TabAtkins, dbaron, and Bert and none of them were available today so it was postponed.
- There was a strong leaning toward using the metrics of the first available font for line height calculations. Rossen wanted to confirm there was minimal compat implications so he asked that the formal resolution wait until TPAC.
- Resolved: Don’t disallow 0 width tab size.
Full Minutes
Minutes Telecon 2016-09-07
- There wasn’t interest at this time in creating a new pseudo-element which would apply offset-path to specify the shape of progress element. Exploration should focus around custom elements and any problems in the implementation of SVG that is causing it not to be performant.
- The scroll-snap-padding vs snap-padding topic will be added to the TPAC agenda.
- Resolved: Keep the name grid-gap (Grid issue #19).
- astearns filed an issue to add an example documenting the difference between the space in grid-gap and a traditional gutter.
- Resolved: Have percentages in grid-gap behave as percentages in tracks (Grid issue #20).
- Resolved: Keep auto-flow in the grid shorthand (Grid issue #24).
- Mats wasn’t on the call, so the discussion to reconsider the block-axis baseline decision will continue on the mailing list or github.
- Resolved: Have grid and flexbox keep saying that empty boxes have no baseline and they’re synthesized with bottom border edge.
- There was general agreement to accept the proposal that layout containment should make an element containing block for absolute/fixed positioned elements, but TabAtkins needed to check with the implementor first.
Full Minutes
Minutes Telecon 2016-08-31
- A reminder that the registration for TPAC closes and registration fees go up soon.
- gregwhitworth will likely be the one to speak at the dev meet-up and he’ll cover topics around Grid.
- The behavior of what we do when there isn’t a natural baseline is inconsistent both between specs and between implementations.
- The proposals of what to standardize around were:
- Make boxes without a natural baseline and boxes establishing an orthogonal flow synthesize a baseline.
- Base this synthesized baseline on the margin box edges
- Base this synthesized baseline on some other box edge
- Make boxes without a natural baseline and boxes establishing an orthogonal flow use start alignment instead of trying to synthesize a baseline.
- Something else.
- Resolved: Accept option A2 with the modification that we’re talking about the border box.
- Several people had reservations on adding a new syntax (+#) to make it easier to read a legacy behavior that could still be written as [ + ]#
- Resolved: Don’t add any new syntax, just add a note explaining it.
- Resolved: Adopt the Gecko/Edge behavior and specify that
.offsetParent is based on the nearest abspos containing block or table cell
- Resolved: Accept the proposal (Proposal: Make the device-width/etc MQs use the same concepts as CSSOM is using for returning device dimensions.)
- The group began discussing adding device-pixel-ratio but didn’t have time to reach a decision
- One opinion was that it shouldn’t be added in order to encourage people to use ‘resolution’
- The other opinion was because ‘-webkit-device-pixel-ratio’ didn’t obviously translate to ‘resolution’, ‘device-pixel-ratio’ should be added to aid authors.
- Right as conversation was wrapping up, smfr asked a question about ‘window.devicePixelRatio’ which he was asked to post on github to allow further conversation.
Full Minutes
Minutes Telecon 2016-08-24
- Resolved: Add text to CSS OM and to Logical Properties as proposed (logical properties take their CSS OM behaviors from their physical equivalents)
- Rossen requested a week to review the request to add
number-optional-number type.
- Florian will reach out to the editing task force for feedback on
user-select: none and selectionchange event
- Ambiguities in handling
ur was deferred to TPAC.
- Algorithm of
Element.offsetParent was deferred to next week.
- astearns will reach out to the Internationalization group for feedback on segment break transformation rules for East Asian width property of A.
- Florian will investigate having two
user-select properties, one of which is a shorthand for the other. If that seems to work he’ll also investigate if there’s a reason to expose the longhands to the author.
Full Minutes
Minutes Telecon 2016-08-17
- Rossen asked group members to ensure that the proposed dates for January F2F are clear so he can finalize plans.
- Resolved: Remove baseline from the block-axis as a way to align
- Resolved: Stretch items the same way we do for non-replaced
- There was some concern that content re-stabilizing not being defined in the Scroll Snap spec will prevent testing.
- Resolved: Accept the changes proposed here. Make sure that if the UA evaluates and thinks it shouldn’t re-snap it’s not required to do so, potentially by merging the first and last sentences in the paragraph.
- Though everyone agreed on the problem space, there were concerns about the proposal to turn scroll-snap-padding into snap-padding. Some of the concerns raised were:
- The proposal wasn’t intuitive for authors.
- The proposal was trying to solve too many use cases to be effective.
- The discussion will continue on the github issue to continue resolving concerns. fantasai emphasized that this needed to happen quickly to keep this from holding up the spec.
- Resolved: Close this topic as no issue.
Full Minutes
Minutes Telecon 2016-08-10
- Resolved: Remove this section from the current level 4 draft and move the work to Houdini
- Rossen was actioned to open an issue on Box 3 for Houdini
- Resolved: Change the
meta viewport text to normative and add two issues. One to test if the description matches reality. Second is while we spec with the same mechanism there may be differences as we tease out compat.
- Resolved: Make display into a short hand and add an issue on naming for the long hands.
- Florian brought his proposal to create
overflow-style: auto|auto-hide|overlay to allow authors more control over scrollbars while balancing out the desires of implementors to control their scrollbars.
- There was a feeling that this was still too problematic and auto-hide and overlay should be merged into one value that behaves depending on the platform behavior.
- The group was heading in the direction of creating value that reserves the same amount of space whether the scrollbar is shown or not in order to solve the re-layout problem, but ran out of time so conversation will continue on github.
Full Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: