Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move "Deactivate/Activate all" to top of list #8878

Open
forteller opened this issue Jan 5, 2022 · 13 comments · May be fixed by #10556
Open

Move "Deactivate/Activate all" to top of list #8878

forteller opened this issue Jan 5, 2022 · 13 comments · May be fixed by #10556
Labels
new contributor opportunity Best for first-time contributors without prior experience. You won’t be assigned; PRs welcome!

Comments

@forteller
Copy link

Description

When choosing which objects to show there's a long list of objects to choose from, and at the very end there's the options "Deactivate all" and "Activate all". Good options to have, but only if you know they're available. And having them at the very end of that long list makes them very easy to overlook. I think it would be much better to have them at the top instead, so they're discoverable by everyone.

Thanks!

Screenshots

Screenshot from 2022-01-05 20-07-06

Here you can see that the options to activate or deactivate all is hidden until you scroll down
@boothym
Copy link
Contributor

boothym commented Jan 6, 2022

I raised this a couple of years ago #7275 - but was told it "looks pretty bad" at the top, despite the obvious UI benefits to not having to scroll down every time.

@forteller
Copy link
Author

Thanks for the heads up!

I really, truly can not see how this looks any worse than having them just as a loose tail at the bottom
Screenshot from 2022-01-06 19-44-40

@bhousel
Copy link
Member

bhousel commented Jan 6, 2022

I really, truly can not see how this looks any worse than having them just as a loose tail at the bottom

hey @forteller I think your screenshot looks pretty good and probably would have accepted PR #7286 if it looked like that.
#7286 instead had these links in a new block with a bunch of padding around it - it just looked too spaced out.

@forteller
Copy link
Author

Hi, @animesh-007, would you be interested in trying to implement this in this way? Thanks! :)

@animesh-007
Copy link
Contributor

Hi @forteller, Sorry but I will not able to implement it now. If you want you can try.😇

@1ec5 1ec5 added the new contributor opportunity Best for first-time contributors without prior experience. You won’t be assigned; PRs welcome! label Oct 15, 2024
@arwin4
Copy link

arwin4 commented Oct 18, 2024

I would like to work on this. (Would be my first issue.)

@draunger
Copy link
Contributor

@forteller can i do that this issue if @animesh-007 is not doing anything ?

@forteller
Copy link
Author

Sure, that would be great! Should just ask is @arwin4 has started yet first :)

@arwin4
Copy link

arwin4 commented Nov 10, 2024

@forteller @draunger
I have already done some work, but was waiting to be assigned the issue. I'll continue this week.

@arwin4
Copy link

arwin4 commented Nov 19, 2024

@forteller @draunger
Sorry for the delay, but I've been unable to continue work on this. Feel free to pick this up.

@draunger
Copy link
Contributor

@arwin4 are you doing this now or not ?

@arwin4
Copy link

arwin4 commented Nov 19, 2024

@arwin4 are you doing this now or not ?

I'm not, sorry.

@draunger
Copy link
Contributor

draunger commented Nov 21, 2024 •
edited
Loading

@arwin4 ok then I will do this issue

@draunger draunger linked a pull request Nov 25, 2024 that will close this issue
Open
@kiralightyagami kiralightyagami mentioned this issue Dec 7, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new contributor opportunity Best for first-time contributors without prior experience. You won’t be assigned; PRs welcome!
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fixed the disable and enable button position draunger/iD-1
7 participants
@bhousel @forteller @1ec5 @arwin4 @boothym @animesh-007 @draunger