Summarized test results:
HTML5, the ruby element and its children

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 browsers support ruby markup.

Updated

These tests check whether user agents support styling and basic default positioning of markup based on ruby markup, including the elements ruby, rb, rt, and rtc.

Note that the snapshot summaries of 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 themselves do not test any vendor prefixes.

results

The tables show results for tests run on the date shown. Above the tables are summaries of the results at that date. The table data may be more up-to-date than the summary. If the tables contain some incorrectly scored tests, or tests that relate to non-released versions of browsers, these are not included in the summary.

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.

Ruby markup styling

Snapshot summary, 2014-02-18
Firefox 33.0, Chrome 35.0.1916.153, Safari 8.0, Internet Explorer 11, Opera 22.0

Firefox and Safari pass all tests, indicating that they have updated their parsers to the HTML5 spec. (Chrome nightlies also pass but those restuls are not recorded here until they are merged in the released version.)

Test link Assertion Details
rb styling, full markup rb elements can be styled when fully marked up.
rb styling, only start tags rb elements can be styled when only start tags are used.
rb styling, rb,rb,rt,rt format rb elements can be styled when all tags are used but all rb elements are grouped together.
rb styling, rb,rb,rt,rt format, start tags only rb elements can be styled when only start tags are used and all rb elements are grouped together.
rt styling, full markup rt elements can be styled when fully marked up.
rt styling, only start tags rt elements can be styled when only start tags are used.
rt styling, rb,rb,rt,rt format rt elements can be styled when all tags are used but all rt elements are grouped together.
rt styling, rb,rb,rt,rt format, start tags only rt elements can be styled when only start tags are used and all rt elements are grouped together.
ruby styling, span on ruby base It is possible to style part of the ruby base text using a span element.
ruby styling, span on ruby annotation It is possible to style part of the ruby annotation text using a span element.

Single-sided ruby position

Snapshot summary, 2014-02-18
Firefox 33.0, Chrome 35.0.1916.153, Safari 8.0, Internet Explorer 11, Opera 22.0

Only Firefox does no positioning of ruby text above the base characters. Support is still limited to simple cases, however.

Test link Assertion Details
ruby position, full markup Ruby annotations appear, by default, alongside the appropriate base text when full markup is used.
ruby position, no rb tag Ruby annotations appear, by default, alongside the appropriate base text when no rb tags are used.
ruby position, only start tags Ruby annotations appear, by default, alongside the appropriate base text when only start tags are used.
ruby position, rb,rb,rt,rt format Ruby annotations appear, by default, alongside the appropriate base text when all tags are used but all rb elements are grouped together.
ruby position, rb,rb,rt,rt format, start tags only Ruby annotations appear, by default, alongside the appropriate base text when only start tags are used and all rb elements are grouped together.

Double-sided ruby

Snapshot summary, 2014-02-18
Firefox 33.0, Chrome 35.0.1916.153, Safari 8.0, Internet Explorer 11, Opera 22.0

The only support for double-sided ruby is for nested mono+group ruby in Chrome/Opera and Safari.

Test link Assertion Details
double-sided ruby, mono, one rtc If there are two sets of mono-ruby annotations, and only one rtc element, both are placed alongside the base text, and alongside the appropriate base character.
double-sided ruby, mono, 2 rtcs If there are two sets of mono-ruby annotations, in two rtc elements, both are placed alongside the base text, and alongside the appropriate base character.
double-sided ruby, mono+group, one rtc If there are two sets of ruby annotations, the first mono- the second group-ruby, and one rtc element, both are placed alongside the base text, with mono-ruby alongside the appropriate base character, and group-ruby spanning all.
double-sided ruby, mono+group, two rtcs If there are two sets of ruby annotations, the first mono- the second group-ruby, and one rtc element, both are placed alongside the base text, with mono-ruby alongside the appropriate base character, and group-ruby spanning all.
double-sided ruby, group+mono, one rtc If there are two sets of ruby annotations, the first group- the other mono-ruby, and one rtc element, both are placed alongside the base text, with mono-ruby alongside the appropriate base character, and group-ruby spanning all.
double-sided ruby, group+mono, two rtcs If there are two sets of ruby annotations, the first group- the other mono-ruby, in two rtc elements, both are placed alongside the base text, with mono-ruby alongside the appropriate base character, and group-ruby spanning all.
double-sided ruby, mono+group, nested If there are two sets of ruby annotations, the first is mono-ruby in a nested ruby element, the second group-ruby, both are placed alongside the base text, with mono-ruby alongside the appropriate base character, and group-ruby spanning all.
double-sided ruby, mono, rt+rtc If there are two sets of mono-ruby annotations, marked up using rt elements immediately followed by rtc elements, the each annotation is placed alongside the appropriate base character.

Ruby annotation gaps

Snapshot summary, 2014-02-18
Firefox 33.0, Chrome 35.0.1916.153, Safari 8.0, Internet Explorer 11, Opera 22.0

Firefox doesn't position ruby text anyway (see above). All the other browsers leave a gap in the rendered ruby for an empty rt element only when the rb and rt markup is interleaved.

Test link Assertion Details
ruby gaps, interleaved An empty rt element causes a gap above it's associated base text in interleaved rb/rt markup.
ruby gaps, separated An empty rt element causes a gap above it's associated base text in markup where all rts appear grouped after all the rbs.