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

Click on the status panel affects the page state #1389

Closed
helen-dikareva opened this issue Apr 10, 2017 · 1 comment
Closed

Click on the status panel affects the page state #1389

helen-dikareva opened this issue Apr 10, 2017 · 1 comment
Assignees
Labels
AREA: client !IMPORTANT! 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

@helen-dikareva
Copy link
Collaborator

Are you requesting a feature or reporting a bug?

bug

What is the current behavior?

handlers which binded with capturing IS EXECUTED after click on status panel

What is the expected behavior?

handlers which binded with capturing should NOT be EXECUTEDafter click on status panel

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

run test step by step

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

Tested page:

<!DOCTYPE HTML>
<html>
<head>
    <title>test</title>
</head>
<body>
<button id="button">BUTTON</button>
<button id="button2" style="display: none">BUTTON 2</button>

<script>
    document.getElementById('button').addEventListener('mousedown', function () {
        document.getElementById('button2').style.display = 'block';

        window.addEventListener('mousedown', function () {
            document.getElementById('button2').style.display = 'none';
        }, true);
    });
</script>
</body>
</html>

Test code:

import { Selector } from 'testcafe';
fixture `fixture`
    .page `http://localhost/testcafe/`;

test('test', async t => {
    await t
        .click('#button')
        .debug()
        .expect(Selector('#button2').visible).ok();
});
@helen-dikareva helen-dikareva added !IMPORTANT! AREA: client SYSTEM: UI TYPE: bug The described behavior is considered as wrong (bug). labels Apr 10, 2017
@helen-dikareva helen-dikareva added this to the Sprint #6 milestone Apr 10, 2017
@helen-dikareva helen-dikareva self-assigned this Apr 10, 2017
helen-dikareva added a commit to helen-dikareva/testcafe-phoenix that referenced this issue Apr 10, 2017
@VasilyStrelyaev VasilyStrelyaev changed the title Page elements handlers which binded with capturing should not be executed after click on status panel Click on the status panel changes the page state Apr 24, 2017
@VasilyStrelyaev VasilyStrelyaev changed the title Click on the status panel changes the page state Click on the status panel affects the page state Apr 24, 2017
@lock
Copy link

lock bot commented Mar 29, 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 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 29, 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 !IMPORTANT! 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

1 participant