#48814 closed defect (bug) (fixed)
Comment marked as spam displays poorly in mobile view
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 5.4 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Comments | Keywords: | good-first-bug has-patch has-screenshots commit |
| Focuses: | ui, css | Cc: |
Description
When a comment is marked as spam from wp-admin/edit-comments.php in a mobile view, the record of the comment with the option to undo is displayed in too small of an area rather than across the comment list table.
I believe this occurs because display of the .undo td is set to block in the list table CSS when it should be the default of table-cell.
Describing this is weird, so I'm attaching a GIF. :)
Attachments (9)
Change History (30)
#1
@
6 years ago
- Keywords good-first-bug added
- Milestone changed from Awaiting Review to Future Release
This ticket was mentioned in Slack in #core by sergey. View the logs.
6 years ago
#4
@
6 years ago
@lorenzof @jeremyfelt If we remove the display property from CSS .wp-list-table tr:not(.inline-edit-row):not(.no-items) td:not(.check-column) then it will fix the issue.
#5
@
6 years ago
Thanks for the update @mukesh27
You removed the display property so that it inherits the table-cell value from td, and in that case there's no need to repeat the display: table-cell as I did my patch, right?
@
6 years ago
display:block change changed with display:table-cell and i have tested in different browsers working fine! @lorenzof
#7
@
6 years ago
@razamalik The .2 version of the patch submitted by @mukesh27 was fine and it's the best one since it's redundant to only change the value, so why you added a new version creating a patch that's the same one I submitted as .1 version, reverting his changes? .2 is fine, that's the one that need testing
#8
follow-up:
↓ 9
@
6 years ago
- Keywords needs-screenshots added
Thanks for the patches @lorenzof, @mukesh27, and @razamalik. If I follow correctly, it sounds like 48814.2.diff is the proposed solution—remove the display property for mobile?
It would also be helpful to have screenshots showing the change.
#9
in reply to:
↑ 8
@
6 years ago
Replying to jeremyfelt:
Thanks for the patches @lorenzof, @mukesh27, and @razamalik. If I follow correctly, it sounds like 48814.2.diff is the proposed solution—remove the
displayproperty for mobile?
It would also be helpful to have screenshots showing the change.
Yes, that's the right one. I appreciate the help from @razamalik who probably hasn't seen my patch but the right one it's the patch from @mukesh27. Less code, same result considering that the display: table-cell is inherited. I'll attach two screenshots from latest trunk.
#10
@
6 years ago
- Keywords has-screenshots needs-design-feedback added; needs-screenshots removed
- Milestone changed from Future Release to 5.4
Excellent, thanks @lorenzof! I'm going to add a design feedback tag here, but I think things are looking good for 5.4.
This ticket was mentioned in Slack in #design by karmatosed. View the logs.
6 years ago
This ticket was mentioned in Slack in #design by karmatosed. View the logs.
6 years ago
#13
@
6 years ago
After today's #design triage, I'm removing the needs-design-feedback as everything looks good :).
I was having some issues applying the patch so it might need a refresh, although it's a small change not sure if a committer can handle it directly :).
#15
@
6 years ago
Hi,
This small change should be refreshed and committed very soon, we are currently punting the remaining tickets in milestone 5.4 to 5.5.
Thanks!
Jb
#16
@
6 years ago
https://core.trac.wordpress.org/attachment/ticket/48814/48814.2.diff looks reasonable - do we need to adjust list-tables-rtl.css as well as in earlier versions of the patch?
This ticket was mentioned in PR #162 on WordPress/wordpress-develop by adamsilverstein.
6 years ago
#17
#18
@
6 years ago
- Keywords commit added; needs-testing removed
- Owner set to adamsilverstein
- Status changed from new to assigned
#20
@
5 years ago
Apologies, but unfortunately this minor change has caused a somewhat major regression in one of my plugins.
I can fix this for my users, but I am concerned about unreported breakage in other plugins due to the relatively reduced footprint of mobile users attempting to manage their content within WordPress Admin.
The display: block; that was removed in r47340 was necessary to override the default display: table-cell styling. Screenshot incoming to show why it is needed.
table-cell and width: auto !important will not allow for the targeted tds to occupy the full-width of the parent element.
It is also why the following rule...
.wp-list-table .is-expanded td:not(.hidden)
...still requires display: block !important;. Otherwise, it would also unintentionally risk not being full-width.
In the following rule, WordPress avoids applying styling to certain tr elements (including the dynamic .inline-edit-row one) using :not() - like:
.wp-list-table tr:not(.inline-edit-row):not(.no-items) td:not(.check-column)
I believe the non-breaking change here would have been to leave the display: block; alone, and then to add the unspam and untrash classes to the group of row classes not to target, like:
.wp-list-table tr:not(.inline-edit-row):not(.no-items):not(.unspam):not(.untrash) td:not(.check-column)
Will leave this up to the contributors here to decide how best to proceed. Sorry again, and thanks for looking & understanding. 💙
#21
@
5 years ago
Mitigated downstream in Sugar Calendar in this pull request.

Hi, I created a patch for the ticket, it's my first patch so please check if everything is ok.