Commit 4179009f authored by David Bokan's avatar David Bokan Committed by Commit Bot

Fix setBrowserControlsState calls in tests

r488774 added a new parameter to this method but a few tests were
forgotten or added in the mean time. The tests weren't failing (default
arguments were ok) but this fixes them explicitly.

Bug: 711828
Change-Id: Ie9f0619aedc2661912c397c2c4572e7f43e18c66
Reviewed-on: https://chromium-review.googlesource.com/587911Reviewed-by: default avatarMatthew Jones <mdjones@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#490116}
parent 583c9dc6
......@@ -8,7 +8,7 @@
// NOTE: It is important that this test be run with the Android viewport
// flags turned on.
if (window.internals) {
window.internals.setBrowserControlsState(100, false);
window.internals.setBrowserControlsState(100, 0, false);
}
addEventListener("load", function() {
......
......@@ -8,7 +8,7 @@
// NOTE: It is important that this test be run with the Android viewport
// flags turned on.
if (window.internals) {
window.internals.setBrowserControlsState(100, false);
window.internals.setBrowserControlsState(100, 0, false);
}
addEventListener("load", function() {
......
......@@ -8,7 +8,7 @@
// NOTE: It is important that this test be run with the Android viewport
// flags turned on.
if (window.internals) {
window.internals.setBrowserControlsState(100, false);
window.internals.setBrowserControlsState(100, 0, false);
}
addEventListener("load", function() {
......
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