On versions after 3.2019-09-09-20-39-39-UTC, some DOM elements are invisible

[alberto56]

Using dcycle/browsertesting:3.2019-09-09-20-39-39-UTC, the following works:

await page.goto('http://drupal/user')
console.log('enter credentials')
await page.type('[name=name]', process.env.DRUPALUSER)
await page.type('[name=pass]', process.env.DRUPALPASS)
await page.keyboard.press('Enter');
await page.waitForSelector('.nodetype')
await page.goto('http://drupal/internal')

http://drupal/internal will be logged in.

Using dcycle/browsertesting:3, http://drupal/internal will not be logged in.

[alberto56]

This seems to have been introduced in puppeteer 1.20:

$ docker run --rm -ti --entrypoint "/bin/bash" dcycle/browsertesting:3.2019-09-09-20-39-39-UTC -c 'cat /app/package-lock.json | grep puppeteer --after-context=1'
    "puppeteer": {
      "version": "1.19.0",
      "resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-1.19.0.tgz",
      "integrity": "sha512-2S6E6ygpoqcECaagDbBopoSOPDv0pAZvTbnBgUY+6hq0/XDFDOLEMNlHF/SKJlzcaZ9ckiKjKDuueWI3FN/WXw==",
$ docker run --rm -ti --entrypoint "/bin/bash" dcycle/browsertesting:3 -c 'cat /app/package-lock.json | grep puppeteer --after-context=1'
    "puppeteer": {
      "version": "1.20.0",
      "resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-1.20.0.tgz",
      "integrity": "sha512-bt48RDBy2eIwZPrkgbcwHtb51mj2nKvHOPMaSH2IsWiv7lOG9k9zhaRzpDZafrk05ajMc3cu+lSQYYOfH2DkVQ==",

[alberto56]

Ref https://github.com/GoogleChrome/puppeteer/issues/4952

[alberto56]

Hmmm cannot reproduce this other than on the newmode project, although I can reproduce it there consistently...