|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Screenshots attached
IMO, there is a pretty simple way to fix this for both camps. The example I'm going to use is in JIRA (5.2 – this version does not behave the same). Several of the fields on the View-Issue page can be edited inline by just hovering over the field (which changes the appearance immediately, making it obvious that it's editable, and introducing a pencil/edit icon next to the field), and when you click (either on the text or on the pencil icon), it transforms into an editable field. You can see that with the 3 screenshots I'm attaching.
I think a good way to fix this problem would be to follow similar logic: instead of having the menu pop up on hover of the link itself, change it so hovering on the link transforms the appearance of the link into something that has the down-arrow icon and draws attention to that icon. Then you can make it where hovering (or clicking, if people are still adamant that it gets in the way) on the down-arrow icon brings up the context menu. That way the hover effect will not be as distracting to people who dislike it, and the context menu is still discoverable and easy to access for people who do like it.
I use the context popup all the time, because it does take so long to jump around, especially when the important part of a build that I need to get to quickly is the build's console. But yes, it does have many quirks – especially when I'm trying to reconfigure several jobs at a time (hover, cmd+click "Configure" link; next job: hover, cmd+click configure; etc...), the menu from one used to always cause the menu for the one I'm aiming for to disappear prematurely, etc. Sounds like KK fixed that particular issue, so that's nice .. but too little too late, since now the hover feature itself is completely gone :\
I think if the down-arrow appears on hover of the link, and hovering on the down-arrow brings up the menu, it would appease those who prefer not to see the context menu, while still making it easily discoverable and accessible for people who do (no clicking required, just hover on the link, move over to the arrow icon, and the menu comes out)