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 353814 - Adding Bidi features to Context menu
Adding Bidi features to Context menu
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTextView
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Behnam Esfahbod
gtk-bugs
Depends on: BidiKeyboard 353812
Blocks: Persian 312006
 
 
Reported: 2006-09-01 10:42 UTC by Behnam Esfahbod
Modified: 2018-04-15 00:29 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Behnam Esfahbod 2006-09-01 10:42:24 UTC 
After detection of a bidi user (bug 353805) and implementation of bidi features (bug 353812), GTK+ should allow user to use bidi features (changing the paragraph direction; embedding the selected part, etc) from the text-entry's context menu.
Comment 1 Elijah Newren 2006-10-22 03:42:13 UTC 
Feature request->not a showstopper.  :-)  I'm clearing the gnome-target field.  (gnome-target is meant to be used on bugs severe enough to possibly require
delaying GNOME releases.  The target milestone field can be set by maintainers for bugs they'd like to remember to fix by a certain release.  See also
the "Target Milestone" and "GNOME Target Milestone" sections of
http://bugzilla.gnome.org/page.cgi?id=bug-status.html.)
Comment 2 Matthias Clasen 2018-02-10 05:07:37 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 3 Matthias Clasen 2018-04-15 00:29:47 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