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.

Sign up for GitHub

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

Jump to bottom

In Android Chrome the pointerdown event triggers twice #5891

Closed
scribetw opened this issue Jan 25, 2021 · 2 comments
Closed

In Android Chrome the pointerdown event triggers twice #5891

scribetw opened this issue Jan 25, 2021 · 2 comments
Assignees
@AlexKamaev
Labels
FREQUENCY: level 1 SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug).

Comments

@scribetw
Copy link

What is your Test Scenario?

Click an element on Android Chrome.

What is the Current behavior?

Received 2 pointerdown events.

What is the Expected behavior?

Receive 1 pointerdown event.

What is your web application and your TestCafe test code?

Your website URL (or attach your complete example): 
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Document</title>
</head>
<body>
    <div id="content" style="width: 100px; height: 100px; border: 1px solid red;">
        click me
    </div>
    <div id="log">
    </div>
    <script type="text/javascript">
    var c = document.getElementById('content'),
        l = document.getElementById('log');
    c.addEventListener('pointerdown', e => {
        l.innerHTML += "pointerdown"
    })
    </script>
</body>
</html>
Your complete test code (or attach your test files): 
import {Selector} from 'testcafe';

fixture `Test Touch`
    .page `./touchevent.html`

test('Test Touch', async t => {
    await t.click('#content')
        .expect(Selector('#log').innerText).eql('pointerdown');
});
Your complete configuration file (if any):
Your complete test report: 
Using locally installed version of TestCafe.
Connecting 1 remote browser(s)...
Navigate to the following URL from each remote browser.
Connect URL: http://10.1.3.158:10240/browser/connect
CONNECTED Chrome 88.0.4324.93 / Android 7.1.2
 Running tests in:
 - Chrome 88.0.4324.93 / Android 7.1.2

 Test Touch
 ✖ Test Touch

   1) AssertionError: expected 'pointerdownpointerdown' to deeply equal 'pointerdown'
      
      + expected - actual
      
      -'pointerdownpointerdown'
      +'pointerdown'
      

      Browser: Chrome 88.0.4324.93 / Android 7.1.2

         3 |fixture `Test Touch`
         4 |    .page `./touchevent.html`
         5 |
         6 |test('Test Touch', async t => {
         7 |    await t.click('#content')
       > 8 |        .expect(Selector('#log').innerText).eql('pointerdown');
         9 |});

         at <anonymous> (/Users/rudyhuang/IdeaProjects/testcafe/test-touch.js:8:45)
         at asyncGeneratorStep (/Users/rudyhuang/IdeaProjects/testcafe/test-touch.js:1:230)
         at _next (/Users/rudyhuang/IdeaProjects/testcafe/test-touch.js:1:568)
         at <anonymous> (/Users/rudyhuang/IdeaProjects/testcafe/test-touch.js:1:733)
         at <anonymous> (/Users/rudyhuang/IdeaProjects/testcafe/test-touch.js:1:474)
         at <anonymous> (/Users/rudyhuang/IdeaProjects/testcafe/test-touch.js:6:5)



 1/1 failed (5s)
Screenshots:

image

Steps to Reproduce:

  1. Save the HTML (touchevent.html) and test js
  2. Execute TestCafe using remote or "chrome:emulation:device=Pixel 2"
testcafe remote --ports 10240,10241 test-touch.js
testcafe "chrome:emulation:device=Pixel 2" test-touch.js
  1. See the error...

Your Environment details:

  • testcafe version: 1.10.1
  • node.js version: v14.15.0
  • command-line arguments: testcafe remote --ports 10240,10241 test-touch.js
  • browser name and version: Chrome 88.0.4324.93
  • platform and version: Android 7.1.2 (Using BlueStacks 4 mac)
  • other:
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jan 25, 2021
@scribetw scribetw changed the title In Android Chrome the pointerdown triggers twice In Android Chrome the pointerdown event triggers twice Jan 25, 2021
@Farfurix
Copy link
Contributor

@scribetw

Hello,

Thank you for the example. I reproduced the issue. Our team will examine this case and check for a suitable solution.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Jan 26, 2021
@Farfurix Farfurix added SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug). FREQUENCY: level 1 labels Jan 26, 2021
@Farfurix Farfurix self-assigned this Jan 26, 2021
@Farfurix Farfurix linked a pull request Jan 28, 2021 that will close this issue
Check a pointer test #5900
Closed
@Farfurix Farfurix mentioned this issue Jan 28, 2021
Closed
@Farfurix Farfurix removed their assignment Oct 5, 2021
@AlexKamaev AlexKamaev self-assigned this Dec 16, 2021
@AlexKamaev
Copy link
Contributor

fixed in DevExpress/testcafe-hammerhead#2718

@Aleksey28 Aleksey28 mentioned this issue Jul 7, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexKamaev AlexKamaev

Labels
FREQUENCY: level 1 SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check a pointer test
3 participants
@AlexKamaev @scribetw @Farfurix