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

Wrong handling of key pressing in input #2070

Closed
helen-dikareva opened this issue Jan 25, 2018 · 3 comments
Closed

Wrong handling of key pressing in input #2070

helen-dikareva opened this issue Jan 25, 2018 · 3 comments
Assignees
Labels
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: automations 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?

Input value changed after click and press "Up" button

What is the expected behavior?

Input value should not be changed

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

import { Selector, ClientFunction } from 'testcafe';

fixture `fixture`
    .page `http://dolzhikov-w8/172/RegressionTestsSite/ASPxEditors/ASPxDateEdit/T187651.aspx`;

test('test', async t => {
    const input = Selector("#ASPxDateEdit1_I");

    await t.click(input);

    var oldValue = await input.value;

    await t
        .pressKey("up")
        .expect(input.value).eql(oldValue);
});

Specify your

  • testcafe version: 0.18.6-dev20171222
@helen-dikareva helen-dikareva added TYPE: bug The described behavior is considered as wrong (bug). AREA: client SYSTEM: automations labels Jan 25, 2018
@helen-dikareva helen-dikareva added this to the Planned milestone Jan 25, 2018
@miherlosev
Copy link
Contributor

I'm working on this

@AndreyBelym
Copy link
Contributor

The issue will be closed after updating testcafe-hammerhead.

@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: automations TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

4 participants