- From: davidsgrogan via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jun 2022 18:15:05 +0000
- To: public-css-archive@w3.org
The graph for the **first** issue from https://github.com/w3c/csswg-drafts/issues/5843#issuecomment-880999145 is at https://chromestatus.com/metrics/feature/timeline/popularity/4237. It overcounts because we don't have the machinery to check this condition: > The static positioning rectangle is not equal in size to the abspos item’s margin box in that axis (thus the alignment properties can have an effect in this axis). So, even if the rectangle and margin box are equal, we count it as a behavior change. That graph also implements the slightly different set of conditions from https://github.com/w3c/csswg-drafts/issues/5843#issuecomment-1120333927, namely only checking the cross axis, not either axis. # For the **second** issue in https://github.com/w3c/csswg-drafts/issues/5843#issuecomment-880999145 (disconnecting `align-self`): I didn't add a UseCounter because I don't really understand it. I don't think my example that prompted it (https://github.com/w3c/csswg-drafts/issues/5843#issuecomment-876794501) is a good one. If you give an example that demonstrates the difference between current behavior and proposed behavior, and we still want a UseCounter for it, I can add one later. Also, I'm confused by this, from the bottom of https://github.com/w3c/csswg-drafts/issues/5843#issuecomment-880999145 > [not disconnecting] would cause all of those absposes to start responding to the align-items value of their flex container parents. Absposes _currently_ respond to the align-items value of their flex container parents, so I don't get what you mean by "start". -- GitHub Notification of comment by davidsgrogan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5843#issuecomment-1143978944 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 June 2022 18:15:06 UTC