[wp-trac] [WordPress Trac] #32395: Truncation is not a good strategy for responsive list tables

[WordPress Trac]

#32395: Truncation is not a good strategy for responsive list tables
-------------------------------------+--------------------------------
 Reporter:  helen                    |       Owner:
     Type:  task (blessed)           |      Status:  new
 Priority:  normal                   |   Milestone:  4.3
Component:  Administration           |     Version:  3.8
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  ui, accessibility
-------------------------------------+--------------------------------
Changes (by helen):

 * keywords:  has-patch => has-patch needs-testing


Comment:

 [attachment:32395.5.diff] is close to a first run, or even possibly a
 first run if we're comfortable with fixing the following afterward:

 * Installed themes (multisite) and plugins list tables already had special
 treatment to show all columns all the time, so they don't need the toggle
 or data attribute label.
 * Custom list tables that don't define a primary column show nothing in
 the collapsed view. We need to figure out how to handle a fallback here -
 perhaps the first column that isn't a checkbox.
 * The special case for the post comments column because the "label" for it
 contains HTML.
 * Any accessibility concerns, particularly screen readers.
 * Should we do accordion style?
 * Not sure if I made all strings translatable (can be handled pre-commit
 or in a new patch).

 Please test and note anything else you might notice.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32395#comment:40>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform