Closed Bug 511288 Opened 15 years ago Closed 14 years ago

No way to set collaborate on if unsaved changes

Categories

(Skywriter Graveyard :: Collaboration, defect, P3)

0.4.0
x86
macOS
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: dion, Unassigned)

Details

If you turn on collaborate and there are unsaved changes a confirm() comes up to let you know that it won't work. If you are in a place where you don't want to save there isn't a path to say "ignore, just do it" and you are left with having to reload the page. Since "reload the page" is akin to "restart the app" this is a bug.
Target Milestone: 0.4.2 → 0.4.3
Assignee: nobody → jwalker
Status: NEW → ASSIGNED
Target Milestone: 0.4.3 → 0.4.4
Target Milestone: 0.4.4 → ---
Assignee: jwalker → nobody
This is a mass change. Every comment has "assigned-to-new" in it. I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Status: ASSIGNED → NEW
ACETRANSITION The Skywriter project has merged with Ajax.org's Ace project (the full server part of which is their Cloud9 IDE project). Background on the change is here: http://mozillalabs.com/skywriter/2011/01/18/mozilla-skywriter-has-been-merged-into-ace/ The bugs in the Skywriter product are not necessarily relevant for Ace and quite a bit of code has changed. For that reason, I'm closing all of these bugs. Problems that you have with Ace should be filed in the Ace issue tracker at GitHub: https://github.com/ajaxorg/ace/issues
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.