Collapse row height on List Tables

[s3w47m88]

This is apart of a bigger project for my staff and I, you can find the context here ​https://www.theportlandcompany.com/2017/09/10/proposed-improvements-to-the-wordpress-ui/.

Our goal is to clean up the UI with two principles in mind:

• Context Visibility - Only show something when it's in context.
• Add With Purpose - If something, such as padding or margins, don't serve a purpose, don't add them.
• Simplify Number of Actions - If a step can be avoided in a process, avoid it.

Currently, when viewing something like All Posts, all of the edit settings are visible for every single item.

We developed a Plugin to hide these options until the relevant item is hovered: ​https://wordpress.org/plugins/enhanced-quickedit-bar/

Benefits

• This decreases vertical space, especially on mobile.
• This also eliminates visual distraction.
• And respect the context that users don't really *need* to see all those options.

We're open to revisions in hopes that this, or something similar to it, can be rolled into the UI.

[joyously]

What exactly is the proposal?

Are you intending different defaults for the Screen Options?

What about plugins that add columns to the list?

[s3w47m88]

Replying to joyously:

What exactly is the proposal?

We propose rolling this Plugin into the Core. My staff and I would happily extrapolate and submit it as a patch.

Are you intending different defaults for the Screen Options?

I'm not sure how this would play into Screen Options. Could you elaborate?

What about plugins that add columns to the list?

We haven't modified how the Quick Edit bar and it's respective items are registered, so Plugins that properly register new options shouldn't have any problems. We've tested this on about a dozen sites so far with a variety of Plugins - like the Clone Posts Plugin and had no issues. We were deliberate in this design decisions because even we have Plugins that add to that row.

[garrett-eclipse]

Replying to s3w47m88:

Currently, when viewing something like All Posts, all of the edit settings are visible for every single item.

We developed a Plugin to hide these options until the relevant item is hovered: ​https://wordpress.org/plugins/enhanced-quickedit-bar/

Closing as this functionality is already in core. The List Table Row Actions are hidden until rollover (hover) for supported devices.

Row Action Links -
​https://make.wordpress.org/docs/plugin-developer-handbook/10-plugin-components/custom-list-table-columns/#row-action-links

[s3w47m88]

Replying to garrett-eclipse:

Replying to s3w47m88:

Currently, when viewing something like All Posts, all of the edit settings are visible for every single item.

We developed a Plugin to hide these options until the relevant item is hovered: ​https://wordpress.org/plugins/enhanced-quickedit-bar/

Closing as this functionality is already in core. The List Table Row Actions are hidden until rollover (hover) for supported devices.

Row Action Links -
​https://make.wordpress.org/docs/plugin-developer-handbook/10-plugin-components/custom-list-table-columns/#row-action-links

The difference is that the current implementation doesn't collapse the right height. So the vertical space isn't saved. I apologize I should have clarified this! Would you consider reopening in light of this?

[garrett-eclipse]

Date Wrap Issue

[garrett-eclipse]

Replying to s3w47m88:

Replying to garrett-eclipse:

Replying to s3w47m88:

Currently, when viewing something like All Posts, all of the edit settings are visible for every single item.

We developed a Plugin to hide these options until the relevant item is hovered: ​https://wordpress.org/plugins/enhanced-quickedit-bar/

Closing as this functionality is already in core. The List Table Row Actions are hidden until rollover (hover) for supported devices.

Row Action Links -
​https://make.wordpress.org/docs/plugin-developer-handbook/10-plugin-components/custom-list-table-columns/#row-action-links

The difference is that the current implementation doesn't collapse the right height. So the vertical space isn't saved. I apologize I should have clarified this! Would you consider reopening in light of this?

Thanks for the context @s3w47m88, I've reopened (EDIT: I was but @SergeyBiryukov beat me to it) for UI/UX feedback and modified the title to have this context.

My two cents would be to leave the existing user experience. Looking at the code to accomplish a height reduction the <br> found in the date would have to be replaced with a space, but on smaller devices this reduction would disappear again as the date will wrap to two lines again and may wrap inconsistently for Modified vs New items as their lengths differ which would display inconsistently. (attached screen - https://core.trac.wordpress.org/attachment/ticket/45004/Screen%20Shot%202018-09-26%20at%204.36.52%20PM.png). As well if row actions show on hover and cause the row height to change this can be jarring for the user.

That being said I'm not on the UI/UX team so will leave this to their input.

[s3w47m88]

Thanks for re-opening.

I agree that hiding options can be confusing. However, I think that needs to be put in context of who the user is.

For example, you and I are power users. So, if you took Screen Options as an example, it's hidden by default and you and I probably agree we wouldn't want those readily visible at all times. Hence the tab effect.

But in my experience training non-developers on WordPress they aren't even aware it's there, much less what it does, until I explain it to them. So having a Custom Pointer is necessary for first-timers.

So maybe we need something like that for this? Or maybe an option in Settings to show them all the time, or hide them all the time.

I actually am working up a proposal for a universal "Hide Text / Show Icons" concept so power users can hide all the text for things that we have memorized, but users with less experience can see all the text in every possible place until they're comfortable hiding it.

Not sure if that last point / concept makes sense, it's a bit of a tangent.

[nrqsnchz]

This ticket was discussed during today's design triage in Slack (​https://wordpress.slack.com/archives/C02S78ZAL/p1583775429261400).

We agreed that this ticket should be closed in favor of #48751 where similar and more recent explorations are being discussed.

[desrosj]

Thanks @nrqsnchz! I am going to just change this to a duplicate of #48751 since that ticket also tries to solve this problem.