Bug Report

@Panda you’d be surprised. If you consider that you’d need to use the API to be able to populate a WordPress widget for example (which in turn would of course be PHP), taking this route is still immensely popular.

@crazycells yes, I’m aware of that. Need to fix

EDIT- fixed. Caused by the same CSS that is used to absolutely position the “verified” group badge in the posts view. Amended this CSS so that is specifically targets the post stream as below

li[component="post"] a[href*="/groups/verified"] { position: absolute !important; left: 8px; z-index: 2; margin-top: 1px; border-radius: 999px !important; line-height: 14px; display: block; height: 22px; margin-left: 0px !important; }

@cagatay You’d target the body tag and use the below line of CSS

background: url(/assets/customcss/backgrounds/default/default.png) no-repeat center center fixed;

Obviously, you need to change the path to suit where your image is being stored.

More info around the background property can be found here

https://www.w3schools.com/cssref/css3_pr_background.php

@pobojmoks Do you see any errors being reported in the console ? At first guess (without seeing the actual code or the site itself), I’d say that this is AJAX callback related

And now, after all this time 😕 I finally discovered that the CSS I previously referenced was for something else - and used the same CSS name, so I’ve had to reinstate this block 🤦

.tab-content { max-height: 0; padding: 0 2em; color: #898989; background: #eeeeee; transition: all 0.35s; margin-top: -5px; }

And, add this below to make it more specific.

.emoji-tabs .tab-content { height: 100%; max-height: 100%; padding: 0; margin: 0; }

OMG make sense

Thanks dude 🙂

@downpw I’m inclined to agree with this. There isn’t much else you can do, and provided it works with no odd looking artefacts in other browsers, then ok. The :before and :after are pseudo classes and very well supported across all browsers (except perhaps Internet Exploder, but who uses that these days ?)