On Wed, Jun 11, 2008 at 7:59 AM, Andrew Fedoniouk <ne...@terrainformatica.com> wrote:

These are mutually exclusive, so which are you proposing?

That's not what you said. Here's what you said:

*Blocks in flex context,* floats, absolutely positioned elements, inline-blocks, table-cells, table-captions, and elements with 'overflow' other than 'visible' (except when that value has been propagated to the viewport) establish new block formatting contexts.

Where "block in flex context" is such a block that either has dimensional attributes (height,margin, etc.) defined in flex units or is contained in a block that has @flow attribute defined.

I guess it's unclear whether "contained" on the last line means transitive containment or direct containment. But this definition does not limit itself to affecting floats only.

Note that CSS does not currently define what it would mean for a a block to be a block formatting context for floats only but not for other purposes.

I've given examples that require spec and implementation changes for flex-units but not for flexboxes, so this is not true.

But it is better to add such mechanism

That could be true.

Concept of flexes is natural for human and is well known and obvious for

That is true, but it's true for flexboxes too.

Tables are using flex concept

See David Baron's message about that.

Rob