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

On device emulation, click on items on the very side of page doesn't work #8057

Closed
Silhm opened this issue Oct 25, 2023 · 1 comment
Closed

On device emulation, click on items on the very side of page doesn't work #8057

Silhm opened this issue Oct 25, 2023 · 1 comment
Labels
TYPE: bug The described behavior is considered as wrong (bug).

Comments

@Silhm
Copy link

Silhm commented Oct 25, 2023

What is your Scenario?

When using device emulation, clicking on very side of the page doesn't trigger anything on my page
Testcafe hangs until timeout

What is the Current behavior?

I know that the design of my snippet is not optimal in real web apps.
The click doesn't trigger the innerText to change.

I tried with Testcafe 2.4.0 without any trouble, but with Testcafe 3.3.0 the test doesn't pass anymore

What is the Expected behavior?

I would expect item to be clickable in the test on Mobile device emulation

What is your public website URL? (or attach your complete example)

On a given html document:

<body style="margin:0">
    <span id="target" style="position:fixed; right:0" onclick="this.innerText='boop'">T</span>
</body>

https://www.silhm.fr/issues/testcafe-click.html

What is your TestCafe test code?

My test.spec.js is quite simple:

import { Selector } from 'testcafe';

fixture('Getting Started')
    .page('https://www.silhm.fr/issues/testcafe-click.html');

test('My first test', async t => {
    await t
        .click('#target')
        .expect(Selector('#target').innerText).eql('boop');
});

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

  1. Run the attached test with testcafe 2.4.0 : it works
  2. Run the attached test with testcafe 3.3.0 : it doen't work anymore

TestCafe version

3.3.0

Node.js version

20.8.1

Command-line arguments

npx testcafe "chrome:emulation:device=Pixel 2" test.spec.js`

Browser name(s) and version(s)

chrome:emulation:device=Pixel 2 (chrome 118)

Platform(s) and version(s)

Linux Mint 21.2

Other

No response
@Silhm Silhm added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 25, 2023
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Oct 25, 2023
@PavelMor25
Copy link
Collaborator

PavelMor25 commented Oct 26, 2023 •
edited by AlexKamaev
Loading

Hello @Silhm,

Thank you for sharing the information.
We already know about this issue, and it's fixed in our repository. The upcoming release should include the fix. This behavior occurs only in Native Automation mode, so you can disable Native Automation to work around the issue until the next version is released.

Please refer to the following help topic to read about disableNativeAutomation.

@PavelMor25 PavelMor25 removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Silhm @PavelMor25