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

I put this on the CSSWG call agenda, but can't make today's meeting. Please do discuss this without me (we need these to be resolved so work in Gecko is not slowed down). 

For me, the question at hand is: What can we do to get something close to an interoperable result?Perhaps these underlines implementations don't need to be precisely identical. But _this_ much difference will be a big problem for any Author who wants to use double or wavy  in combinnation with thickness.

Should we:
1) Attempt to spec _identical_ behavior? Or define some bit-more-vague guidelines?
2) What should those details be? What's reasonability possible given the realities of our different rendering engines?
3) What could be discussed on the call (with a very full agenda), decided, and worked on after by the spec writers? Or??

Personally, I prefer what's going on with Firefox's double line as it grow thicker. I'd love to see Safari (and everyone else) reduce the amount of space between the lines, and have the thickness of both each double line + space between them grow as text-underline-thickness gets bigger..... but to do so proportionately. Not 1:1:1. 

As for wavy, I do believe the wavy line itself should grow thicker, not just the amplitude. Firefox's line doesn't really get thick enough for my tastes. As I adjust thickness to be thicker and thicker if _feels_ like the line doesn't get thicker, the wave gets taller only. Also, the wavy gets taller really fast — each increment of one pixel makes a huge difference, which makes it hard for an Author to find a nuanced place in their design. Each px jumps jumps jump. I do like how thickness affects amplitude, I just wish it has less of an effect / made the wave taller less quickly.

Safari — I like how the line gets thicker, but I do wish the wave would get taller as well. A bit more like Firefox. A mashup of the two / something halfway in-between might be best. 

I do understand that with the legacy of different implementation, true intro might be far more effort than it's worth. I just believe we need to get it 'in the ballpark' / get something close. 

-- 
GitHub Notification of comment by jensimmons
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4134#issuecomment-516813993 using your GitHub account

Received on Wednesday, 31 July 2019 11:44:48 UTC