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

Re: [csswg-drafts] [css-text-decor] What happens to the wavy & double lines when `text-decoration-thickness` is applied? (#4134)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 08 Aug 2019 00:04:58 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-519311865-1565222696-sysbot+gh@w3.org>
The CSS Working Group just discussed ``What happens to the wavy & double lines when `text-decoration-thickness` is applied?``.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: What happens to the wavy &amp; double lines when `text-decoration-thickness` is applied?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4134<br>
&lt;dael> astearns: Should we spec how wavy lines should be drawn?<br>
&lt;dael> heycam: More control over these thigns, more authors will expect specific effects. Presence of thickness will make people aware of difference in render for wavy lines<br>
&lt;dael> AmeliaBR: Agree something should be spec. No strong opinion of what. Clear rendering def is worthwhile<br>
&lt;dael> Rossen_: Any expectation that this property will be different then stroke?<br>
&lt;dael> fantasai: Yes b/c when scaling stroke thickness you're not changing path. Here you expect thickness of line and size of wave will scale<br>
&lt;dael> Rossen_: Suggestion is botht he control points and stroke change?<br>
&lt;tantek> more thickness = lower frequency?<br>
&lt;dael> fantasai: Yeah b/c if you don't change control points you just get a thick line. It is spec as wavy line<br>
&lt;astearns> tantek: more thickness = more amplitude<br>
&lt;tantek> text-decoration-radius?<br>
&lt;fantasai> :(<br>
&lt;dael> AmeliaBR: Better compare at least for double line is double borders where as you scale up the total width of broder is devided between wo strokes and pace between. I'd expect that for double line. Wavy I'd expect waves to take full width. If the waves stretch to keep rpoportional curve that's unspecified since we don't define what it is to start with.<br>
&lt;dael> Rossen_: I'd be interested to hear behavior on differen platforms. Desktop word when scaling overall text the thickness and waviness of underlines does not change. Consistent across office products. Curious if different<br>
&lt;fantasai> rossen, the issue here is that the thickness of the underline is specified to change, in that case we can't be consistent with the platform if the platform isn't changing the thickness<br>
&lt;dael> myles: Couple points. Straight double underlines we've got platform conventions for position. Shouldn't spec gap. Wavy underlines a use case is spelling market or cjk names/titles as an honorific. The shape of those might intend to be different. SHould't give amplitude and frequency controls. If give controls should be for semantic.<br>
&lt;dael> myles: I don't see authors asking for high level of control on shaping underline<br>
&lt;dael> astearns: I don't think talkign adding properties. Just specifying something so get slightly mroe consistent rendering across brwosers and platforms<br>
&lt;dael> fantasai: Might need to jsut spec that for wavy lines that thickness of line as well as amplitude and frequency are meant to scale up. UA can adjust and it doesn't have to be a linear curve. If you're increasing thickness of line then amplitude and frequency needs to scale up<br>
&lt;dael> fantasai: Can say something similar for doubling. THickness of 2 underlines and space between should scale. Should look good in large font sizes.<br>
&lt;dael> astearns: We're past time. We should close this.<br>
&lt;dael> astearns: fantasai can you come up with a proposal for what to do?<br>
&lt;dael> fantasai: If people are happy with the general guidlines I can draft<br>
&lt;dael> astearns: Draft it, put in issues, and then we'll agenda+ for specific text<br>
&lt;dael> fantasai: Agree with myles shouldn't spec exact curves and amplitude.<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4134#issuecomment-519311865 using your GitHub account
Received on Thursday, 8 August 2019 00:04:59 UTC

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