protractor: Chrome 91 will break more Protractor tests

I can also confirm. I know this is just saying +1, but if we could get the attention of some of the Angular team, it’d be great. Our whole CI/CD pipline is in shatters because of this.

The last chromedriver that worked with getAttribute("value") was version 90.0.4430.24.

Until chromedriver gets patched (which seems like it will be according to this thread posted by @StanislavKharchenko) we use this fix in our ci pipeline to use that version run our angular protractor tests.

This is what out pipline looked like before:

Setup:
    npm install
    node ./node_modules/.bin/webdriver-manager update
Script:
    ng e2e --protractorConfig=./path/to/protractor/config.js

This is what it looks like after:

Setup:
    npm install
    node ./node_modules/.bin/webdriver-manager update --versions.chrome=90.0.4430.24
Script:
    ng e2e --protractorConfig=./path/to/protractor/config.js --webdriver-update false

Good luck!

I also confirm that element.getAttribute(‘value’) where element is input or textarea always returns null when used with chromedriver=91.0.4472.19 (chrome=91.0.4472.77). Also element.clear() doesn’t work anymore.

Workarounds:

// getAttribute('value')
async getValue(elem: ElementFinder): Promise<string> {
    return browser.executeScript(
        'return arguments[0].value',
        await elem.getWebElement()
    );
}
    
// clear();
async clearInput(elem: ElementFinder): Promise<string> {
  return elem.sendKeys(
      protractor.Key.chord(protractor.Key.CONTROL, 'A'), // Linux, Windows
      protractor.Key.chord(protractor.Key.COMMAND, 'A'), // macOS
      protractor.Key.BACK_SPACE
  );
}

I confirm that element.getAttribute('value') where element is an <input> always returns null when used with chromedriver=91.0.4472.19 (chrome=91.0.4472.77).

Perhaps, element.getAttribute('id') or element.getAttribute('class') are working fine.

It’s possible to use this hack to get the value of the <input> while waiting for the fix:

browser.executeScript(``return document.getElementById("${id}").value``)

@evilaliv3 Thanks for posting that! Looks like the firefox was the next. However, I see that chromium fixed this. I’m not checked yet, since in our team we migrated to my fork Protractor v6 with selenium 4.0 and all is fine.

@angular team, @kyliau, @Splaktar Could you please give to community some info about upgrades to selenium 4.0? I’ve added a PR, but any activities are stalled again 😦

@navix There was a decision to continue Protractor as v6 without control flow. That’s why this issue was registered and PR added. For now the master branch reflects v6. The next step should merge PR and release.

This seems to be related to https://github.com/angular/protractor/issues/5522

I was actually verifying the error with getAttribute(‘value’) on firefox but from this ticket i understand the error is more broad.

what do you think?

I confirm that element.getAttribute('value') where element is an <input> always returns null when used with chromedriver=91.0.4472.19 (chrome=91.0.4472.77).

Perhaps, element.getAttribute('id') or element.getAttribute('class') are working fine.

It’s possible to use this hack to get the value of the <input> while waiting for the fix:

browser.executeScript(return document.getElementById(“${id}”).value)

Using class but still unable to get the value. Tried with id also but not working.