-
Notifications
You must be signed in to change notification settings - Fork 1.4k
browser.expect.element().value.equals() works with Chrome 90, but not 91 #2730
Replies: 2 comments · 8 replies
-
that can be due to changes in chromedriver, not finding the element any more. can you post a verbose log? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Probably worth noting that the element I'm testing is actually a custom element wrapper around an input. With Chrome 90, that
Is this |
Beta Was this translation helpful? Give feedback.
All reactions
-
I tried switching my test to browser.expect
.element(input)
.to.have.property('value')
.equals('typed input string'); But that results in a 500 error
|
Beta Was this translation helpful? Give feedback.
All reactions
-
The property endpoint is only available for W3C Webdriver compatible drivers, so you'll need to set |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi! i think this could be the same problem, after chrome 91 this is happening: I`m using 'elementIdValue' and 'elementIdAttribute', he finds the element but the value is always null: My code:
Log of both callbacks:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
can you please run nightwatch in '--verbose' mode and paste the logs here |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Complete log chrome 91:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Log chrome 91:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Log using chrome 90
|
Beta Was this translation helpful? Give feedback.
All reactions
-
@Dharin-shah @beatfactor Using chrome 90: returns value: '(48) 99999-9999' |
Beta Was this translation helpful? Give feedback.
-
I'm more curious than anything what would cause this to stop working in the latest Chrome.
I use browserstack, and I just realized that I don't set a
browser_version
for chrome, so browserstack has been giving me the latest. Some of our tests started failing recently, particularly ones that expect a value:This works in Chrome 90, but not 91. I get the error:
What would cause this to behave differently? Is this a bug in Chrome?
Beta Was this translation helpful? Give feedback.
All reactions