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

Additional delay between actions that lead to prevented form submit event #1115

Closed
miherlosev opened this issue Jan 9, 2017 · 2 comments
Closed
Labels
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

@miherlosev
Copy link
Contributor

See video.

Test for reproduce:

fixture `angular`
    .page('http://todomvc.com/examples/angularjs');

test('test', async t => {
    for(let i = 0; i < 5; i++) {
        await t.typeText('#new-todo', String(i + 1))
            .pressKey('enter');
    }
});

It doesn't reproduce with hammerhead playground - http://screencast.com/t/xxCgR5YHucX

  • testcafe version: 0.12.0-alpha3
@miherlosev miherlosev added the TYPE: bug The described behavior is considered as wrong (bug). label Jan 9, 2017
@AlexanderMoskovkin AlexanderMoskovkin self-assigned this Jan 10, 2017
@AlexanderMoskovkin
Copy link
Contributor

I'm working on it

@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #3 milestone Jan 10, 2017
@AlexanderMoskovkin AlexanderMoskovkin changed the title Strange delay after 'pressKey' action Additional delay between actions that lead to prevented form submit event Jan 12, 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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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
Development

No branches or pull requests

2 participants