Running with latest Chrome version #167

ReneJBosch · 2022-02-06T15:11:32Z

Latest Chrome version no longer supports the "--disable-infobars" argument, so lorca now runs with the text "Chrome is being controlled by automated test software" in the info-bar.
To be fair ...It does not break the running of the program but it is annoying.
Argument should be replaced by an "enable-automation" Chrome option.

pierrejoye · 2022-02-09T03:25:51Z

While it should be added, in the meantime you can pass custom args to the New method:

func New(url, dir string, width, height int, customArgs ...string) (UI, error)

ReneJBosch · 2022-02-09T15:55:06Z

Yes, I have seen that, but how? It is not just a matter of specifying something like "--enable-automation" because no such argument exists.
It appears to be a Chrome option called "excludeSwitches" which must be followed by an array of such switches, so in this case - as there's only one - by "[enable-automation]". I don't know how to specify that as a (custom) argument (provided you can)

FrankFang · 2022-02-10T12:47:24Z

I could not find a method to set "excludeSwitches" via Chrome's command-line arguments.

pierrejoye · 2022-02-11T03:31:17Z

Ah, it seems to be a flag, experimental, the New method does not allow to pass flags. The chrome instance object must have the methods to enable/disable flags, I did not check yet.

FrankFang · 2022-02-12T05:55:13Z

Any ideas?

gg3083 · 2022-02-17T01:53:38Z

hi guys, Has good idea?

bin16 · 2022-02-19T15:40:26Z

Can you guys check this: https://peter.sh/experiments/chromium-command-line-switches/#enable-automation

--enable-automation | Enable indication that browser is controlled by automation.

It looks that the --enable-automation flag is used to show that message "Chrome is controlled by...", removing it from defaultChromeArgs in ui.go may help.

lorca/ui.go

Line 52 in 1006348

"--enable-automation",

bin16 · 2022-02-19T16:07:29Z

Tiny demo, no message bar and no shadow:

package main

import (
	"os/exec"
)

func main() {
	browser := "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
	args := []string{
		"--no-first-run",
		// "--enable-automation",
		"--app=data:text/html, <h1>hello!</h1>",
		"--window-size=300,200",
		"--remote-debugging-port=0",
		"--user-data-dir=./a/",
	}
	cmd := exec.Command(browser, args...)
	cmd.Start()
}

May be you should clear the user data dir at first.

gg3083 · 2022-02-21T01:40:33Z

Can you guys check this: https://peter.sh/experiments/chromium-command-line-switches/#enable-automation

--enable-automation | Enable indication that browser is controlled by automation.

It looks that the --enable-automation flag is used to show that message "Chrome is controlled by...", removing it from defaultChromeArgs in ui.go may help.

lorca/ui.go

Line 52 in 1006348

"--enable-automation",

it`s work

cgostuff · 2022-02-21T08:37:42Z

Can you guys check this: https://peter.sh/experiments/chromium-command-line-switches/#enable-automation

--enable-automation | Enable indication that browser is controlled by automation.

It looks that the --enable-automation flag is used to show that message "Chrome is controlled by...", removing it from defaultChromeArgs in ui.go may help.

lorca/ui.go

Line 52 in 1006348

"--enable-automation",

it`s work

Doesn't work for me. Did you have to delete some cached data? I pass an empty string to lorca.New dir parameter, so the user data should be deleted already in my case.

gg3083 · 2022-02-21T08:45:02Z

Can you guys check this: https://peter.sh/experiments/chromium-command-line-switches/#enable-automation

--enable-automation | Enable indication that browser is controlled by automation.

It looks that the --enable-automation flag is used to show that message "Chrome is controlled by...", removing it from defaultChromeArgs in ui.go may help.

lorca/ui.go

Line 52 in 1006348

"--enable-automation",

