Is there a way to remove these from showing up in the posts section?

[45thj5ej]

These:

It really clutters up the feed, especially on mobile. Would love if it could just be sent as a notification or something. It’s annoying to constantly go and delete system messages when they happen every time, or even messages from Staff that an action was done on a post.

[bryce (Bryce Huhtala)]

You could try writing some CSS to hide them. From what I’m seeing, all of the posts in a topic are contained within a div element with class post-stream. Those particular messages appear to be article elements with the classes small-action and onscreen-post. I’d be careful to make sure that there aren’t other types of messages that would be caught by the CSS selector and hidden!

[45thj5ej]

Yeah, I was thinking of doing something like:

.small-action {
display: none
}

but I’m not sure what other sort of messages show up like these. Is there a list of them anywhere by chance?

[bryce (Bryce Huhtala)]

Hmm, I’m not aware of a full list but I did notice at least one other element that uses small-action: the last visited line!

Hopefully article.small-action.onscreen-post would be specific enough to not affect anything else.

[Lilly (Lillian)]

Hide post footer links pins etc info

You could hide them, and then display them only for staff using something like this: .small-action.onscreen-post { Display:none; } .staff .small-action.onscreen-post { Display :initial; }

[45thj5ej]

This would be perfect, but it isn’t working for me on my non-staff account, nor non-signed in users. See anything wrong?

Even just having this alone isn’t doing anything:

.small-action.onscreen-post {
    Display:none;
}

This is being done on a component I made for CSS stuff that I use for a couple themes.

[Firepup650 (Firepup Sixfifty)]

For me, here on Meta, non-staff, this works:

.small-action.onscreen-post {
    display: none;
}

You seem to have capitalized display by mistake?

Just another note, this might occasionally cause weird visual bugs:

[45thj5ej]

Yeahh, even with the regular lowercase display, it still didn’t work when I tried earlier.

@Firepup650

this might occasionally cause weird visual bugs:

Would these bugs be for everyone or just Staff to see? But yeah, the CSS still isn’t working for me, though

[Firepup650 (Firepup Sixfifty)]

@45thj5ej

Would these bugs be for everyone or just Staff to see?

If you’re showing it to staff, then everyone but staff.

@45thj5ej

But yeah, the CSS still isn’t working for me, though

Throw an !important on it then, that usually works

.small-action.onscreen-post {
    display: none !important;
}

[45thj5ej]

So weird, even with the important part, still not hiding it. hmmm. And that’s on multiple themes. Is it because I’m using a component to do this?

[Firepup650 (Firepup Sixfifty)]

Are you sure the component is applied to themes?

[45thj5ej]

Yes, showing as applied to both I’ve tried it on.

[Firepup650 (Firepup Sixfifty)]

Strange. I made a test component, and it works for me. Could you try this component?
https://github.com/activememberchat/test-no-staff-small-actions

[45thj5ej]

Ok, what the heck? Yours works, lol. I have the literal same thing in mine, though.

Ok, so after disabling my component from the theme and re-applying it, it’s working now…what in the world?

[Firepup650 (Firepup Sixfifty)]

Perhaps it was a caching issue?

[45thj5ej]

You mean on my browser? If so, I doubt it. I tried multiple browsers in incognito mode. Maybe found a bug somehow, haha?

EDIT: Come to think of it, I had a similar issues like 12hrs ago. One of my CSS things randomly stopped working and I had to re-apply it. Totally forgot about that until now, but I guess that’s expected when you’re building your site 18hrs a day

[Lilly (Lillian)]

Syntax is important and you have a space before the colon instead of after that caused yours to not work. also best not to capitalize properties.

[Firepup650 (Firepup Sixfifty)]

@Lilly

you have a space before the colon instead of after that caused yours to not work

That doesn’t seem to cause an issue when applying styles via inspect, except it confuses the syntax highlighter: