Both are correct. They are variants of the same kanji. I believe the stroke order you are getting from this script is technically the more modern variant, but as of JIS X 0213 the stroke order on Jisho is the recommended version. I’m not sure which WK intends to teach. It could just be a font issue on your end
Ah, then it’s all good, I never thought it could be due to standards and fonts…I just assumed it was a mistake. My bad…
As for fonts, I don’t usually mess with those, but I remember installing a font from https://www.nihilist.org.uk/ on October.
Anyway I’ll just keep it in mind for the next time I find discrepancies.
First a big thanks to @looki for this awesome script!!!
Unfortunately it still uses HTTP and not HTTPS to load the data from JISHO, which puts all users at risk.
The stroke order images are loaded through an unencrypted connection from JISHO to our browsers. Therefore, anyone who accesses this connection in between can modify it without you even noticing. This can of course be your Internet Service Provider or anyone other in between your PC and the JISHO web server.
Since internet traffic is not determinable (meaning the sent packages can go all around the world before arriving at their goal) the packets could also easily go through countries with authoritarian governments. Even if your not the primarily “intended target” you can easily get malicious code (software) loaded into your browsers/computers, which in turn puts you at risk.
In short: DON’T use HTTP without encryption if you care about your privacy and security.
QUICK FIX (which doesn’t solve this problem entirely but it is way better than the current state):
Use the modified script from this user. Open your Tampermonkey add-on Dashboard and navigate to the Stroke Order Diagram script. Then replace the script with the one from the link above (it has a .TXT file attached).
This loads the images through a Content Delivery Network (CDN) which basically caches the images and delivers it to you through httpS (means: encrypted). Since the CDN knows it wants to deliver images it (hopefully! xD) sends you correct images and not malicious scripts. I think we can trust a CDN with this.
@looki Please consider fixing this problem in another way or maybe update your current public script with the one above? Thank you so much for your efforts!
(Btw., one could alternatively use the userscript from @atzkey, which uses a locally installed font (currently) and therefore doesn’t have this issue. But the presentation of the stroke order is a matter of taste, of course. )
Hello there
I always get the message “Error while loading” in the field where the stroke order should be displayed.
Installed the script without problem, also gave the authorisation to access Jisho when asked during my first review.
I use Safari 13.1, would rather not want to change to Chrome of Firefox. Other scripts seem to work well until now.
Any idea?
Hi,
I am trying to install this script because I would really love been able to know the stroke order while learning the Kanjis. However when I try to install the scrit a message apears:
Having discovered this first on Chrome, I agree that this is a great script from @looki and that the proposed changes should get added for everyone’s safety.
However, I’d also like to flag that I doubt this will work on Safari either due to not parsing/passing the kanji correctly (console will log the kanji but doesn’t seem to make it into the URL) or due to the over aggressive implementation of CSP v3 by Apple. The script fails to get a 200 response for a page when loading JISHO content so the stroke order sections will error or be stuck saying “Loading”.
Sadly, not really much we can do here to fix it for Safari users but I’ll cast my eye over the script from @atzkey to see if I can work any magic for Safari users. Apple just love to make things difficult!
This script is really useful and I thank you so much for making it, but I keep running into a problem where I have to close and open the info tab again in order for the stroke order section to show up during reviews. Occasionally it shows up the first time, but 99% of the time I have to close and reopen it. I don’t know if anyone else faces this problem or if its just a loading problem, but yeah.