Skip to content

Invisible hitbox at bottom of screen blocks clicks after dock floats (v92, Animation enabled) #338

Description

@dangbach204

Environment

Extension: Dash2Dock Animated (dash2dock-lite@icedman.github.com)
Extension version: 92
GNOME Shell version: 46
OS: Ubuntu 24.04
Session type: X11
Ubuntu Dock: disabled (only Dash2Dock Animated is active)

Description

After the dock animates/floats up from the bottom of the screen, I can no longer click on the area at the very bottom of the screen — specifically the strip where the dock meets the application window behind it. It looks like an invisible hitbox belonging to the dock remains anchored at the bottom edge of the screen even after the dock itself has floated upward, blocking all click-through to windows underneath.

Steps to reproduce

Enable Dash2Dock Animated with "Animate icons" / floating dock animation turned on.
Let the dock auto-hide, then trigger it to float up by hovering near the bottom edge.
Try to click on a window/application element located directly behind or below where the dock used to sit (bottom strip of the screen).
Click does not register — the area appears to still be intercepted by the dock's hitbox even though the dock is no longer visually there.

Expected behavior

Once the dock floats up, the invisible hitbox/reactive area should move with it. The screen area it vacates at the bottom should become clickable again, same as with the standard Dash to Dock extension.

Actual behavior

The hitbox appears to remain fixed at the bottom edge of the screen, permanently blocking clicks in that region regardless of the dock's current floating position.

What I've tried

Disabled Ubuntu Dock, running Dash2Dock Animated exclusively.
Confirmed I'm on X11 (not Wayland).
Tried adjusting various extension settings (animation, autohide, floating dock options) without success.
Was advised in community forums to roll back to v82, where this issue reportedly does not occur.

Additional notes

Happy to provide a screen recording or journalctl/Looking Glass logs if helpful — please let me know what would be most useful for debugging.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions