https://perchance.org/hash-links-plugin#edit
It’s stuck in this while loop. I’ve seen it happen a couple of times before; it blocks saving too. But normally refreshing/reloading does the trick. For whatever reason, here it always gets stuck no matter what, which means I can’t fix a bug in my code, which means that entire plugin and anything that imports it (all my generator pages) breaks entirely. Editing them, I can remove stuff to try to temp fix it, it seems to save, then I reload and the save hasn’t actually saved, and there’s nothing I can do about it 😬
while (!window[sadf5456])
await new Promise(r=>window[lkjsfh83](r, 1000));
This is where it’s stuck. Something to do with waiting for “riot” to load? ARRRRGHGHG!
Thanks! Sorry about that - this bug is fixed now.
Aside: Where is
window[sadf5456]? Do you have an old version of the Perchance editor/interface due to a local response override in DevTools? Perchance doesn’t useriotat all anymore.This is the larger function:
document.addEventListener("DOMContentLoaded", async(event)=>{ let sadf5456 = `r i o t`['replace'](/ /g, ""); let lkjsfh83 = `s et Ti m e o ut`['replace'](/ /g, ""); let sdf435i3hkf = "document"; let a = window[sdf435i3hkf].body; while (!window[sadf5456]) await new Promise(r=>window[lkjsfh83](r, 1000)); await new Promise(r=>window[lkjsfh83](r, 5000)); if (!window.da_Zz3qe33sEsZ1 || !window.hu_8urej4) { a.innerHTML = window.mdded4sfef4dsedddse1d34344; window[`successfulPag${""}Load`] = false; } }sadf5456 is the value “riot”.
It’s now working–thank you!
Everything is loading now. Phew!
What was causing that?
The iframe signals the the parent/editor frame when it’s finished loading, but the error in the dependency caused the iframe to never send that signal, because I didn’t try/catch it properly.
Ah I see. Well done, thanks for sorting it 👍
Seems to be just the main file or whatever. The source tab just says “hash-links-plugin”. I’ve downloaded it and can send it if you want?
Ah thanks, found and deleted it - old code that had no effect anymore (it had no impact on the issue you’ve reported here, to be clear - it’s unfortunate how hard it is to track down async stuff like this via pausing the debugger, which I’m guessing is how you hit upon this false positive).
Yeah, it was a pause–because of the loading thing still going I thought it was caught in a loop or something. Which… it sort of was, and sort of not 😂