Commit fb539f2e authored by tonyg@chromium.org's avatar tonyg@chromium.org

Roll web page replay 513:515.

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
parent ab24fc42
...@@ -240,7 +240,7 @@ deps = { ...@@ -240,7 +240,7 @@ deps = {
"/trunk/tools/deps2git@202885", "/trunk/tools/deps2git@202885",
"src/third_party/webpagereplay": "src/third_party/webpagereplay":
(Var("googlecode_url") % "web-page-replay") + "/trunk@513", (Var("googlecode_url") % "web-page-replay") + "/trunk@515",
"src/third_party/pywebsocket/src": "src/third_party/pywebsocket/src":
(Var("googlecode_url") % "pywebsocket") + "/trunk/src@662", (Var("googlecode_url") % "pywebsocket") + "/trunk/src@662",
......
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