Open emilio opened 5 years ago
The Houdini Task Force just discussed unregistered layout functions
, and agreed to the following:
RESOLVED: An unregistered or error'd layout() value causes blockification of the child elements, like the default value of childDisplay for a registered layout worker.
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
orblock
... 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.