Opened 6 years ago
Last modified 4 days ago
#52151 accepted defect (bug)
Post / Page / Plugin Title Columns broken
| Reported by: | pascoedj | Owned by: | audrasjb |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Administration | Version: | 5.6.3 |
| Severity: | normal | Keywords: | has-patch early has-unit-tests |
| Cc: | Focuses: | css |
Description
The posts screen in wp-admin is wrapping the post title vertically so that the page becomes unreadable.
WordPress 5.6 running WP-Blossom theme.
screen cap here
https://1drv.ms/u/s!As8R6Nv2QLWnk9MRrGAJmuNIJ1QDoA?e=dcHWT7
sorry couldn't work out how to upload image ....
Attachments (9)
Change History (65)
#2
@
6 years ago
- Component General → Administration
- Focuses css added
- Keywords needs-patch added
- Milestone Awaiting Review → Future Release
@pascoedj Thanks for the report!
The Title column does not have a set width, and I think it needs a min-width. Categories and Tags columns are 15%, Author is 10%, Comments is 5.5em, etc. So having multiple columns added by plugins can make the Title column very narrow.
When looking at Draft posts only, you probably have fewer columns. Until this is fixed, I'd recommend opening Screen Options (at the top) and unchecking any columns you don't need to show.
#3
@
5 years ago
I have also noticed that this is NOT happening when drafts are listed, but I am not sure why.
As @sabernhardt pointed out, the title column needs a minimum width.
#4
@
5 years ago
- Milestone Future Release → 5.9
Setting min-width did not work for me with the table-layout: fixed, but there could be a better way.
#6
@
5 years ago
From what I can see, there are four options:
- Add a
widthto the title (such as 15/20%) - This will result in other columns being wrapped. - Add
overflow: hidden,text-overflow: ellipsis, andwidth: XXXpxto.fixed .column-title, truncating the title to Visible part of titl..., which will also need atitleattribute added to the link so that users can hover over to see the full title. - Remove
table-layout: fixedfrom.wp-list-table- This will reduce rendering performance for large tables, in addition to adding a horizontal scrollbar when there are a larger number of columns. - Accept that issue is caused by the number of columns and manage the column count using Screen Options.
Short of additional ideas, I would imagine that the availability of Screen Options allows most users to resolve this issue to their satisfaction, and those with specific needs have one of the other options above.
However, if the core aspect of this issue is that title in particular should never be wrapped and this is a case of tidying up, I think the first option above could be a desirable solution.
#7
@
5 years ago
I would also favor the first option you suggest, @costdev. Titles are probably the most important piece of information and the one that tends to be longer so we should prioritize it.
Also, I wonder why titles do not wrap when drafts are listed and whether we should follow that "glitch" for a possible solution.
#8
@
5 years ago
Hi @mrfoxtalbot I've tried switching to "Drafts" and adding in some extra columns, but I still get the wrapping issue.
Can you tell me the setup that you have when "All" wraps the title but "Drafts" doesn't?
- WP version
- Active theme
- Active plugins
- The columns you have displaying (in order left-to-right)
- A sample post title that doesn't wrap for you on the "Drafts" page
Thanks!
#9
@
5 years ago
The (main) difference between Drafts and All is the Comments column.
Setting a 15-20% width on the Title column can help with extra columns, but in a default installation, that can make the checkbox column wider.
#52426 is a very similar ticket, and I probably should have closed that one so the discussion there would be included here. Any change would affect both.
#10
@
5 years ago
@sabernhardt Between the CSS solution provided in the related ticket, the 15-20% width on the Title column, and the other solutions mentioned in this ticket, which (if any) seems to move us in the best direction in your opinion, including any accessibility concerns you may have?
I can submit a PR with the solution that seems most appropriate right now and we can put it out for further feedback.
#11
@
5 years ago
If we adjust the column width values, I'm not sure which is the best method. I think a change that helps in one case can be worse than the current layout in another.
Overall, removing the percentage widths from columns (including Date and/or Author, Categories and Tags) might be better than the other options. We may still want to define a width for the Title column in the Extended view:
.fixed.table-view-excerpt .column-title {
width: 20%;
}
If there is a way to count the shown columns, then keeping the current percentage widths could be better when few columns display.
Truncating the title would be an accessibility/usability concern, but the other suggested solutions are likely no less accessible than a crowded table in the current layout.
#13
@
5 years ago
- Summary post title broken on posts screen → Post / Page Title Columns broken
For the sake of reference and confirmation there is an issue how WordPress styles the columns in the Post and Page list.
So, for the benefit of this ticket, I copied the content from my other ticket (52426) and post it here since my ticket was closed and referred to this ticket here.
Below: My Report On Columns Widths Issue / Post-Page List
The width of the columns in the Post or Page table list is causing display issues in WordPress. This is especially when plugins, like Yoast, add columns.
The current CSS WordPress uses to display the table list of post or pages ends up creating a poor column layout display because it is trying to restrict the column widths.
The CSS is coming from this WordPress File:
/wp-admin/load-styles.php
These are the "ISSUE" CSS entries:
.fixed .column-author, .fixed .column-format, .fixed .column-links, .fixed .column-parent, .fixed .column-posts {
width: 10%;
}
.fixed .column-categories, .fixed .column-rel, .fixed .column-response, .fixed .column-role, .fixed .column-tags {
width: 15%;
}
.fixed .column-date {
width: 14%;
}
Here is the CSS "FIX" I applied:
.fixed .column-author, .fixed .column-format, .fixed .column-links, .fixed .column-parent, .fixed .column-posts {
width: auto !important;
}
.fixed .column-categories, .fixed .column-rel, .fixed .column-response, .fixed .column-role, .fixed .column-tags {
width: auto !important;
}
.fixed .column-date {
width: auto !important;
}
I had use "Important" because I applied the fix using a browser extension called "Stylus", which allows me to use Custom CSS and apply it to any page the browser displays.
I tested this fix in other WordPress installations and the fix works fine.
The issue is certain columns were given widths of a certain size, instead of allowing the browser to automatically adjust the columns.
You can see the difference in the screenshots I created and named them accordingly (Issue & Fix) to match the above CSS I posted.
Screenshot Images:
(1) 20210102-ISSUE-Current-Columns-Width-Post-List-Page.jpg
See Here: https://prnt.sc/y1r9nc
(2) 20210102-FIX-Current-Columns-Width-Post-List-Page.jpg
See here: https://prnt.sc/y1rd5i
Hope this helps.
Thank-you.
This ticket was mentioned in Slack in #core by audrasjb. View the logs.
5 years ago
#15
@
5 years ago
I know it's an old ticket. But the same issue still exists. In order to easily regenerate the issue, you only need to install the "Ninja Popup" plugin which is a third-party paid plugin. I had a copy of the plugin and tested it with that. Along with Ninja Popup, I've also installed and enabled the Yoast SEO plugin to make sure the issue always happens.
Ninja popup forcefully occupying 20% of the space in the table & the title column doesn't have a width value like other columns, which is the main reason behind this issue.
Now as we identified the issue if we approach a fix using min-width it won't work. Post/Page listing tables are fixed with and min-width max-width doesn't work well with this. It's a CSS issue since CSS 2.1
for this specific scenario, a solution could be applying table-specific CSS to make sure the Title column gets a fixed width. But this will break the auto-expanding of the title column while there is less column.
I'll be adding a patch for table specific CSS for Posts & Pages table.
This ticket was mentioned in Slack in #core-css by sabernhardt. View the logs.
5 years ago
This ticket was mentioned in Slack in #core by audrasjb. View the logs.
5 years ago
#19
@
5 years ago
- Milestone 5.9 → Future Release
As per today's Core bug scrub and last week's CSS scrub, let's move this patch to Future Release as it still needs a design and technical decision.
This ticket was mentioned in PR #6226 on WordPress/wordpress-develop by @D SIGNED.
2 years ago
#21
- REMOVED:
fixedvalue for table-layout - ADD: min-width to title column
Edit : New Trac ticket: https://core.trac.wordpress.org/ticket/52151
This ticket was mentioned in Slack in #core-test by ankit-k-gupta. View the logs.
2 years ago
This ticket was mentioned in Slack in #core by stoyangeorgiev. View the logs.
2 years ago
#26
@
2 years ago
OK, I reproduced the bug on WP 6.6.2 with Polylang install
Tested the fix with PR https://github.com/WordPress/wordpress-develop/pull/6226/files
cf. 
#27
@
2 years ago
Bug reproduced in reduced window with plugin Polylang setuped with 9 langs and SEO Press
Fixed with PR : https://github.com/WordPress/wordpress-develop/pull/6226
#28
@
2 years ago
Hello and thanks for the patch, its update and for testing the patch.
I also tested the patch and it introduces a change on Post screens since it adds an horizontal scrollbar on medium screen sizes when there is a lot of columns.
I'm fine with the current implementation, but perhaps we could only make the table scrollable instead?
#29
@
2 years ago
Indeed, it should be better to have table scrollable horizontally.
However, we would need to wrap the .wp-list-table inside a div like .wp-list-table-wrapper which would be styled with overflow: scroll;
See https://stackoverflow.com/questions/19794211/horizontal-scroll-on-overflow-of-table
https://core.trac.wordpress.org/attachment/ticket/52151/wp-list-table-wrapper.png
#30
@
2 years ago
- Milestone 6.7 → 6.8
With 6.7 RC 1 releasing today this ticket is being moved to 6.8.
If any maintainer or committer feels the remaining work can be competed in time for 6.7 feel free assume ownership and update the milestone accordingly.
This ticket was mentioned in Slack in #core by audrasjb. View the logs.
21 months ago
#34
@
21 months ago
In order to make an accessible side-scrolling container, we'll need to 1) add tabindex="0" to the wrapper, so that it can accept keyboard focus and be scrolled from the keyboard; 2) add role="region" and aria-label="[context label]", so that when screen reader users reach the table, they are given context about what they've navigated to.
The aria-label can probably use the existing screen reader text placed in the hidden heading above the table, but can't be a substitute for it; they serve different purposes.
It can be helpful for usability to provide a visual cue that the table requires horizontal scrolling; something like horizontally scrolling shadows can be helpful.
Overall, the reality of tables is that sometimes scrolling is necessary, and we should adapt for it as best we can. It is pretty crucially important that the title is always readable.
#35
@
21 months ago
- Keywords early added
- Milestone 6.8 → 6.9
Moving to 6.9 early as 6.8 beta 1 is today. We should get this committed before the first beta of the cycle and it's too late now for 6.8.
#37
@
13 months ago
- Summary Post / Page Title Columns broken → Post / Page / Plugin Title Columns broken
- Version 5.6 → 5.6.3
Hello Team,
Additionally, the plugin listing table has an issue with the plugin name column. If the plugin name is too long, the table adds a horizontal scroll.
Here is a screenshot of the issue:

