-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Update Puppeteer to 1.18 #355
Comments
angrykoala
added
the
blocked
Block by external issue or cause, defined in the description
label
May 8, 2019
Closed
Some examples with raw Puppeteer reproducing the 422 status code problem reported at: |
Incognito appears to not be working properly on 1.16.0 |
angrykoala
changed the title
Update Puppeteer to 1.15.0 or higher
Update Puppeteer to 1.16.0 or higher
May 20, 2019
Incognito is working as expected, recent changes in chromium make the test unreliable. Failing tests will be removed |
Issue still happening on Puppeteer@1.17.0 |
Release of puppeteer@1.18 (est. June, 21st) should fix the regression problem |
angrykoala
changed the title
Update Puppeteer to 1.16.0 or higher
Update Puppeteer to 1.18
Jun 10, 2019
angrykoala
pushed a commit
that referenced
this issue
Jun 21, 2019
angrykoala
added a commit
that referenced
this issue
Jul 8, 2019
angrykoala
added a commit
that referenced
this issue
Jul 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blocked by #354
Puppeteer 1.15.0 does not properly respond to 422 errors
The text was updated successfully, but these errors were encountered: