W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2020

Re: [csswg-drafts] [css-position] physical inset properties (#5005)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 May 2020 16:41:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-634790756-1590597697-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-position] physical inset properties`, and agreed to the following:

* `RESOLVED: Close issue, add a note tot he spec trying to explain the confusion`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-position] physical inset properties<br>
&lt;AmeliaBR> s/ except regular input/, same as regular input/<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5005<br>
&lt;dael> TabAtkins: In position spec physical is tlbr. Logical inset properties names -start etc. incl inset shorthand<br>
&lt;dael> TabAtkins: Jonathan Neill suggested corrisponding names for phsyical so they're under same inset prefix. Rejected b/c only do aliases when original name is bad. Not the case here.<br>
&lt;dael> TabAtkins: Slightly bad that t/l/b/r are not unified, but they're perfectly good names.<br>
&lt;dael> TabAtkins: I wanted to confirm with WG that rejection is okay<br>
&lt;oriol> +1<br>
&lt;dael> astearns: Seeing +1 from heycam|away and mostly +1 from miriam in issue<br>
&lt;dael> astearns: Prop is close no change<br>
&lt;dael> miriam: I think there is a clear potential for confusion here, but I don't know this is right solution. I don't have something else in mind. Confusion I see is less that they're not all unified and more that inset is a shorthand for something different than it looks like a shorthand for<br>
&lt;dael> TabAtkins: I forgot, inset shorthand does set phsyically unless ue logical keyword. True...I don't think we want precident of when both phsyical and logical if there's a shorthand we defualt logical. Worth calling out in the spec. Still think current definition is right for overall consistancy<br>
&lt;dael> fantasai: Needs to be consistent with margin<br>
&lt;dael> TabAtkins: Happy to add a call out for potential of confusion that it by default sets phsyicals though can set logicals<br>
&lt;dael> miriam: Works for me<br>
&lt;dael> astearns: Prop: Add text to the spec trying to explain away the confusion<br>
&lt;dael> TabAtkins: It'll be a notes<br>
&lt;dael> astearns: Nice to figure out some solution to this.<br>
&lt;dael> astearns: Objections to Close issue?<br>
&lt;dael> RESOLVED: Close issue, add a note tot he spec trying to explain the confusion<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5005#issuecomment-634790756 using your GitHub account
Received on Wednesday, 27 May 2020 16:41:39 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:07 UTC