download.prompt_for_download: false does not have effect in images from quay.io/browser/google-chrome-stable

[O5ten]

Hello!

We're doing a migration to moon (2.7.3) from selenoid and are running into issues in regards to download-prompts. It seems that despite setting download.prompt_for_download-pref in chromeOptions it does not have any effect but renders the dialog below. This was not an issue in selenoid with the exact same setup.

I did some debugging and can see that we're setting the same capabilities as we used to.

"Capabilities":{
   "acceptInsecureCerts":true,
   "browserName":"chrome",
   "goog:chromeOptions":{
      "args":[
         "--password-store=basic",
         "--remote-allow-origins=*",
         "start-maximized",
         "--enable-extensions",
         "no-sandbox",
         "disable-dev-shm-usage",
         "use-fake-ui-for-media-stream",
         "--disable-search-engine-cho...",
         "--lang=en"
      ],
      "excludeSwitches":[
         "enable-automation"
      ],
      "prefs":{
         "credentials_enable_service":false,
         "download.default_directory":"/home/git/...",
         "download.directory_upgrade":true,
         "download.prompt_for_download":false,
         "profile.default_content_setting_values.clipboard":1,
         "profile.password_manager_enabled":false
      }
   },
   "moon":"options":{
      "enableVNC":true,
      "enableVideo":true,
      "name":"TelephonyTests:validatePush...",
      "videoName":"TelephonyTests:validatePush..."
   }
}

I'm not sure whether this worked in older browser-versions but i'm sure it worked when using selenoid.
I've also tried backporting the browserimage version to 128.0 (which we used with selenoid) so it doesn't seem to be the version change. I also tried to run with the selenoid/vnc:chrome_128 but that didn't work at all. :D

Any idea on how to move forward here?

[aandryashin]

Do not use download.default_directory, files will be stored to default path /home/user/Downloads where there are permissions to write. пт, 21 февр. 2025 г., 17:24 Mikael Östberg ***@***.***>:

…

Hello! We're doing a migration to *moon* (2.7.3) from *selenoid* and are running into issues in regards to download-prompts. It seems that despite setting download.prompt_for_download-pref in chromeOptions it does not have any effect but renders the dialog below. This was not an issue in selenoid with the exact same setup. image.png (view on web) <https://github.com/user-attachments/assets/483f1323-e667-4a78-9fe2-a66bec5210cb> I did some debugging and can see that we're setting the same capabilities as we used to. "Capabilities":{ "acceptInsecureCerts":true, "browserName":"chrome", "goog:chromeOptions":{ "args":[ "--password-store=basic", "--remote-allow-origins=*", "start-maximized", "--enable-extensions", "no-sandbox", "disable-dev-shm-usage", "use-fake-ui-for-media-stream", "--disable-search-engine-cho...", "--lang=en" ], "excludeSwitches":[ "enable-automation" ], "prefs":{ "credentials_enable_service":false, "download.default_directory":"/home/git/...", "download.directory_upgrade":true, "download.prompt_for_download":false, "profile.default_content_setting_values.clipboard":1, "profile.password_manager_enabled":false } }, "moon":"options":{ "enableVNC":true, "enableVideo":true, "name":"TelephonyTests":"validatePush...", "timeZone":"Europe/Stockholm", "videoName":"TelephonyTests":"validatePush..." } } I'm not sure whether this worked in older browser-versions but i'm sure it worked when using selenoid. I've also tried backporting the browserimage version to 128.0 (which we used with selenoid) so it doesn't seem to be the version change. I also tried to run with the selenoid/vnc:chrome_128 but that didn't work at all. :D Any idea on how to move forward here? — Reply to this email directly, view it on GitHub <#439>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKY23OXURSH2RQF5PYED2L2Q4ZK5AVCNFSM6AAAAABXTLLGCOVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA3DSMJWHE4DSMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> [image: O5ten]*O5ten* created an issue (aerokube/moon#439) <#439> Hello! We're doing a migration to *moon* (2.7.3) from *selenoid* and are running into issues in regards to download-prompts. It seems that despite setting download.prompt_for_download-pref in chromeOptions it does not have any effect but renders the dialog below. This was not an issue in selenoid with the exact same setup. image.png (view on web) <https://github.com/user-attachments/assets/483f1323-e667-4a78-9fe2-a66bec5210cb> I did some debugging and can see that we're setting the same capabilities as we used to. "Capabilities":{ "acceptInsecureCerts":true, "browserName":"chrome", "goog:chromeOptions":{ "args":[ "--password-store=basic", "--remote-allow-origins=*", "start-maximized", "--enable-extensions", "no-sandbox", "disable-dev-shm-usage", "use-fake-ui-for-media-stream", "--disable-search-engine-cho...", "--lang=en" ], "excludeSwitches":[ "enable-automation" ], "prefs":{ "credentials_enable_service":false, "download.default_directory":"/home/git/...", "download.directory_upgrade":true, "download.prompt_for_download":false, "profile.default_content_setting_values.clipboard":1, "profile.password_manager_enabled":false } }, "moon":"options":{ "enableVNC":true, "enableVideo":true, "name":"TelephonyTests":"validatePush...", "timeZone":"Europe/Stockholm", "videoName":"TelephonyTests":"validatePush..." } } I'm not sure whether this worked in older browser-versions but i'm sure it worked when using selenoid. I've also tried backporting the browserimage version to 128.0 (which we used with selenoid) so it doesn't seem to be the version change. I also tried to run with the selenoid/vnc:chrome_128 but that didn't work at all. :D Any idea on how to move forward here? — Reply to this email directly, view it on GitHub <#439>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKY23OXURSH2RQF5PYED2L2Q4ZK5AVCNFSM6AAAAABXTLLGCOVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA3DSMJWHE4DSMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[O5ten]

Do not use download.default_directory, files will be stored to default
path /home/user/Downloads where there are permissions to write.

Do you think that is the cause?

[aandryashin]

IHMO permissions are caused the issue, in moon browser runs as regular user. вс, 23 февр. 2025 г., 17:14 Mikael Östberg ***@***.***>:

…

Do not use download.default_directory, files will be stored to default path /home/user/Downloads where there are permissions to write. Do you think that is the cause? — Reply to this email directly, view it on GitHub <#439 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKY23NHJWWQVD5KSGDCHJL2RHJVFAVCNFSM6AAAAABXTLLGCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWHA4DINZZGI> . You are receiving this because you commented.Message ID: ***@***.***> [image: O5ten]*O5ten* left a comment (aerokube/moon#439) <#439 (comment)> Do not use download.default_directory, files will be stored to default path /home/user/Downloads where there are permissions to write. Do you think that is the cause? — Reply to this email directly, view it on GitHub <#439 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKY23NHJWWQVD5KSGDCHJL2RHJVFAVCNFSM6AAAAABXTLLGCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWHA4DINZZGI> . You are receiving this because you commented.Message ID: ***@***.***>

[O5ten]

It seems to work, thank you!