It seems there is no way to have scripts run after everything else. Normally I’d use window.onload or similar things, but all that’s been and gone by the time any script is run anyway. So I tried defer. Normally defer means that script will run after non-defer scripts. That would be useful, but the defer attribute isn’t heeded by the engine, currently.

https://perchance.org/085unhhfqe#edit

For now I’m going to try using a [code block] just to have it run later. But obviously that won’t be sufficient for all situations. So it still would be useful to have some callback or addEventListener thingy to use to run code after perchance has done everything it does.

  • @perchanceM
    link
    English
    1
    edit-2
    25 days ago

    Seems to be working fine for me in both cases - i.e. I see “loaded” alert when I load the page with and without #edit at the end of the URL. Can you give more details? I’ve tested in Chrome and Firefox.

    • @wthit56OP
      link
      English
      125 days ago

      I’m on Chrome. 126.0.6478.214 (Official Build) (64-bit)

      For me, it only alerts when I click Reload or click Auto. Doesn’t alert when I open the editing page. Doesn’t alert when I go to the main page. https://imgur.com/a/jEv8ZS5

      • @perchanceM
        link
        English
        1
        edit-2
        25 days ago

        Hmm, I’m not sure what’s going on there. Can’t seem to replicate. Which OS? I tested on Ubuntu, Windows, and an old Chromebook.

        Can you try swapping it for a console.log instead of alert? I figure there’s a small chance that it’s a ‘user agent intervention’ where it hides the alert due to it seeming like a spammy thing.

        • @wthit56OP
          link
          English
          124 days ago

          Chromebook. Same issue for console.log(). And debugger.

          I guess you’re manually running it somehow?

          • @perchanceM
            link
            English
            122 days ago

            Same issue for console.log(). And debugger.

            Hmm, okay, thanks for bearing with me on this - can you try again now? I think I may have fixed it. If not, can you try logging document.readyState == 'complete' above your addEventListener call and tell me what it says?

            • @wthit56OP
              link
              English
              221 days ago

              Okay it all seems to work now. Maybe the change didn’t make it to my browser or something but it’s all good now 👍