Community
Participate
Working Groups
Created attachment 192301 [details] screenshot The hovering actions disappear when you mouse out of a navigator row. This is okay except for the case where you are selecting something from an action's push button menu that is dropped down past the row. In that case we want the actions column to stay visible.
I think it makes sense to address this alongside bug 338888, where we will introduce some kind of lifecycle for menus for inserting commands on menu open.
this bug is particularly bad on git clones page, where there is a lot of space between the branch name and the actions column. It's hard to be sure you fetched, etc. from the right repo.
we need to revisit the hover approach in general (for touch, etc.) and once we know what we wish to do, fix problems like these (if they still exist)
fixed in 0381955c9eef7286e3804cb07b13be2d3fb5ee1b This has been driving me nuts forever. The idea that we could have "menu knows when it is open" styling behavior was not going to work as long as we were hiding the parent span in the navigator. This also was an accessibily problem because you could never tab to the actions. I removed the nav code that hide/shows the containing parent. I added command service code to allow active/inactive classes in addition to the classes the command framework uses. I also added some dijit styling to keep the hover background when the menu is selected (focused). So now the menu button stays "hover gray" while it's active. The only time that it's hard to tell is if you have a bunch of rows selected with the checkbox. Then the gray background is the same as selection background. But even then, the text itself is darker when the menu is active.