it`s work

Doesn't work for me. Did you have to delete some cached data? I pass an empty string to lorca.New dir parameter, so the user data should be deleted already in my case.

I only modified the source code 'defaultChromeArgs' .
(ui.go 52 line) // '--enable-automation'

cgostuff · 2022-02-21T08:46:24Z

Can you guys check this: https://peter.sh/experiments/chromium-command-line-switches/#enable-automation

--enable-automation | Enable indication that browser is controlled by automation.

It looks that the --enable-automation flag is used to show that message "Chrome is controlled by...", removing it from defaultChromeArgs in ui.go may help.

lorca/ui.go

Line 52 in 1006348

"--enable-automation",

it`s work

Doesn't work for me. Did you have to delete some cached data? I pass an empty string to lorca.New dir parameter, so the user data should be deleted already in my case.

I only modified the source code 'defaultChromeArgs' . (ui.go 52 line) // '--enable-automation'

Strange, I do the same, and "Chrome is being controlled by automated test software" is still shown.

gg3083 · 2022-02-21T08:49:38Z

Can you guys check this: https://peter.sh/experiments/chromium-command-line-switches/#enable-automation

--enable-automation | Enable indication that browser is controlled by automation.

It looks that the --enable-automation flag is used to show that message "Chrome is controlled by...", removing it from defaultChromeArgs in ui.go may help.

lorca/ui.go

Line 52 in 1006348

"--enable-automation",

it`s work

Doesn't work for me. Did you have to delete some cached data? I pass an empty string to lorca.New dir parameter, so the user data should be deleted already in my case.

I only modified the source code 'defaultChromeArgs' . (ui.go 52 line) // '--enable-automation'

Strange, I do the same, and "Chrome is being controlled by automated test software" is still shown.

my code

ui, err := lorca.New("", "", 1366, 768, []string{})

cgostuff · 2022-02-21T08:52:44Z

Can you guys check this: https://peter.sh/experiments/chromium-command-line-switches/#enable-automation

--enable-automation | Enable indication that browser is controlled by automation.

It looks that the --enable-automation flag is used to show that message "Chrome is controlled by...", removing it from defaultChromeArgs in ui.go may help.

lorca/ui.go

Line 52 in 1006348

"--enable-automation",

it`s work

Doesn't work for me. Did you have to delete some cached data? I pass an empty string to lorca.New dir parameter, so the user data should be deleted already in my case.

I only modified the source code 'defaultChromeArgs' . (ui.go 52 line) // '--enable-automation'

Strange, I do the same, and "Chrome is being controlled by automated test software" is still shown.

my code
ui, err := lorca.New("", "", 1366, 768, []string{})

Thanks, now it does work for me too. The issue for me was that the source code was in read-only mode.

cgostuff · 2022-02-23T12:16:53Z

Actually, I've found that removing the "--enable-automation" flag alone is not a great fix. This causes the "save password" bubble to pop up whenever you use lorca to log in somewhere.

This comment explains the side effects of disabling automation: puppeteer/puppeteer#2070 (comment)

The flag "--disable-save-password-bubble" has apparently also been removed a while back. It seems they have made it very difficult to hide both the password bubble and the automation infobar at the same time.

aviscaerulea · 2022-03-14T21:27:54Z

I am also having the same problem.
When I run the code from #167 (comment) the info bar does not show up. However, removing --enable-automation from github.com/zserge/lorca/ui.go in vendor does not hide the info bar.

Deleting Chrome's cache and temporary files did not change the result.

Is there a temporary way to address this issue?

Environments :
Chromium 98.0.4758.106 Built on Debian , running on Debian 11 (on Raspberry Pi 3 aarch64)

cgostuff · 2022-03-31T16:51:56Z

Has anyone had any luck removing both the infobar and the save password prompt at the same time?

On a somewhat related note, I have been able to disable the google translate UI by passing an experimental flag into New() like this: "--disable-features=Translate". Can we perhaps leverage the "--disable-features=x" argument to solve the issue?

Based on some additional research, it seems that the CommandLineFlagSecurityWarningsEnabled policy can actually control the infobar on newer chrome versions, like disable-infobars used to.

Bellisario · 2022-06-20T14:20:41Z

