- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Jul 2024 16:25:25 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-text] Specify HTML alignment as text-align: -webkit-{left,right,center}`, and agreed to the following:
* `RESOLVED: Specify the -webkit-* values for text-align in the Compat spec.`
<details><summary>The full IRC log of that discussion</summary>
<TabAtkins> emilio: WEbsites try to depend on this -webkit value being exposed<br>
<TabAtkins> emilio: Right now nobody implements the justify-items:legacy stuff<br>
<TabAtkins> emilio: My original idea was to just spec reality here, which is a bit underwhelming<br>
<TabAtkins> emilio: but i'm okay trying to implement justify-items<br>
<TabAtkins> emilio: But we'll probably need to keep the -webkit value for compat<br>
<TabAtkins> emilio: So we should probably choose to spec -webkit-left/right/center either in Alignment or Compat (probably Compat), and let browsers implement Alignment eventually<br>
<TabAtkins> TabAtkins: So your proposal is we spec the -webkit in Compat, and have HTML refer to those, and later see if we can compat-wise fix to Alignment?<br>
<TabAtkins> emilio: Yes. We can possibly have HTML refer to Alignment.<br>
<TabAtkins> TabAtkins: I don't think HTML would take a patch for features that aren't impelmented yet.<br>
<TabAtkins> emilio: Yeah, possibly.<br>
<TabAtkins> astearns: So two steps. First, add -wekbit value to text-align because we have to, not becuase we want to.<br>
<TabAtkins> emilio: yes, because widely depended on<br>
<TabAtkins> astearns: But then a little unclear what the second step is<br>
<TabAtkins> astearns: Oriol talksa bout using justify-items:legacy opting into those values, but I thought the point was sites depending on the values without using justify-items<br>
<TabAtkins> emilio: Right, you have to support the text-align values anyway.<br>
<astearns> ack dbaron<br>
<TabAtkins> emilio: So my pref is to keep them both defined, and then start with having HTML referring to the text-align values, and later switch to justify-items once implemented<br>
<TabAtkins> dbaron: This sounds reasonable to me<br>
<iank_> q+<br>
<TabAtkins> dbaron: Given that everyone does the same thing, and it's not completely clear what the space of changes we can make compatibly *is*, it seems reasonable to spec what we currently have, maybe with a note about what we want to change it to in the future.<br>
<TabAtkins> dbaron: This legacy thing is defined in a way that's supposed to deal with this issue, but it's not clear, for example, how much pages depend on this actually working via text-align<br>
<TabAtkins> dbaron: Because for example you can override this inherited behavior by setting another value on text-align. We need to see if that's something that's ok to break.<br>
<TabAtkins> dbaron: So i'm supportive of moving closer ot reality.<br>
<astearns> ack iank_<br>
<TabAtkins> iank_: dbaron just said what I was gonna<br>
<TabAtkins> astearns: so proposed resolution is: specify the -webkit value for text-align, with a note about what we'd like to do in the future<br>
<TabAtkins> emilio: I think we should specify them without a note, and have HTML take the note about the intended migration<br>
<TabAtkins> dbaron: Sounds fine.<br>
<TabAtkins> TabAtkins: speciy in Text or in Compat?<br>
<TabAtkins> astearns: Compat sounds slightly easier to quarantine<br>
<TabAtkins> emilio: sounds fine, don't mind either way<br>
<TabAtkins> RESOLVED: Specify the -webkit-* values for text-align in the Compat spec.<br>
<TabAtkins> astearns: Who's doing the HTML patch?<br>
<TabAtkins> emilio: I can.<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10388#issuecomment-2233714476 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 July 2024 16:25:26 UTC