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 379735 - GOK inserts a blank when user selects word from composer.
GOK inserts a blank when user selects word from composer.
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks: 519096 519313
 
 
Reported: 2006-11-27 09:59 UTC by Tim Miao
Modified: 2018-02-10 03:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Tim Miao 2006-11-27 09:59:26 UTC 
Please describe the problem:
This is a bug for gok composer.

Steps to reproduce:
1. Launch gedit and gok.
2. Select composer in GOK main window.
3. Input several words in the gedit.
4. Save this file, in Save dialog, grab the file name with gok ui grab.
5. Click "te" in gok composer, the word "text" will be displayed in composer top row, select this word.


Actual results:
The word "text" will be filled in the name entry with "te xt", gok inserts a blank in the word.

Expected results:
GOK should fill "text" to the text entry.

Does this happen every time?
Yes.

Other information:
This can be found only in save dialog, in gedit multiple text area, it is not reproducible.
Comment 1 David Bolter 2006-11-27 15:28:27 UTC 
This sounds like a problem specific to the text area in the save dialog.  I'm reassigning to GtkFileChooser for a second opinion.
Comment 2 Joanmarie Diggs (IRC: joanie) 2012-04-11 20:28:04 UTC 
Is this relevant w.r.t. Caribou, or something we can close out as obsolete?
Comment 3 Matthias Clasen 2018-02-10 03:27:21 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.