Re: [csswg-drafts] [css-overflow][css-text-decor] should text-decoration include ellipsis? (#6531)

The CSS Working Group just discussed `should text-decoration include ellipsis?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fremy> Topic: should text-decoration include ellipsis?<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/6531<br>
&lt;florian> q+<br>
&lt;fremy> fantasai: I have no strong opinion on this issue<br>
&lt;fremy> TabAtkins: The question is whether the text decoration should apply to the ellipsis dots<br>
&lt;fremy> TabAtkins: currently all implementations don't do it<br>
&lt;fremy> TabAtkins: but the dots use the font, color, etc of the text it replaces<br>
&lt;tantek> interesting that every implementation "missed it"<br>
&lt;fremy> TabAtkins: so this seems like a bug to me<br>
&lt;astearns> ack florian<br>
&lt;fremy> TabAtkins: but are there implementations where this would be difficult to do?<br>
&lt;PeterC> q+<br>
&lt;tantek> I’m curious if there's author consensus on this rather than reasoning from a spec/purity perspective<br>
&lt;fremy> florian: my intuition is similar<br>
&lt;fremy> florian: an issue is that the ellipsis is not supposed to be scrollable<br>
&lt;fremy> florian: so that makes it different from the rest of the text<br>
&lt;iank_> q+<br>
&lt;fremy> florian: because the text is located elsewhere<br>
&lt;fremy> florian: so it's a different line, not the same line<br>
&lt;fremy> TabAtkins: ah yes, if you have a wavy underline, the junction would be very undefined<br>
&lt;astearns> ack PeterC<br>
&lt;tantek> q?<br>
&lt;tantek> I'm not seeing any author input on the issue<br>
&lt;fremy> TabAtkins: so, this looks more like an abspos, which don't have text decoration inherit<br>
&lt;fremy> PeterC: from an implementation perspective, if the text is using a color font and the following characters might or might have had color characters<br>
&lt;fremy> PeterC: it's not clear what the implementation should do with the ellispsis<br>
&lt;astearns> ack iank_<br>
&lt;fremy> PeterC: but indeed that doesn't sound like easy case all the time<br>
&lt;fremy> iank_: I think the scrolling of ellipsis is not a requirement, it's a may<br>
&lt;fremy> iank_: we would likely object to a change to make normative<br>
&lt;tantek> q+ to say I’m a soft -1 on this, absent any author input/prefs on this, I’d rather NOT ask implementaitons to change something they happen to be interoperable on<br>
&lt;fremy> iank_: because we want to keep shaping<br>
&lt;fremy> iank_: so we would not want to make it an abspos<br>
&lt;astearns> ack tantek<br>
&lt;Zakim> tantek, you wanted to say I’m a soft -1 on this, absent any author input/prefs on this, I’d rather NOT ask implementaitons to change something they happen to be interoperable<br>
&lt;Zakim> ... on<br>
&lt;fremy> iank_: webkit does the same<br>
&lt;fremy> iank_: but not firefox, which does the abspos<br>
&lt;fremy> tantek: I haven't seen much request for it<br>
&lt;fremy> tantek: and we have interop now<br>
&lt;fremy> tantek: so maybe not changing is an option too<br>
&lt;fremy> astearns: ok, time is up, let's bring this back to the issue<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6531#issuecomment-1076576647 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 23 March 2022 17:09:40 UTC