Skip to content

[css-position] Planning for 'position' being a shorthand #10069

Open
@tabatkins

Description

@tabatkins

With the planned addition of 'position-container', and the recent rename of 'anchor-default' to 'position-anchor', it starts being reasonable to ask if 'position' needs to become a shorthand, and what it can set.

In particular, I think it's definitely the case that 'position-container' should be reset by 'position'. It seems reasonable that 'position-anchor' also be reset, tho I could be convinced otherwise. That is, for both of these, it seems reasonable that if you're changing the type of positioning, you'd want to lose these values too.

Setting these values in the shorthand also seem reasonable. Both of them are using anchor names, tho, so we'll need a way to differentiate them. In theory we could use a / to separate them, but I don't think there's an obvious "first" one, so instead I suggest a syntax like:

position: <'position-type'> || <'position-container'> || anchor <'position-anchor'>

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