@run-at document-body is a good idea, but I don’t think I can use it because Open Framework needs to run before any scripts that depend on it.
Instead, I’ve made some new changes to repeatedly try to install the turbo:load listener until it succeeds. I’ve also added detection for whether turbo:load fired at startup. If it hasn’t fired by the time the document is ready, I call the pageload handlers manually.
There is a possibility that scripts might receive two pageload callbacks the first time, but I’ll work on that when I get more time (and more sleep!).
for some reason, for the past few days double-check has a decently high chance of just … not realizing that open framework is installed and prompting me to download/install it (it is installed, active, and fully updated) despite the fact that double check seems to be working fine. Unsure if its just me but its getting really annoying to close the prompt every time i visit the homepage.
Please confirm that you have the latest Open Framework (1.2.3) and Double-Check (3.2.1), and that both scripts are unmodified (e.g. you didn’t change the @run-at line or anything)
Which browser and script-hosting plugin are you using?
firefox (latest stable), got the correct versions (ive force updated every time it pops up but nothing changes), greasemonkey.
What’s weird is it’s not consistent. itll happen a few times in a row and then stop. it’s happened across different PCs using a JS blocker (confirmed its not interfering) and a canvasblocker but i don think those are modifying it at all.
If everything is set up correctly, you should see a gear icon in the upper-left corner of the Reviews screen. Click on that and go into the Double-Check settings to select which buttons you want to enable on the Reviews button bar. I would recommend the Retype button, because it allows you correct typos, but it won’t let you just mark it ‘correct’ without knowing the right answer.
Hi Robin, I’m suffering a similar issue ;-; It was running fine on v.3.1.15 and WKOF v.1.1.10, and I’ve made no changes since updating. Javascript console screenshots attached. Using a Windows 11 Firefox browser (though suffering the same issue on Mac)
I’m not sure if it’s related, but it does look like Show Context Sentence encountered an error. Just to make sure, could you try turning that one off temporarily to see if anything changes?
Edit: Unlike other parts of Open Framework, I realize I didn’t include an error-catching block around the pageload callbacks, so if a script throws an error upon pageload, other scripts may not start up. I’ll add error-catching sometime this morning.
Yes, that is correct. I don’t see any relevant errors in your screenshot, so I’m not sure if what I’m working on will help, but we can check again after the next update.
Sorry for the late reply, turning off Show Context Sentence didn’t change anything, I’m still getting the “Double-Check requires WKOF.” error. I can confirm that 3.1.15 still works with WKOF ver.1.2.3 and that version 3.2.0 also doesn’t work, if that helps at all.
I know it sounds stupid but please everyone check if tampermonkey is enabled.
I dont know how but somehow my tampermonkey wasnt enabled, as soon as i enabled it everything worked
Yeah, that sounds like a relatively quick one to address, and tomorrow morning I’m going to be waiting on a code update from my client before I can proceed on my current task, so I think I’ll have a little bit of time to tackle that.
Done!
Also, I added a 3-second retry period for wkof to load before alerting the user, in case people are still having problems with Double-Check apparently loading before wkof.
I noticed with V3.2.2 a strange thing happening (sometimes!):
the lightning mode button appears now twice on the header
toggle buttons are shown despite them being disabled in my settings
Most of the functionality works, so it’s not a critical bug. Only the buttons are broken (always greyed out), but the shortcut for retyping (backspace) still works.
Was working on the Jitai userscript, so I had to refresh the page a few times and therefore noticed it. Very loose statistics here, but I’d say it happens to me in 1 out of 4 page refreshes. I don’t know if it appears when coming from the dashboard.
