You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The changes should only be saved when tapping the "Published" button.
This expected behaviour is my interpretation of the app's offline editing support. The editor should behave like a text editor: it writes to the opened file only when user taps "Save" button.
Actual behavior
Changes are saved automatically after sending the app to background.
Steps to reproduce the behavior
Go to Posts list -> Draft.
Create a post and tap the "Publish" button.
Go back to the Posts list. You should see a draft post here.
Tap the draft post and make some changes to it.
Go to the device's home screen, wait for a couple of seconds, and kill the app.
Btw, if you remove "and make some changes to it" from step 4, it will still save the revision and display "local change" (incorrectly).
The editor should behave like a text editor:
That's an interesting thought. If you also compare it to Notes, the Notes app syncs files seamlessly/automatically and merges changes in the case of a conflict automatically.
But Notes are private. I think there can be more potential negative implications of unintentionally posting content to a user's public website. I'd rather be on the side of caution and only upload when the user publishes/saved explicitly, as you suggested. It should never auto-retry, especially not after closing the app.
Expected behavior
The changes should only be saved when tapping the "Published" button.
This expected behaviour is my interpretation of the app's offline editing support. The editor should behave like a text editor: it writes to the opened file only when user taps "Save" button.
Actual behavior
Changes are saved automatically after sending the app to background.
Steps to reproduce the behavior
Here is a video recording:
local-post-edits.mp4
Tested on [device], iOS [version], Jetpack iOS / WordPress iOS [version]
The text was updated successfully, but these errors were encountered: