-
Notifications
You must be signed in to change notification settings - Fork 17
In-page search fails on ruby-annotated text #255
Copy link
Copy link
Open
Labels
doc:clreqdoc:jlreqUsed for gap analysis (only) to indicate target document.Used for gap analysis (only) to indicate target document.doc:klreqdoc:mlreqgapThe first comment in this issue is read by the gap-analysis document.The first comment in this issue is read by the gap-analysis document.i:inline_notesInline notes & annotationsInline notes & annotationsl:jaJapaneseJapanesep:basicUsed for gap analysis issues (only) to indicate priority.Used for gap analysis issues (only) to indicate priority.s:jpanJapanese scriptJapanese scriptx:blinkx:clreqx:geckox:jpanx:mongx:webkit
Description
Metadata
Metadata
Assignees
Labels
doc:clreqdoc:jlreqUsed for gap analysis (only) to indicate target document.Used for gap analysis (only) to indicate target document.doc:klreqdoc:mlreqgapThe first comment in this issue is read by the gap-analysis document.The first comment in this issue is read by the gap-analysis document.i:inline_notesInline notes & annotationsInline notes & annotationsl:jaJapaneseJapanesep:basicUsed for gap analysis issues (only) to indicate priority.Used for gap analysis issues (only) to indicate priority.s:jpanJapanese scriptJapanese scriptx:blinkx:clreqx:geckox:jpanx:mongx:webkit
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Browser bug raised
This issue is applicable to all languages that use ruby markup.
Inline annotations (often referred to as ruby) are commonly used for Japanese, Chinese, Korean, and Mongolian texts to provide information about pronunciation and sometimes meaning. (See What is Ruby?) Users searching for a phrase within a web page should be able to find phrases that correspond to both base text and annotations.
The GAP
If text is marked up for ruby using the interleaved markup approach, currently required by the HTML spec, a browser's in-page search no longer recognises the text. For example, if you search for 東京 (Tokyo) on a page that has this markup:
<ruby><rb>東<rt>とう<rb>京<rt>きょう</ruby>the search will fail to locate the word.
Note that a tabular arrangement of markup, such as
<ruby><rb>東<rb>京<rt>とう<rt>きょう</ruby>would work fine but, although it is parsed correctly, this tabular markup is currently not displayed correctly by Blink or Webkit, and therefore the HTML specification has obsoleted the
rbandrtcelements.The HTML specification currently blocks the workaround (which is to use tabular markup), but a solution needs to also be found for the interleaved markup.
Blink and Webkit browsers all fail to recognise strings when they have ruby text. Gecko appears to recognise the search string in the ruby element, but doesn't display the highlight correctly (see #255 (comment)). (If you copy the text, you also get the ruby text, but not the one at the end of the ruby element.)
Gecko, Blink, and Webkit browsers all recognise strings when they have ruby text arranged in tabular format, however support for that arrangement was removed from the HTML spec because currently only Gecko and Amazon have browsers that display the markup correctly.
Priority
This is an obstacle to basic interaction with web pages, especially while the HTML spec blocks the use of tabular markup.
Tests
Interactive test, In page search will find text that has ruby annotations in interleaved markup
Interactive test, In page search will find text that has ruby annotations in tabular markup
Action taken
Browser bug reports: Gecko • Blink • Webkit
Work is in preparation in the W3C HTML Working Group to spec out the full ruby model in a way that can be incorporated into the WhatWG spec in future.
Outcomes
tbd