Closed
Bug 79797
Opened 24 years ago
Closed 24 years ago
JS Front end should not touch offline setting
Categories
(SeaMonkey :: MailNews: Backend, defect, P2)
Tracking
(Not tracked)
mozilla0.9.1
People
(Reporter: Bienvenu, Assigned: Bienvenu)
Details
(Whiteboard: [nsbeta1+])
The JS Front end (commandglue.js) is setting the offline state and then asking
the backend to download messages for offline use. This is difficult, since I
need a network connection to do that stuff. The way it's supposed to work is the
front end leaves the state alone and the backend will set the offline state
appropriately when it's done. That's why there's a parameter to the offline sync
methods that say whether to go offline when done or not. I'll attach a patch
shortly removing the front end code.
Assignee | ||
Comment 1•24 years ago
|
||
this has to be fixed for beta - going offline can't do any network operations.
I'm going to fix this as part of cleaning up all the front end online/offline
state handling.
Keywords: nsbeta1
Comment 2•24 years ago
|
||
marking nsbeta1+
Priority: -- → P2
Whiteboard: [nsbeta1+]
Target Milestone: --- → mozilla0.9.1
Comment 3•24 years ago
|
||
bienvenu, see my latest patch for #65704.
will that solve this problem, too?
Assignee | ||
Comment 4•24 years ago
|
||
yes, you've done what I did - remove all the code in commandglue.js that
directly poked the offline state. thanks for fixing this!
*** This bug has been marked as a duplicate of 65704 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•