http://www.w3.org/Bugs/Public/show_bug.cgi?id=10828
--- Comment #60 from CE Whitehead <cewcathar@hotmail.com> 2011-03-24 16:41:31 UTC ---
(In reply to comment #59)
> Here's the implementation data from smontagu's tests:
> Impl <BR> <PRE> CR/LF
> ===============================
> IE7 PS PS
> IE8 LS LS
> IE9 LS PS
> Chrome9 PS/LS PS/LS
> Safari5 PS/LS PS/LS
> FF3.6 LS LS
> Opera11 LS LS
> WebKit's behavior is really weird. Whether the break is LS or PS seems to
> depend on what type of content is near the break: if there is an *embedded*
> element after the <br>, it's treated as LS (the RTL effect passes through the
> <br>).
> To summarize, the ideal behavior would be IE9's, i.e.
> Ideal LS PS
O.k; under this p is the only way to get paragraph breaks; this does solve the
use case described in comment 18 (I assume br clear="all" which is for images
would at least force a hard break).
> The safest behavior is probably IE7's,
> Safe PS PS
I thought this behavior however was to be relegated to quirks mode only,
and that people who wanted to use break as a paragraph separator would have to
be in quirks mode from now on. But I still have my question about br
clear="all" (but I drop my request to have any other hard bidi break as you
all are right; people who use it would know to use the p element).
Best,
--C. E. Whitehead
cewcathar@hotmail.com
(In reply to comment #59)
> Here's the implementation data from smontagu's tests:
> Impl <BR> <PRE> CR/LF
> ===============================
> IE7 PS PS
> IE8 LS LS
> IE9 LS PS
> Chrome9 PS/LS PS/LS
> Safari5 PS/LS PS/LS
> FF3.6 LS LS
> Opera11 LS LS
> WebKit's behavior is really weird. Whether the break is LS or PS seems to
> depend on what type of content is near the break: if there is an *embedded*
> element after the <br>, it's treated as LS (the RTL effect passes through the
> <br>).
> To summarize, the ideal behavior would be IE9's, i.e.
> Ideal LS PS
> The safest behavior is probably IE7's,
> Safe PS PS
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.