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

Error when I click on the "Unlock Page" button #3652

Closed
LavrovArtem opened this issue Apr 8, 2019 · 3 comments · Fixed by DevExpress/testcafe-hammerhead#1989
Closed

Error when I click on the "Unlock Page" button #3652

LavrovArtem opened this issue Apr 8, 2019 · 3 comments · Fixed by DevExpress/testcafe-hammerhead#1989
Assignees
Labels
!IMPORTANT! 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

@LavrovArtem
Copy link
Contributor

What is your web application and your TestCafe test code?

Your website URL (or attach your complete example): http://todomvc.com/examples/vue/

Your complete test code (or attach your test files):

fixture `Fixture`
    .page `http://todomvc.com/examples/vue/`;

test('Test', async t => {
    await t.debug();
});

Steps to Reproduce:

  1. Start the test
  2. Open developer tools
  3. Click the "Unlock Page" button
  4. See the error Uncaught TypeError: Cannot read property 'call' of undefined

Your Environment details:

  • testcafe version: 1.1.1
  • node.js version: 10.15.0
  • command-line arguments: testcafe chrome test.js
  • browser name and version: Chrome 73.0.3683
  • platform and version: Windows 10.0.0
@LavrovArtem LavrovArtem added the TYPE: bug The described behavior is considered as wrong (bug). label Apr 8, 2019
@jafin
Copy link

jafin commented Apr 9, 2019

Seeing same error for internal page,
test ran fine in 1.1, failing in 1.1.1 Click unlock on page returns
Uncaught TypeError: Cannot read property 'call' of undefined at hammerhead.js:7
Node: 10.15.3
Browser: Chrome 73
Platform: windows 10

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Apr 9, 2019
@miherlosev miherlosev removed the STATE: Need response An issue that requires a response or attention from the team. label Apr 9, 2019
@AndreyBelym AndreyBelym added this to the Sprint #31 milestone Apr 10, 2019
@helen-dikareva
Copy link
Collaborator

We have 3 internal handlers for mousedown event: one preventRealEventHandler and two (somehow) downHandler from StatusBar._bindClickOnce. preventRealEventHandler works fine and the first downHandler calls removeInternalEventListener. That causes the error.
For me it looks like we should handle such a situation when one handler removes itself during execution.

@lock
Copy link

lock bot commented Apr 25, 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 Apr 25, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
!IMPORTANT! 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
5 participants