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

No change detection (if Dropdown value is changed with keyboard down arrow key) #2845

Closed
burhanyldz opened this issue May 22, 2017 · 4 comments
Assignees

Comments

@burhanyldz
Copy link

I'm submitting a ... (check one with "x")

[ x ] bug report => Search github for a similar issue or PR before submitting

Plunkr Case (Bug Reports)
http://plnkr.co/edit/m1H88j8un6R6HgFiAXgX?p=preview

Current behavior
If navigate and focus the dropdown using the keyboard TAB key (while it is untouched and displaying the placeholder), if down arrow key is used to change the dropdown value, the first change is not detected. It works if dropdown is changed with mouse click.

Expected behavior
It should detect the first change from the default value (null) while using keyboard to navigate through the form as with mouse.

Minimal reproduction of the problem with instructions
Focus the dummy input, press TAB button and change dropdown option with down arrow key.

Please tell us about your environment:
plunkr

  • Angular version: 2.0.X
    4.0.0

  • PrimeNG version: 2.0.X
    4.0.1

@burhanyldz burhanyldz changed the title No change detection changing Dropdown value with keyboard down arrow key No change detection (if Dropdown value is changed with keyboard down arrow key) May 30, 2017
@Christhecoleman
Copy link

I also have encountered this issue

@bnazare
Copy link

bnazare commented Jun 9, 2017

I'm encountering this issue too, albeit in template-driven forms. Also, I would like to add that it affects validation.
Say you have a dropdown marked as required, the first selection with keyboard will keep the field (and hence the form) as invalid.

@cagataycivici cagataycivici self-assigned this Jun 23, 2017
@cagataycivici cagataycivici added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Jun 23, 2017
@cagataycivici cagataycivici added this to the 4.1.1 milestone Jun 23, 2017
@Christhecoleman
Copy link

Upgraded to primeng: 4.1.0-rc3 to see if the issue had been resolved, it's now worse as no value is selected if you tab into the dropdown list now reverted back to 4.0.0 where it works, also tooltip text is no longer displaying either

@cagataycivici
Copy link
Member

Fixed via 3481

@mertsincan mertsincan removed the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Oct 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants