A Coruña F2F January 2020

Logistics / Registration

• Host: Igalia
• Location: Igalia, A Coruña, Galicia, Spain
• Dates: Wednesday-Friday, January 22-24, 2020
• Times: Each day will be 10:00 to 19:00 (10am to 7pm) (resolution)
• Lunch: In the office all days 14:00-15:00
• Participants / Registration
• See also Developers Meetup

Agenda

• Also see csswg-drafts issues and fxtf-drafts issues.
• Display Level 4: Display Noneness of Various Kinds (LINK PLEASE???)

Schedule

Wednesday Morning

• V&U issues:
  • round()/floor()/ceil()/mod() (tab)
  • sign() (tab)
  • the rest of the JS math functions (tab)
  • require double precision for calculation trees (tab)
  • vhc unit, or other ways to address the shortcomings of viewport units in mobile cases (fantasai, jensimmons)

Wednesday Afternoon

• Finalize dates for summer meeting
• Align
  • vertical-align in orthogonal table cells - side prep discussion with fremy, fantasai, florian, Tab, then WG discussion
  • [css-align] Special case for inline-block+scroll-container elements needs to cover inline blocks that **contain** scroll containers
  • [css-align] Does stretch work when width/height only behaves as auto?
  • [css-align] Center alignment can be improved
  • [css-align-3] Punt baseline-alignment to level 4
  • All remaining issues, go to CR?
• Scroll Snap
  • [css-scroll-snap-1] Snapping on both axes allows re-snap after layout to choose inconsistent snap targets
  • [css-scroll-snap-1] re-snapping after layout with animations
  • [css-scroll-snap-1] Snap area trapping behavior of non scrollable elements
  • [css-scroll-anchoring] [css-scroll-snap] What’s the optimal viewing rect on the root scroller?
  • [css-scroll-snap-1] Clarify which writing-mode is used for scroll-snap-align, scroll container or snap position element?
• CSS Backgrounds Level 3
  • [css-backgrounds] Number of layers in getComputedStyle results
  • [css-backgrounds-3] background-size with “<length-percentage> auto” and gradient image is not interoperably implemented
  • Remaining issues: do we need to do anything with them, or close them out?

• Support pathLength via CSS — request from SVG WG for CSS WG to sign off on a new geometry property (pending review of implementability, as discussed in the issue) (tab, others?)

• [css-cascade] Custom cascade origins (jensimmons, perhaps with Miriam Suzanne calling in)

Thursday Morning

• Multicol
  • [css-multicol] Defining what happens with column-fill in unconstrained containers for continuous and fragmented contexts
  • Organizing cross-spec multicol tests
• [css-grid-2] Masonry layout
• [css-sizing-3] Why was min-content, etc. redefined to do nothing in the block axis?
• Rhythm, line-grid and tests

• [css-transforms-1] ‘view-box’ definition doesn’t make sense
• [css-overflow-4] scrollbar-gutter is too complex
• [css-env] safe-area-insets-* for embedded document by iframe
• [web-animations-1][css-ui] Animating user-interaction controls

• TRIAGE ALL THE SPECS - What needs publishing? What’s blocked? What has outstanding edits needed? Let’s get things up-to-date.
  • FPWD!!!!! resize-observer, mediaqueries-5, css-transforms-2, css-conditional-4, css-highlight-api-1, css-color-5, anything else?

Thursday Afternoon

• Constructable Style Sheets (heycam)
  • CSSStyleSheetInit dictionary may have unintended usage
  • Defined location/href of Constructed Stylesheets
  • Should adoptedStyleSheets be ordered before other style sheets in the tree, instead of after?
  • Instead of assignable FrozenArray, use add / remove

• Color
  • Serialization/OM issues
    • [css-color-4][cssom] Overlap between the definition of resolving color values and serializing <color> component values.
    • [css-color] Serializing color() values
    • [css-color][cssom] Serialization of specified <color> values
    • [css-color-4] Computed/used value of color doesn’t specify how to serialize.
    • [cssom][css-color] Need clarification on serialization of `rgb` & `rgba` in light of css-color-4’s syntax changes

• Fonts
  • [css-fonts] The Cursive = Chinese Kaiti equivalent
  • Add ISO 15924 script codes to unicode-range

• [dialog element] <dialog> positioning should be describable in CSS (smfr would like to call in)
• [css-om-view] How does scrolling relate to mouseWheel event propagation? (smfr would like to call in)

• Motion
  • Decide on final approach for merging all uses of shapes (amelia, tab, krit?)
  • [motion-1] The definition of “containing box” for ray() function
• Fonts for afternoon callers
  • [css-fonts-4] font-display: optional without relayout (tabatkins, chrishtr)

Friday Morning

• [css-fonts] limit local fonts to those selected by users in browser settings Pete Snyder may call in
• Text part 1
  • [css-text-decor] Clarifying skip-ink:auto behavior in relation to CJK text
  • [css-ruby-1] ruby overhang control
  • [css-text] Line breaking for ambiguous characters; e.g., U+2010, U+2013
• Inline 3: leading-trim etc.
  • higher priority
    • make text of leading-trim interoperable?
    • apply leading-trim to inlines?
    • initial-letter feedback from implementation
• Text part 2
  • [css-text] Atomic inlines being equivalent to ID for line breaking is not web-compatible
  • [css-text] Writing System prose is currently unimplementable on ICU

Friday Afternoon

• [css-color-adjust] Used color-scheme should affect the root element color, not initial color
• idea to resolve the mod() conflict (tab)
• Text part 3
  • [css-text] Line breaking for ambiguous characters; e.g., U+2010, U+2013
  • [css-text] treat all-neutral lines same as empty ones for plaintext alignment
  • [css-text] Hanging spaces can’t be scrollable overflow
  • [css-text] Remove collapsible line breaks adjacent to word separators
  • [css-text] https://github.com/w3c/csswg-drafts/issues/337
• Inline 3: leading-trim etc.
  • lower priority
    • vertical-align: middle in vertical text
    • leading-trim overflow: ink or scrollable?
    • leading-trim vs descendant inlines
    • resolved value of line-height - follow-up
    • initial-letter zero sink?

• 5PM [css-sizing] intrinsic-size lost the thread
• Fonts for afternoon callers part 2?
  • [css-fonts-4] font-display: optional without relayout (tabatkins, chrishtr)

Constraints

* Please schedule motion topics in AM (Eric will dial in)

* Dialog positioning, mouseWheel (and maybe vhc unit) at a US-friendly time for smfr

* cbiesinger has to leave a bit early on Friday, please schedule intrinsic size before that

* chrishtr will be able to dial in at 4:45pm or later on Friday for the intrinsic size discussion