I have a CL that does this at https://codereview.chromium.org/2949313002. Updated all WebUI tests accordingly, but it requires some more work to get the PDFExtensionTest to work [1]. Essentially instead of accessing mock-interactions.js [2] from a chrome:// URL it should be made available otherwise only during testing. @pdf OWNERS: Any ideas on how to include mock-interactions.js during testing? [1] https://cs.chromium.org/chromium/src/chrome/browser/pdf/pdf_extension_test.cc [2] https://cs.chromium.org/chromium/src/third_party/polymer/v1_0/components-chromium/iron-test-helpers/mock-interactions.js
Figured out how to load mock-interactions.js alternatively during PDFExtensionTest, see https://codereview.chromium.org/2949883006.
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4bf10fb33e766df1ec8071c27cfb5a13dd7edc88 commit 4bf10fb33e766df1ec8071c27cfb5a13dd7edc88 Author: dpapad <dpapad@chromium.org> Date: Sat Jun 24 07:19:39 2017 PDFExtensionTest: Stop using chrome:// URL to load mock-interactions.js This is in preparation of removing Polymer's testing related files from the production binary. BUG= 736124 Review-Url: https://codereview.chromium.org/2949883006 Cr-Commit-Position: refs/heads/master@{#482144} [modify] https://crrev.com/4bf10fb33e766df1ec8071c27cfb5a13dd7edc88/chrome/browser/pdf/pdf_extension_test.cc [modify] https://crrev.com/4bf10fb33e766df1ec8071c27cfb5a13dd7edc88/chrome/test/BUILD.gn [modify] https://crrev.com/4bf10fb33e766df1ec8071c27cfb5a13dd7edc88/chrome/test/data/pdf/basic_test.js [modify] https://crrev.com/4bf10fb33e766df1ec8071c27cfb5a13dd7edc88/chrome/test/data/pdf/material_elements_test.js [modify] https://crrev.com/4bf10fb33e766df1ec8071c27cfb5a13dd7edc88/chrome/test/data/pdf/page_change_test.js [modify] https://crrev.com/4bf10fb33e766df1ec8071c27cfb5a13dd7edc88/chrome/test/data/pdf/test_util.js [modify] https://crrev.com/4bf10fb33e766df1ec8071c27cfb5a13dd7edc88/chrome/test/data/pdf/toolbar_manager_test.js
https://codereview.chromium.org/2949313002 also refers to this bug, but was not marked appropriately.
Comment 1 by dpa...@chromium.org
, Jun 23 2017