In-page search fails on ruby-annotated text
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 809
- Forks
- 66
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
This issue is applicable to all languages that use ruby markup (Chinese, Japanese, Mongolian, Korean).
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 東京 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 not displayed correctly by Blink or Webkit currently, and therefore the HTML specification has obsoleted the rb and rtc elements.
For more details, see this GitHub issue, which is being used to track this gap.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the interleaved and tabular ruby markup examples in the issue, then review the linked w3c/jlreq issue 255 for the current requirements. No repository files or tests are named; completion would require an agreed resolution for in-page search behavior across the listed languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- internationalization
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100