- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jul 2018 03:54:15 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `issue 1429`. <details><summary>The full IRC log of that discussion</summary> <tantek> topic: issue 1429<br> <dbaron> github: https://github.com/w3c/csswg-drafts/issues/1429<br> <tantek> dbaron: one of the cases where I was disagreeing was in some ways some of these new properties are better than the old way of doing things, and I don't feel that strongly about this one, but there are some cases where it would be relatively simple to make these properties work in more cases, but it means making the 'normal' or whatever initial value do today's behavior<br> <tantek> dbaron: this one in particular is about justify self and align self on abs pos elements<br> <tantek> this is not static position stuff, this is actual absolute positioning<br> <tantek> dbaron: IDK maybe this is kinda the same as earlier<br> <tantek> fantasai: we discussed early j-s a-s on a abs pos element when ...<br> <tantek> TabAtkins: this is about one offset not being ...<br> <tantek> fantasai: per 2.1 the 2nd offset is computed after you compute the width<br> <tantek> TabAtkins: in other words like an auto margin<br> <tantek> fantasai: yeah<br> <tantek> dbaron: my perspective, i've never particularly liked auto margins as a mechanism, and these properties ought to override them<br> <tantek> fantasai: specific examples?<br> <tantek> dbaron: e.g. ...<br> <tantek> dbaron: maybe it's ok, I'm ok with this one, but I've kinda forgotten what we resolved here<br> <tantek> dbaron: I'm ok with it<br> <tantek> dbaron: there was one other one I thought was worth discussing, and I need to find the list of issues again<br> <tantek> end topic<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1429#issuecomment-402599784 using your GitHub account
Received on Thursday, 5 July 2018 03:54:18 UTC