[wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-13 Thread 'watirQ' via Watir General
No. This works as the very beginning, but the browser sill jumps into the front of the screen as soon as it's loading.. 在 2019年4月11日星期四 UTC+8上午9:27:21,NaviHan写道: > > args = ['--window-position=-3000,0'] > browser = Watir::Browser.new :chrome, options: {args: args} > > Doesnt work either. >

[wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-10 Thread NaviHan
args = ['--window-position=-3000,0'] browser = Watir::Browser.new :chrome, options: {args: args} Doesnt work either. Can the OP confirm if it works for him? On Wednesday, 10 April 2019 22:42:13 UTC+10, watirQ wrote: > > Experts > > Each time when use .goto or open a new tab, the browser win

[wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-10 Thread Justin Ko
The --window-position arguments should be without a space - eg: args = ['--window-position=-3000,0'] browser = Watir::Browser.new :chrome, options: {args: args} Note that this is just positioning it off-screen; not actually minimizing. Justin On Wednesday, April 10, 2019 at 12:33:41 PM UTC-4,

Re: [wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-10 Thread Titus Fortner
I think it needs to be two strings separated by a comma. I have no idea if it actually works. On Wed, Apr 10, 2019, 11:33 AM NaviHan wrote: > Tried this, browser didnt minimize > > args = ['--allow-running-insecure-content --window-position=-3000, 0'] > browser = Watir::Browser.new :chrome,

[wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-10 Thread NaviHan
Tried this, browser didnt minimize args = ['--allow-running-insecure-content --window-position=-3000, 0'] browser = Watir::Browser.new :chrome, options: {args: args} Titus is this correct? On Wednesday, 10 April 2019 22:42:13 UTC+10, watirQ wrote: > > Experts > > Each time when use .goto or

Re: [wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-10 Thread rajagopalan madasami
It would still bring the screen to the front when alert appears. On Wed, 10 Apr, 2019, 9:50 PM Titus Fortner, wrote: > You can set it up to move off the screen when it opens by passing in the > args to the ChromeOptions class: > https://peter.sh/experiments/chromium-command-line-switches/#window

Re: [wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-10 Thread Titus Fortner
You can set it up to move off the screen when it opens by passing in the args to the ChromeOptions class: https://peter.sh/experiments/chromium-command-line-switches/#window-position it probably will still steal focus momentarily even if it isn't on top of your screen, On Wednesday, April 10

Re: [wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-10 Thread rajagopalan madasami
But it will still shows up for some seconds. On Wed, 10 Apr, 2019, 7:42 PM NaviHan, wrote: > Try this after you open the browser > browser.window.move_to(-3000, 0) > > This will minimize the window > > On Wednesday, 10 April 2019 22:42:13 UTC+10, watirQ wrote: >> >> Experts >> >> Each time when

[wtr-general] Re: How to keep the Watir browser run on the backend?

2019-04-10 Thread NaviHan
Try this after you open the browser browser.window.move_to(-3000, 0) This will minimize the window On Wednesday, 10 April 2019 22:42:13 UTC+10, watirQ wrote: > > Experts > > Each time when use .goto or open a new tab, the browser window will lump > to the frontend of the screen. How to keep the