Paris F2F August 2015

Dael Jackson edited this page Oct 17, 2015 · 9 revisions

Meeting Minutes

Friday, 28 August:

  • Part I Script API, Elephants in the Room
  • Part II CSSOM2
  • Part III Properties and Values, Generalized Cascading Sheets
  • Part IV Font Metrics, Lineboxes, and Their Interaction, Custom Layouts
  • Part V DeadRange, Building Blocks for Pagination, Spec Management, Issue Tracking on the Mailing List vs GitHub

Saturday, 29 August:

  • Part I Next F2F Meeting, Custom Paint
  • Part II Async Style
  • Part III Scroll Customization, Rendering Pipeline, Passing Data Between Custom Phases
  • Part IV Prioritization of Effort

Location

Mozilla Paris, 16bis Boulevard Montmartre, 75009 Paris, France

See Mozilla Paris wiki for important directions on finding and entering the space

Participants

(alphabetical by family name)

Name Arrival Departure Hotel Flight info and notes
Rossen Atanassov CSSWG F2F ?? ?? ??
Tab Atkins
L. David Baron ?? ?? Apartment ??
Bert 24 Aug 29 Aug Vivienne train (Gare de Lyon) A: 21:41 / D: 18:19
Rick Byers 26 Aug 30 Aug Lyric hotel AC886 / AC887
Tantek Çelik 2015-08-22 2015-08-29 apartment UA0990 / UA0991
Dave Cramer CSSWG F2F 30 Aug Hotel Peletier-Haussmann UA 987 / UA 986
Simon Fraser ?? ?? ??
Dael Jackson CSSWG F2F 30 Aug Apt Share AA754 / AA755
Ian Kilpatrick ?? ?? ??
Chris Lilley CSSWG f2f 30 Aug Hôtel Eugène en Ville AF6207/ AF6248
Peter Linss CSSWG F2F ?? ?? ??
Simon Pieters CSSWG f2f August 30 Vivienne AF1263 / AF1262 (CDG)
Matt Rakow CSSWG f2f ?? ?? ??
Florian Rivoal CSSWG f2f ?? ?? ??
Simon Sapin home
Dirk Schulze ?? ?? ?? ??
Elliott Sprehn ?? ?? ?? ??
Alan Stearns 21 Aug 30 Aug Apt ??
Shane Stephens ?? ?? ?? ??
Ojan Vafai ?? ?? ?? ??
Lea Verou 21/8 30/8 Hôtel Eugène en Ville AF1441
Jet Villegas ?? ?? ?? ??
Ian Vollick 23 Aug 30 Aug AirBnB AC880 / AC887
Greg Whitworth CSSWG f2f ?? ?? ??
Johannes Wilm ?? ?? ?? ??
Steve Zilles 8/24 8/31 Appartment on Ile de Cite

Observers:

  • François Remy
  • Ojan Vafai
  • Elliot Sprehn
  • Bruce Lawson
  • Robert Flack

Agenda

Friday

am

  • scripts API - add to list of Houdini specs? Discussion of open questions. (ian)
  • Elephants in the room (gregwhitworth) - The apply model for custom properties means that you can’t have two custom properties that apply to the same used values coexisting on the same element. Is being restrictive and relying on user shims the right way to get somewhat future-proofed composition?
  • CSSOM 2.0 - should this be a separate spec or rolled into Properties & Values? (shans)

pm

  • Properties & Values - status of ED, discussion of open questions, are we ready for FPWD?
  • Generalized Cascading Sheets (Lea)
  • Custom Layout - summary of current status (ian, greg)
  • Font metrics, lineboxes, their interaction (chris) (jdaggett dialin, friday after 2pm)
  • Non-metric information on a Font object (e.g. OpenType features, Unicode coverage) (chris) (jdaggett dialin, friday after 2pm)
  • Deadrange (or whatever we call it) (chris)
  • Building blocks for pagination (dauwhe)
  • Spec and discussions management (shans)

Saturday

am

  • Next f2f meetings
  • Custom Paint - status of ED, discussion of open questions, are we ready for FPWD?
  • Async Style (compositor worker) - status update and name bikeshedding (vollick)
  • scroll customization (rbyers/vollick)

pm

  • rendering pipeline (ojan)
  • Passing data between custom phases (style, layout, paint). Also do want namespacing of that data? (shans)
  • some tasks need info from outside the element (e.g. nearest ancestor scroller, margin information from descendants, etc.) - how do we incorporate feeding this information to the elements that need it and what limits should be emplaced? (shans)
  • prioritization of effort - we think that Custom Paint and Properties & Values are good areas to prioritize because they’re simpler than other areas and can independently provide value (shans, ian, tab)

Proposed Agenda Topics

  • Building blocks for pagination (dauwhe)
  • Elephants in the room (gregwhitworth) - The apply model for custom properties means that you can’t have two custom properties that apply to the same used values coexisting on the same element. Is being restrictive and relying on user shims the right way to get somewhat future-proofed composition?
  • Generalized Cascading Sheets (Lea)
  • prioritization of effort - we think that Custom Paint and Properties & Values are good areas to prioritize because they’re simpler than other areas and can independently provide value (shans, ian, tab) Custom Paint - status of ED, discussion of open questions, are we ready for FPWD?
  • Properties & Values - status of ED, discussion of open questions, are we ready for FPWD?
  • CSSOM 2.0 - should this be a separate spec or rolled into Properties & Values? (shans)
  • scripts API - add to list of Houdini specs? Discussion of open questions. (ian)
  • Async Style (compositor worker) - status update and name bikeshedding (vollick)
  • Custom Layout - summary of current status (ian, greg)
  • Passing data between custom phases (style, layout, paint). Also do want namespacing of that data? (shans)
  • some tasks need info from outside the element (e.g. nearest ancestor scroller, margin information from descendants, etc.) - how do we incorporate feeding this information to the elements that need it and what limits should be emplaced? (shans)
  • Deadrange (or whatever we call it) (chris)
  • Font metrics, lineboxes, their interaction (chris) (jdaggett dialin, friday after 2pm)
  • Non-metric information on a Font object (e.g. OpenType features, Unicode coverage) (chris) (jdaggett dialin, friday after 2pm)
  • Which wiki should we use? (shans)