Hi, since yesterday Kanji and radicals have been invisible during reviews. Oddly, vocab are fine and work normally. I disabled all user scripts and even reinstalled chrome but the problem persists.
Highlighting and dragging reveals it.
If anyone has any advice I would be grateful. 
Just a couple of thoughts
Alsoā¦ while Iām hereā¦
\textcolor{pink}{\huge \textsf{WELCOME! ^-^}}
Take the time to check out the FAQ and GUIDE if you havenāt already.
Thereās also a lot of good stuff on the forum to help you, like:
The Ultimate Guide for WK
The Ultimate Additional Japanese Resources List!
The New And Improved List Of API and Third Party Apps
I hope your Japanese learning journey goes well and that you enjoy your time with us on the forums.
Thanks. No, I havenāt installed anything new like fonts or any extensions like that. I only have adblock and tampermonkey, which I turned off but there was no change.
Yea, I just tried Edge and the problem doesnāt happen there. Bit inconvenient but maybe Iāll have to move to it and reinstall a couple of scripts.
Anyway thanks for the suggestions. 
Have you tried clearing your cache? No idea if that could affect it, but thought Iād mention it
Hi, Im not directly affected by this kind of problem, but also since yesterday/today all Kanji (including Radicals and Vocabulary) appear to be āboldā. Like really really bold. I thought after reading this thread that it might be related somehow.
I am also using Chrome but this persists throughout every browser on my side.
Best regards and gl on fixing your problem
Hmm, a change from thin to bold usually indicates a newly installed font or that the IME has been installed, which adds some different fonts.
Did you install the Japanese keyboard recently? It comes with a font for kanji and kana that appears a lot bolder than before.
Hehe, thatās what I just asked; Japanese IME == Japanese Keyboard ^-^
Oops, sorry. Since I didnāt pick up on it I think they also have a good chance to miss it.
Hi, Iāve had the Japanese keyboard/IME installed for about a year and this only started yesterday :/. Plus vocab is still visible so not sure if thatās it
Thanks, if you mean the browsing cache from chrome yeah I did try this but no luck
Hmm odd, I experienced the exact same thing (it took a while for the vocabulary to update) but this was within a day of the font being installed.
It takes a while but youāll get used to it.
Edit: Oh I thought youāre the other guy, the reply wasnāt meant for you.
Hey! Sorry to see that. Very odd indeed. Weāve had some other users who have have issues with Chrome recently. Weāre wondering if itās because of the latest update last week. Email us at hello@wanikani.com and weāll have our devs take a look at it.
Yeah, thatās exactly what happened. Never thought this would have impact on website fonts, thanks (and also thMike) for pointing that out
No worries!
Thereās a list of fonts that the framework WaniKani uses to display characters from, which are in order of priority. I think @Kumirei posted it, but I canāt find it now. Regardless, if you put a font on the system (such as the one the IME uses) then if itās higher on the list, itāll switch to that one. At least, I believe thatās how it works.
If you donāt have it already, our team suggests installing Source Hans Sans: GitHub - adobe-fonts/source-han-sans at release
Donāt think I ever did, but I guess I can do it now
Hiragino Kaku Gothic Pro
Meiryo
Source Han Sans Japanese
NotoSansCJK
TakaoPGothic
Yu Gothic
ćć©ć®ćč§ć“ Pro W3
ć”ć¤ćŖćŖ
Osaka
MS PGothic
ļ¼ļ¼³ ļ¼°ć“ć·ććÆ
Noto Sans JP
sans-serif
Hmm, I misremembered, but somebody definitely posted it and youāre usually the one with all the useful information, so I naturally thought it was you 
On the plus side, the next time I claim that it will be true 
Edit: I searched for a font name and found that it was @sornvru, hehe
Hey everyone thanks for the help! However it seems the crabigator has decided to take mercy on me. The problem is randomly gone and I have absolutely no idea why! I just started a batch and everything was fine again! (After 2 days 
) I havenāt even closed the browser since it last happened, so I donāt even know if it was chromeās faultā¦
