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.

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

Data Views: when trying to bulk edit on a site with many pages, the bulk edit option counts up #63150

Closed
annezazu opened this issue Jul 4, 2024 · 4 comments
Labels
[Feature] DataViews Work surrounding upgrading and evolving views in the site editor and beyond Needs Design Feedback Needs general design feedback. [Type] Bug An existing feature does not function as intended

Comments

@annezazu
Copy link
Contributor

annezazu commented Jul 4, 2024

When selecting the bulk edit option, the option to select all counts up in situations where you have 20+ pages:

count.up.mov

This gets worse the more pages you have visible and have on your site. This is using WP 6.5.5 & GB 18.7.1 & Chrome on MacOS. You can replicate this using this link (might make you login) which will spin up a playground instance of the site I found this issue on.

@annezazu annezazu added [Type] Bug An existing feature does not function as intended [Feature] DataViews Work surrounding upgrading and evolving views in the site editor and beyond labels Jul 4, 2024
@jorgefilipecosta
Copy link
Member

Good catch @annezazu, I think this happens because the permissions of the user need to be checked to make sure the user can execute some action, while the permission checks are in place the count goes up.

There are some mitigations:

  • Not show the count while permission checks are in progress.
  • Do not show the bulk edit UI at all while the checks are in progress.

@WordPress/gutenberg-design any thoughts on the best path forward?

@jorgefilipecosta jorgefilipecosta added the Needs Design Feedback Needs general design feedback. label Jul 9, 2024
@jasmussen
Copy link
Contributor

Not show the count while permission checks are in progress.
Do not show the bulk edit UI at all while the checks are in progress.

None of those options necessarily seem great.

The thing is, select all is actually select all on the current page, not select all across every page. Correct?

Gmail has this thing where first you click this checkbox to select across all:
Screenshot 2024-07-09 at 11 35 28

That checkbox serves also as a dropdown, and is essentially the bulk-edit tool for gmail. By being a checkbox at the top of the column of checkboxes, it also implies you are selecting all on this page.

Once you do, and you have more pages, you'll see a message such as this:

Screenshot 2024-07-09 at 11 35 21

Outside of an argument to consider the same checkbox+dropdown interface for the bulk tool, one thing we could do would be to lean into the idea that "select all" is for the current page. I don't know that we need to change the wording, but we certainly don't need to check permissions do do expensive counts for anything other than the current page. I.e. the count can only ever be between the bounds of 1 and [items per page].

Secondly when selecting all, we could show either a snackbar, a notice, or that floating bulk toolbar at the bottom, to show a similar action as that of Gmail: Select all items. For this interface, we could consider showing all items in the taxonomy.

What do you think?

@jameskoster
Copy link
Contributor

I suppose this would be indirectly resolved by updating the bulk edit interface as suggested in #63193 (which needs design feedback).

The Snackbar select-all affordance is neat!

@jameskoster
Copy link
Contributor

This UI has changed and the issue no longer seems to be present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] DataViews Work surrounding upgrading and evolving views in the site editor and beyond Needs Design Feedback Needs general design feedback. [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

4 participants