#32691 closed defect (bug) (fixed)
No-wrap the date column on post listing screens
| Reported by: | johnbillion | Owned by: | wonderboymusic |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.4 |
| Component: | Posts, Post Types | Version: | |
| Severity: | normal | Keywords: | good-first-bug has-patch has-screenshots |
| Cc: | Focuses: | ui, administration |
Description
When viewing a post listing screen in excerpt mode, the Date column can easily become very narrow. When the date text wraps, it looks awful.
Preventing wrapping in this column might be an option. Might also get messed up in some browsers due to the table-layout:fixed on the list table.
Attachments (4)
Change History (15)
#3
@
11 years ago
Agreed that the following rule makes additional styling fairly difficult to accomplish in any sort of flexible way:
table.fixed {
table-layout: fixed;
}
Most columns seem to be set to a hard 10% with the exception of the checkbox column and the excerpt column. My question is: why is this .fixed class in use? It seems like overkill given responsive best practices and prevents natural resizing for the table. Anyone know of other screens/situations in which these hard widths are necessary?
#4
@
11 years ago
First post here, looking to start helping with bug fixes.
Simply removing the .fixed class from the table seems to help. The text wraps nicely in Excerpt mode even at very small table widths once that class is removed.
But there's a lot of CSS that depends on that class being in place. If .fixed is removed, the rest of the column widths aren't declared anymore and things like the comment bubble icon get broken. I'd be hesitant to remove that class and just start rewriting all that CSS, especially as a newbie.
Changing the CSS for .fixed tables to table-layout: auto seems to work nicely, but I'm not sure what the impact of the change would be across the rest of the back-end. Can anyone confirm this suggested fix?
#8
@
11 years ago
- Resolution fixed
- Severity minor → normal
- Status closed → reopened
[34083] will break tables which have long "words" which aren't wrapped, see screencast: https://cloudup.com/iGMeRBWfHc8.
The same happens with the Syntaxhighlighter plugin.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)



Screenshot of what I'm talking about