@KiraNoot I think the report button should be moved out of focus, to the upper or lower right corner of a comment. I believe this would reduce the amount of false reports that are meant to be comments.
Posted under Site Bug Reports & Feature Requests
@KiraNoot I think the report button should be moved out of focus, to the upper or lower right corner of a comment. I believe this would reduce the amount of false reports that are meant to be comments.
This garbage kind of works:
.forum-post .content-menu menu li + li {float:right} .comment:not([data-creator="dubsthefox"]) .content-menu menu li + li + li + li + li + li + li {float:right} .comment[data-creator="dubsthefox"] .content-menu menu li + li + li + li + li + li + li + li + li {float:right}
Seconding this.
I agree, i have clicked the report button when i meant to reply to someone.
Fourthing this, the ticket queue is backed up enough with people reporting stuff they should blacklist and/or comments from a decade ago. At least eliminating the mistaken comments posted using the report button would cut the queue down a bit.
dubsthefox said:
@KiraNoot I think the report button should be moved out of focus, to the upper or lower right corner of a comment. I believe this would reduce the amount of false reports that are meant to be comments.
I still favor color deviation forum #320071
Looking through tickets, it looks like people still accidentally submit comments as reports. It would be helpful to the mods if the report button was made distinct in some way, as well as benefit the people who unknowingly have their comment put in the wrong place.
lance_armstrong said:
This garbage kind of works:.forum-post .content-menu menu li + li {float:right} .comment:not([data-creator="dubsthefox"]) .content-menu menu li + li + li + li + li + li + li {float:right} .comment[data-creator="dubsthefox"] .content-menu menu li + li + li + li + li + li + li + li + li {float:right}
Hm, this might be more generic, and doesn't depend on :not():
.forum-post .content-menu menu li { float: left; } .forum-post .content-menu menu :last-child { float: right; }
It does depend on the 'Report' link being the last one, but that seems to already be the case as far as I know.
Edit 1: Hm, it also causes the cluster of links for one's own post to be slightly closer together than before, probably due to the float: left;.. But without that, for some reason floating only the one link to the right causes them all to jumble up on the far right side with no spacing at all.
Edit 2: Ah, it also messes up the positioning of the edit box. Simple enough to fix, though:
.forum-post .content-menu menu li { float: left; } .forum-post .content-menu menu :last-child { float: right; } .forum-post .content-menu menu::after { content: ''; display: block; clear: both; }
Updated
tynach said:
Hm, this might be more generic, and doesn't depend on :not():
I changed it to this months ago. Probably in a different thread about this topic.
.forum-post div.content-menu li:nth-child(2n):not([class]) { float: right; font-size:80%; }
Flawless AFAIK
The font size reduction reflects the fact that we don't want to click on Report or Hide as often as Reply and Edit.
I think I did one for post comments too but I'm not using it for some reason.
lance_armstrong said:
I changed it to this months ago. Probably in a different thread about this topic..forum-post div.content-menu li:nth-child(2n):not([class]) { float: right; font-size:80%; }Flawless AFAIK
The font size reduction reflects the fact that we don't want to click on Report or Hide as often as Reply and Edit.
I think I did one for post comments too but I'm not using it for some reason.
Aah, ah'see. Yeah, that seems to work here (Linux version of Firefox and Chrome).