Re: [csswg-drafts] [css-position-3] Section 3.5.1 Conflicts with CSS2 Positioning Behavior (#11258)

>I don't know what you mean here, CSS2 resolves auto too.

For CSS2 developers, there is no change in the semantics of auto (i.e., it is not resolved to 0).

 >This is not a "lone auto" case. We know both insets in the inline axis, and none in the block one.
 
I assumed your suggestion was general and attempted to explore how it might apply to a different scenario.
 
>Doesn't follow? As you just said, both insets are 0, so none of them is auto, so the margins don't resolve to 0.

You're right—my mistake. In this case, the margins remain, and we can calculate the horizontal position.

>it is impossible to determine the size of the inset-modified containing block based on any specific offsets

>How so? Here we know both insets so the inset-modified containing block is 200px - 0px - 0px = 200px wide.

1. How do we solve for the top and bottom when auto is no longer converted to 0?
2. How is the vertical position of #child determined in this scenario?



 

-- 
GitHub Notification of comment by gitspeaks
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11258#issuecomment-2492544019 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 21 November 2024 23:14:11 UTC