Closed Bug 100277 Opened 24 years ago Closed 17 years ago

no visualisation when quick-launching an application

Categories

(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)

x86
Windows NT
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: erik.fornoff, Assigned: law)

References

Details

(Keywords: helpwanted)

Environment: ============= OS: WinNT 4.0 SP5 Mozilla BuildID: 2001091303 Summary: ========= if you quick launch an application (independent which one) there's no visible indication whether the action is currently performing or not Reproducible: Always Steps to Reproduce: ==================== 1. Start Mozilla Navigator with quick launch feature enabled in preferences 2. Close Mozilla Navigator => Navigator window closes and mozilla icon is visible in system tray 3. right click on mozilla icon => choose any application to launch out of context menu Actual Results: ================ Mouse cursor stays like the default one (e.g. arrow)! Expected Results: ================== At least the hour glass should be shown while the application is beeing quick launched as otherwise the user has no feedback whether the action is really performing in the background or not!
Over to XP Apps:gui
Assignee: asa → blakeross
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps: GUI Features
Ever confirmed: true
QA Contact: doronr → sairuh
QA Contact: sairuh → tpreston
-> quicklaunch
Assignee: blakeross → law
Component: XP Apps: GUI Features → QuickLaunch (AKA turbo mode)
QA Contact: tpreston → gbush
->Future Getting from the back-end code that opens the file to the UI code that can change the cursor is too hard.
Keywords: helpwanted
Target Milestone: --- → Future
*** Bug 213233 has been marked as a duplicate of this bug. ***
Quicklaunch/Turbo Mode is no longer supported in Seamonkey 2 and Seamonkey1.X is in the maintenance mode (fixing only security bugs)
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.