W3C home > Mailing lists > Public > www-style@w3.org > January 2015

Re: [css-text][css-writing-modes] Line breaking around Emoji, Gaiji, U+FFFC, and text-combine-horizontal

From: fantasai <fantasai.lists@inkedblade.net>
Date: Sun, 25 Jan 2015 16:46:26 -0500
Message-ID: <54C56432.6010004@inkedblade.net>
To: www-style@w3.org
On 01/21/2015 01:42 PM, Koji Ishii wrote:
>
>>> 2. Add ‘line-break-string’ property. When this property is set to a string
>>> of 1 character length, the element looks as if its text is the character to
>>> line breakers and justification algorithms.
>>
>> I don't understand this property, and do not want to add a new property.
>
> It'll let <img> handled as if it were a single specified character to
> the line breaker, just like text-combine is treated as if it were
> U+FFFC. I wish to limit the effect to the minimal set of elements such
> as img. So:
>
> img.emoji { line-break-string: 'U+4E00'; }
>
> can make the img to break just like an ID character. Does this make clearer?

Yes, much clearer. I think this needs to go in to Level 4, though.

I suggest to rename to 'line-break-as' and give it some keyword values
for common cases like 'ideographic', so authors don't have to pick
arbitrary characters. What do you think?

Also, should have an auto value that uses value of the 'alt' attribute.

>>> One of the experts recommended ID (Ideographic) class[2] for inline images
>>> such as Emoji. One idea is to have a boolean property to opt-in to this
>>> behavior. Another idea was to for authors to specify UAX#14 class. Among the
>>> three options, I think the 1 character length string gives the best
>>> flexibility.
>>
>> Is there a reason we can't just treat as ID always?
>
> It was pointed out that all browsers except Presto breaks
> <img>&nbsp;<img> and following UAX#14 will break web-compatibility[1].
> It's a bit hard to imagine for me if authors expect this sequence to
> break before and after the &nbsp;, so if we want to go that route, I'm
> good, but I suspect this route needs discussion?
>
> [1] https://lists.w3.org/Archives/Public/www-style/2013Nov/0136.html

Yes, sounds like it needs discussion. I agree with your assessment. :)
Let's discuss it in WG; I think if we can avoid the need to introduce
a property for the common cases, that's a benefit worth having.
I think for authors the main cases where they need line breaks around
images are images placed side-by-side, but it's going to be tricky to
evaluate web-compat here.

~fantasai
Received on Sunday, 25 January 2015 21:46:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:56 UTC