Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Unified Diff: test/runners/chromium_process.js

Issue 29891680: Issue 6986 - Don't use chromium remote interface on Windows (Closed) Base URL: https://hg.adblockplus.org/adblockpluscore/
Patch Set: Removed the changes in chrome_remote_interface Created Nov. 9, 2018, 8:02 p.m.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | test_runner.js » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: test/runners/chromium_process.js
===================================================================
--- a/test/runners/chromium_process.js
+++ b/test/runners/chromium_process.js
@@ -29,21 +29,23 @@
// Chromium 65.0.3325.0 is 530368
// We currently want Chromiun 63, as we still support it and that's the
// loweset version that supports WebDriver.
const CHROMIUM_REVISION = 508578;
function runScript(chromiumPath, script, scriptName, scriptArgs)
{
const options = new chrome.Options()
- .headless()
// Disabling sandboxing is needed on some system configurations
// like Debian 9.
.addArguments("--no-sandbox")
.setChromeBinaryPath(chromiumPath);
+ // Headless doesn't seem to work on Windows.
+ if (process.platform != "win32")
+ options.headless();
const driver = new Builder()
.forBrowser("chrome")
.setChromeOptions(options)
.build();
return executeScript(driver, "Chromium (WebDriver)",
script, scriptName, scriptArgs);
« no previous file with comments | « no previous file | test_runner.js » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld