tiddly_on_tahoe says "saving please wait...done" *after* it is finished saving #1312
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1312
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At least on Firefox-3, when you click "Save Changes" then nothing happens for a while, and then it says "saving...please wait" and "thign saved" all at once. It would be nicer if it would pop up "saving...please wait" before the nothing-happens-for-a-while part.
Changed 21 months ago by zooko
Wait a minute. Nowadays I can manually test this and see that it says "saving...please wait / RSS feed saved / Empty template saved / Main TiddlyWiki? file saved" before it has finished uploading (I can tell by looking at Tahoe node's "Recent Uploads and Downloads"). This is erring on the opposite side and this error is much worse, because if someone sees that it says "Done" and then goes and modifies the same wiki from a different web browser they can cause write collisions and all sorts of confusion. I'm pretty sure that this is what just broke my blog.
So the easiest way to fix this ticket is just to take out the "saving please wait..." entirely and make sure that the "saved" message doesn't appear until after the HTTP PUTs or POSTs have all completed. The best way to fix this ticket is then to add in "saving please wait..." which appears immediately, before any of those operations have been started.
Changed 13 months ago by zooko
Okay it is more complicated than I thought. When you click "save" it seems to do some network traffic, then pop up the "I'm finished saving!" announcement, then wait for a few seconds (while evaluating some Javascript?) then do a whole bunch more network traffic, and only then is it really saved so that other people can see it. This is very ugly -- it is easy for people (including me) to think that it is done long before it is actually done. If they close the window at that point then they'll probably lose their work. If the click "save" in another window at that point then they'll probably lose their work. In any case it is a pain-in-the-neck. Here is a listing of the "recent operations" from clicking save. Hey what the hell! Where is the upload? I do not know why there is not "upload" in there. :-( Is it a bug in Tahoe-LAFS's "current and recent operations" display?
Changed 6 days ago by zooko
see also #5 and and #10 . ducki2p may have fixed some or all of these in his branch for i2p.