Open Bug 1738454 Opened 3 years ago Updated 3 years ago

DND window sets window type as normal instead of _net_wm_window_type_dnd

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 93
defect

Tracking

()

UNCONFIRMED

People

(Reporter: spamreceiver23, Unassigned)

References

(Blocks 1 open bug)

Details

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

Steps to reproduce:

make a selection and drag it.

Actual results:

window for the selection gets type set to _net_wm_window_type_normal

Expected results:

type should be set to _net_wm_window_type_dnd . Unless a window manager puts in a firefox specific workaround the window will appear manageable.
If the type can't be corrected then perhaps at the very least the window should be unmapped? I'm not understanding why it's kept around or why the type is set to normal.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Blocks: linuxdad
Priority: -- → P3

We use Gtk functions gtk_drag_set_icon_widget() and gtk_drag_set_icon_pixbuf() which should set that.

(In reply to Martin Stránský [:stransky] (ni? me) from comment #2)

We use Gtk functions gtk_drag_set_icon_widget() and gtk_drag_set_icon_pixbuf() which should set that.

I'm unfamiliar with gtk and so not sure if that is where this occurs. but do these functions create the window or just set properties on the window?

Can you please check how other Gtk application behaves?
For instance when you you drag and drop text from gedit to Firefox - if the _net_wm_window_type_dnd is set to the window.
Thanks.

Flags: needinfo?(spamreceiver23)

So I tried as suggested. Both gtk and firefox pop up a window, gedit with :|XdndActionList| :|XdndTypeList| :|XdndAware| properties set and firefox with :|XdndAware| , both windows have window type set to normal.

Flags: needinfo?(spamreceiver23)
You need to log in before you can comment on or make changes to this bug.