diff options
author | michaelpg <michaelpg@chromium.org> | 2016-03-14 12:21:42 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2016-03-14 19:23:17 +0000 |
commit | 7441ba884861e8483074a51a9a16b3f632526aa0 (patch) | |
tree | 495c7034cb8298e8f8d2d93f7b2eda02e8eee070 /WATCHLISTS | |
parent | 2082ffeac7b24255684c99255c3c734edc52e1c0 (diff) | |
download | chromium_src-7441ba884861e8483074a51a9a16b3f632526aa0.zip chromium_src-7441ba884861e8483074a51a9a16b3f632526aa0.tar.gz chromium_src-7441ba884861e8483074a51a9a16b3f632526aa0.tar.bz2 |
Use polymer_config.html instead of polymer.html
Polymer must be configured before loading. Several files imported polymer.html and not polymer_config.html. When these files are opened in a browser test, either:
* polymer_config.html is never imported, so the test is run under shady DOM, or
* the file indirectly imports polymer_config.html via its dependencies, causing the configuration to happen after Polymer is already loaded (an error)
Using polymer_config.html in place of polymer.html will eliminate this problem, meaning one less error to debug when writing tests. Since every custom Polymer element should import polymer_config.html, we can just place the actual Polymer import in there.
This CL applies this to MD Downloads, MD Settings, and cr_elements.
Review URL: https://codereview.chromium.org/1767913002
Cr-Commit-Position: refs/heads/master@{#381036}
Diffstat (limited to 'WATCHLISTS')
0 files changed, 0 insertions, 0 deletions