Closed
Bug 89166
Opened 25 years ago
Closed 25 years ago
*nsBranch only* dialog for File|Exit and x-close window when in -turbo mode
Categories
(SeaMonkey :: UI Design, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.4
People
(Reporter: cathleennscp, Assigned: bugzilla)
References
Details
Attachments
(5 files)
|
11.63 KB,
patch
|
Details | Diff | Splinter Review | |
|
10.97 KB,
patch
|
Details | Diff | Splinter Review | |
|
22.60 KB,
image/gif
|
Details | |
|
13.49 KB,
patch
|
Details | Diff | Splinter Review | |
|
10.41 KB,
patch
|
Details | Diff | Splinter Review |
Updated•25 years ago
|
QA Contact: sairuh → paw
no description means you're asking for someone to provide a spec, which is what
UID does best.
Assignee: vishy → mpt
Component: XP Apps: Cmd-line Features → User Interface Design
QA Contact: paw → zach
cc: rudman. Steve - can you provide the wording for this dialog? cc: mcarlson
for localization. I'd suggest assigning this bug to rudman for wording and then
vishy for implementation.
Cathleen/vishy - did we want this for nsbranch? I thought we did. If so, pls
mark this. Thanks.
Summary: dilaog for File|Exit and x-close window when in -turbo mode → dialog for File|Exit and x-close window when in -turbo mode
Ccing Jatin. He's already provided input for wording on the feature, so any
additional wording would be best if it came from him.
Comment 4•25 years ago
|
||
we will take this dialog on only the Netscape branch. This is not for the
mozilla trunk or a long term solution. Blake is coding up a fix for this for the
Netscape branch.
Updated•25 years ago
|
Component: User Interface Design → XP Apps
Summary: dialog for File|Exit and x-close window when in -turbo mode → *nsBranch only* dialog for File|Exit and x-close window when in -turbo mode
Target Milestone: --- → mozilla0.9.3
Updated•25 years ago
|
Whiteboard: [PDT+] → [PDT+] eta=07/06 for branch only.
Comment 5•25 years ago
|
||
I need more information about how this patch entails. Cathleen, you mentioned in
an email "that user passwords, email, aim are still been active if you stay with
-turbo mode running in the background." Can you elaborate on this? And how is
this bug affected by Bug 89165 ?
Comment 6•25 years ago
|
||
CORRECTION: I need more information about *what* this patch entails.
| Assignee | ||
Comment 7•25 years ago
|
||
| Assignee | ||
Comment 8•25 years ago
|
||
Comment 9•25 years ago
|
||
Here is my suggested wording for Blake's patch:
"Quick Launch is active, so Netscape remains in memory and can be started again
quickly. You are still connected to mail accounts, instant messenging, and web
sites. To completely exit Netscape, right click on the Netscape icon in the
bottom right of the taskbar and select Exit."
For the title bar, my suggestion:
+<!ENTITY exitWarningTitle.label "Quick Launch">
Comment 10•25 years ago
|
||
CORRECTION: "messenging" should be "messaging"
Comment 11•25 years ago
|
||
CORRECTION: Remove the extra space so it reads, "web sites. To completely"
| Assignee | ||
Comment 12•25 years ago
|
||
I like it. Clearer and less wordy than the current text.
* I think users are going to wonder when we say they're connected to websites
(they're not, just some cookies might be hanging around). Still, I can't think
of any non-technical and accurate explanation...
* I don't think we have to go into so much detail about where the icon is,
because the dialog is supplemented with a picture (I'll post a screenshot).
Also, although they could have hidden the clock, most users won't, and I think
it's an easier way to refer to that area than trying to describe it
geographically (plus, if the taskbar is on the left or right side, it won't be
in the bottom right...but that's an even more obscure case than the hidden
clock, I suppose). The "near the clock" text was inspired by MSN Messenger's
dialog.
* Will most users understand that there's an implied "if you were connected"
about the instant messaging, mail accounts, etc.? i.e. they'll only still be
logged in to NIM if they already were. I guess that's obvious.
| Assignee | ||
Comment 13•25 years ago
|
||
Is "in memory" non-technical enough that the average user is going to know what
it means, or care? MSN Messenger doesn't give so much information, nor do other
apps I've seen (where such info appears, it's typically in the help file).
| Assignee | ||
Comment 14•25 years ago
|
||
Comment 15•25 years ago
|
||
How about this:
"Quick Launch is active, so Netscape stays in memory and can be started again
quickly. You are still logged in to mail accounts, instant messaging, and web
sites. To completely exit Netscape, right click on the taskbar icon (near the
time) and select Exit."
Comment 16•25 years ago
|
||
Index: resources/locale/en-US/profileSelection.dtd
===================================================================
RCS file: /cvsroot/mozilla/profile/resources/locale/en-US/profileSelection.dtd,v
Why are these resources being put into profile mgr's resources? What on earth
does this dialog have to do with profiles? Looks fine but I really, really think
it should go elsewhere in the tree.
+ nsCOMPtr<nsIDOMWindowInternal> domWin = do_GetInterface(docShell);
I'd check that domWin != nsnull before using it.
| Assignee | ||
Comment 17•25 years ago
|
||
I was trying not to add another file since this is only going on the branch.
Also, the Exit item in the QuickLaunch context menu is already in a profile
resource...But if you want, I'll add the file.
If domWin is null, our only choice is an unparented alert anyways, no? So why
check?
Comment 18•25 years ago
|
||
If it's not a problem to make another file, it would be good - in case we want
this dialog down the road on the trunk. For now, since it's only the branch, I'm
OK with it.
With the domWindow, the check would avoid a crash.
If the dialog was put up this way:
nsCOMPtr<nsIWindowWatcher> windowWatcher = do_GetService(...);
if (!windowWatcher) return NS_ERROR_FAILURE;
nsCOMPtr<nsIDOMWindowInternal> domWin = do_GetInterface(docShell);
windowWatcher->OpenWindow(domWin, ...)
and domWindow was NULL, we wouldn't crash - the dialog would be unparented.
| Assignee | ||
Comment 19•25 years ago
|
||
Er, yes, sorry...I was thinking of the old patch, which used windowwatcher and
domWin as the parent.
New patch coming.
| Assignee | ||
Comment 20•25 years ago
|
||
Comment 21•25 years ago
|
||
A small part of the last patch is missing - confirmed with Blake. Assuming that
bit goes in, r=ccarlen
Comment 22•25 years ago
|
||
Arg.
jatin a few warnings: 1. Time might or might not be visible. On w2k terminal
sessions iirc it is not by default. 2. What happens if a users runs -turbo and
doesn't have an explorer.exe compatible shell (or it crashes)?
If mozilla does not support the explorer notice (comes from an ie4 integration
or newer explorer.exe) alerting all tray apps to reregister then when exploer
restarts (after it crashes) users will be unable to quit netscape, this is a
serious concern. it takes <5 lines to add this support but it must be done.
risk: 0.1%.
The following is a rant, if someone feels i put it in the wrong bug please
indicate the correct bug, thank you for your patience.
There _must_ be a way for me to safely Quit (#define Quit
NS_LITERAL_STRING("unload Application; Leaving No Instances Or Traces In
Memory") this application w/o using the tray.
Comment 23•25 years ago
|
||
box? what is this box?
sr=ben@netscape.com
Comment 24•25 years ago
|
||
Update ETA per IM w/blake. Will land when tree opens.
Whiteboard: [PDT+] eta=07/06 for branch only. → [PDT+] eta=07/09 for branch only.
| Assignee | ||
Comment 25•25 years ago
|
||
Fixed on branch.
Status: NEW → RESOLVED
Closed: 25 years ago
QA Contact: zach → sairuh
Resolution: --- → FIXED
Comment 26•25 years ago
|
||
On a branch just pulled and built, this is doing something bad: When the dialog
comes up, it's empty, fills the screen, and I have to exit using the task
manager. Is anybody else seeing this?
| Assignee | ||
Comment 27•25 years ago
|
||
Oops, missed a line in my checkin; just checked it in. Thanks for catching that.
update xpfe/browser/
Updated•25 years ago
|
QA Contact: sairuh → paw
| Assignee | ||
Comment 29•25 years ago
|
||
Needs to go on trunk.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 30•25 years ago
|
||
blake - can you correct target milestone to 0.9.4 or later then?
| Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Comment 31•25 years ago
|
||
nav triage team:
Marking nsbeta1+ and p1, cc-ing pchen
Keywords: nsbeta1+
Priority: -- → P1
Comment 32•25 years ago
|
||
PChen - Is Blake still working on this one? Is this a "stop-ship"? Will this one
be completed by today?
---> Pchen, because blaker has finished his internship, and now is blakeross, again.
Assignee: blaker → pchen
Status: ASSIGNED → NEW
| Assignee | ||
Comment 33•25 years ago
|
||
Yes, this is a stop ship, I'm working to juggle back-to-school and mozilla and
one is losing out. I will have it in by tonight. Please don't reassign my bugs,
even as blakeross, I'm still a real person.
Assignee: pchen → blakeross
Comment 34•25 years ago
|
||
Blake, you probably realized but just in case:
There's a better place to put this than was done back on the branch
http://lxr.mozilla.org/mozilla/source/xpfe/bootstrap/nsNativeAppSupportWin.cpp#1847
Here, the condition that the last window closing is the special window is
already dealt with.
Comment 35•25 years ago
|
||
sure thing blake . . . keep up the good work.
| Assignee | ||
Comment 37•25 years ago
|
||
| Assignee | ||
Comment 38•25 years ago
|
||
- the showDialog pref defaults to true.
- disregard
+#include "nsIWindowsHooks.h"
+#include "nsIPromptService.h"
that's for another bug.
Status: NEW → ASSIGNED
Comment 39•25 years ago
|
||
If Turbo is IN, we should nsbranch+ this bad boy, and request a PDT+.
| Assignee | ||
Comment 40•25 years ago
|
||
The fix is on the trunk...
Comment 41•25 years ago
|
||
Moving to nsbranch+, we still need this for the current release.
Comment 42•25 years ago
|
||
Is this fixed on the branch w/Law's checkin?
Comment 43•25 years ago
|
||
Yes, resolving as FIXED.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•