Use standalone widget pages rather than the integrated widget sampler

Use standalone widget pages rather than the integrated widget sampler

We'll add an integrated page as a further test case next.

Also, this fixes the missing URL for core-scroll-header

BUG=401203, 394756
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=290698

[Sami, 2014-08-07 14:51:06]

lgtm assuming the answer to my question is yes :)

https://codereview.chromium.org/451483002/diff/20001/tools/perf/page_sets/pol...
File tools/perf/page_sets/polymer.py (right):

https://codereview.chromium.org/451483002/diff/20001/tools/perf/page_sets/pol...
tools/perf/page_sets/polymer.py:108: self.iframe_js = 'document'
Are you planning to use this same code for the integrated page test you
mentioned? If not, it's probably worth cleaning up |iframe_js| and the other
iframe weirdness from here.

[Sami, 2014-08-07 14:53:50]

Of course I wouldn't be opposed also to cleaning up the logic a little to
prepare for the combined use case too. Something like a |is_standalone_widget|
parameter.

[tonyg, 2014-08-09 18:17:32]

lgtm

https://codereview.chromium.org/451483002/diff/20001/tools/perf/page_sets/pol...
File tools/perf/page_sets/polymer.py (right):

https://codereview.chromium.org/451483002/diff/20001/tools/perf/page_sets/pol...
tools/perf/page_sets/polymer.py:112:
#action_runner.ExecuteJavaScript('window.location.href="about:blank";')
Don't we want to completely remove the above two lines rather than comment out?

[wiltzius, 2014-08-19 22:29:22]

The CQ bit was checked by wiltzius@chromium.org

[wiltzius, 2014-08-19 22:30:32]

On 2014/08/09 18:17:32, tonyg wrote:
> lgtm
> 
>
https://codereview.chromium.org/451483002/diff/20001/tools/perf/page_sets/pol...
> File tools/perf/page_sets/polymer.py (right):
> 
>
https://codereview.chromium.org/451483002/diff/20001/tools/perf/page_sets/pol...
> tools/perf/page_sets/polymer.py:112:
> #action_runner.ExecuteJavaScript('window.location.href="about:blank";')
> Don't we want to completely remove the above two lines rather than comment
out?

Yes, done.

I've got a new patch set up that addresses that and updates the WPR archives
because some of the underlying pages have changed.

Sami, I do intend to use this for the end-to-end flow, so I'm skipping that
refactor for now. Highest priority is getting the page set passing again :)

Hitting commit because I believe this will fix the failing perf bots (it
consistently runs successfully on my local N5, using no page filter). Will
babysit it.

[commit-bot: I haz the power, 2014-08-19 22:31:28]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/wiltzius@chromium.org/451483002/40001

[commit-bot: I haz the power, 2014-08-19 23:42:52]

Committed patchset #3 (40001) as 290698