here's a list of known issues:

everything works perfectly fine.

Reporting issue: sometimes some people complain about so-called "issues" with Porom.

Proposed solution: taking these people's devices away so they can never complain again.

im not a web dev but i never saw that behaviour before when i post a reply and i go backward in page history, it brings me back to the same thread so i have to do backward twice

i have at work a tool that uses forms a lot and i never had something like this so idk what's going on but it doesnt feel normal

kaesa said:

im not a web dev but i never saw that behaviour before when i post a reply and i go backward in page history, it brings me back to the same thread so i have to do backward twice

i have at work a tool that uses forms a lot and i never had something like this so idk what's going on but it doesnt feel normal

it's because there's no AJAX / nothing is dynamically inserted on the client. what happens is you send a post, then the server processes it, and it sends you a 302 redirect to go to the latest post so that you can see it on your end.

admin said:

kaesa said:

im not a web dev but i never saw that behaviour before when i post a reply and i go backward in page history, it brings me back to the same thread so i have to do backward twice

i have at work a tool that uses forms a lot and i never had something like this so idk what's going on but it doesnt feel normal

---

it's because there's no AJAX / nothing is dynamically inserted on the client. what happens is you send a post, then the server processes it, and it sends you a 302 redirect to go to the latest post so that you can see it on your end.

what about location.replace()?

veclavtalica said:

<snip> location.replace()

but what would i replace? and when? a hidden input that only gets sent by the server when redirecting after creating a new post and if it's present, js will rewrite the history? im having a hard time wrapping my head around it tbh.

not to mention, is history tracked for query strings or hash links? idk, too much to think about. just use the back button twice

I think the solution would just be to use JS's fetch API to manually submit the form when the button is pressed, and if it worked correctly, just reload the page from JS.

code blockCopyform.onsubmit = function(ev) {
    ev.preventDefault();

    let res = await fetch(window.location.pathname, { method: 'POST', body: new FormData(form) });
    
    if( res.ok ) 
        window.location.reload();
    else
        alert("failed to send post"); 

    return false; // i think needed as well as the preventDefault? not sure
}

That's what i found online regarding that issue. Surprisingly that isnt a very common or documented issue.

It's slightly odd that the post body is still saved after posting a reply

wanp said:

It's slightly odd that the post body is still saved after posting a reply

yeah, it is. i was going to fix it but i forgot til now

this is fixed now in pyrom :)

Deleting a thread leaves you with an error page when it refreshes, because the dead link doesn't redirect anywhere... Also, deleting a thread doesn't remove it from being the "latest thread" in a topic (possibly applies to the "latest post" as well?) which means you can click that dead link and get an error too.