- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Sat, 24 Jul 2010 00:51:27 -0400
- To: Asmus Freytag <asmusf@ix.netcom.com>
- CC: "Tab Atkins Jr." <jackalmage@gmail.com>, "L. David Baron" <dbaron@dbaron.org>, fantasai <fantasai.lists@inkedblade.net>, Ian Hickson <ian@hixie.ch>, Simon Montagu <smontagu@smontagu.org>, www-html@w3.org, WWW International <www-international@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, "www-style@w3.org" <www-style@w3.org>
On 7/24/10 12:41 AM, Asmus Freytag wrote: > On 7/23/2010 6:31 PM, Tab Atkins Jr. wrote: >> No, inline elements don't trigger this. Only block elements, >> list-items, and table elements. The only way to trigger problems is >> to take a ton of block-level elements, make them display:inline, and >> nest them. > Like insanely nested lists... Lists are not display:inline by default. If you take insanely nested lists and make them display:inline.... then they become unreadable, for the most part. > My feeling will be that it will occur so rarely that few people will be > able to recognize the real nature when this happens to them. This is probably true. Then again, browsers could issue a warning in their consoles when they hit the bidi embedding limit and this warning could point out this possible source for itself, right? -Boris
Received on Saturday, 24 July 2010 04:53:10 UTC