ModernPrimula

Well well well, back here we are again.

Now major things have happened since last time, but mostly of all the MFA websockets work as intended (or at least enough for the beta).

The core issue in regards to those was that the timings on the emit and on (listening), got messed up once I ported the site from localhost to public-IP.

THAT'S RRRRRRIGHT, the site is LIVE, or at least live for the time being, since I host it from this very PC. As the site will reach beta, I will most likely migrate over to either a digitalocean droplet, or flat out run it on an old machine at home.

But back to the timing issue with the sockets, I can honestly say that I do not have a slightest clue on what I changed in order to make it work, but whatever I did, fixed it completely, and I have tested it and nothing is "broken" at all, so safe to say that something was causing it to add extra delay, and that line got removed :D!

Anyhow, at the moment, I am finalizing, the input into Primula, and then all that's left is to display a sweet, sweet UI overview screen and a final submit button and we should be ready to do the initial beta launch!

The current issue that I am facing is regarding the dynamic, but structured code in Primula.

I am seriously regretting using puppeteer over playwright, but at the very least it feels like puppeteer is a lot faster imo...

So the core of the issue is that the form looks like this:

Pretty bad if you ask me, but that isn't even the worst part. The single worst part is that the fields are dynamic and not logical.

The "New row" button in HTML looks something like this:
<input type="submit" class="button wide" value="Ny rad" title="Ny rad" name="actionButtonText[10].valueString">

BUT remember there are several of them:

<input type="submit" class="button wide" value="Ny rad" title="Ny rad" name="actionButtonText[10].valueString">

<input type="submit" class="button wide" value="Ny rad" title="Ny rad" name="actionButtonText[19].valueString">

<input type="submit" class="button wide" value="Ny rad" title="Ny rad" name="actionButtonText[44].valueString">

<input type="submit" class="button wide" value="Ny rad" title="Ny rad" name="actionButtonText[56].valueString">

So the issue has been that I can use xpath to select the default top button, but that won't work in puppeteer since the view is limited, meaning that if you need to press it 15 times, then by the time you have pressed it around 12 times or so, the button is no longer visible on the screen for puppeteer, and that creates a bit of an issue.

And when I did it using playwright, I could simply define the nth element and loop through them, but that doesn't seem to work in puppeteer, so I am going to have to figure out some type of a workaround.

archways404 signing out, peace! :D