It would be feasible for the Editor to record the current tab on change in browser storage and move to the appropriate tab on reload. If, that is, someone wanted to submit a PR containing the code changes
I had not considered that the browser would save the open tabs in a cookie, or that doing so would cause NR to open with the same current editor flow open, simply because it has never run on my machine with cookies retained.
And if you shut down your machine (as opposed to hibernating) and restart in the same place within the editor tabs then NR must be getting the info from somewhere, probably a cookie.
I'll have to experiment when I get back to the PC.
OK some observations:
I turned off Firefox' settings to always browse in a private window and to delete cookies on shutdown, then rebooted.
Next I opened several browser tabs and pointed them to different sites. The middle tab was the Node-red editor on my Pi, pointing to a flow tab somewhere in the middle.
After restarting the computer I ran Firefox and it opened the same tabs as before, with the same tab and the same editor tab having focus.
I guess what I'm saying is Node-red behaves exactly as I think it should. How hateful is that?
Now lets see if I can tune Firefox to throw away everything but the NR cookies...
I do need :1880, that's the port that Node-red listens on.
It is possible to change it by using a different web server and/or a proxy but I prefer to type :1880 over learning how to do use a proxy. I've always thought I should leave jobs like that to someone else.
It wasn't I was wanting to be argumentative about the port.
I just wasn't sure you needed to qualify it in the setting to tell the browser which IP addresses to not clear the cookies (etc).
Anyway: It is strange that your browser isn't remembering the pages.
Ok, dumb question: (and to re-check what you said) If you do NOT use private browsing does it remember the page/load the previous pages?
Given you do not QUIT the browser and rather restart the computer which the browser running.