To address this, I have figured out the following CSS fix:
.plugins .inactive .plugin-title strong {
font-weight: 400;
white-space: break-spaces;
}
This should prevent the horizontal scroll for long plugin names.
This ticket was mentioned in PR #13866 on WordPress/wordpress-develop by @mattmiklic.
7 weeks ago
#39
- Keywords has-unit-tests added
List tables can squeeze columns into an extremely narrow state when they need more space than the table has available. Plugins that add columns can leave little room for content like post titles, producing tall rows that are difficult to scan.
This adds a scrollable wrapper around the existing table. Above the existing mobile breakpoint, tables switch from fixed to automatic layout, with minimum widths for selected Core columns. When the columns exceed the available space, the wrapper scrolls horizontally. Filters, bulk actions, and pagination stay outside the wrapper.
The table's border moves to the new wrapper, and a fade to white inside it indicates that there is hidden content on the right edge. When scrolling, the fade appears on the left as well, when content is hidden on that edge. These are reversed for RTL content. JavaScript in common.js updates the fades during scrolling, resizing, and when tables are replaced or refreshed in place, like when searching Plugins.
When there is horizontal scrolling, the wrapper enters the Tab order so it can be focused and scrolled with the arrow keys. When a table's content fits in the viewport, the wrapper isn't included in the Tab order.
Screenshots
Narrow columns
With enough columns enabled, titles and headers become difficult to read. The updated table ensures readable column widths and scrolls to reveal the remaining content.
| Before | After |
|---|---|
| | |
Columns that fit without scrolling
With fewer columns visible, the table fits without horizontal scrolling. Automatic layout gives the date column more room, reducing wrapping and row height in this example.
| Before | After |
|---|---|
| | |
Content that prevents wrapping
Preformatted text, text forced onto one line, or a fixed-width widget previously overflowed outside their column, colliding with the content in any that follow. Now, that column expands to contain whatever is in it, and the horizontal scrolling contains it.
| Before | After |
|---|---|
| | |
Testing
The included tests cover initialization, LTR/RTL scrolling, fractional positions and overscroll, resizing, keyboard focus, and cleanup when tables or wrappers are replaced or moved.
To test in the admin:
- Open Posts with enough visible columns enabled to crowd the table. Size the window larger than the mobile breakpoint, and confirm the columns remain readable as the table begins to scroll.
- Scroll to both ends and confirm each fade appears only when content is hidden on that side. Repeat in an RTL locale.
- Tab to an overflowing wrapper and scroll with the arrow keys. Check that a table which fits does not add a Tab stop, and that sorting links retain a complete focus indicator.
- Resize below the mobile breakpoint and check the existing mobile layout remains unchanged.
Trac ticket: https://core.trac.wordpress.org/ticket/52151
Use of AI Tools
AI assistance: Yes
Tool(s): Codex (ChatGPT)
Model(s): GPT-6 Astra
Used for: Developing and iterating on the implementation, writing regression checks and documentation, researching browser support, and assisting with code review.
#40
in reply to: ↑ description
@
7 weeks ago
I keep seeing this issue come up, so I opened this PR to try a new approach to solving it. I'd appreciate any thoughts you have! https://github.com/WordPress/wordpress-develop/pull/13866
@Joen commented on PR #13866:
7 weeks ago
#41
This has kept coming up for me constantly over the years, I've multiple friends and family I've helped with website, they install a single plugin and on their 14 inch laptops, their columns implode. A contextually available scrollbar feels like such a better choice.
I would love if folks could give deep reviews of this one so we can land it. If not in 7.2 then 7.3—it's been an issue for a while and it's worth going straight at it.
#42
@
6 weeks ago
Love this. It seems to also relate to this issue in the Gutenberg repo: https://github.com/WordPress/gutenberg/issues/84036
@westonruter commented on PR #13866:
4 weeks ago
#43
Preformatted text, text forced onto one line, or a fixed-width widget previously overflowed outside their column, colliding with the content in any that follow. Now, that column expands to contain whatever is in it, and the horizontal scrolling contains it.
This doesn't seem ideal to me. Wouldn't it be better if the cell column itself became horizontally scrollable? If you had 25 comments on a page, and only one of them was extremely wide, then all of the other rows would similarly have their content unnecessarily shown without any line breaks, making reading much harder.
@Joen commented on PR #13866:
4 weeks ago
#44
Just noting a thank you Weston, for reviewing!
@mattmiklic commented on PR #13866:
4 weeks ago
#45
This doesn't seem ideal to me. Wouldn't it be better if the cell column itself became horizontally scrollable? If you had 25 comments on a page, and only one of them was extremely wide, then all of the other rows would similarly have their content unnecessarily shown without any line breaks, making reading much harder.
Sure, I gave this a try. I think it mostly works, aside from a bit of unease about the edge case where there's scrolling content inside a scrolling table (where there's both overflowing content and the table is wider than the viewport). But I do think it's quite an edge case. This approach seems to fix the main issue of overly-narrow columns while supporting overflowing content better than we did before.
With standard scrollbars:
https://github.com/user-attachments/assets/1f5baa1d-704b-4d20-842f-f9e93c54fb2c
With MacOS "automatically based on mouse or trackpad" scrollbars:
https://github.com/user-attachments/assets/4adf8ed1-5611-4a5c-bc2c-ac836bc7343f
I've also incorporated the other suggestions. Thanks for the review, @westonruter!
@mattmiklic commented on PR #13866:
4 weeks ago
#46
aside from a bit of unease about the edge case where there's scrolling content inside a scrolling table (where there's both overflowing content and the table is wider than the viewport)
I think I've managed to address this, too. My changes were forcing the comment column to be wide when there was scrolling content inside it; now it reduces in width as the viewport is sized down.
https://github.com/user-attachments/assets/32cabce0-99f7-4f82-945e-54aad2d49d39
@Joen commented on PR #13866:
4 weeks ago
#47
Thanks all for keeping at this, this is a decade-old bug and it seems clear as day that this branch is better than trunk: an extreme-edgecase nested horizontal scrollbar is substantially preferable to columns imploding to illegible single-letter columns. It must surely be more accessible to be able to read what's there.
My understanding is that this _nested_ horizontal scrollbar exists only in edgecases where a comment uses a pre tag and has very wide text, e.g. code samples. The two solutions discussed are: allow this to stretch, and force a nested scrollbar.
Have you considered the third option? Enforcing word-breaks on nested pre-tags? It could look like this:
td pre {
white-space: pre-wrap;
overflow-wrap: anywhere;
}
Add in some !importants if you have to. The point is: the contents of a comment table cell is an excerpt. This isn't where you're meant to read code samples. It exists to give you an impression of the comment, what it's about, in part in order to let you decide if this is spam or not. Enforcing wrapping would very probably make this effort both more responsive, simple, accessible, and legible, yes?
@mattmiklic commented on PR #13866:
4 weeks ago
#48
Thanks, @jasmussen!
My understanding is that this _nested_ horizontal scrollbar exists only in edgecases where a comment uses a
pretag and has very wide text, e.g. code samples. The two solutions discussed are: allow this to stretch, and force a nested scrollbar.
Have you considered the third option? Enforcing word-breaks on nested pre-tags? It could look like this:
That can definitely be a solution when it's just preformatted text with no spaces. I think we need the horizontally scrolling containers in other cases, like where a plugin adds markup to a comment that sets white-space: nowrap or a fixed width, like in this example:
But as you see there, I think this could be a "yes, and" situation where we scroll if there's markup that requires it, but uses simpler forced wrapping when it's just a long preformatted string.
One unrelated change: I've flip-flopped between a white fade and a shadow a few times. I've switched back to a shadow after seeing how the yellow background of an unapproved comment clashes with the white fade. This also looks a bit nicer with the zebra-stripe gray backgrounds elsewhere in list tables. It's subjective though, and I don't hold this opinion strongly, so I'm happy to commit to either the fade or the shadow.
@Joen commented on PR #13866:
4 weeks ago
#49
To be clear and to reiterate, this feels substantially better than trunk, so wherever we land in this first version, it will be an improvement. And it doesn't preclude further optimisations around nested horizontal scrolling or not.
I'm still not fully understanding why pre-wrap'ed text needs to be allowed in a list table. But well, with such a massive part of the web using the software, sure: there's probably a good use case out there some where. While I would _personally_ start with enforcing wrapping, I'll defer to you all as the experts.
One unrelated change: I've flip-flopped between a white fade and a shadow a few times.
I honestly still prefer the white fade, for system reasons, actually. The shadow implies depth where there isn't any depth, this is just a single flat surface. So I'd still like to start with the white one. But as with all things, if you feel strongly: go with your gut on this one. I'm just providing opinions, and the end-goal of this one remains, as my first paragraph noted, such an improvement.
@mattmiklic commented on PR #13866:
4 weeks ago
#50
No problem, like I said, I have an aesthetic preference for the shadow because it feels like it plays better with the colors that can be applied to a list table row background, but it's not strongly held. I've switched back to the white fades.
I'm still not fully understanding why pre-wrap'ed text needs to be allowed in a list table. But well, with such a massive part of the web using the software, sure: there's probably a good use case out there some where. While I would personally start with enforcing wrapping, I'll defer to you all as the experts.
Yep, I've got the CSS in place so <pre> wrapped strings will wrap now. The main reason to include the content wrapping is because plugins can inject HTML into comments that can make text flow outside their cells:
It's certainly an edge case though. The alternative would be letting the cell expand to fit, as shown in the initial screenshots:
@Joen commented on PR #13866:
3 weeks ago
#51
I would love to start with the forced wrapping, and then we can respond to issues raised by plugins that inject HTML there, perhaps. It's ideally going to land early in 7.3 so there will be plenty of surface area to test.
On the shadow, if you feel strongly, I'll personally support you. A quick ping to @jameskoster though, I think as we chatted about this he suggested the white.
@jameskoster commented on PR #13866:
3 weeks ago
#52
@mattmiklic commented on PR #13866:
3 weeks ago
#53
Thanks @jasmussen and @jameskoster.
I would love to start with the forced wrapping, and then we can respond to issues raised by plugins that inject HTML there, perhaps. It's ideally going to land early in 7.3 so there will be plenty of surface area to test.
Totally fair; I was solving for plugins that could cause excessive wrapping, but I'm fine with taking a simpler approach and expanding if it's needed. I backed out the in-cell content wrapping JS, but left the pre wrapping as it was just too lines of CSS.
I think the fade works better when it matches the row background.
I didn't think this was possible, but I had an agent give it another try and it worked fine. Also works on the yellow cells for unapproved comments.
These changes have been committed and pushed to the branch if you want to take another look.
@mattmiklic commented on PR #13866:
3 weeks ago
#54
@westonruter just for awareness -- based on the feedback from @jasmussen I removed the in-cell scrolling when there's plugin-generated wide content in a comments row. The logic is that it's enough of an edge case to leave out unless we discover a real-world case where it's an issue -- the cases I designed for initially were theoretical. There should be plenty of time for this to be tested and iterated upon if it's needed. Let me know if you disagree or have any other feedback here!
@Joen commented on PR #13866:
5 days ago
#55
I'd love to get this in as early as possible in the 7.3 cycle, so I pinged a few folks! Thank you all for looking.

I should add that if I select Drafts(X) to show just the drafts, it works fine, but when I select All(X) the bug shows again. The post breaking the display is a draft.