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 333485 - The row separator behaves like a normal row
The row separator behaves like a normal row
Status: RESOLVED DUPLICATE of bug 441219
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.8.x
Other All
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2006-03-05 13:58 UTC by Sebastian Heinlein
Modified: 2007-05-25 22:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sebastian Heinlein 2006-03-05 13:58:45 UTC
Please describe the problem:
If you set a row to be a separator in the treeview, the separator row can be
acccesd with the up/down keys. furthermore the shading of the reading help
treats the row as a normal row:

row      -> blue
separato -> white
2nd row  -> blue

Regards,

Sebastian

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Matthias Clasen 2006-03-07 18:22:38 UTC
I don't know what you mean with the "shading of the reading", but you are
right that we need to fix keynav to skip insensitive rows
Comment 2 Kristian Rietveld 2006-03-07 20:17:24 UTC
I guess the "shading of the reading" is the rules hint?

Anyway, it might indeed be useful to disallow the cursor to come on row separators, but it should really be possible for the cursor to come on insensitive rows.  It can be possible for an insensitive row to have children (see one of the combo box examples in gtk-demo), and in such a case the insensitive row should be expandable/collapsable using the keyboard, and thus it should be possible for a cursor to come on an insensitive row.
Comment 3 Sebastian Heinlein 2006-03-07 23:10:33 UTC
Yes. It is the rules hint. I was quite in a hurry yesterday. So please excuse the bad English.
Comment 4 Kristian Rietveld 2007-05-25 22:25:10 UTC

*** This bug has been marked as a duplicate of 441219 ***