Prefs change for the ChromeOptions not working

[yzvezdin]

Hi guys,
We need to change the download path and set it via prefs as all the documentation says. However these values are not implemented in Chrome. Default path to Downloads is set and not changed

'goog:chromeOptions': {
            args: ['--disable-extensions', '--auth-server-whitelist="_"', '-window-position=0,0', '--start-maximized','--window-size=1920,1080'].concat(additionalArgs),
            prefs: { 'download.default_directory': `${process.cwd()}\\downloads` }
        }

[christian-bromann]

@yzvezdin the following worked for me:

const { remote } = require('webdriverio')

let browser

const opts = {
    // automationProtocol: 'devtools',
    capabilities: {
        browserName: 'chrome',
        'goog:chromeOptions': {
            prefs: {
                'download.default_directory': __dirname
            }
        }
    }
}

;(async function () {
    browser = await remote(opts)
    await browser.url('https://the-internet.herokuapp.com/download')
    const link = await browser.$("a[href*='some-file.txt']")
    await link.click()
    await browser.pause(5000)

    await browser.deleteSession()
})().catch(async (e) => {
    console.error(e.stack)
    await browser.deleteSession()
})

Note: this of course only works for local test. If you run tests in a remote location (e.g. Selenium Grid or a vendor like Sauce Labs) this obviously won't work.

[Yurii397]

Hey guys,
I'm upgrading the Chrome version from 95 to 112 and am faced with strange behavior, that in v112 I can't set a new download directory using the following options :
prefs: {
directory_upgrade: true,
prompt_for_download: false,
'download.default_directory': global.downloadFolder,
},
The most strange thing is that it only doesn't work in headless mode. In headed it works well.
Tried both Chrome headless (new and old one) - https://developer.chrome.com/articles/new-headless/

BTW, I'm using standalone-service without Pupetter

Is there any idea what was changed or how to handle it?
cc. @christian-bromann @NavyMint

[christian-bromann]

no

[Yurii397]

no

is it a direct Chrome issue?
and maybe any suggestion where it can be reported plz?

[christian-bromann]

you might want to check here: https://chromedriver.chromium.org/

[Yurii397]

I've found a clue! - https://stackoverflow.com/questions/60313027/setting-download-directory-in-webdriver-using-js
in the new versions of Chrome the prefs should be provided like this
prefs: {
'download': {
directory_upgrade: true,
prompt_for_download: false,
'default_directory': global.downloadFolder,
}
I'm still wondering what is the difference between headless and headed mode. why it's working differently. Probably will ask there
@christian-bromann thank you for the help!