[klreq] In-page search fails on ruby-annotated text (#34)

r12a has just created a new issue for https://github.com/w3c/klreq:

== In-page search fails on ruby-annotated text ==
<i class="meta">This issue is applicable to all languages that use ruby markup (Chinese, Japanese, Mongolian, Korean).</i>

If text is marked up for ruby, browser's in-page search no longer recognises the text.  For example, if you search for 東京 on a page that has this markup:

<code>&lt;ruby>&lt;rb>東&lt;rt>とう&lt;rb>京&lt;rt>きょう&lt;/ruby></code>

the search will fail to locate the word.



<b class="subhead">Specs:</b>
This is probably not relevant to W3C specifications.



<b class="subhead">Tests & results:</b>
<i>Interactive test</i>, [In page search will find text that has ruby annotations](https://github.com/w3c/character_phrase_tests/issues/44)<br>
<span class="fail">Gecko</span>, <span class="fail">Blink</span>, and <span class="fail">Webkit</span> browsers all fail to recognise strings when they have ruby text.



<b class="subhead">Browser bug reports:</b>
[Gecko](https://bugzilla.mozilla.org/show_bug.cgi?id=1699599) • [Blink](https://bugs.chromium.org/p/chromium/issues/detail?id=1189963) • [Webkit](https://bugs.webkit.org/show_bug.cgi?id=223493)



<b class="subhead">Priority:</b>
This is an obstacle to basic interaction with web pages.

Please view or discuss this issue at https://github.com/w3c/klreq/issues/34 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 19 March 2021 10:51:24 UTC