Closed
Bug 13695
Opened 25 years ago
Closed 25 years ago
[DOGFOOD] Window close box needs to call JS close routines
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
VERIFIED
FIXED
M12
People
(Reporter: sujay, Assigned: danm.moz)
References
Details
(Whiteboard: [PDT+])
using 9/13 build of apprunner 1) launch apprunner 2) launch editor 3) open a new blank window 4) type some chars in it. 5) close the window by clicking in upper right hand corner "X". Notice no save dialog/panel comes up all platforms. additional comments from Charley's mail message: "But I do notice that you can use the Window's "X" to close the window. Is that why you reported failing on that item? We have no control over that in the editor. To fix that problem, someone in XPFE widgets or XPApps (whoever owns window management) needs to help us wire up the close-window message to do the same as "Close" on the menu."
Updated•25 years ago
|
Assignee: cmanske → danm
Summary: clicking on XX to close document doesn't prompt save dialog → Window close box needs to call JS close routines
Comment 1•25 years ago
|
||
This bug describes a more general problem, in that we need to have some kind of JS handler called when the user clicks the close box in the native window frame. Note that responding to this click may, in fact, abort the closing of the window (e.g. the user could cancel saving a modified document).
Also wanted to add that windows shortcut Alt-F4 is also problematic in that it doesn't prompt a save dialog/panel just like "x" close ..
*** Bug 17007 has been marked as a duplicate of this bug. ***
Comment 5•25 years ago
|
||
mass-moving all m12 bugs to m13
Updated•25 years ago
|
Summary: Window close box needs to call JS close routines → [DOGFOOD] Window close box needs to call JS close routines
Comment 6•25 years ago
|
||
Marking dogfood. This bug can cause serious data loss in editor.
Updated•25 years ago
|
Target Milestone: M13 → M12
Comment 8•25 years ago
|
||
pulling back to m12
Updated•25 years ago
|
Whiteboard: [PDT+] sched 5 Dec → [PDT+] sched 12/5
Comment 9•25 years ago
|
||
Reformatted date field, without changing value
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: [PDT+] sched 12/5 → [PDT+]
Assignee | ||
Comment 10•25 years ago
|
||
Can't read date field, which has naked numbers in arbitrary order. Deleting. Oh, well, and the bug is fixed, at least from my end. If the mood strikes you, you can now add a "close" event handler to a window, much as you've always been able to have "unload" handlers. The close event fires before the window actually closes, and its handler has an opportunity to abort window closure (by returning false, the same as link click event handlers.)
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Comment 11•25 years ago
|
||
Since the critical need for this to be fixed is for the editor, where the user can click on the "X" and close the window, loosing all of their changes, and thus I need to add the appropriate "close" handler to the editor to finish fixing the problem, I'm reopening this and assigning to me to finish this work.
Updated•25 years ago
|
Resolution: FIXED → ---
Updated•25 years ago
|
Assignee: danm → cmanske
Status: REOPENED → NEW
Comment 12•25 years ago
|
||
adding composer pdt+ tracking
Updated•25 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+] [by 12/3]
Comment 13•25 years ago
|
||
Adding target date for fix as this Friday
Updated•25 years ago
|
Assignee: cmanske → danm
Status: ASSIGNED → NEW
Comment 14•25 years ago
|
||
The editor work is checked in. Passing back to Dan to let him mark as fixed.
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 15•25 years ago
|
||
verified in 12/6 build.
You need to log in
before you can comment on or make changes to this bug.
Description
•