- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 25 Jun 2013 17:59:13 +1200
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "Aharon (Vladimir) Lanin" <aharon@google.com>, W3C style mailing list <www-style@w3.org>
- Message-ID: <CAOp6jLbYDoeDX4wF36DCLiTjQ7Soz2r58CHtUAetd5aVdPV9tA@mail.gmail.com>
On Tue, Jun 25, 2013 at 4:08 AM, Tab Atkins Jr. <jackalmage@gmail.com>wrote: > We had this exact discussion some time ago, and decided very > deliberately that we wanted the ellipsis to be a visual effect, not a > logical one. I'd recommend searching the mailing lists for these > discussions first, so you can see the older arguments for it. > I tried to make those arguments all over again, but Aharon was not dissuaded. I think I should have just sent him to you :-). One additional issue that Aharon didn't bring up is that in Webkit/Blink at least, the implementation of logical text-overflow is, shall we say, "partial". In particular, full support for logical text-overflow would require changing the positions of inline boxes. For example: א: beginning middle e<img src="testfile.png" width="5" height="5">nd. With dir="rtl", text-overflow:ellipsis, white-space:pre and certain widths, the position of the <img> would depend on the width. But it looks like Blink never changes the line layout for logical text-overflow; it just looks at the last visible text run and reorders glyphs within that text run (or something like that). Thus, I think it's not fair to say that Blink/Webkit "implement logical text-overflow" --- they implement a rough and very simplified approximation to it. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * *
Received on Tuesday, 25 June 2013 05:59:39 UTC