-
-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(scaffold-navigation): upgrade to bootstrap v4 and fontawesome v5 #1167
Conversation
@shahabganji could you help to have a look of test_docker_2? I cannot reproduce that protractor error locally.
|
@3cp Sure I will |
9beb9d6
to
fbc6aeb
Compare
fbc6aeb
to
64467ff
Compare
@@ -56,7 +56,8 @@ const config = { | |||
'--disable-renderer-backgrounding', | |||
'--disable-device-discovery-notifications', | |||
'--no-sandbox', | |||
'--disable-dev-shm-usage' | |||
'--disable-dev-shm-usage', | |||
'--window-size=1024,768' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shahabganji this fix did the job. The reason for element not interactable
is that the protractor browser window size is too small.
Nobody knows why the default screen size is so small inside docker(or maybe vm). Explicit window size does the trick.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When element is off screen, protractor says it's not interactable
.
This has been a long requested upgrade.