[css-flexbox-1] Time for a CR Draft of Flexbox 1

[svgeesus]

What do you mean I'm referencing an outdated TR from 2018? This is the latest published version, and all the quotes in this issue are taken directly from it. Specifically, the issue regarding "available space" originates from this version.

Why isn't this considered a bug in the specification? While many things in drafts reflect improvements and enhancements, the current published version should, at the very least, be correct, shouldn't it?

For example, why hasn't the link for width been updated? How can common reader make sense of things ? If the logic is to always goto the latest draft to verify things, than what's the value of the published version ?

Originally posted by @gitspeaks in #11392 (comment)

[svgeesus]

Having the latest /TR be six years old is suboptimal and misleading.

The changes list in the ED needs updating, and it does not capture all resolutions to date. The first one is much less effort to fix, and would allow publishing a CR Draft.

[fantasai]

Tab and I spent some time updating the draft, we're down to one issue that still needs edits to have a draft that represents WG consensus. Would be nice to fix that and then publish.

[fantasai]

(This was the issue not yet edited in. We had trouble interpreting the resolution.)

[svgeesus]

Removing Agenda+ until that one issue is edited in. Please add it back once the doc is ready (or, of course, if the earlier resolution needs additional discussion).

[gitspeaks]

Any update on the status of this?

Also, here are two additional things to keep in mind:

• [css-flexbox-1] Merge section 9.2 with 9.3 #11885
• Frozen items do not guarantee complete distribution of free space #11405

[svgeesus]

Tab and I spent some time updating the draft, we're down to one issue

@fantasai @tabatkins how is that going? Is it still critical path for publication?

[gitspeaks]

When revising the specification, please also address #12108