3 | | * For the sake of (future) consistency, should a registration pattern for modes (eg `array( key => label )`) not be better suited? The new hooks (looking at `wp_table_view_modes`) provide a lot of room for deviations in HTML markup. Might I suggest to use a filterable list of modes, which would allow for removing modes and reordering modes, as well as a consistent output of HTML markup handled by core. |
| 3 | * For the sake of (future) consistency, should a registration pattern for modes (eg `array( key => label )`) not be better suited? The new hooks (looking at `wp_table_view_modes`) provide a lot of room for deviations in HTML markup. Might I suggest to use a filterable list of modes, which would allow for removing and reordering modes, as well as a consistent output of HTML markup handled by core. |
| 4 | * Also, why is renaming the `excerpt` mode key not expected to affect backwards compatibility? |