onDrop breaks onSelect event

[tobiasandersen]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
After an onDrop event has fired inside an "editable" element (input, textarea, contentEditable), the onSelect event on that element will no longer fire when changing selection using the keyboard.

As you can see in this gif below, the onSelect event gets called each time I move the cursor around (using the arrow keys). But once the onDrop event has fired, onSelect will no longer fire when I move the cursor around (also using the keys):

Here's the jsfiddle I used to record the video above.

What is the expected behavior?
The onSelect event should always fire when selection changes.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
React 16 / Chrome 62

[clemmy]

Thanks for the report! I can't seem to reproduce it in my browser - Chrome Version 62.0.3202.75 (Official Build) (64-bit). Does it happen to you in Firefox as well?

[tobiasandersen]

Hm that's weird, I can reproduce it 100% of the times in both Chrome Version 62.0.3202.89 (Official Build) (64-bit) and in Firefox 56.0.2 (64-bit).

If you click anywhere after the drop, everything will go back to normal (see #11380). So in order to reproduce you must first drop the text, and then move the cursor around using the arrow keys (without clicking anywhere first).

Please let me know if there's anything else I can do to demonstrate the issue!

[clemmy]

@tobiasandersen Got it. Looks like a legitimate problem - I'll look into it.

[clemmy]

Hey @tobiasandersen, wondering if you could still reproduce this. The JSFiddle points to 16.1.1 now, and I can't seem to reproduce it anymore there.

[tobiasandersen]

Just tried it in that fiddle again, and it's still an issue for me on Chrome Version 62.0.3202.94 (Official Build) (64-bit) and on Firefox 57.0 (64-bit). I wonder what I'm doing differently since I can reproduce it 100% of the times.

[gaearon]

I can reproduce this. I think maybe @clemmy missed the "using arrow keys" part — it's crucial to reproducing.