Closed Bug 66833 Opened 24 years ago Closed 23 years ago

profile manager should disappear more quickly after choosing a profile

Categories

(SeaMonkey :: Startup & Profiles, defect)

x86
Windows 98
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED WORKSFORME
mozilla0.9.4

People

(Reporter: jruderman, Assigned: ccarlen)

Details

(Keywords: perf)

Attachments

(3 files)

mozille.exe -profilemanager mozilla.exe -console -profilemanager When I try to close profile manager (by double-clicking on a profile name or by clicking "start mozilla"), it takes about a second for the dialog to disappear. This is a little confusing. (If making the window disappear more quickly would hurt startup performance, feel free to wontfix.)
Summary: profile manager should disappear more quickly → profile manager should disappear more quickly after choosing a profile
Keywords: perf
nav triage team: Reassigning to ccarlen
Assignee: ben → ccarlen
When you click on the "Start" button in the dialog, the profile is set and this is a fair amount of work. For other reasons, I am investigating closing the dialog before doing any of this work. That would solve this. While the total time would not be much different, the dialog would disappear instantly.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.2
Attached patch The rest of the patch (deleted) — Splinter Review
Profile Mgr has up to now, posed its modal dialogs by using appshell and spinning up an event loop. The front-end code exits the modal loop by calling Quit() on the appshell. The current profile is set after the confirm button is clicked but before the dialog is closed - hence the delay described here. While this delay is a small problem, using appshell to pose dialogs this way is a big problem. When nsAppShellService::Quit is called in exiting the modal loop, appshell's mNativeAppSupport is killed off. The patch here uses window watcher to pose the dialogs and dialog param blocks to get data info from the dialog. The dialog can be posed, closed, then interrogated, then the action is taken. This cleans up the back end considerably.
Attached patch update to 2nd attachment (deleted) — Splinter Review
Adding Dan & Alec for r and sr. Ignore the .js changes in the 2nd patch which are in the 3rd.
ok, I think I'm understanding where the actual fix is :) sr=alecf
-> 0.9.3 Because the patch is sizable but does not fix a crucial bug, but is more of a structural improvement, I doubt it's going to be allowed in any time soon.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
changing QA contact
QA Contact: gbush → ktrina
Much of this work has been done as part of other things. The final bit will have to wait until 0.9.4.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
This patch was incorporated into another bug (bugscape 8046) which already is reviewed. That makes this one moot. Problem will be solved when that's checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
I think "worksforme" or "fixed" would be a more appropriate resolution.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Marking wfm.
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → WORKSFORME
Verified (problem solved when fix for bugscape bug 8046 is checked in)
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: