Design Review #224

#224: CSS Layout API

Visit on Github.

Opened Jan 11, 2018

Hello TAG!

I'm requesting a TAG review of:

Name: CSS Layout API
Specification URL: https://drafts.css-houdini.org/css-layout-api/
Explainer, Requirements Doc, or Example code: https://github.com/w3c/css-houdini-drafts/blob/master/css-layout-api/EXPLAINER.md
Tests: No tests yet, but will be upstreamed to wpt during initial development.
Primary contacts: @bfgeek

Further details (optional):

I have read and filled out the Self-Review Questionnare on Security and Privacy. The assessment is here.
I have reviewed the TAG's API Design Principles

You should also know that...

This is an early review, so things might be difficult to understand and/or out of date in the specification and explainer. I'll ping this issue when large changes have been made / clarified, and when some initial code can be used in chromium.

We'd prefer the TAG provide feedback as (please select one):

open issues in our Github repo for each point of feedback
open a single issue in our Github repo for the entire review
leave review feedback as a comment in this issue and @-notify [github usernames]

Discussions

2018-04-24

Minutes

Travis: I still have an action to file issues on their repo.

Dan: I'll move the milestone.

2018-05-22

Minutes

@travisleithead: Filed issue with general points from Alex: Fragments should have ctors. Second: requesting what happens when exceptions are thrown, 3) Whether a dictionary should be used instead of interface for IntrinsicSizes. 4) Question about renaming layoutNextFragment 5) IDL usage bugs in various examples 6) General comment about readability - none are dealbreakers... Suggest that we close this issue. We can also mark it as pending external feedback and check back in in 6 months.

@torgo: let's do it at the F2F