Don't report single find match after all matches have already been reported.

Don't report single find match after all matches have already been reported.

There is a place in RenderFrameImpl::OnFind where after one find match is found, it reports that single match just to indicate that there is at least one match in the frame. This is useful when searching the frame for the first time, but pretty meaningless during a "find next" request since the whole frame will have already been searched and all of the matches reported beforehand. It's also detrimental since it will temporarily lower the global match count and then have to recalculate various things when it goes back up.

This patch prevents this single match reply during "find next" requests.

BUG=457440
Committed: https://crrev.com/8d7aa843119033dc876d3017931d0272d048b20e
Cr-Commit-Position: refs/heads/master@{#406008}

[paulmeyer, 2016-07-07 19:15:45]

Description was changed from

==========
Don't report single find match after all matches have already been reported.

There is a place in RenderFrameImpl::OnFind where after one find match is found,
it reports that single match just to indicate that there is at least one match
in that frame. This is useful when searching the frame for the first time, but
pretty meaningless during a "find next" request since the whole frame will have
already been searched and all of the matches reported beforehand. It's also
detrimental since it will temporarily lower the global match count and then have
to recalculate various things when it goes back up.

This patch prevents this single match reply during "find next" requests.

BUG=457440
==========

to

==========
Don't report single find match after all matches have already been reported.

There is a place in RenderFrameImpl::OnFind where after one find match is found,
it reports that single match just to indicate that there is at least one match
in the frame. This is useful when searching the frame for the first time, but
pretty meaningless during a "find next" request since the whole frame will have
already been searched and all of the matches reported beforehand. It's also
detrimental since it will temporarily lower the global match count and then have
to recalculate various things when it goes back up.

This patch prevents this single match reply during "find next" requests.

BUG=457440
==========

[paulmeyer, 2016-07-07 19:16:18]

paulmeyer@chromium.org changed reviewers:
+ nick@chromium.org

[ncarter (slow), 2016-07-07 19:50:40]

lgtm.

I think I'd seen these IPCs arrive when debugging the browser process side, and
was confused by it. So this is cool.

[paulmeyer, 2016-07-07 20:51:28]

The CQ bit was checked by paulmeyer@chromium.org

[commit-bot: I haz the power, 2016-07-07 20:51:54]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-07 22:53:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-07 22:53:46]

Try jobs failed on following builders:
  mac_chromium_gyp_rel on master.tryserver.chromium.mac (JOB_TIMED_OUT, no build
URL)

[commit-bot: I haz the power, 2016-07-07 22:53:46]

Try jobs failed on following builders:
  mac_chromium_gyp_rel on master.tryserver.chromium.mac (JOB_TIMED_OUT, no build
URL)

[paulmeyer, 2016-07-18 14:20:24]

The CQ bit was checked by paulmeyer@chromium.org

[commit-bot: I haz the power, 2016-07-18 14:20:50]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-18 16:08:22]

Description was changed from

==========
Don't report single find match after all matches have already been reported.

There is a place in RenderFrameImpl::OnFind where after one find match is found,
it reports that single match just to indicate that there is at least one match
in the frame. This is useful when searching the frame for the first time, but
pretty meaningless during a "find next" request since the whole frame will have
already been searched and all of the matches reported beforehand. It's also
detrimental since it will temporarily lower the global match count and then have
to recalculate various things when it goes back up.

This patch prevents this single match reply during "find next" requests.

BUG=457440
==========

to

==========
Don't report single find match after all matches have already been reported.

There is a place in RenderFrameImpl::OnFind where after one find match is found,
it reports that single match just to indicate that there is at least one match
in the frame. This is useful when searching the frame for the first time, but
pretty meaningless during a "find next" request since the whole frame will have
already been searched and all of the matches reported beforehand. It's also
detrimental since it will temporarily lower the global match count and then have
to recalculate various things when it goes back up.

This patch prevents this single match reply during "find next" requests.

BUG=457440
==========

[commit-bot: I haz the power, 2016-07-18 16:08:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-18 16:08:36]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-18 16:11:34]

Description was changed from

==========
Don't report single find match after all matches have already been reported.

There is a place in RenderFrameImpl::OnFind where after one find match is found,
it reports that single match just to indicate that there is at least one match
in the frame. This is useful when searching the frame for the first time, but
pretty meaningless during a "find next" request since the whole frame will have
already been searched and all of the matches reported beforehand. It's also
detrimental since it will temporarily lower the global match count and then have
to recalculate various things when it goes back up.

This patch prevents this single match reply during "find next" requests.

BUG=457440
==========

to

==========
Don't report single find match after all matches have already been reported.

There is a place in RenderFrameImpl::OnFind where after one find match is found,
it reports that single match just to indicate that there is at least one match
in the frame. This is useful when searching the frame for the first time, but
pretty meaningless during a "find next" request since the whole frame will have
already been searched and all of the matches reported beforehand. It's also
detrimental since it will temporarily lower the global match count and then have
to recalculate various things when it goes back up.

This patch prevents this single match reply during "find next" requests.

BUG=457440

Committed: https://crrev.com/8d7aa843119033dc876d3017931d0272d048b20e
Cr-Commit-Position: refs/heads/master@{#406008}
==========

[commit-bot: I haz the power, 2016-07-18 16:11:35]

Patchset 1 (id:??) landed as
https://crrev.com/8d7aa843119033dc876d3017931d0272d048b20e
Cr-Commit-Position: refs/heads/master@{#406008}