Intended audience: users, XHTML/HTML coders (using editors or scripting), script developers (PHP, JSP, etc.), CSS coders, Web project managers, and anyone who wants to know whether ruby markup works in current browsers.
These tests check whether user agents correctly apply the new markup added to HTML5 to improve handling of bidirectional text in languages such as Arabic, Hebrew, Persian, Thaana, Urdu, etc.
Note that these test results are for released versions of the browsers tested. Versions that are still in development may provide better support for these features. The tests do not use any vendor prefixes.
A number of tests could not be fully checked because there was no font on the system to support one or more of the glyphs in the test. These tests were skipped.
To see the test, click on the link in the left-most column. To see detailed results for a single test, click on the link in the right-most column. To submit test data for a single test, click on the link in the right-most column and then follow the link on that page.
The tables show the latest results from the W3C Test Framework. Below the tables are summaries of the results at a given date. The table data may be more up-to-date than the summary. The tables may also contain some incorrectly scored tests, and tests that relate to non-released versions of browsers. These are not included in the summary.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| BDI: has dir=auto by default | 'The dir global attribute defaults to auto on this element (it never inherits from the parent element like with other elements).' | bidi-html5-001 | ||||
| BDI: neutral when BR | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' Thus, a BDI containing a BR (which serves as a paragraph break in the content of the BDI) must not serve as a paragraph break in the content around the BDI. | bidi-html5-002 | ||||
| BDI: neutral when contains LRO or RLO without PDF | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' Thus, if a BDI contains LRO or RLO characters lacking a matching PDF, these must not affect the visual ordering of the content outside the BDI. | bidi-html5-003 | ||||
| BDI: neutral when nested | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' This must apply when a BDI is nested within a BDI. | bidi-html5-004 | ||||
| BDI: neutral when number | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' | bidi-html5-005 | ||||
| BDI: paragraph-level container | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' Thus, under no circumstances should any part of the content outside a BDI be visually reordered inside the BDI's content. | bidi-html5-006 | ||||
| BDI: neutral to following letter | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' | bidi-html5-007 | ||||
| BDI: neutral to immediately following letter | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' | bidi-html5-008 | ||||
| BDI: neutral to preceding letter | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' | bidi-html5-009 | ||||
| BDI: neutral to immediately preceding letter | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' | bidi-html5-010 | ||||
| BDI: neutral to following number | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' | bidi-html5-011 | ||||
| BDI: neutral to immediately following number | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' | bidi-html5-012 | ||||
| BDI: neutral to surrounding letters | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' Thus, regardless of its content and its dir attribute (if any), a BDI will not prevent a strongly RTL (or LTR) character preceding it from forming a single directional run with another strongly RTL (LTR) character following it. | bidi-html5-013 | ||||
| BDI: neutral when wrapped | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' Obviously, this should hold even if the BDI's content is wrapped over more than one line. A single character (U+FFFC or otherwise) obviously never gets wrapped over more than one line, but we still expect the part of the content preceding the BDI, if any, that is displayed on the same line as some part of the BDI to be ordered the same as it would be if that part of the BDI were replaced with U+FFFC. Similarly, we expect the part of the content following the BDI, if any, that is displayed on the same line as some part of the BDI to be ordered the same as it would be if that part of the BDI were replaced with U+FFFC. | bidi-html5-014 | ||||
| BDI: paragraph-level container | 'For the purposes of applying the bidirectional algorithm to the contents of a bdi element, user agents must treat the element as a paragraph-level container.' Thus, under no circumstances should the content outside a BDI affect the visual ordering of the BDI's content. | bidi-html5-015 | ||||
| BDI: neutral to another BDI | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' Thus, when a BDIs contains text of the same strong direction as another BDI following it, the two must not form a directional run as would be the case if the BDIs were just SPANs. | bidi-html5-016 | ||||
| BDI: neutral to another immediately following BDI | 'For the purposes of applying the bidirectional algorithm to the paragraph-level container that a bdi element finds itself within, the bdi element must be treated like a U+FFFC OBJECT REPLACEMENT CHARACTER.' Thus, when a BDIs contains text of the same strong direction as another BDI following it, the two must not form a directional run as would be the case if the BDIs were just SPANs, even if the two BDIs are not separated by anything at all. | bidi-html5-017 |
Links: Section 4.6.23 • Latest results for section 4.6.23 • Submit data for section 4.6.23 • Related tests
The bdi element isolates text from its surrounding content for the purposes of the Unicode Bidirectional Algorithm, and automatically sets the value of the dir attribute if none is explicity set.
Support for the bdi element is still either weak or non-existent. Only Firefox and Chrome pass any of the tests. The number passed by Chrome is increasing, from version to version. Firefox supports a lot more, but still far from all.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| BR separates bidi paragraph | A br element should separate paragraphs for the purposes of the Unicode bidirectional algorithm. | bidi-html5-018 | ||||
| BR in inline ancestors | 'A br element should separate paragraphs for the purposes of the Unicode bidirectional algorithm.' 'If an inline element is broken around a bidi paragraph boundary (e.g. if split by a block or forced paragraph break), then the bidi control codes corresponding to the end of the element are added before the interruption and the codes corresponding to the start of the element are added after it. (In other words, any embedding levels or overrides started by the element are closed at the paragraph break and reopened on the other side of it.)' | bidi-html5-019 |
Links: Section 4.6.26 • Latest results for section 4.6.26 • Submit data for section 4.6.26 • Related tests
This test checks whether a br element separates paragraphs for the purposes of the Unicode bidirectional algorithm.
Of the browsers tested, only Chrome and Firefox do this for both tests.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| newline in pre separates bidi paragraphs | A newline in a pre element should separate paragraphs for the purposes of the Unicode bidirectional algorithm. | bidi-html5-020 |
Links: Section 4.5.3 • Latest results for section 4.5.3 • Submit data for section 4.5.3 • Related tests
This test checks whether a newline in a pre element separates paragraphs for the purposes of the Unicode bidirectional algorithm.
In all browsers except Opera, it did.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| newline in <textarea> separates bidi paragraphs | A newline in a textarea element, and in its raw value, should separate paragraphs for the purposes of the Unicode bidirectional algorithm. | bidi-html5-021 |
Links: Section 4.10.13 • Latest results for section 4.10.13 • Submit data for section 4.10.13 • Related tests
These tests check whether a newline in a textarea element, and in its raw value, separates paragraphs for the purposes of the Unicode bidirectional algorithm.
In all browsers it does.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| dir=auto, inline auto direction | When dir='auto', the direction is set according to the first strong character of the text. dir=auto is applied to an inline element here, in various base direction contexts. | bidi-html5-901 | ||||
| dir=auto, inline isolation | dir='auto' on an inline element will directionally isolate its contents from a following number. | bidi-html5-902 | ||||
| dir=auto, start with L | When dir='auto', the direction is set according to the first strong character of the text. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-057 | ||||
| dir=auto, start with R | When dir='auto', the direction is set according to the first strong character of the text. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-065 |
Links: Section 3.2.3.5 • Latest results for section 3.2.3.5 • Submit data for section 3.2.3.5 • Related tests
This summary applies to the above, basic tests that check whether dir=auto automatically applies direction and isolates its content. See following tables for more detailed tests.
Chrome passes all tests, automatically detecting the direction according to the first strong character, and also isolating content when inline.
Safari does the auto-detection, but doesn't isolate inline content.
Firefox isolates inline content, but doesn't auto-detect direction.
Opera and Internet Explorer don't yet do anything with the auto value of dir.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| dir=auto, isolated in LTR text | When dir='auto', the direction is set according to the first strong character of the text, but the element behaves externally as a neutral character. In this test, it allows a preceding R to form a single directional run with a succeeding number. | bidi-html5-056 | ||||
| dir=auto, start with bdi, then L | When dir='auto', the direction is set according to the first strong character of the text while ignoring bdi elements. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-022 | ||||
| dir=auto, start with bdi, then R | When dir='auto', the direction is set according to the first strong character of the text while ignoring bdi elements. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-023 | ||||
| dir=auto, start with dir=auto, then L | When dir='auto', the direction is set according to the first strong character of the text while ignoring contained elements with an explicit dir of their own. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-024 | ||||
| dir=auto, start with dir=auto, then R | When dir='auto', the direction is set according to the first strong character of the text while ignoring contained elements with an explicit dir of their own. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-025 | ||||
| dir=auto, start with dir, then L | When dir='auto', the direction is set according to the first strong character of the text while ignoring contained elements with an explicit dir of their own. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-026 | ||||
| dir=auto, start with dir, then R | When dir='auto', the direction is set according to the first strong character of the text while ignoring contained elements with an explicit dir of their own. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-027 | ||||
| dir=auto, start with L within contained element | When dir='auto', the direction is set according to the first strong character of the text, including text within contained elements. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-028 | ||||
| dir=auto, start with R within contained element | When dir='auto', the direction is set according to the first strong character of the text, including text within contained elements. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-029 | ||||
| dir=auto, start with script, then L | When dir='auto', the direction is set according to the first strong character of descendant text while ignoring descendant script elements. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-030 | ||||
| dir=auto, start with script, then R | When dir='auto', the direction is set according to the first strong character of descendant text while ignoring descendant script elements. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-031 | ||||
| dir=auto, start with style, then L | When dir='auto', the direction is set according to the first strong character of descendant text while ignoring descendant style elements. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-032 | ||||
| dir=auto, start with style, then R | When dir='auto', the direction is set according to the first strong character of descendant text while ignoring descendant style elements. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-033 | ||||
| dir=auto, start with textarea, then L | When dir='auto', the direction is set according to the first strong character of descendant text while ignoring descendant textarea elements. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-034 | ||||
| dir=auto, start with textarea, then R | When dir='auto', the direction is set according to the first strong character of descendant text while ignoring descendant textarea elements. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-035 | ||||
| dir=auto, start with EN, then L | When dir='auto', the direction is set according to the first strong character of the text. In this test, it is the Latin letter A since digits are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-036 | ||||
| dir=auto, start with EN, then R | When dir='auto', the direction is set according to the first strong character of the text. In this test, it is the Hebrew letter Alef since digits are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-037 | ||||
| dir=auto, start with N, then EN, then L | When dir='auto', the direction is set according to the first strong character of the text. In this test, it is the Latin letter A since neutrals and digits are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-058 | ||||
| dir=auto, start with N, then EN, then R | When dir='auto', the direction is set according to the first strong character of the text. In this test, it is the Hebrew letter Alef since neutrals and digits are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-059 | ||||
| dir=auto, start with N, then EN, then L | When dir='auto', the direction is set according to the first strong character of the text, ignoring neutrals and numbers. If there is no strong character, as in this test, the direction defaults to LTR. | bidi-html5-060 | ||||
| dir=auto, start with N, then L | When dir='auto', the direction is set according to the first strong character of the text. In this test, it is the Latin letter A since neutrals are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-061 | ||||
| dir=auto, start with N, then R | When dir='auto', the direction is set according to the first strong character of the text. In this test, it is the Hebrew letter Alef since neutrals are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-062 |
Links: Section 3.2.3.5 • Latest results for section 3.2.3.5 • Submit data for section 3.2.3.5 • Related tests
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| input with dir=auto, start with L | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-040 | ||||
| input with dir=auto, start with R | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-046 |
Links: Section 3.2.3.5 • Latest results for section 3.2.3.5 • Submit data for section 3.2.3.5 • Related tests
This summary applies to the above, basic tests that check whether dir=auto on the input element automatically applies base direction to the contents of the form field. See following tables for more detailed tests.
Of the browsers tested, only Chrome slides the text to the side of the input field indicated by the first strong character in the input. Safari consistently aligns the input value to the left, which is why it passes one test but not the other. Other browsers tested align the text with regards to the current base direction.
See below for additional tests of auto on the input element .
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| input with dir=auto, start with EN+L | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Latin letter A since digits are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-038 | ||||
| input with dir=auto, start with EN+R | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Hebrew letter Alef since digits are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-039 | ||||
| input with dir=auto, start with N+EN+L | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Latin letter A since neutrals and digits are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-041 | ||||
| input with dir=auto, start with N+EN+R | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Hebrew letter Alef since neutrals and digits are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-042 | ||||
| input with dir=auto, all N+EN | When dir='auto', the direction of an input element is set according to the first strong character of its value, or to LTR if there is no such character. In this test, there is no strongly directional character in the value, thus the direction must be resolved as LTR. | bidi-html5-043 | ||||
| input with dir=auto, start with N+L | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Latin letter A since neutrals are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-044 | ||||
| input with dir=auto, start with N+R | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Hebrew letter Alef since neutrals are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-045 |
Links: Section 3.2.3.5 • Latest results for section 3.2.3.5 • Submit data for section 3.2.3.5 • Related tests
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| input with dir=auto, script assigns to start with EN+L | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Latin letter A since digits are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-047 | ||||
| input with dir=auto, script assigns to start with EN+R | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Hebrew letter Alef since digits are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-048 | ||||
| input with dir=auto, script assigns to start with L | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Latin letter A, thus the direction must be resolved as LTR. | bidi-html5-049 | ||||
| input with dir=auto, script assigns to start with N+EN+L | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Latin letter A since neutrals and digits are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-050 | ||||
| input with dir=auto, script assigns to start with N+EN+R | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Hebrew letter Alef since neutrals and digits are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-051 | ||||
| input with dir=auto, script assigns to all N+EN | When dir='auto', the direction of an input element is set according to the first strong character of its value, or to LTR if there is no such character. In this test, there is no strongly directional character in the value, thus the direction must be resolved as LTR. | bidi-html5-052 | ||||
| input with dir=auto, script assigns to start with N+L | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Latin letter A since neutrals are not strongly directional, thus the direction must be resolved as LTR. | bidi-html5-053 | ||||
| input with dir=auto, script assigns to start with N+R | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Hebrew letter Alef since neutrals are not strongly directional, thus the direction must be resolved as RTL. | bidi-html5-054 | ||||
| input with dir=auto, script assigns to start with R | When dir='auto', the direction of an input element is set according to the first strong character of its value. In this test, it is the Hebrew letter Alef, thus the direction must be resolved as RTL. | bidi-html5-055 |
Links: Section 3.2.3.5 • Latest results for section 3.2.3.5 • Submit data for section 3.2.3.5 • Related tests
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| dir=auto, pre, paragraph by paragraph | When dir='auto', the direction is set according to the first strong character of the text. For pre elements, the heuristic is applied on a per-paragraph level. | bidi-html5-903 | ||||
| pre with dir=auto, mixed L and R paragraphs | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. | bidi-html5-063 | ||||
| pre with dir=auto, all N+EN | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. If there is no strong character, as in this test, the direction defaults to LTR. | bidi-html5-064 | ||||
| pre with dir=auto, all-N between all-Rs | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. If there is no strong character, as in this test, the direction defaults to LTR. | bidi-html5-070 |
Links: Section 3.2.3.5 • Latest results for section 3.2.3.5 • Submit data for section 3.2.3.5 • Related tests
These tests check what effect dir=auto has on the contents of the pre element.
Of the browsers tested, only Firefox aligns the text on a paragraph by paragraph basis according to the first strong character in the paragraph and also assigns base direction on a line by line basis.
Chrome applies base direction on a paragraph by paragraph basis, but the alignment is determined by the first strong character in the pre element, rather than at the start of each paragraph. Safari also bases the alignment on the first strong character in the pre, but doesn't vary the base direction on a line by line basis.
Internet Explorer and Opera both fail to either assign base direction or align according to the content of the pre element at all. Alignment and base direction are those of the surrounding context.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| dir=auto, textarea, paragraph by paragraph | When dir='auto', the direction is set according to the first strong character of the text. For textarea elements, the heuristic is applied on a per-paragraph level. | bidi-html5-904 | ||||
| textarea with dir=auto, mixed L and R paragraphs | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. | bidi-html5-066 | ||||
| textarea with dir=auto, all N+EN | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. If there is no strong character, as in this test, the direction defaults to LTR. | bidi-html5-067 | ||||
| textarea with dir=auto, script assigns to mixed L and R paragraphs | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. | bidi-html5-068 | ||||
| textarea with dir=auto, script assigns to all N+EN | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. If there is no strong character, as in this test, the direction defaults to LTR. | bidi-html5-069 | ||||
| textarea with dir=auto, all-N between all-Rs | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. If there is no strong character, as in this test, the direction defaults to LTR. | bidi-html5-071 | ||||
| textarea with dir=auto, script assigns to all-N between all-Rs | When dir='auto', the direction is set according to the first strong character of the text. For textarea and pre elements, the heuristic is applied on a per-paragraph level. If there is no strong character, as in this test, the direction defaults to LTR. | bidi-html5-072 |
Links: Section 3.2.3.5 • Latest results for section 3.2.3.5 • Submit data for section 3.2.3.5 • Related tests
These tests check what effect dir=auto has on the contents of the textarea element.
The results for textarea are the same as those for pre.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| dirname, ltr | Dir is set to ltr on the input tag. The dirname attribute will cause the direction of the input element to be passed with the form parameters. | bidi-html5-905 | ||||
| dirname, rtl | Dir is set to rtl on the input tag. The dirname attribute will cause the direction of the input element to be passed with the form parameters. | bidi-html5-906 | ||||
| dirname, inherits ltr | Dir is set to ltr on an ancestor of the input tag. The dirname attribute will cause the direction of the input element to be passed with the form parameters. | bidi-html5-907 | ||||
| dirname, inherits rtl | Dir is set to rtl on an ancestor of the input tag. The dirname attribute will cause the direction of the input element to be passed with the form parameters. | bidi-html5-908 | ||||
| dirname, default | No dir attribute is set, so the document is ltr by default. The dirname attribute will cause the direction of the input element to be passed with the form parameters. | bidi-html5-909 | ||||
| dirname, auto, ltr text | The dir attribute is set to auto. If the form field auto-detects ltr direction based on first strong character input, the dirname attribute will cause the direction of the input element to be passed with the form parameters. | bidi-html5-910 | ||||
| dirname, auto, rtl text | The dir attribute is set to auto. If the form field auto-detects rtl direction based on first strong character input, the dirname attribute will cause the direction of the input element to be passed with the form parameters. | bidi-html5-911 | ||||
| dirname, scripted | The dir attribute is set using JavaScript. The dirname attribute will cause the direction of the input element to be passed with the form parameters. | bidi-html5-912 |
Links: Section 4.10.7.3.2 • Latest results for section 4.10.7.3.2 • Submit data for section 4.10.7.3.2 • Related tests
These tests check whether a dirname attribute passes information about the direction of an input field.
Chrome and Opera both support dirname, and pass the direction information to the server.
Unfortunately, Opera doesn't support dir=auto at the moment, which restricts the usefulness of dirname for auto-detection.