W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2020

Re: [csswg-drafts] [css-text] [css-inline] Define how to deal with inline backgrounds whose boundary falls into a ligature (#5251)

From: jfkthame via GitHub <sysbot+gh@w3.org>
Date: Wed, 24 Jun 2020 09:34:47 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-648711079-1592991287-sysbot+gh@w3.org>
> > One interesting consequence of Chromium's approach is that you can't select the ligature individually...
> Blink supports caret-and-selection-within-a-ligature by, currently, similar method as Gecko, 

Partly, but not entirely. Using a font that supports an "ffi" ligature, for example:

    data:text/html,<div style="font:100px linux libertine o" >office

If I drag-select slowly across this text, I can see that the individual characters making up the "ffi" ligature can be selected one by one; so I can, for instance select just the middle "f".

But now try this version:

    data:text/html,<div style="font:100px linux libertine o" >of<span>f</span>ice

Here, when I try drag-selecting across the text, the "ffi" ligature gets highlighted as an indivisible unit.

> For painting, we don't apply this logic because while there are cases where this works good, like this example, as @jfkthame pointed out, there are cases where this looks strange. For example:
> https://output.jsbin.com/tatovac

Agreed, that looks strange, but I don't see how Blink's result (where the entire ligature is painted with the color/background of its first component) is better. That means the intended styling in something like

    data:text/html,<div style="font:100px linux libertine o" >o<span style="background:cyan">f</span><span style="background:magenta">f</span><span style="background:yellow">i</span>ce

is essentially lost.

If an author doesn't want the "strange" result Firefox gives with your jsbin example, they can disable the ligature, or they can apply the background to the whole word instead of a single character; but Blink's approach here makes it extremely awkward to go the other way.

GitHub Notification of comment by jfkthame
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5251#issuecomment-648711079 using your GitHub account
Received on Wednesday, 24 June 2020 09:34:49 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:09 UTC