- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Fri, 14 Nov 2025 00:23:56 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[CSS2][css-position-3] Negative containing blocks and `auto` margins``, and agreed to the following: * `RESOLVED: close with previous resolution accepted` <details><summary>The full IRC log of that discussion</summary> <noamr> oriol: we resolved this issue in Paris. when the inset is big enough so that the containing block is negative, what should happen? browsers seem inconsistent. Servo allows it to have a negative size. We resolved to go with the blink way. but we implemented it in servo we realized that blink it does this for sizing, auto sizing and margin, but for alignment it uses negative size inset-modified containing block<br> <noamr> iank_: it's not what's happening in blink<br> <noamr> iank_: it's a bug in blink. when we clamp the IMCP we have 3 options. adjust end inset, start inset, or both<br> <noamr> iank_: we shift the inset based on alignment to be negative<br> <noamr> iank_: the other option is to take the dominant side and always do that. blink always has a positive IMCP for alignment<br> <noamr> iank_: the other option is just to take the dominant side based on writing mode and direction. I think we resolved on that.<br> <noamr> oriol: we resolved on aligning with blink and then I found a case where this is different. no strong opinion<br> <noamr> iank_: I am fine with changing this<br> <astearns> ack fantasai<br> <noamr> fantasai: between blink and resolved behavior, no strong opinion. unlikely people would intentionally run into this. intuition from authoring perspective anyone?<br> <noamr> iank_: I want to clamp the negative size to non-negative<br> <noamr> astearns: keep resolution and consider it a bug in blink; or amend it slightly to specify blink's current behavior<br> <noamr> PROPOSED RESOLUTION: close with previous resolution accepted<br> <noamr> RESOLVED: close with previous resolution accepted<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11478#issuecomment-3530286524 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 November 2025 00:23:56 UTC