this post was submitted on 16 Jul 2024
3 points (100.0% liked)

Perchance - Create a Random Text Generator

448 readers
19 users here now

โš„๏ธŽ Perchance

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!

Rules

1. Please follow the Lemmy.World instance rules.

2. Be kind and friendly.

  • Please be kind to others on this community (and also in general), and remember that for many people Perchance is their first experience with coding. We have members for whom English is not their first language, so please be take that into account too :)

3. Be thankful to those who try to help you.

  • If you ask a question and someone has made a effort to help you out, please remember to be thankful! Even if they don't manage to help you solve your problem - remember that they're spending time out of their day to try to help a stranger :)

4. Only post about stuff related to perchance.

  • Please only post about perchance related stuff like generators on it, bugs, and the site.

5. Refrain from requesting Prompts for the AI Tools.

  • We would like to ask to refrain from posting here needing help specifically with prompting/achieving certain results with the AI plugins (text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"
  • See Perchance AI FAQ for FAQ about the AI tools.
  • You can ask for help with prompting at the 'sister' community Casual Perchance, which is for more casual discussions.
  • We will still be helping/answering questions about the plugins as long as it is related to building generators with them.

6. Search through the Community Before Posting.

  • Please Search through the Community Posts here (and on Reddit) before posting to see if what you will post has similar post/already been posted.

founded 1 year ago
MODERATORS
 

I'm not sure if this is a bug or what, but there's something unexpected going on.

I've set up a test for you to see here: https://perchance.org/sxvghvl53i#edit

I've got an $output that creates HTML, which contains the code [a.html], but escaped so that it's not processed. So: \[a.html\].

This is then injected into the page, and actually processed correctly, replacing the contents with the a.html value. But then calling update() on that element either does nothing or throws an error of one kind or another.

It says that a_elem is undefined, when it should have already been injected into the page.

Honestly, I've been fiddling with this test for a while now and I can't quite pin down exactly how it works or what this works and that doesn't or what order things are being processed in... But some sort of shenanigans is going on.

If this is all working as expected, I'd love to learn how it works. But if not, consider this a bug report ๐Ÿ˜…

you are viewing a single comment's thread
view the rest of the comments
[โ€“] VioneT 1 points 4 months ago* (last edited 4 months ago) (5 children)

The problem with it is that (I think, I'm not sure), while it reads from left to right and top to bottom, the function add() has been called before even the [a] is resolved. You can fix that by enclosing it in a setTimeout to wait for the element to be loaded first before adding the new one.

  add(msg) =>
    setTimeout(() => {
      a.html+=msg;
      update(a_elem);
      return "";
    }, 1);
    return '';

Another problem is when you use <span id="a_elem">\[a.html\]</span> for the [a], upon loading it on the HTML, the \[a.html\] is gone. It would only have the 'A', so even if you update it, you aren't updating anything (essentially saying that [a.html] has been evaluated and you are only updating 'A').

[โ€“] wthit56 1 points 4 months ago (2 children)

Why has add() been called first? It comes after [a], so it should be resolved after a. Right?

[โ€“] VioneT 1 points 4 months ago (1 children)

What I mean is after [a] has been called, the [a.add(...)] is called immediately after, without waiting for [a] to finish placing the element, in which the add(...) cannot call the a_elem since it hasn't loaded yet.

[โ€“] wthit56 1 points 4 months ago

Interesting... I don't know why [a] would be async like that. Or if all [brackets] are processed later, processing them in order seems to be the easiest way anyway. Like... it's not a big deal to put something in the DOM, it doesn't need any delay, it can all be immediate.

I think you're right, that's how it works, for whatever reason. This behaviour is just quite intuitive even for web devs like me--I'd avoid it at all costs in my own projects! ๐Ÿ˜‚

@perchance Any word on why it works like this, behind the scenes? I'm curious to understand it better.

load more comments (2 replies)