#36380 closed defect (bug) (fixed)
Moderate Comment screen no longer displays raw content
Reported by: | SergeyBiryukov | Owned by: | rachelbaker |
---|---|---|---|
Milestone: | 4.5 | Priority: | normal |
Severity: | normal | Version: | 4.6 |
Component: | Comments | Keywords: | has-patch commit |
Focuses: | ui, administration | Cc: |
Description
Background: #34133
Since [36588], comment content on Moderate Comment screen is formatted for display (previously it was raw HTML code, apparently since [5543]).
It looks much better, but it also makes it much easier for commenters to insert hidden spammy links on commas and other punctuation marks that cannot be caught on moderation (see the screenshots).
So it's now harder to make sure the comment has no bogus links, which I think is the purpose of this screen.
Are we all comfortable with this change?
Attachments (11)
Change History (37)
#2
in reply to:
↑ 1
@
9 years ago
Replying to johnbillion:
Maybe we need to take a leaf out of Akismet's book and display the URL after the link.
Indeed, integrating that Akismet feature would resolve this.
#6
@
9 years ago
- Milestone changed from Awaiting Review to 4.5
@SergeyBiryukov @johnbillion @helen Is this something we should fix in 4.5?
#7
@
9 years ago
- Keywords has-patch ux-feedback dev-feedback added; needs-patch needs-unit-tests removed
In 36380.diff I used the CSS :after
pseudo-element along with the content
property to output the value of the href
attributes. This is the same approach Akismet uses.
I am not happy with the CSS selectors I am using. If this approach looks good, feedback on how to best target the comment_content
here without impacting the "Edit Comment" comment link within the same table cell would be appreciated.
#8
@
9 years ago
Looks good. I'd maybe also wrap the url in parenthesis, but that's just a minor stylistic preference.
@michaelarestad what do you think about the selectors?
#9
@
9 years ago
36380.2.diff variation with parenthesis, looks like this:
I also tested in ie8 to verify the css works properly; the targeting isn't quite right in ie8, the Edit link at the bottom is also getting the link added after:
#10
@
9 years ago
- add an
edit-comment
class the<p>
tag surrounding the final link. Fixes targeting of final link in ie8.
#11
@
9 years ago
In 36380.4.diff I removed a change from #34133 (https://core.trac.wordpress.org/attachment/ticket/34133/34133_filter_text.2.diff) that wasn't intended to be included in this ticket.
This ticket was mentioned in Slack in #core by mike. View the logs.
9 years ago
#14
@
9 years ago
- Keywords dev-feedback removed
Assuming no other style changes from @melchoyce or @michaelarestad, 36380.4.diff is good to commit.
#15
@
9 years ago
- Keywords commit added; ux-feedback removed
36380.5.diff refreshes the patch after [37158]. (No lines of code were touched, but some adjacent lines were modified, making it impossible to apply cleanly.)
+1 from me to commit.
#16
@
9 years ago
The grey used ( #82878c ) has a contrast ratio of only 3.6:1 which is below the 4.5:1 WCAG 2.0 AA recommendation. Can we go darker? Perhaps using a monospaced font to help it stand out?
Patch to follow.
#17
@
9 years ago
Not sure if using the same color as the default text is a good idea. Maybe go with #555d66
instead?
#18
@
9 years ago
@ocean90 In your screenshots, are those URLs actually linked in the comment as written or were they made links through make_clickable()
? The redundancy there is pretty distracting.
#19
@
9 years ago
@helen Yeah, that's the result of make_clickable()
. I agree that it looks weird but I don't see an easy way to not target them.
#20
follow-up:
↓ 21
@
9 years ago
My goal of using the same color was to not introduce yet another gray. The difference between #444
and the other grays we have available that are accessible is fairly low.
Besides color, what other ideas do people have for making this distinct? We could try a background color, but I worry that will be to distracting.
#21
in reply to:
↑ 20
@
9 years ago
Replying to jorbin:
My goal of using the same color was to not introduce yet another gray. The difference between
#444
and the other grays we have available that are accessible is fairly low.
I think the handbook page needs an update, because http://codepen.io/hugobaeta/full/RNOzoV/ has other colors, #555d66
gets used a few times in core.
Edit: NVM, the handbook page lists just a few of them.
This ticket was mentioned in Slack in #design by jorbin. View the logs.
9 years ago
#23
@
9 years ago
Can we pick a grey that is not indistinguishable from the normal text and go with it?
Leaning towards the patch that has already been approved, but with a color with high enough contrast.
Maybe we need to take a leaf out of Akismet's book and display the URL after the link. Akismet does this on the comment listing screen: