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

Green plus sign in Chrome #414

Closed
fredguest opened this issue Mar 18, 2016 · 22 comments
Closed

Green plus sign in Chrome #414

fredguest opened this issue Mar 18, 2016 · 22 comments

Comments

@fredguest
Copy link

@fredguest fredguest commented Mar 18, 2016

Has anyone figured out how to get rid of the green plus sign that pops up momentarily at the beginning of a drag operation in Chrome?

dnd quicktime player today at 8 24 18 pm

@fredguest fredguest changed the title Green plus sign Green plus sign in Chrome Mar 18, 2016
@jchristman
Copy link

@jchristman jchristman commented Mar 26, 2016

+1

@EvHaus
Copy link

@EvHaus EvHaus commented Apr 2, 2016

Cannot reproduce this issue on Chrome 49 on Mac, or Chrome 49 on Windows on this page: http://gaearon.github.io/react-dnd/examples-drag-around-naive.html

Is this still happening for you? What version of Chrome are you using and which OS?

Also, can you control the cursor behaviour as described here: http://gaearon.github.io/react-dnd/examples-customize-drop-effects.html?

@eliot-akira
Copy link

@eliot-akira eliot-akira commented Apr 2, 2016

I'm seeing the issue in all the examples, on Chrome 49 on Mac (still 10.10). On drag start, the cursor changes to a green plus sign (usually displayed by cursor: copy); and then becomes the "move" cursor.

@billyjanitsch
Copy link
Collaborator

@billyjanitsch billyjanitsch commented Apr 3, 2016

I'm able to reproduce this sporadically in the example you linked @globexdesigns (Chrome 49, OSX 10.11) -- it only appears for a split second before behaving as expected.

My guess is that it's either a short delay between React's batched render cycle and the browser's dnd implementation (in which case we might be able to fix it) or a bug in Chrome. I'll play around with other browsers (unless someone beats me to it) and see if I can get a repro there.

@jchristman
Copy link

@jchristman jchristman commented Apr 4, 2016

I'm seeing the same thing on Chrome 49 OSX 10.11.4 - appears for a split second then returns to normal. The behavior does not happen for me in Safari or Firefox.

@fredguest
Copy link
Author

@fredguest fredguest commented Apr 9, 2016

@EvNaverniouk I'm on Chrome 49 and OS X 10.11.4 and yes, still seeing the issue, and yes, I see the copy copy icon when expected in this link that you referenced http://gaearon.github.io/react-dnd/examples-customize-drop-effects.html

@pvande
Copy link

@pvande pvande commented Jun 7, 2016

Also seeing this issue in Chrome 50 on OS X 10.11.2.

@goivemaster
Copy link

@goivemaster goivemaster commented Jun 16, 2016

also seeing this Chrome 51 on OS X 10.10.1

@dwthomas77
Copy link

@dwthomas77 dwthomas77 commented Jul 18, 2016

I'm also seeing this on Chrome Version 51 on OSX 10.11.4.

Edit: after adding some more functionality implementing a drag layer and properly including the code using connectDragPreview and getEmptyImage() the problem seems to have gone away for now.

@kesne
Copy link
Collaborator

@kesne kesne commented Aug 20, 2016

I've seen this randomly in React DnD as well as other libraries and even just raw HTML5 draggable. My guess is that it has to do with us not setting effectAllowed in the dragstart.

@f0rr0
Copy link

@f0rr0 f0rr0 commented Oct 15, 2016

Any updates on this? Facing the same issue on Chrome 53 OSX 10.10.5

@MinaAzimov
Copy link

@MinaAzimov MinaAzimov commented Nov 10, 2016

Seeing the same thing Chrome 54.0.2840.71 10.11.6, any updates?

@gvohra
Copy link

@gvohra gvohra commented Dec 29, 2016

+1

Using {dropEffect: 'copy'} masks the problem (by making the green plus always visible); but doesn't properly fix it.

In addition, it seems {dropEffect: 'move'} doesn't appear to successfully make the cursor a 4-pointed cross-hair.

Chrome version: 55.0.2883.95 (Official Build) (64-bit)

@fredguest
Copy link
Author

@fredguest fredguest commented Jan 13, 2017

Closing this issue as it does not seem to be a function of this library.

@fredguest fredguest closed this Jan 13, 2017
@Yamikamisama
Copy link

@Yamikamisama Yamikamisama commented Jan 30, 2017

@fredguest did you ever find a solution to this?

@fredguest
Copy link
Author

@fredguest fredguest commented Jan 30, 2017

@Yamikamisama sadly no.

@fej-snikduj
Copy link

@fej-snikduj fej-snikduj commented Oct 1, 2017

The green plus button doesn't show up for me until my canDrop function returns false, then it appears.

@oinkbark
Copy link

@oinkbark oinkbark commented May 5, 2018

event.dataTransfer.dropEffect = 'none'
event.dataTransfer.effectAllowed = 'none'

This worked for me on chrome. Just put it in the "dragstart" and "dragend" events as those are the only ones that have access to the dataTransfer object.

@willb335
Copy link

@willb335 willb335 commented Aug 1, 2018

This didn't help me

event.dataTransfer.dropEffect = 'none'
event.dataTransfer.effectAllowed = 'none'

It happens only for a moment between cursor: 'grab' and cursor: 'grabbing'
It doesn't show in the gif format unfortunately but the pic below the gif shows the problem

greenplus

screen shot 2018-08-01 at 12 57 15 pm

@PawelDecowski
Copy link

@PawelDecowski PawelDecowski commented Oct 3, 2018

I’m also experiencing this problem. It looks like a bug in Chrome.

@worsnupd
Copy link

@worsnupd worsnupd commented Feb 8, 2019

+1

@Phinodel
Copy link

@Phinodel Phinodel commented Jul 24, 2020

+1 chrome version 84.0.4147.89

edit: this only happens when using the following code to not have a preview image:

useEffect(() => {
    preview(getEmptyImage(), { captureDraggingState: true });
  }, [preview]);

implementing a preview solves this problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet