Tried setting window.riot = true;
which does break that loop. But it's stuck in some other infinite loop it seems?
Could theoretically not be the cause of it not being savable, but it's all I got.
This is a Lemmy Community for perchance.org, a platform for sharing and creating random text generators.
Feel free to ask for help, share your generators, and start friendly discussions at your leisure :)
This community is mainly for discussions between those who are building generators. For discussions about using generators, especially the popular AI ones, the community-led Casual Perchance forum is likely a more appropriate venue.
See this post for the Complete Guide to Posting Here on the Community!
1. Please follow the Lemmy.World instance rules.
2. Be kind and friendly.
3. Be thankful to those who try to help you.
4. Only post about stuff related to perchance.
5. Refrain from requesting Prompts for the AI Tools.
text-to-image-plugin
and ai-text-plugin
) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"6. Search through the Community Before Posting.
Tried setting window.riot = true;
which does break that loop. But it's stuck in some other infinite loop it seems?
Could theoretically not be the cause of it not being savable, but it's all I got.
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 use riot
at all anymore.
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 ๐
Everything is loading now. Phew!
What was causing that?
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 ๐
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!