2048629 - drag and drop link inverted

Status: NEW

(Core :: Widget: Gtk, defect)

Description

[Enzo]

Attachment: Capture d’écran du 2026-06-18 15-23-08.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:151.0) Gecko/20100101 Firefox/151.0

Steps to reproduce:

Using Ubuntu 22.04 with Wayland.
Open Firefox and perform any Google search (e.g., search for "mozilla").
Click and hold one of the search result hyperlinks.
Drag the link outside the browser window towards another application.

Actual results:

The visual "ghost" or preview image of the dragged link is displayed upside down (rotated 180°). See attached screenshot.

Expected results:

The visual preview of the link should remain in its normal, upright orientation while being dragged.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, but is not confident enough to move the bug to that component.

Comment 2

[Ed Lee :Mardak]

The bug is: dragging a hyperlink (e.g. Google search result) produces an upside-down/180°-rotated visual "ghost" preview when dragging the link out of Firefox on Ubuntu 22.04 + Wayland.

• The entire drag icon/preview generation + platform handoff for the visual lives in widget/gtk/:
• nsDragService.cpp (SetDragIcon, SetAlphaPixmap using gtk_drag_set_icon_surface / pixbuf / widget, DrawDrag integration, invisibleSourceDragBegin, etc.)
• Wayland-specific paths in the drag session and InvokeDragSessionImpl.
• The actual image comes from PresShell::RenderNode/PaintRangePaintInfo (or selection) but the upside-down symptom is triggered in the GTK-specific icon surface setup + offset/scale handling passed to GTK.
• All similar Linux/Wayland DND bugs (tab drags, file drags, download drags, unresponsive drags, etc.) are consistently triaged to Core :: Widget: Gtk.
• widget/gtk/moz.build (and widget/gtk/wayland/moz.build) explicitly tags the relevant code as ("Core", "Widget: Gtk").

Comment 3

[Thinker Li [:sinker]]

I can reproduce it locally.

Comment 4

[Martin Stránský [:stransky] (ni? me) (PTO till June 6)]

Is there any regression range? Can you use mozregression to find broken commit?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.

Comment 5

[Enzo]

(In reply to Martin Stránský [:stransky] (ni? me) (PTO till June 6) from comment #4)

Is there any regression range? Can you use mozregression to find broken commit?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.

7:14.15 INFO: Narrowed nightly regression window from [2022-12-09, 2022-12-12] (3 days) to [2022-12-11, 2022-12-12] (1 days) (~0 steps left)
7:14.15 INFO: Got as far as we can go bisecting nightlies...
7:14.15 INFO: Last good revision: 6811f459c2c281807c73f6443bfbcee8d4b314ca (2022-12-11)
7:14.15 INFO: First bad revision: d9b14b6b3a524e622cff771d8074baa88895f8f1 (2022-12-12)
7:14.15 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6811f459c2c281807c73f6443bfbcee8d4b314ca&tochange=d9b14b6b3a524e622cff771d8074baa88895f8f1