Community
Participate
Working Groups
Created attachment 204455 [details] screenshot I was trying to stage a bunch of commits and thought, "hey, where did that select all checkbox and unstage command go?" The problem was I had scrolled down a little and didn't expect the command to scroll with it. (since our "real" commands do not scroll, and since the compare commands on the right don't scroll. I started to open a bug saying "the unstage command shouldn't scroll" but I think the real fix here is for us to have a common way to do select all/deselect all, and then Stage would just be a normal selection based command (up in the toolbar).
See also bug 359404.
Libing, I'd like to steal this bug from you because we have differing selection/scrolling/cursoring models in many places and we want to try to make these consistent for 0.5. (This will probably break out into a bunch of different bugs, but for now I'd like to steal it and then break it out from there....)
(In reply to comment #2) > Libing, I'd like to steal this bug from you because we have differing > selection/scrolling/cursoring models in many places and we want to try to make > these consistent for 0.5. > > (This will probably break out into a bunch of different bugs, but for now I'd > like to steal it and then break it out from there....) You are not stealing, you already let me know :-)... Yeah, I think you mentioned a good point as well in Bug 349328 comment 19. I am putting dependency again.
The original problem here will probably go away given the rework of git status in bug 349328. We expect the "selection list" to go away, replaced by an outliner and diff sections. However I'd like to keep it open and own it as a reminder to revisit the new git status page and ensure that we are good.
(In reply to comment #4) > The original problem here will probably go away given the rework of git status > in bug 349328. We expect the "selection list" to go away, replaced by an > outliner and diff sections. However I'd like to keep it open and own it as a > reminder to revisit the new git status page and ensure that we are good. I think we've done the initial work here in bug 377018. Note there is still some work to do but this is tracked in more specific bugs (bug 380004 and bug 379811)
