Closed
Bug 313344
Opened 20 years ago
Closed 13 years ago
after upload onStopRequest there is a delay before the uploaded RDF file can be refreshed with remote datastore refresh
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: marja, Unassigned)
References
()
Details
(Whiteboard: [testday-20120713])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
I upload file, and onStopRequest start code that refreshes it back. The file
always uploads but sometimes the after Refresh onEndLoad I see the old version
of the file until I close browser and start again or do something else that
causes a another Refresh.
Biesi said something about Necko returning to do some code and asked me to do a
window.setTimeout at onStopRequest for the Refresh function. I'm not sure why
but it seems to help, at least I haven't gotten any problems after I started
using that. But could also be that delays are now hiding from me.
Anyway, it is a bug and setTimeoutlooks ugly and is complicated with all the
context information going on.
Reproducible: Sometimes
Steps to Reproduce:
1.install http://www.annotea.org/mozilla/ubiwin_0_3.xpi
2.configure http:// datastore as read and write datastore that accepts HTTP PUT
3.create a new topic or bookmark or update or delete already existing bookmarks
and topics (e.g. update title names as they are shown in bookmark tree view)
4. Also open bookmark view bookmarks tree view of bookmarks and topics
Actual Results:
user is informed that upload was successful, then refresh is done
if everything went well the view bookmarks view is updated
if refresh was not successful the view has old information
Expected Results:
always do upload onStopRequest so that refresh is done on uploaded file
I guess this will be thrown to trash also with the other bugs I have reported
but doing it anyway...
Comment 1•20 years ago
|
||
a minimal testcase would be nice, ideally not involving RDF...
Keywords: qawanted
Updated•20 years ago
|
Summary: after upload onStopReques there is a delay before the uploaded RDF file can be refreshed with remote datastore refresh → after upload onStopRequest there is a delay before the uploaded RDF file can be refreshed with remote datastore refresh
I think this might have something to do with refreshing from http cache instead of from the updated file.
With firefox 1.5 in Windows XP an updated http://...rdf file is not refreshed even after I start the browser from the beginning. However, I can see it working in Linux with all the updated info.
When I look the file with the browser in Windows XP I also see the old version. Only after I did shift refresh in the browser window I could see the changes in my application when reading the refreshed file.
Seems to work now with firefox 1.5.0.1 in Windows.
Linux version that already seemed to work might be different (firefox 1.5 gecko 20060123) as I took it from CVS but who knows.
However, I'm not sure if the error of refreshing from cache is corrected or if the http cache is just updating more so it seems it does not update from cache. In this case it will probably still occasionally fail to get my or other user's updates.
Updated•19 years ago
|
Assignee: darin → nobody
Reporter, is problem reproducible in modern Firefox versions?
Whiteboard: [testday-20120713], [closeme 2012-08-01]
Resolving this bug INCOMPLETE. Please reopen if it's still reproducible in the latest Firefox nightly.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Keywords: qawanted
Resolution: --- → INCOMPLETE
Whiteboard: [testday-20120713], [closeme 2012-08-01] → [testday-20120713]
You need to log in
before you can comment on or make changes to this bug.
Description
•