Separate names with a comma.
Discussion in 'Site and Forum Feedback' started by cube, Oct 19, 2018.
The editor loads the content from the browser, not the server.
Surely you already know this.
Can you explain in more detail please?
You can lose previous work if you start editing from a page that has not been refreshed.
This is not new.
I'm not sure what problem you are having but you need to click the save pages button to upload the edited post to the server.
I think they mean that if you’re editing a post or replying to a post, if you then refresh the page before submitting it will lose some of what you’ve written and only partially saves it.
I’m just guessing... cause that’s the only problem I’ve experienced related to posting (except the iOS 12 issue where dragging text selects all).
Who knows. ¯\_(ツ)_/¯
Why you would refresh a page halfway through making an edit though?
I dunno man, maybe they opened a new tab and were expecting the live half edit to all be there, or have a broken F5 key that randomly presses itself.
Honestly I’m stumped. Customer service’s worst call.
“IT’S ALWAYS BEEN BROKEN FIX IT”
I don't know how often that feature auto saves, but if you need to refresh or leave the page for some reason, you should be able to save the draft by clicking here. Would that address your issue?
Holy ****, I've never seen so many people up vote a post simultaneously.
The editor grabs the old version of the post from a non refreshed page instead of the latest version from the server, so you end up overwriting your previous changes.
Can you explain step by step exactly what you are doing and what the issue is? I'm not clear now what you mean.
You have a couple of tabs with the same thread in the history and go back to an outdated page, for example.
You then edit from there without reloading the page first.
I think it is that way by design, and you will need to refresh the page if you go back to an old page. I don't see how it could be made to work otherwise.
It is easy and normal, when you click on the edit button, it should make a server request to fill the editor, not read the DOM.
And if you make a serious mistake and cancel the edit, it will just load the same garbage again.
Yeah, he seems to be trying to battle some browser behaviors vs. the forum code (client side events/service/server-side content load). Like wanting a history traversal trigger to force a remote reload or something[?]
Sounds like an outlier, at least that's what I'd tell my clients
It's not an outlier. The datasource should be the server, not the browser.
A browser is not supposed to reload when you hit back or switch tabs.
I meant you are the outlier with this being an issue and/or misinterpreting/not having proper expectations as to how things are supposed to work.
I have proper expectations. The latest data is at the server and a web page on a browser can be modified at the client side by the user. It is basic web programming.
While I haven't run into your original problem (although I do understand it), this one's stung me a couple of times. The Cancel button doesn't cancel, it just hides the editor. I agree that it's broken.
Again I lost an edit.