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)

defect

Tracking

()

VERIFIED FIXED

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."
Assignee: cmanske → danm
Summary: clicking on XX to close document doesn't prompt save dialog → Window close box needs to call JS close routines
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).
Status: NEW → ASSIGNED
Target Milestone: M15
Target Milestone: M15 → M12
Setting to M12 per buster
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. ***
mass-moving all m12 bugs to m13
Summary: Window close box needs to call JS close routines → [DOGFOOD] Window close box needs to call JS close routines
Marking dogfood. This bug can cause serious data loss in editor.
Whiteboard: [PDT+]
Putting on PDT+ radar.
Whiteboard: [PDT+] → [PDT+] sched 5 Dec
Target Milestone: M13 → M12
pulling back to m12
Target Milestone: M12 → M13
Target Milestone: M13 → M12
Whiteboard: [PDT+] sched 5 Dec → [PDT+] sched 12/5
Reformatted date field, without changing value
Blocks: 20203
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: [PDT+] sched 12/5 → [PDT+]
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.)
Status: RESOLVED → REOPENED
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.
Resolution: FIXED → ---
Assignee: danm → cmanske
Status: REOPENED → NEW
Blocks: 12658
adding composer pdt+ tracking
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+] [by 12/3]
Adding target date for fix as this Friday
Assignee: cmanske → danm
Status: ASSIGNED → NEW
The editor work is checked in.
Passing back to Dan to let him mark as fixed.
Status: NEW → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Whiteboard: [PDT+] [by 12/3] → [PDT+]
Blocks: 20870
Status: RESOLVED → VERIFIED
verified in 12/6 build.
No longer blocks: 20203
No longer blocks: 20870
You need to log in before you can comment on or make changes to this bug.