FontAwesome emoji in old post
-
@Tsaukpaetra said in Can we have an official NodeBB-Stylish/userscript topic now?:
That " un " thing should be ... apparently something in the update failed to rebake that post (and maybe others, but that's just the one I happened to come across).
-
I searched and found one like this:
-
@anotherusername said in FontAwesome emoji in old post:
something in the update failed to rebake that post
my fault. will fix.
-
@anotherusername said in FontAwesome emoji in old post:
That " un " thing
E_NO_REPRO
Refresh... Wait a minute...
-
@tsaukpaetra hard refresh shows up the way I screenshot it for me... AJAX-y load makes it look like undefined.
Regardless, it's broken in your screenshots -- your browser's just doing something differently than mine is, for raisins.
-
@ben_lubar I've come across other posts too, so hopefully your fix will fix all of them?
-
@anotherusername For me at least the update fixed other posts.
-
I was able to find some posts where the fa_emoji had a .png suffix, but that's just how they autocompleted for a short while.
-
And i'm not actually seeing any of the :fa_* items show as anything but a box, even after a complete cache clear ( Chrome 66.0.3343.3 (Official Build) dev (64-bit) ).
-
@m_adams can you inspect the box? Is something overriding the
font-family: 'FontAwesome'style that should apply to.emoji-fontawesome(and its children)?
-
User CSS:
*:not( .fa ) { font-family: DejaVu !important; }Need to change it. Font awesome at some point was emojified w/ a class of
.fa(discourse? has my style been broken that long??)...changing to
*:not( .emoji-fontawesome )...doesn't seem to work. Hmmm. Broke everything :(TaDa! added
font-family: DejaVu !important;to mybody{}overrides in stylish.All good now.
dammit @ben_lubar ! Making me fix my own shit :(
-
@m_adams said in FontAwesome emoji in old post:
changing to
*:not( .emoji-fontawesome )...doesn't seem to work. Hmmm.Well no, that wouldn't work. It'd still match the inner
<span>, which will prevent it from inheriting the font style from its parent:
-
@anotherusername said in FontAwesome emoji in old post:
It'd still match the inner
so I probably wanted
*:not( .emoji-fontawesome ) > span {}
-
@m_adams probably more like
*:not(.emoji-fontawesome):not(.emoji-fontawesome *). You don't want it to apply to the element with that class, or to its child element.
-
@anotherusername said in FontAwesome emoji in old post:
:not(.emoji-fontawesome *)I thought
:not()didn't allow combinatorial selectors.
-
@m_adams ah. You're right, it doesn't. I guess you'd want
*:not(.emoji-fontawesome) > *:not(.emoji-fontawesome).Although, those
*s aren't really necessary; you could just as well write:not(.emoji-fontawesome)>:not(.emoji-fontawesome).
-
@anotherusername said in FontAwesome emoji in old post:
:not(.emoji-fontawesome)>:not(.emoji-fontawesome)that makes post fontawesome emoji show, but borks the navibar fa-emojis since they are
class="fa fa-fw fa-…". Yay
for being canonical in your class namings just leaving the font override in bodyWFM.
-
@anotherusername said in FontAwesome emoji in old post:
@tsaukpaetra hard refresh shows up the way I screenshot it for me... AJAX-y load makes it look like undefined.
Regardless, it's broken in your screenshots -- your browser's just doing something differently than mine is, for raisins.
IMPOSSIBLE! If it works in one browser it works in ALL browsers! There's no need to test crossplatform! Stop using something that isn't my browser!!!!
BANNED!
-
@lorne-kates use chrome
-
-
@pie_flavor said in FontAwesome emoji in old post:
@lorne-kates use chrome
Chrome?
Filed under: Paging @PJH