Any solution? I'm having the same problem...

buildnewapp · 2022-07-16T02:48:41Z

modify lorca/ui.go:
remove "--enable-automation",

	"--no-default-browser-check",
	"--safebrowsing-disable-auto-update",
	//"--enable-automation",
	"--password-store=basic",
	"--use-mock-keychain",

it's ok for me, chrome v103 with mac

prospero78 · 2022-11-28T08:50:11Z

modify lorca/ui.go:
remove "--enable-automation",

Two tea for this sir!

tooolbox · 2022-11-30T22:50:05Z

Removing the "--enable-automation" flag from ui.go did solve the problem for me, although I'm concerned about Lorca popping up Save Password dialogs. Ideally this gets a solution which doesn't break something else.

dcboy · 2023-09-15T15:54:03Z

use this args --disable-features=automation

kujirahand mentioned this issue Feb 11, 2022

「chrome は自動テストソフトウェアによって制御されています。」と表示されます kujirahand/nadesiko3webkit#5

Open

bin16 mentioned this issue Feb 23, 2022

remove --enable-automation flag to disable browser is controlled message #169

Open

alonelucky mentioned this issue Apr 10, 2023

Remove --enable-automation and disabled password dialog #187

Open

unlimitun mentioned this issue Aug 29, 2023

can exclude some args from defaultChromeArgs #191

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Running with latest Chrome version #167

Running with latest Chrome version #167

ReneJBosch commented Feb 6, 2022

pierrejoye commented Feb 9, 2022

ReneJBosch commented Feb 9, 2022

FrankFang commented Feb 10, 2022

pierrejoye commented Feb 11, 2022

FrankFang commented Feb 12, 2022

gg3083 commented Feb 17, 2022

bin16 commented Feb 19, 2022 •

edited

Loading

bin16 commented Feb 19, 2022

gg3083 commented Feb 21, 2022

cgostuff commented Feb 21, 2022

gg3083 commented Feb 21, 2022

cgostuff commented Feb 21, 2022

gg3083 commented Feb 21, 2022

cgostuff commented Feb 21, 2022

cgostuff commented Feb 23, 2022 •

edited

Loading

aviscaerulea commented Mar 14, 2022 •

edited

Loading

cgostuff commented Mar 31, 2022 •

edited

Loading

Bellisario commented Jun 20, 2022

buildnewapp commented Jul 16, 2022

prospero78 commented Nov 28, 2022 •

edited

Loading

tooolbox commented Nov 30, 2022

dcboy commented Sep 15, 2023

Running with latest Chrome version #167

Running with latest Chrome version #167

Comments

ReneJBosch commented Feb 6, 2022

pierrejoye commented Feb 9, 2022

ReneJBosch commented Feb 9, 2022

FrankFang commented Feb 10, 2022

pierrejoye commented Feb 11, 2022

FrankFang commented Feb 12, 2022

gg3083 commented Feb 17, 2022

bin16 commented Feb 19, 2022 • edited Loading

bin16 commented Feb 19, 2022

gg3083 commented Feb 21, 2022

cgostuff commented Feb 21, 2022

gg3083 commented Feb 21, 2022

cgostuff commented Feb 21, 2022

gg3083 commented Feb 21, 2022

cgostuff commented Feb 21, 2022

cgostuff commented Feb 23, 2022 • edited Loading

aviscaerulea commented Mar 14, 2022 • edited Loading

cgostuff commented Mar 31, 2022 • edited Loading

Bellisario commented Jun 20, 2022

buildnewapp commented Jul 16, 2022

prospero78 commented Nov 28, 2022 • edited Loading

tooolbox commented Nov 30, 2022

dcboy commented Sep 15, 2023

bin16 commented Feb 19, 2022 •

edited

Loading

cgostuff commented Feb 23, 2022 •

edited

Loading

aviscaerulea commented Mar 14, 2022 •

edited

Loading

cgostuff commented Mar 31, 2022 •

edited

Loading

prospero78 commented Nov 28, 2022 •

edited

Loading