layout/reftests/bidi/712600-3-ref.html

Thu, 15 Jan 2015 21:03:48 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Thu, 15 Jan 2015 21:03:48 +0100
branch
TOR_BUG_9701
changeset 11
deefc01c0e14
permissions
-rw-r--r--

Integrate friendly tips from Tor colleagues to make (or not) 4.5 alpha 3;
This includes removal of overloaded (but unused) methods, and addition of
a overlooked call to DataStruct::SetData(nsISupports, uint32_t, bool.)

michael@0 1 <!DOCTYPE html>
michael@0 2 <html>
michael@0 3 <head>
michael@0 4 <meta charset="utf-8">
michael@0 5 <title>HTML Test: BDI: neutral when wrapped</title>
michael@0 6 <link rel="reference" href="bdi-neutral-wrapped-ref.html">
michael@0 7 <link rel="author" title="Aharon Lanin" href="mailto:aharon@google.com">
michael@0 8 <link rel="author" title="HTML5 bidi test WG" href="mailto:html5bidi@googlegroups.com">
michael@0 9 <link rel="help" href="http://dev.w3.org/html5/spec/Overview.html#the-bdi-element">
michael@0 10 <meta name="assert" content="
michael@0 11 'For the purposes of applying the bidirectional algorithm to the paragraph-level
michael@0 12 container that a bdi element finds itself within, the bdi element must be treated
michael@0 13 like a U+FFFC OBJECT REPLACEMENT CHARACTER.'
michael@0 14
michael@0 15 Obviously, this should hold even if the BDI's content is wrapped over more than one line.
michael@0 16 A single character (U+FFFC or otherwise) obviously never gets wrapped over more than one
michael@0 17 line, but we still expect the part of the content preceding the BDI, if any, that is
michael@0 18 displayed on the same line as some part of the BDI to be ordered the same as it would be
michael@0 19 if that part of the BDI were replaced with U+FFFC. Similarly, we expect the part of the
michael@0 20 content following the BDI, if any, that is displayed on the same line as some part of the
michael@0 21 BDI to be ordered the same as it would be if that part of the BDI were replaced with U+FFFC.
michael@0 22
michael@0 23 In the test below, the content surrounding the BDI forms a single directional run (despite
michael@0 24 the containing element and the BDI both having the opposite direction, because the BDI is
michael@0 25 treated as a neutral). Thus, on the line containing the first part of the BDI, the BDI's
michael@0 26 content appears after the content preceding it, and on the line containing the last part of
michael@0 27 the BDI, the BDI content appears before the content following it, where both 'before' and
michael@0 28 'after' are defined relative to the surrounding content's direction. And, of course, the line
michael@0 29 containing just BDI content should be ordered in the BDI's direction.">
michael@0 30 <style>
michael@0 31 body{
michael@0 32 font-size:2em;
michael@0 33 }
michael@0 34 .box {
michael@0 35 border: medium solid gray;
michael@0 36 width: 400px;
michael@0 37 margin: 20px;
michael@0 38 }
michael@0 39 </style>
michael@0 40 </head>
michael@0 41 <body>
michael@0 42 <!-- Key to entities used below:
michael@0 43 &#x05D0; ... &#x05D5; - The first six Hebrew letters (strongly RTL).
michael@0 44 &#x202D; - The LRO (left-to-right-override) formatting character.
michael@0 45 &#x202C; - The PDF (pop directional formatting) formatting character; closes LRO. -->
michael@0 46 <div class="box">
michael@0 47 <div dir="ltr">&#x202D;b &lt; &#x05D0;&#x202C;<br/>&#x202D;&gt;&gt;&gt;&#x202C;<br/>&#x202D;&#x05D3; &lt; c...&#x202C;</div>
michael@0 48 <div dir="rtl">&#x202D;a &gt; &#x05D1;&#x202C;<br/>&#x202D;&lt;&lt;&lt;&#x202C;<br/>&#x202D;...&#x05D2; &gt; d&#x202C;</div>
michael@0 49 </div>
michael@0 50 </body>
michael@0 51 </html>

mercurial