GUI sinks input, even when GUI element above it has the "active" property set to true

Bug Reports Engine Bugs
#1

Before I describe this, take a look at the below GIF. Anything that has “MouseEnter” highlights, and “MouseLeave” deactivates.

bxEG21dP

Notice that there seems to be input sinking. For example, if I place my cursor in the bottom-right corner of “layer 2” of the blue frames, all three frames highlight; this is because all three had the “MouseEnter” input fire. Also, notice how the same happens for the green frames. The blue frames all have Active set to true, while for the green, it’s false. This is incorrect behavior.

Here is a reproduction place file:
InputSinkingRepro.rbxl (53.5 KB)

Expected behavior

Input shouldn’t sink! The highest-level “active” object should claim input, and the active property should affect how it behaves. This is so frustrating in UI design and requires all sorts of hacky workarounds.

7 Likes
#2

Thanks for the report! We’ve filed a ticket in our internal database.

3 Likes
#3

Hello! Upon review of this bug we agree that it is not ideal, however changing this behavior directly will break some experiences that rely on this sinking behavior. We do have some ideas around new features that would correct for this behavior, but we aren’t ready to announce anything regarding this yet. Please know that we are working on ways to fix this for you in the future!

2 Likes
#4

Gotcha. Maybe make it a StarterGui option? You could have “Sink” and “Active” behavior options, along with a “Default” one. This could keep previous experiences functional while making it a possible functional change for current and newer ones.

#5