-
tonyg@chromium.org authored
This picks up a change which reverts the use-closest-match functionality to find the closest match using ratio() instead of quick_ratio(). This fixes the ability to sign in to google accounts on Android which fixes the smoothness_measurement. Since ratio() is more expensive than quick_ratio(), it may also cause the page cyclers to regress a little on all platforms. This is not a chrome regression. BUG=252786 NOTRY=True TBR=slamm@google.com Review URL: https://codereview.chromium.org/16943014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207880 0039d316-1c4b-4281-b951-d872f2087c98
fb539f2e
