- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Dec 2018 03:45:21 +0000
- To: public-houdini-archive@w3.org
emilio has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-layout-api] Unregistered layout function and blockification. == As I see the way unregistered layout functions are handled right now is ad-hoc: You always create a Layout API Container, but if the definition is not there you fall back to flow layout in some cases. But the data in the definition is used for other stuff (i.e., blockification, for example, via `childDisplay`). https://drafts.css-houdini.org/css-layout-api/#layout-api-box-tree doesn't define what happens if the definition is missing, and it should. I have no particularly strong opinion on what to do in that case... I tend to thing that instead of monkey-patching all the handling depending on the registeredness of the layout function and unregistered layout property should maybe just compute to `flow-root` or `block`... But I don't have all the context to know why the currently-specified handling is the way it is so I may be missing something. Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/844 using your GitHub account
Received on Tuesday, 4 December 2018 03:45:23 UTC