<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - AX: WKContentView needs to implement UITextInput methods to make speak selection highlighting work"
href="https://bugs.webkit.org/show_bug.cgi?id=166955#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - AX: WKContentView needs to implement UITextInput methods to make speak selection highlighting work"
href="https://bugs.webkit.org/show_bug.cgi?id=166955">bug 166955</a>
from <span class="vcard"><a class="email" href="mailto:n_wang@apple.com" title="Nan Wang <n_wang@apple.com>"> <span class="fn">Nan Wang</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=166955#c17">comment #17</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=166955#c15">comment #15</a>)
> > (In reply to <a href="show_bug.cgi?id=166955#c14">comment #14</a>)
> > > > e.g. we want to search for the second "the" in "the car is the fastest in the world" at offset 12 (at "h" of the second "the"), findPlainText might return the range of the first or third "the" depending on the range and direction we passed in.
> > >
> > > What's the desired behavior then?
> >
> > We want it to return the range of the second "the", from offset 11 to 14.
> > This is the closest match to the offset we passed in.
>
> Ah, in that case, we should probably add a new variant of findPlainText that
> does this instead of implementing a brand new text search algorithm in WK2
> layer. The code you're adding doesn't take care of case differences, code
> point equivalency, etc... that we've fixed over many years of the
> development of WebKit.</span >
I think in our case we want case sensitive matched result. But I'll take a look at the findPlainText function.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>