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

Firefox hangs with dialog asking to set it as standard browser #1926

Closed
TauPan opened this issue Nov 6, 2017 · 5 comments
Closed

Firefox hangs with dialog asking to set it as standard browser #1926

TauPan opened this issue Nov 6, 2017 · 5 comments
Assignees
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@TauPan
Copy link

TauPan commented Nov 6, 2017

Are you requesting a feature or reporting a bug?

Feature

What is the current behavior?

When starting tests with firefox, firefox shows the modal dialog to set itself as standard browser. No matter what is clicked here, the dialog appears every time. No tests are executed as long as the dialog is in place. The user needs to press escape or click a button to make tests run.

Since there's no error about a dialog handler, I guess that it won't help to try to install a dialog handler at that point. Also it's not clear from the documentation what would be the correct way to do this, if any.

What is the expected behavior?

Tests should run without user interaction, i.e. modal dialogs should be dismissed.

How would you reproduce the current behavior (if this is a bug)?

testcafe firefox ...

Specify your

  • operating system:
NAME="openSUSE Leap"
VERSION="42.2"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.2"
PRETTY_NAME="openSUSE Leap 42.2"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.2"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
  • testcafe version:
    [email protected]
  • node.js version:
    v6.11.2
  • firefox version
    Firefox ESR 52.4.0 (64-bit)
@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: bug The described behavior is considered as wrong (bug). label Nov 7, 2017
@AlexanderMoskovkin
Copy link
Contributor

AlexanderMoskovkin commented Nov 7, 2017

Hi @TauPan,

Since the 0.18.0 version TestCafe opens a Firefox instance with a clean profile. We setup settings for Firefox testing profile there: https://github.com/DevExpress/testcafe/blob/master/src/browser/provider/built-in/firefox/runtime-info.js#L18.
It's possible we've missed some flag. @AndreyBelym will investigate it.
As a workaround you can try to run your tests in your current user profile: testcafe firefox:userProfile test.js

(it possible this is a related ticket: https://support.mozilla.org/en-US/questions/1152757)

@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #10 milestone Nov 7, 2017
@TauPan
Copy link
Author

TauPan commented Nov 7, 2017

As a workaround you can try to run your tests in your current user profile: testcafe firefox:userProfile test.js

Thanks, that helps.

@TauPan
Copy link
Author

TauPan commented Nov 7, 2017

(Incidently, chromium also displays the dialog to "Set chromium as standard browser" for me, but since it isn't modal, it doesn't cause test execution to hang.)

@AndreyBelym
Copy link
Contributor

Yes, we should include "browser.usedOnWindows10" flag to generated profile.

AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Dec 29, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Dec 29, 2017
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

3 participants