After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 667739 - Moving a anchored widget does not work
Moving a anchored widget does not work
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTextView
3.13.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-01-12 09:37 UTC by Egon A. Rath
Modified: 2018-04-15 00:10 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Testcase (1.39 KB, text/plain)
2012-01-12 12:07 UTC, Egon A. Rath 		Details

Description Egon A. Rath 2012-01-12 09:37:00 UTC 
When a Widget is anchored within a TextView and you move around a selection which contains text and a widget, the text is moved but the widget disappears.

Steps to reproduce:

1.) Insert some text and a widget (e.g. a button) into a textview
2.) make a selection to include some text and the widget
3.) drag around the selection and release the mouse button
4.) The text has been moved, the widget is gone.

From what i've found out so far the associated Gdk Window of the widget is unrealized when it's anchor is moved within the textbuffer.
Comment 1 André Klapper 2012-01-12 09:50:20 UTC 
Which gtk+ version is this about?
Comment 2 Egon A. Rath 2012-01-12 10:38:34 UTC 
I am using Gtk 2.24 using the Gtk# 2.12 Bindings
Comment 3 André Klapper 2012-01-12 10:42:29 UTC 
Okay, just to get this straight, what makes you sure that this is not an issue of the ancient and outdated Gtk# bindings?
A plain C testcase is welcome, I guess...
Comment 4 Egon A. Rath 2012-01-12 12:07:17 UTC 
Created attachment 205085 [details]
Testcase
Comment 5 Sébastien Wilmet 2014-07-20 12:25:24 UTC 
I confirm this bug, it still occurs with gtk+ 3.13.
Comment 6 Sébastien Wilmet 2014-07-20 14:53:12 UTC 
Probably related: bug #596989.
Comment 7 Matthias Clasen 2018-02-10 05:16:59 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 8 Matthias Clasen 2018-04-15 00:10:31 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new