- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Nov 2022 23:30:50 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-align] *-items properties might need to resolve directions early`, and agreed to the following: * `RESOLVED: Take the changes listed in https://github.com/w3c/csswg-drafts/issues/7612#issuecomment-1230963091` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-align] *-items properties might need to resolve directions early<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/7612#issuecomment-1230963091<br> <dael> fantasai: There was an issue raised against how we interp varios items on abspos<br> <dael> fantasai: Alignment spec says when you abspos a box with specific offsets alignment prop apply in inset rectangle.<br> <dael> fantasai: You can stetch, center, left align in inset box.<br> <dael> fantasai: None is impl yet, but that was the direction<br> <dael> fantasai: What we were saying is when you abspos the box you're in a formatting context that's not your parent's that you're out of flow from<br> <dael> fantasai: Spec that align items property of parent don't effect your alignment as an abspos<br> <dael> fantasai: Problem we ran into is when staticpos there's existing behavior where alignment prop do effect your position<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/7612#issuecomment-1230963091<br> <dael> fantasai: Seems like we're at the summary we linked to<br> <dael> fantasai: If you are abspos and not staticpos the align and justify: self align you in inset box. If you're static they align you in staticpos rectangle<br> <dael> fantasai: If you're align or justify-self is auto and you're not staticpos you ignore parent. If you are static pos we look at -items of your parent and use alignment based on that<br> <dael> fantasai: [reads out comment]<br> <dael> fantasai: That's my understanding of where we're at. Bringing to WG to ask for review and decide if that makes sense<br> <dael> iank_: One thing good to clarify is what writing mode does align-self:start operate in when insets are set?<br> <dael> fantasai: I think that's the next issue<br> <dael> iank_: This is just about static pos rectangle?<br> <dael> fantasai: That's the focus<br> <dael> iank_: Prop is static pos rect operates in writing mode direction of parent?<br> <dael> fantasai: Yeah. I think it would need to for flex stuff follow parent formatting context<br> <dael> iank_: Okay. So if it's static pos it's within the writing mode of the parent. I think that's probably fine.<br> <dael> iank_: Side note- do we ahve an open issue for when static pos rectangle is fragmented?<br> <dael> fantasai: I don't believe we do I think fragment like whatever it's derived from<br> <dael> iank_: There's complexities I can add to an issue<br> <dael> astearns: What we're talking about would apply to curent grid and flex children but the rest is waiting on impl for other formatting context?<br> <dael> iank_: As far as I understand this is broadly status quo for grid and flexbox<br> <dael> fantasai: I believe so. Might be clarifying for grid but this is for flex<br> <dael> astearns: As much as I followed it seems good to me<br> <dael> astearns: Other comments?<br> <dael> astearns: Shall we resolve on taking the changes in https://github.com/w3c/csswg-drafts/issues/7612#issuecomment-1230963091 ?<br> <dael> astearns: Objections?<br> <dael> RESOLVED: Take the changes listed in https://github.com/w3c/csswg-drafts/issues/7612#issuecomment-1230963091<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7612#issuecomment-1301489903 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 November 2022 23:30:52 UTC