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: Shinyu Murakami <murakami@vivliostyle.com>
Date: Thu, 29 Jan 2015 01:54:35 +0900
To: Koji Ishii <kojiishi@gmail.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <20150129015431.97CE.3B6C55AB@vivliostyle.com>
Koji Ishii <kojiishi@gmail.com> wrote on 2015/01/27 22:41:27
> On Tue, Jan 27, 2015 at 5:00 AM, fantasai <fantasai.lists@inkedblade.net> wrote:
> > 
> > >  This property is to opt-out the fix and bring back the behavior
> > >  we defined in the LC, so I think we need this in the Level 3.
> > 
> > The ideal behavior is, I think, to treat as ID. I can't imagine
> > anyone intentionally *wanting* the current behavior (ignoring
> > nbsp etc.)
> > 
> > 
> > FWIW, just checked Presto with some of your test cases (using
> > comma, period, brackets, etc.), and it seems to treat images
> > as ideographic. E.g. it keeps an image together with an
> > immediately following close-bracket, comma, or period. This
> > means it was Web-compatible enough for Presto, so maybe it's
> > Web-compatible enough for everyone.
> > 
> > I propose we treat TCY, U+FFFC, and images all as ID by default.
> > What do you think?

I think it's nice idea.

> 
> It's great if we can make that. UAX#14 LB1 says "resolve CB... to other classes" so I guess it's good from that perspective too IIUC.
> 
> The only concern is web-compat. We knew Presto doing as defined in LC, Kenny pointed out in his original mail, but we were too scared to change all other browsers and that's why we fixed the way it is in the spec today. Practically speaking, if impls don't see enough values to break existing sites and don't follow the spec, we can't solve the problem. From that perspective, I have mild preference to keep the legacy but allow authors to opt-in to the ideal behavior for emoji.
> 
> But I also feel that it's not a proper approach for the web to evolve. I'd like to know what others would say on this balance.

I can't understand this sort of "web-compat" is really important. Breaking at nbsp seems a bug. Presto behavior is fine.


--
Shinyu Murakami (ζ‘δΈŠ ηœŸι›„)
CEO & Founder, Vivliostyle Inc.
http://vivliostyle.com
murakami@vivliostyle.com
Received on Wednesday, 28 January 2015 16:55:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:50 UTC