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

Value and selectedIndex are not valid in input event handler for dropdown select element #1366

Closed
AndreyBelym opened this issue Mar 28, 2017 · 1 comment
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

@AndreyBelym
Copy link
Contributor

AndreyBelym commented Mar 28, 2017

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

The value and selectedIndex properties of a dropdown select are not set in input event handler.

What is the expected behavior?

The value and selectedIndex properties should be changed according to the selected child when executing input event handler.

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

Run the test.

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

Tested page URL: https://andreybelym.github.io/test-pages/gh-1366.html

Test code

import {ClientFunction} from 'testcafe';                                   
                                                                           
fixture `test`
    .page`https://andreybelym.github.io/test-pages/gh-1366.html`;

test(`choose value`, async t => {                                                                                                             
    await t                                                                
        .click(`select`)                                                   
        .click(`option[value=Nissan]`)                                     
        .expect(ClientFunction(() => window.selectValue)()).eql('Nissan'); 
});                                                                        

Specify your

  • operating system: Windows 10
  • testcafe version: 0.14.0-alpha6
  • node.js version: 7.4.0
@AndreyBelym AndreyBelym added AREA: client SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug). labels Mar 28, 2017
@AndreyBelym AndreyBelym added this to the Sprint #6 milestone Mar 28, 2017
@AndreyBelym AndreyBelym self-assigned this Mar 28, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 4, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 14, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 18, 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
…#1366) (DevExpress#1377)

* Update dropdown select before emitting input event (closes DevExpress#1366)

* Fix tests

* Increase timeout for after in functional tests
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

1 participant