Skip to content

.getAttribute('outerHTML') stopped working #496

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

Open
4Tel-SteveM opened this issue Jun 4, 2021 · 3 comments
Open

.getAttribute('outerHTML') stopped working #496

4Tel-SteveM opened this issue Jun 4, 2021 · 3 comments

Comments

@4Tel-SteveM
Copy link

Hello,

This is my first issue so my apologies if I mess anything up.

I ran webdriver-manager update the other day as it a testing session could not be started (this appeared to be due to a chrome update). Then I noticed that .getAttribute('outerHTML') started returning null where it was previously working. I reported this to my colleagues and it worked on their systems, until they did the update. We tested one system specifically and .getAttribute('outerHTML') worked immediately before running webdriver-manager update and then it failed afterwards.

webdriver-manager version tells me that I am running I/version - webdriver-manager 12.1.7 which is a little confusing as i can see that webdriver-manager 12.1.8 was released 5 months ago.

We are using
Protractor: Version 5.4.3
Jasmine: jasmine v3.5.0 jasmine-core v3.5.0
Chrome : Version 91.0.4472.77 (Official Build) (64-bit)

Is this issue known? is it just on my end? is anyone else experiencing this?

@nataliaDem
Copy link

Hello!

I have the same issue. I've investigated that it's happen due to the latest version of chromedriver
https://bugs.chromium.org/p/chromium/issues/detail?id=1205107
This bug affects on .getAttribute(), .getText() and others methods which requires attribute getting.

Can't understand the status of issue, but there is a commit to fix that on chromium https://chromium.googlesource.com/chromium/src/+/ccdde0d5a2741228c88e8cdfa1c5fc87fc690bf6%5E%21/#F0
Waiting for new version of chromedriver with fix.

@4Tel-SteveM
Copy link
Author

Thank you for the reply @nataliaDem.
It is interesting that the first link talks about the issue being related to "w3c:false" which they used due to issues with sending keys.
I believe that we have also turned W3C off for the same reason.
I will have to look into it further.
Thanks again.

@Splaktar
Copy link

Duplicate issue #497 has a lot of updated information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants