Make WordPress Core

Opened 2 years ago

Last modified 4 months ago

#26575 new defect (bug)

Dashboard widgets should be able to specify a min-width at which they span two columns

Reported by: markjaquith Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 3.8
Component: Administration Keywords:
Focuses: Cc:


Some dashboard widgets don't do well in skinny columns. Maybe we should let them specify a min-width. If breached, they could span two columns. Certainly would be useful for stats/traffic widgets.

Change History (6)

#1 @mattbeck
2 years ago


Large screens with small numbers of widgets are implemented badly in the current responsive design.

Content is squashed into tiny columns, and the column count expands past the number of active widgets.

Best case would be for the number/width of columns to adjust to the number of active dashboard widgets instead of displaying the empty drag/drop areas.

In lieu of that some mechanism to specify either column-count of a widget intended to be wide and/or better yet - maximum number of columns to display on the dashboard would be great.

#2 @helen
2 years ago

I actually asked about multi-column width widgets and a Masonry-esque layout during DASH dev - I think it'd be a great thing to iterate and make better. I also really like the idea of being even smarter and adjusting based on how many widgets are shown as well.

#3 follow-up: @toscho
2 years ago

  • Cc info@… added

The existing user controls worked well. They still do, once reactivated, see #26354.

The plain number of widgets doesn’t tell us anything about the space they need. That depends on their content and the user’s font size settings.

#4 in reply to: ↑ 3 @SergeyBiryukov
2 years ago

Replying to toscho:

The existing user controls worked well. They still do, once reactivated, see #26354.

FWIW, that snippet only works for switching between 1 or 2 columns. I've tried to increase the max parameter to 4, but that didn't work.

#5 @RobertPHeller
23 months ago

  • Cc heller@… added

#6 @lkraav
4 months ago

Sounds like the column system needs to make some kind of a solid promise about what a column means at its minimum width. Then widget implementations should define their width in columns, not pixels. Math magic should try to work out the rest - responsive collapsing, fitting 2x2 grid where needed at higher resolutions, etc.

Is anybody actively looking into this as of lately?

Note: See TracTickets for help on using tickets.