Still seeing that undefined warning.
[ v2.1.3 ] - Fix no-cigar āundefinedā message, add item-info settings, rearrange settings
The Settings dialog is rearranged onto several tabs now:
2 Likes
Iāve just tested it. Excellent! It worked now!
4h later. Edit: The SRS Level in Review only worked for the last item (Thing like āApprenticeā after I answered reading and meaning for an item). The other itemsā message were still swallowed/gone like my first bug report (though I donāt have to press āFā when Iām wrong now). Iām back to WK Override & WK Lightning Mode now until itās fixed.
Iām definitely going to get this a go Because I use voice For the English definitions and sometimes Siri doesnāt understand me.
Have you thought about adding a toggled option āAutomatically open Item Infoā to āDelay when multiple meaningsā?
You know where the question is coming from)
A shortcut for lightning mode would be nice 
Override stopped working for me so I finally switched to Double Check. I have one issue, though. With Double Check off and the old lightning mode on, I get no green bar when I answer something correctly, but with Double Check on, and only āallow retypingā checked, I do. Itās rather annoying.
Is this something you can fix?
[ v2.2.0 ]
- Fix SRS up/down popup in lightning mode
- Fix green bar blink in lightning mode
- Fix button auto-layout (was incorrect when Reorder not installed)
- New auto-info options.
- New option for setting SRS up/down popup duration in lightning mode.
@Kumirei, @Oshin, @EyeShield77
@FlamySerpent ,
Iām not convinced of the value of a hotkey for lightning mode, though youāre welcome to persuade me.
Did you know about the quick-enable button? (You can enable it in the settings)
If so, do you really toggle it often enough that clicking the button is burdensome?
5 Likes
Sometimes I would love to check all of the other meanings/reading to the word or kanji so I would have to toggle lighting off. I do that by clicking that button, but I have to take my mouse. That takes a lot of time and lightning mode is all about the speed, isnāt it? 
Was that good enough?:DD
Edit: Also Iām sometimes afraid that I might get (in)transitivity wrong, so the quick check would be nice. And some other instances where I might forget how to write that word correctly in english
Thank yoooou!! I really do appreciate it!
1 Like
@rfindley Looks like the popovers generated by the script no longer show up on top of the buttons.
1 Like
Interestingā¦ they did for me. Could you investigate the z-index?
The z-index of the popover message is 1000. The buttons themselves donāt seem to specify a z-index, but the div containing the button set has a z-index of 11 (id=additional-content). When I turn my scripts off, the z-index for that element is 0 and it displays correctly. It looks like line 569 of double check adds css that changes the z-index to 11.
Of course, 1000 is obviously greater than 11, so Iām not sure why this is happening. Granted, my knowledge of how z-index works isnāt greatā¦
Iām out of reviews for the night now, so I canāt help investigate anymore. If you look into it more, close but no cigar from double check or an onāyomi/kunāyomi warning should demonstrate the issue. The āmultiple readingsā warning doesnāt demonstrate it because that message is displayed lower.
Ahh, that explains it. Thanks for the investigation!! Iāll work on this in the next few days.
If youāre ever interested, I have a script that blocks review submission. Itās super handy for testing review-screen scripts. Just refresh, and all of your reviews are back where they started.
1 Like
Thanks! 
1 Like
This script doesnāt seem to work for me 
I get the following error message:
āERROR: Execution of script āWanikani Double-Checkā failed! wkof is not definedā
Iām running firefox 65.0 on Linux
Edit: I clearly just forgot the dependency on Wanikani Open Framework
2 Likes
Still getting this with 2.2.1.
I have enabled retyping, delay when wrong, lightning mode (and button), and open item info when wrong.
Thank you! Youāre a national hero!
Hmmā¦ I was unable to reproduce it originally, so the changes I made were speculative. I think Iām even skipping the part where it turns green, though WKās code still undoubtedly changes it very brieflyā¦ though that should be true of the standalone Lightning, too.
Are you on Firefox? I know FF rendering is much slower (in my experience), so maybe thatās why Iām not seeing it in Chrome.
1 Like