Summary: | find-in-page fails on ruby-annotated text | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Fuqiao Xue <xfq.free> | ||||
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | NEW --- | ||||||
Severity: | Normal | CC: | bfulgham, ishida, mmaxfield, simon.fraser, webkit-bug-importer, zalan | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
There's some more detail, and links to a couple of tests, at https://w3c.github.io/jlreq/gap-analysis/#issue255_inline_notes This is important for klreq. See https://w3c.github.io/klreq/gap-analysis/#issue34_inline_notes |
Created attachment 423680 [details] find-in-page fails on ruby-annotated text If text is marked up for ruby, find-in-page no longer recognizes 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.