Commit 2fa627cb authored by dmazzoni@chromium.org's avatar dmazzoni@chromium.org

Call reportFindInPageResultToAccessibility from additional code path.

We should always call reportFindInPageResultToAccessibility whenever
reportFindInPageSelection is called; previously we were only calling it
from TextFinder::find and that didn't cover all cases.

BUG=426414

Review URL: https://codereview.chromium.org/719913002

git-svn-id: svn://svn.chromium.org/blink/trunk@185259 bbb929c8-8fbe-4397-9dbb-9b2b20218538
parent 0bdf4bde
......@@ -191,7 +191,6 @@ bool TextFinder::find(int identifier, const WebString& searchText, const WebFind
if (selectionRect) {
*selectionRect = ownerFrame().frameView()->contentsToWindow(m_activeMatch->boundingBox());
reportFindInPageSelection(*selectionRect, m_activeMatchIndexInCurrentFrame + 1, identifier);
reportFindInPageResultToAccessibility(identifier);
}
}
......@@ -449,6 +448,10 @@ void TextFinder::reportFindInPageSelection(const WebRect& selectionRect, int act
// Update the UI with the latest selection rect.
if (ownerFrame().client())
ownerFrame().client()->reportFindInPageSelection(identifier, ordinalOfFirstMatch() + activeMatchOrdinal, selectionRect);
// Update accessibility too, so if the user commits to this query
// we can move accessibility focus to this result.
reportFindInPageResultToAccessibility(identifier);
}
void TextFinder::resetMatchCount()
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment