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

Debug mode and emulation don't seem to work together - debug menus freeze #2268

Closed
viking2917 opened this issue Mar 29, 2018 · 3 comments
Closed
Labels
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: UI TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@viking2917
Copy link

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

If I run

testcafe -d "chrome:emulation:device=iphone 6" test.js

When the first menus appear, they are locked - i.e. I cannot select "Resume" or any other buttons.

However,

testcafe "chrome:emulation:device=iphone 6" test.js
testcafe -d chrome test.js

both work as expected.

What is the expected behavior?

Debug menus should work in emulation mode

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

This occurs with any test I run. For example, the code in this issue will reproduce it: #2251

Provide the test code and the tested page URL (if applicable)

Tested page URL:

Test code

Specify your

  • operating system: 0.13.3
  • testcafe version: 0.19.1
  • node.js version: v8.9.4
@AndreyBelym AndreyBelym added TYPE: bug The described behavior is considered as wrong (bug). AREA: client SYSTEM: UI labels Mar 30, 2018
@AndreyBelym
Copy link
Contributor

Hi @viking2917, I reproduced the issue. Strange, but looks like Chrome doesn't emit touch events when emulating touch devices in some cases. We have to find a workaround for this.

@AndreyBelym
Copy link
Contributor

AndreyBelym commented Mar 30, 2018

Chrome devs changed emulation API: method setTouchEmulationEnabled was renamed to setEmitTouchEventsForMouse.

@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
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: UI TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

3 participants