Fix content verification failures on unusual content script paths
commit73d92c7c8328979eb489a8af59b8d61940a296c6
authorasargent <asargent@chromium.org>
Thu, 10 Sep 2015 19:20:12 +0000 (10 12:20 -0700)
committerCommit bot <commit-bot@chromium.org>
Thu, 10 Sep 2015 19:22:18 +0000 (10 19:22 +0000)
tree25e911453b6ae75fff907f52f0bb95a3139ce171
parenta068d381e200d311d6fa7e387507924d06494b89
Fix content verification failures on unusual content script paths

If content script paths had a leading "./" in them, we'd fail to find
expected hashes for them because we weren't properly stripping the
leading junk from the relative path.

BUG=437675

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

Cr-Commit-Position: refs/heads/master@{#348207}
chrome/browser/extensions/content_verifier_browsertest.cc
chrome/test/data/extensions/content_verifier/dot_slash_paths.crx
chrome/test/data/extensions/content_verifier/dot_slash_paths/_metadata/verified_contents.json [deleted file]
chrome/test/data/extensions/content_verifier/dot_slash_paths/cs1.js [new file with mode: 0644]
chrome/test/data/extensions/content_verifier/dot_slash_paths/cs2.js [new file with mode: 0644]
chrome/test/data/extensions/content_verifier/dot_slash_paths/manifest.json
extensions/browser/content_verifier.cc