Skip to content
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

Lighthouse fails to dismiss page dialogs #2423

Closed
pmeenan opened this issue Jun 2, 2017 · 3 comments · Fixed by #8894
Closed

Lighthouse fails to dismiss page dialogs #2423

pmeenan opened this issue Jun 2, 2017 · 3 comments · Fixed by #8894
Labels

Comments

@pmeenan
Copy link

pmeenan commented Jun 2, 2017

Lighthouse is having issues with pages that have dialogs (at least some types of dialogs) and times out when loading the page.

FWIW, WebPageTest had similar issues and now tries first to "accept": false the dialog and if that fails tries "accept": true. Similar logic in Lighthouse should make it more robust for pages with dialogs.

Test page: http://www.dlsite.com/

Log:

  status Loading page & waiting for onload +7ms URL, Viewport, ViewportDimensions, ThemeColor, Manifest, ChromeConsoleMessages, ImageUsage, Accessibility, EventListeners, AnchorsWithNoRelNoopener, AppCacheManifest, DOMStats, OptimizedImages, ResponseCompression, TagsBlockingFirstPaint, WebSQL
  Driver:warn confirm dialog opened by the page automatically suppressed. +4s
  method <= browser ERR:error Page.handleJavaScriptDialog +1ms 
@pmeenan
Copy link
Author

pmeenan commented Jun 2, 2017

It looks like Lighthouse only tries "accept":true and tries that first and it intentional.

@pmeenan
Copy link
Author

pmeenan commented Jun 2, 2017

At a minimum, the test should fast-fail when the dialog dismissal fails (whether or not it falls back to false).

@patrickhulce
Copy link
Collaborator

Ah thanks for the tip @pmeenan we've been struggling with this in CI too!

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

Successfully merging a pull request may close this issue.

3 participants