.MouseEnter fires after clicking a GUI

Bug Reports Engine Bugs
#1

I’m not even completely sure this is a bug, but it is VERY annoying. If you have a GUI, for example, a button. If you use .Entered on the GUI, it will fire after you click the GUI and move your mouse, even if your mouse hasn’t left the GUI area.

This bug happens every time.

You can reproduce it very easily. Just insert a TextButton, and the following code in a localscript:

PATH TO THE BUTTON.MouseEnter:connect(function()
print(“Mouse has entered”)
end)

And click the GUI then move the mouse. It prints.

I would provide screenshots, but lightshot doesn’t captured the mouse.

I’m not sure if this is intended or not, but it is quite bothersome. I am not sure of when the bug originated, I just found it myself doing some work with GUI’s and MouseEnter.

Note: You can workaround this by adding an “Entered” variable yourself that is set true when MouseEnter is fired, and set to false when MouseLeave is fired.

MouseEnter triggers after MouseClick
#2

I can second this - it breaks my button animations.

#3

I’ve been having an issue with this, too. I was just about to file my own bug report.
I have nice little animations for mousing over a Gui, but it plays again if you click on it and move the mouse a little. MouseEnter fires again even though the mouse never left the Gui in the first place.

Can someone put this in the ‘Client Bugs’ subcategory?

#4

You should make your own thread at this point. Check the date of the posts, it’s not a relevant thread any more.

If it was like a few months old it may be acceptable to just bump it, but this is over 2 years old now.

#5

Blugh. I thought I was being on top of things.

I guess it’s too late now.

#6

I’m already working on it

2 Likes
#7

This is an issue again. Repro:
MouseEnter repro.rbxl (12.0 KB)

#8

The fix isn’t live yet.

#9

Oh, alright. Any ETA?

#10

Soon TM

1 Like
#11

Any news on this?

1 Like
#12

That’s one heck of a Soon TM - 3 years!

3 Likes
#13

Whoa, how comes UI events can be this unreliable for years?

#14

Any news @Sharksie? It’s still happening ;(

4 Likes
#15

I absolutely adore the fact that after 4 years when provided documentation and reproduction steps, this is still around. I’d love to get some eyes on it.

#16

And still unfixed.

1 Like