Make WordPress Core

Opened 16 months ago

Last modified 5 months ago

#58638 assigned enhancement

Add 'close' button to dashboard widgets

Reported by: oglekler's profile oglekler Owned by: oglekler's profile oglekler
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Administration Keywords: needs-patch 2nd-opinion needs-design-feedback
Focuses: ui, administration Cc:

Description

In the Dashboard it isn't obvious that widgets can be removed from it via Screen options and sometimes widgets are annoying, or you just don't need them. I suggest adding close button into dashboard widget header.

Attachments (1)

58638-close-button-to-widget.png (25.7 KB) - added by oglekler 16 months ago.

Download all attachments as: .zip

Change History (18)

This ticket was mentioned in Slack in #mobile by oglekler. View the logs.


16 months ago

#2 @costdev
16 months ago

Sounds like a good idea!

Which is more appropriate in this case, "close" or "hide"?

Also, it may not be clear that the dashboard widget can be re-added. An "Undo?" button would only be good in case of a mistake, but wouldn't appear on the next page load, so it might be worth having messaging after clicking a close/hide button to direct the user to the "Screen" tab.

#3 @peterwilsoncc
16 months ago

This came out of discussion on #56277, a proposal to market the mobile apps on the WordPress dashboard.

To be clear, I don't think this is needed for all the widgets but rather for marketing and other widgets widgets that aren't needed on an ongoing basis.

A little friction to prevent people hiding the site health, at a glance widgets and other core widgets is a good thing. It limits hiding them to people who are more likely to know what they are doing.

The Welcome banner widget includes a dismiss button in addition the screen options setting as it isn't needed on an ongoing basis.

#4 follow-up: @oglekler
14 months ago

  • Milestone changed from Awaiting Review to 6.4

We have another proposal about Dashboard widget: #57785 and I think this close button can be useful to remove clutter and leave only widget user needs. It looks like it is not difficult to implement, and I am moving it into 6.4 but not sure if this can be a good-first-bug.

This ticket was mentioned in Slack in #core by oglekler. View the logs.


14 months ago

#6 @oglekler
14 months ago

  • Keywords needs-patch added

This ticket was mentioned in Slack in #core by marybaum. View the logs.


14 months ago

#8 @marybaum
14 months ago

  • Owner set to oglekler
  • Status changed from new to assigned

@oglekler has volunteered to take this on. Close button, here we come!

#9 in reply to: ↑ 4 @peterwilsoncc
14 months ago

Replying to oglekler:

We have another proposal about Dashboard widget: #57785 and I think this close button can be useful to remove clutter and leave only widget user needs. It looks like it is not difficult to implement, and I am moving it into 6.4 but not sure if this can be a good-first-bug.

I agree a close button is useful for widgets that can be considered clutter, to use your term, but I don't think that means they're a good idea for all widgets.

The site health widget warns site owners of issues with their site, including if they are running a version of PHP no longer receiving security updates. The current friction for closing the widget is necessary as it prevents mis-clicks.

The "Welcome to WP X.X" widget includes a dismiss button as once it's read, it's purpose is reduced: site owners have been informed of the key new features and, possibly, clicked through to the about page to read more.

#10 @azaozz
13 months ago

  • Keywords 2nd-opinion added

In the Dashboard it isn't obvious that widgets can be removed from it via Screen options

How about instead of adding yet another button to (some) widgets, the fact that the screen can be customized and widgets can be shown, hidden, moved around, opened, closed, etc. is made more discoverable? Thinking this would be more beneficial than "cluttering" the widgets top bars with more and more buttons (the three existing buttons are somewhat confusing as is, with the different shape arrows) :)

One possible solution would probably be to remove the existing buttons, and add one "hamburger" or perhaps "gear" button to the top bar. Clicking that would open the Screen Options. This will also mean closing and opening widgets may need to be added to Screen Options too, and of course some more text explaining that clicking on the top bar would toggle the widget.

Last edited 13 months ago by azaozz (previous) (diff)

#11 @oglekler
13 months ago

  • Milestone changed from 6.4 to 6.5

I didn't have time to work on this patch and no one picked up this so far, so I am moving this ticket into 6.5 in hope that we will make a progress there.

This ticket was mentioned in Slack in #core by abhanonstopnews. View the logs.


11 months ago

#13 @jorbin
11 months ago

I'm not sure a link to screen options on every widget is going to have enough good friction to discourage the removal of site health and other core widgets like events.

If the goal is improving discovery for screen options, perhaps a solution would be an admin notice on the dashboard that shows up a week or so (or perhaps after a certain number of widgets are present) after install in order to promote them? That allows some time for people to install plugins that can contribute to the "clutter" that some folks feel?

#14 @oglekler
11 months ago

  • Keywords needs-design-feedback added

This ticket was discussed during bug scrub: https://wordpress.slack.com/archives/core/p1699990223695029

Add props to @webcommsat

Continuing the conversation, admin notices are very annoying and this is not a solution users will like. We have another ticket to improve screen options: #21583

It was also suggested already not to add this close button to the Health widget.

To ensure that people will understand how to access widgets, the close button needs to add a message that with something like this: "Widget is removed. It can be returned to the Dashboard from the Screen options (see tab in the right top corner of the window)" instead of the widget, give it a time and remove as well. This way, people will know what to do.

@joedolson can you please provide feedback on such solution. Thank you!

This ticket was mentioned in Slack in #core by abhanonstopnews. View the logs.


10 months ago

#16 @swissspidy
8 months ago

  • Milestone changed from 6.5 to Future Release

Moving out of the milestone as there is no patch and 6.5 Beta is approaching.

This ticket was mentioned in Slack in #core-restapi by petitphp. View the logs.


5 months ago

Note: See TracTickets for help on using tickets.