Further ensure that PDFFindController._requestMatchesCount won't return broken data (PR 10052 follow-up)

This prevents the findbar from intermittently displaying `0 of {number} matches`, which *could* theoretically happen for large and/or slow loading documents.
This commit is contained in:
Jonas Jenwald 2018-09-13 11:40:12 +02:00
parent fafd8819bc
commit be7fdf148c

View File

@ -510,7 +510,7 @@ class PDFFindController {
// When searching starts, this method may be called before the `pageMatches` // When searching starts, this method may be called before the `pageMatches`
// have been counted (in `_calculateMatch`). Ensure that the UI won't show // have been counted (in `_calculateMatch`). Ensure that the UI won't show
// temporarily broken state when the active find result doesn't make sense. // temporarily broken state when the active find result doesn't make sense.
if (current > total) { if (current < 1 || current > total) {
current = total = 0; current = total = 0;
} }
return { current, total, }; return { current, total, };