W3C home > Mailing lists > Public > public-houdini@w3.org > August 2015

[css-layout-api] An initial starting point for the Layout API

From: Ian Kilpatrick <ikilpatrick@chromium.org>
Date: Thu, 27 Aug 2015 10:36:46 +0200
Message-ID: <CAJL3UpQVU5bEv6FnoaHgB1Eu0-auaM_7GngCW21P0avQBg+3ag@mail.gmail.com>
To: public-houdini@w3.org
Hi all,

Before we meet on Fri/Sat I wanted to quickly send out to the list
what we think might be a good scope for an initial level of the Layout
API so that we can discuss F2F.

Please note that this isn’t a list of things that we’ll never want to
support. This is merely a list of what we think is a minimum useful
set of features for authors.

 - Expose minInlineContent/maxInlineContent
 - AbsPos is handled automatically (in the same fashion as flex/grid).
 - The custom layout container establishes a formatting context, which
implies that:
    - Floats cannot intrude into the custom layout
    - Margins do not collapse
 - Blockify all children (similar to flex/grid)
    - Note that in a future version of the spec this may be toggled with a flag
 - No changing paint order (like the CSS order property on flex/grid).
 - Float does not have any effect on children of a custom layout
container (similar to flex/grid).

Please have a think about what other items could be in a future level,
or what should be included in level 1.

Received on Thursday, 27 August 2015 08:37:19 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 August 2015 08:37:20 UTC