Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Select event.value !== event.target.value

See original GitHub issue

When I change the option in a Select, event.value is the one I selected, and event.target.value is the previously selected option. This is obviously not the correct behavior.

This is a pretty simple issue so unless this is unknown behavior / hard to repro, I’ll leave it at that.

Your Environment

Grommet version: 2.7.1
Browser Name and version: Chrome 74.0.3729.169
Operating System and version (desktop or mobile): Desktop

Issue Analytics

State:
Created 4 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

bojan88commented, May 7, 2021

I just verified this. It is fixed in v2.17.2 with 518373864c2608df9faf4a6de8900ef5a55d8f20 Note that event.target.value === event.value will be true for single selection only.

If multiple prop is set these 2 values will not be equal. In that case event.target.value will hold previous value, and event.value will be an array. In my opinion event.target.value should be avoided when multiple prop is true.

@ShimiSun I guess this can be closed now

0reactions

jcfilbencommented, Jun 30, 2021

Closing since #5155 was merged