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 754019 - Inactive tab groups are not distinguishable from active tab groups
Inactive tab groups are not distinguishable from active tab groups
Status: RESOLVED OBSOLETE
Product: gedit
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-24 12:03 UTC by Sopot Cela
Modified: 2020-11-24 09:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot (59.02 KB, image/png)
2015-08-24 12:03 UTC, Sopot Cela 		Details

Description Sopot Cela 2015-08-24 12:03:24 UTC 
Created attachment 309909 [details]
Screenshot

Originally created from https://bugzilla.redhat.com/show_bug.cgi?id=1255705

Description of problem:

If you open gedit and create two tab groups by doing Right-Click on Tab -> Move to new tab group, you can not distinguish visually which one is active (has focus).

There needs to be a way of distinguishing an active tab group from an inactive one (graying out a bit, bold text etc.). 

Clarification: this is _not_ about a selected tab within a tab group but an active tab group between tab groups.
Comment 1 Sopot Cela 2016-03-31 09:33:15 UTC 
ping
Comment 2 Matthias Clasen 2016-04-02 16:38:55 UTC 
Tab groups are not a gtk concept. Moving to gedit
Comment 3 Sébastien Wilmet 2020-11-24 09:57:47 UTC 
Mass-closing of all gedit bugzilla tickets.

Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing:

2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3

By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements.

We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.