[foldspace]

In the above (TRUE MATH) post, The tab I was on froze up and was waiting for somethin'.

IN REAL TIME,
I experienced what users experience when FR is 'slow'.

(it is not slow, the throughput via their hosting site is slow).

I simply returned to my main page (tab) on the thread and continue to work.





TECH:
Your browser is waiting for the server to send an HTTP status code (like 200, 302, or 201) to confirm the data arrived safely and tell the browser what to display next.

[foldspace]

STEVEN MILLER UP TO BAT AS CHIEF OF STAFF?? LETS' GO!!!

---

DO IT Q!

[thinden]

thanx FS

gotta hop out for a while now & will try this later

[Bob Ireland]

***when FR is 'slow'.

(it is not slow, the throughput via their hosting site is slow)***

What I labeled a possible 'server problem' - rightly or wrongly. That is how we identified the 'slow' problem in the early days of FR. 🤷

Your separate 'tab' solution is correct. I keep 'My Posts' on a separate browser tab from the thread that I am responding to. If the 'posted' confirmation hangs up for some time, I go to the 'My Posts' tab and hit refresh. Almost always the posting shows up as successful. --- Easier than hitting 'Post' repeatedly.

Patience, Butterfly...