Minutes Seattle F2F Part IV: 2014-01-28 PM – Fragmentation, Flexbox, Styling, Serialization of Shapes, Regions
Fragmentation
- Extensively discussed element/box/fragment distinction.
- Resolved: Use the terminology “element”, “box”, and “fragment”
- Resolved: Put fantasai’s explanation (see full minutes for explanation) of element/box/fragment distinction in Display and Fragmentation.
- Resolved: Don’t use “element”, “box”, or “fragment” in new terms that aren’t elements, boxes, or fragments. Where possible, convert old terminology accordingly as well.
- Resolved:
border-radius
should get sliced across fragments, maintaining unfragmented geometry.
- Resolved: Overflow that breaks into a new fragment container does so by forcing its container to generate an additional zero-height fragment (which then contains the transform origin).
Full Minutes || Specs Referenced: Display, Fragmentation
Flexbox
- Tab explained that the flex distribution algorithm is changing for flex totals between zero and one (non-inclusive). Intent is to make this range continuous (rather than discontinuous, as currently). Reviews on recent changes to Flex Distribution Algorithm are welcomed.
- Discussed problem of implied minimum size of flex items (issue listing), which has gone back and forth a couple times as various cases come up for consideration (and was left open since Eliott’s post on it last year).
- Resolved: No change to Flexbox spec for handling
br
(but see below).
Full Minutes || Spec Referenced
Styling br
- Resolved: In Display Module, define
br { display-box: contents; content: '\A'; white-space: pre; }
to work. (This should result in change to handling of display: none
, and change to HTML spec once published.)
Full Minutes || Spec Referenced
Serialization of Shapes
- Resolved: Serialize a computed shape value per the email from astearns.
- Resolved: New Last Call for Shapes with a 3-week period.
Full Minutes || Spec Referenced
Regions
- Long discussion of:
- whether or not elements (as opposed to just pseudo-elements) should be allowed to become regions,
- whether or not / how this question is blocking progress,
- whether we care about flowing through chained boxes (we do),
- various other concerns with regions and handling of issues thereof.
- Resolved: Close issue #1 on Regions. Noted that there was a formal objection from at least one person.
Full Minutes || Spec Referenced
« Previous article
Next article »