Thanks! It appears that the setting is inverted to me. When it is unchecked, the difficulty appears in the info page.
hey, im having weird bug, it does not update automatically the next grading, but when i open settings and change âbox around indicatorâ on and off it updates the rating. Iâm using newest version of ghostery dawn browser (firefox fork)
I sadly couldnât make this any cleaner because the error message showing is handled by another script. Though I exchanged that message for the checkbox being deactivated (meaning itâs not clickable) when âIn Item Infoâ or âNowhereâ is selected. This is much cleaner anyway in my opinion. Thanks for reporting it!
Oops, I noticed that before and thought I changed it already, sorry! Iâve gone right ahead and fixed that (although when you update now you might have to change the setting again ). Thanks for telling me about it!
Hmm, weird. I checked in with compatibility with firefox and the way I do it should be supported by firefox. Iâve also gone ahead and implemented an extra layer to try to detect the item change so that it hopefully works for you now too, when you update the script. If it still doesnât work just say so and Iâll look into it further!
Thanks, I really like the idea behind this script! Unfortunately, I am facing more or less the same bug as @Elkyo.
I am running version 0.14 of the script (the latest to this date) using Firefox v. 107.0.1 and Tampermonkey. Here are some screenshots.
Review ćŻ vocab item : the displayed difficulty level is 0 and will remain 0 for all upcoming items unless I go to the script settings
Open script setting window : the difficulty level is updated to level 1
Also, on startup of a review bunch, the difficulty level is not displayed until the script setting window is opened
I hope that this can help to improve the script.
Hey again! I tried few diffrent settings together and now it works when I have the âIndicator Position for Reviewsâ in the âIn item infoâ but it does not update the rating still on the âBeside the characterâ option. If I recall correctly it wasnât working there either so something got fixed. cheers
Thanks for telling me!
Okay, so I installed firefox and found out there are some weird shenanigans going on that are slightly different to all the other browsers (probably because itâs not chromium-based). Anyway, I managed to fix them so that they worked on my firefox browser. Hopefully with version 0.15 they will work for you too!
Now, it should work for âBeside the Characterâ too, if you even want to change to that now!
I just updated and it seems that it works as a charm
Thank you so much
Happy to hear that!
Hey Iâm having the same difficulty mentioned above where it wonât refresh for the beside the character options, is it due to the fact Iâm using a mobile browser? Itâs safari on my iPad
Lemme try redownloading it first since you mentioned you updated it, sorry for the bother
Did that fix your issue, or does it still persist?
Thanks for downloading!
It fixed the issue, thanks a bunch
I weirdly love being able to compare myself to everybody, it gives me a better reason to kinda try harder I guess
Script did not load for me, had to add âhttps://www.wanikani.com/*â to match for it to load.
Apparently the wildcard for http(s) doesnât work on chrome/macos.
Script doesnât load at the same place too:
Kanji is at the top (which I like)
Vocabulary is at the bottom
Thanks for reporting this!
I added âhttpsâ to the match because I donât think âhttpâ is needed anyway.
For the info pages I use WK Item Info Injector to inject the data and I think for vocab items the best I can do is putting it just under the âMeaningâ section (which Iâve gone ahead and done).
These changes should be visible in the new version (0.16). If thereâs something still not quite right please donât hesitate to say it!
For the initial version of Item Info Injector this is true, but later I shoehorned some additional actions in which override the default positioning: appendAtTop(), appendAtBottom(), appendSideInfoAtTop(), appendSideInfoAtBottom(). You could use something like wkItemInfo.spoiling('nothing').appendSideInfoAtTop(...)
to always have your section near the top.
Ah, wow! I missed that in the documentation (probably because I used your script so often already I didnât think there would be any updates). Great that itâs now possible though. Iâm going to use that, thank you very much!
Iâm happy to hear that my library script is useful to other script authors! If you ever have a specific positioning in mind but donât know how to achieve it with Item Info Injector feel free to ask me. As said before, some shoehorning took place in the past, so some parts have sadly become a bit more convoluted. [1]
-
For example, the reason why I added
.spoiling('nothing')
to the code snippet above:.appendSideInfoAtTop()
is only available for meaning and reading (because WK only splits up meaning and reading into the two columns during lessons and reviews), so at least âmeaningâ or âreadingâ has to be included in.under()
. In the snippet, I omitted theunder()
selector, so it uses the full list of âcomposition, meaning, reading, examplesâ. However, if I would also omit thespoiling()
selector, it would use âcomposition, meaning, reading, examplesâ here as well and assume that your info contains spoilers for any of these sections, leading to the section being initially hidden during reviews until the user expands the info to view both meaning and reading info.When I created Item Info Injector, I tailored it to the needs of a few selected scripts, but for other use cases it can become a bit clunky and/or hard to understand, so itâs best to just ask me when something does not immediately work. âŠď¸
Yes, itâs incredibly useful! Iâve used it in a lot of scripts before, thanks for making it. I definitely will ask you directly next time I guess that it becomes convoluted is quite unpreventable because of the way userscripts have to work around the structure of the website they canât/shouldnât change.
I just noticed a small bug: if I navigate to a kanji item page by going to this page and then clicking one of the kanji, the difficulty section does not appear. The problem is that WK has recently changed the item page navigation to avoid complete page reloads and instead uses ajax and history.pushState
. Tampermonkey ignores this type of page navigation, so your script is not injected in this case. You could probably fix this for now by using
// @match https://www.wanikani.com/radicals*
// @match https://www.wanikani.com/kanji*
// @match https://www.wanikani.com/vocabulary*
But maybe WK will also expand this navigation behavior to other parts of the website in the future.
Oh, and another problem I noticed: You @require
Item Info Injector without the version number. The problem with this is that the default setting for Tampermonkey is to never check for updates for externals. It will only download a newer version of Item Info Injector if the URL has changed (e.g. if the version number in the @require
d URL has changed).
Oh, youâre right! I noticed something was off when I had to reload the page for the difficulty to appear but couldnât quite figure out what it was.
I updated the @require
too, thanks!