Skip to content

[css-layout-api] Unregistered layout function and blockification. #844

Open
@emilio

Description

@emilio

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions