You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
I'm experiencing a weird issue and I'm not sure on which side things go wrong.
I have a couple of tests with disabled javascript and disabled cookies. In order to disable js, you need to pass --disable-javascript argument in the chrome arguments; in oder to disable cookies, you need to set profile.default_content_settings.cookies preference to 2. This is proven to work for me.
The problem is that setting prefs object inside the chromeOptions doesn't work for browserstack:
I'm experiencing a weird issue and I'm not sure on which side things go wrong.
I have a couple of tests with disabled javascript and disabled cookies. In order to disable js, you need to pass
--disable-javascript
argument in the chrome arguments; in oder to disable cookies, you need to setprofile.default_content_settings.cookies
preference to2
. This is proven to work for me.The problem is that setting
prefs
object inside thechromeOptions
doesn't work for browserstack:In this case javascript would get disabled, but cookies would be still enabled.
FYI, running the tests locally (changing
seleniumAddress
and omitting browserstack-specific keys) works perfectly.Is it something on the protractor's side, or the problem is browserstack-specific? Thank you.
The text was updated successfully, but these errors were encountered: