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 596985 - [dash] Allow clicking on any part of section header to browse
[dash] Allow clicking on any part of section header to browse
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2009-10-01 13:22 UTC by Colin Walters
Modified: 2010-12-04 03:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
[dash] Allow clicking on any part of section header to browse (3.22 KB, patch)
2009-10-01 13:22 UTC, Colin Walters
needs-work Details | Review
Updated patch (2.43 KB, patch)
2009-11-16 13:43 UTC, Florian Müllner
accepted-commit_now Details | Review
Allow clicking on any part of section header to browse (2.37 KB, patch)
2009-12-17 22:09 UTC, Florian Müllner
committed Details | Review

Description Colin Walters 2009-10-01 13:22:19 UTC
This is more intuitive, though we need to make the whole thing
feel more like a button.
Comment 1 Colin Walters 2009-10-01 13:22:21 UTC
Created attachment 144499 [details] [review]
[dash] Allow clicking on any part of section header to browse
Comment 2 Owen Taylor 2009-10-01 21:16:40 UTC
Review of attachment 144499 [details] [review]:

I think the behavior is OK as an easter-egg addition, but nobody is going to find it - it's very clear with the dull gray text as opposed to the bright text of More and no prelighting that the header isn't clickable :-) One problem with the code noted below.

::: js/ui/dash.js
@@ +526,3 @@
+
+    _onButtonPress: function() {
+        this.moreLink.activate();

Chaining this through moreLink, when the moreLink is no longer reactive is a little peculiar. 

Also, clicking on Places, which doesn't have a moreLink now produces:

    JS ERROR: !!!     message = 'this.moreLink is undefined'
Comment 3 drago01 2009-10-02 11:16:37 UTC
(In reply to comment #2)
> Review of attachment 144499 [details] [review]:
> 
> I think the behavior is OK as an easter-egg addition, but nobody is going to
> find it - it's very clear with the dull gray text as opposed to the bright text
> of More and no prelighting that the header isn't clickable :-) 

There are some users that try to click on "Application" even though it does not look click able.

Maybe we could even get rid of "More" and make the bar highlighted on mouse over (and change the cursor to make it clear that it is click able), that would fix the translation issue for good too.
Comment 4 Florian Müllner 2009-11-16 13:43:50 UTC
Created attachment 147885 [details] [review]
Updated patch

Updated Colin's patch to apply to master and fix the places error.
Comment 5 Colin Walters 2009-12-17 17:12:42 UTC
Review of attachment 147885 [details] [review]:

The design is still evolving in this area; talking to mccann a plan is to move the section headers away from feeling like boxes/buttons, and making the clickable area for the expander bigger.  But as a shorter term thing I think we can put this in.
Comment 6 Florian Müllner 2009-12-17 22:09:32 UTC
Created attachment 149944 [details] [review]
Allow clicking on any part of section header to browse

No code change since the previous patch, but applies cleanly to master.
Comment 7 Florian Müllner 2009-12-20 01:14:16 UTC
Comment on attachment 149944 [details] [review]
Allow clicking on any part of section header to browse

Attachment 149944 [details] pushed as 6e1a791 - Allow clicking on any part of section header to browse