W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2019

Re: [csswg-drafts] [css-text-decor] Rename `text-decoration-thickness` to `text-decoration-weight`? (#4138)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Aug 2019 23:56:34 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-519310165-1565222192-sysbot+gh@w3.org>
The CSS Working Group just discussed ``Rename `text-decoration-thickness` to `text-decoration-weight`?``.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Rename `text-decoration-thickness` to `text-decoration-weight`?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4138<br>
&lt;dael> astearns: jen suggested weight b/c typographic term. We have width, thickness, and weight as possibilities for the prop that determines how wide/thick a text underline is<br>
&lt;dael> astearns: Opinions on what we should do?<br>
&lt;dael> myles: We shipped thickness. Pref no change<br>
&lt;dael> astearns: Anyone else?<br>
&lt;TabAtkins> I prefer no change<br>
&lt;TabAtkins> (I prefer we'd kept it as 'width', but oh well.)<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/4138#issuecomment-517121344<br>
&lt;dael> fantasai: I personally favor width b/c every other line thickness in css is width and that's helpful to authors<br>
&lt;dael> fantasai: bradk said same ^<br>
&lt;tantek> +1 fantasai<br>
&lt;dael> heycam: Prefer not to change here. I'd like to stick with [missed]<br>
&lt;dael> AmeliaBR: Would have leaned width, but not worth changing shipped impl<br>
&lt;tantek> seriously how did we all screw this up?<br>
&lt;dael> astearns: I believe heycam wanted preference for width<br>
&lt;dael> astearns: jen suggested weight b/c it's typographic. Somewhat against because we don't use it for line thickness elsewhere. Font has more then line thickness<br>
&lt;dael> myles: Also 400 is  reasonable weight<br>
&lt;dael> astearns: Should reject weight. Have people on both sides of width and thickness<br>
&lt;tantek> outline-width etc.<br>
&lt;dael> fantasai: Sympathetic that we impl and shipped. Inconsistency will effect authors going forward and will have to remember this is only one that has a different name for what it's doing. THat's an ongoing cost<br>
&lt;dael> devin: Would argue it's different. Thickness of line under text I don't think is a width. border-width is how wide is it. Underline people think thick or heavy<br>
&lt;tantek> agreed with fantasai, for non-native English speakers, it makes no sense to appeal some minute difference of meaning between thickness and width<br>
&lt;dael> fantasai: majority of people don't speak english, they're looking for patterns. It's just another line.<br>
&lt;dael> myles: Value in css matching coloqueal talk<br>
&lt;astearns> tantek: https://github.com/w3c/csswg-drafts/issues/3118#issuecomment-432288810<br>
&lt;dael> fantasai: Yes. And in css matching itself<br>
&lt;dael> astearns: tantek asked for where we resolved on thickness<br>
&lt;fantasai> s/And in/But higher value in/<br>
&lt;dael> myles: At f2f, forget location. Did twitter poll asking people what width means, horizontal distance or vertical distance of line. 60/40 split with 60% being wrong answer<br>
&lt;tantek> wow those linked minutes do not have any reasoning for thickness<br>
&lt;tantek> that's really bad<br>
&lt;dael> astearns: I'm torn. Like consistency, but things are shipped. I'm inclined to leave things as they are with thickness. It's poss a mistake and we need to create line-weight alias<br>
&lt;fantasai> https://lists.w3.org/Archives/Public/www-style/2018Dec/0004.html<br>
&lt;tantek> "shipped" is not good enough<br>
&lt;tantek> webcompat would be<br>
&lt;dael> fantasai: We won't make an alias. We'll either get this right now or we live with this<br>
&lt;dael> myles: Agree. If we didn't do font-stretch we won't do this<br>
&lt;dael> astearns: tantek in IRC says shipped isn't enough, should only consider web compat. Do we have content using this?<br>
&lt;dael> fantasai: Hardly any I think, shipped recently<br>
&lt;dael> myles: We did resolve before we shipped<br>
&lt;dael> tantek: There's no reasoning in that, not even a straw poll. I think we should throw that resolution out. I don't trust it.<br>
&lt;dael> myles: You were in the room tantek<br>
&lt;dael> tantek: I don't remember it.<br>
&lt;dael> astearns: I remember more discussion that in minutes, but it was short.<br>
&lt;dael> tantek: Well, it was scribed more now then it was then<br>
&lt;dael> tantek: We had resolution on some discussion. I see a non-trivial amount of folks uncomfortable after the fact. I'd request a straw poll to see if it's a few of us uncomfortable or if it's wider questions of the resolution<br>
&lt;dael> astearns: Can straw poll<br>
&lt;dael> Rossen_: We don't have as many people as compared to other calls. If this is problematic resolution let's push to next week with more people and give a week to think<br>
&lt;dael> tantek: I don't disagree, but doesn't conflict with my straw poll<br>
&lt;bkardell_> 14<br>
&lt;fantasai> fantasai: 1<br>
&lt;dael> astearns: For people on call to get tone of room. Please type 0 if don't care. 1 if prefer width. 2 if you prefer thickness<br>
&lt;astearns> 0<br>
&lt;fantasai> bradk: 1<br>
&lt;myles> 2<br>
&lt;smfr> 2<br>
&lt;dbaron> 2<br>
&lt;Rossen_> 2<br>
&lt;bkardell_> 0<br>
&lt;heycam> 2 (because I prefer not changing)<br>
&lt;AmeliaBR> 1<br>
&lt;drousso> 2 (because i'd rather not change)<br>
&lt;xfq> 0<br>
&lt;birtles> 0<br>
&lt;melanierichards> 0<br>
&lt;tantek> 1 / 0 (weak preference)<br>
&lt;dael> astearns: People on call slight preference for no change<br>
&lt;dael> astearns: Let's set this to go over next week with more people on call. Decision will be keep thickness or change it back to width<br>
&lt;tantek> I'm not seeing fantasai or tab on the poll who previously said 'width' in the above<br>
&lt;bkardell_> slight/weak preference prob, but I said 0 because i think it is weak<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4138#issuecomment-519310165 using your GitHub account
Received on Wednesday, 7 August 2019 23:56:37 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:51 UTC