Closed
Bug 108795
Opened 23 years ago
Closed 15 years ago
Quicklaunch issues
Categories
(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)
Core Graveyard
QuickLaunch (AKA turbo mode)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: trudelle, Assigned: samir_bugzilla)
References
()
Details
(Keywords: meta)
Attachments
(1 file)
1.03 KB,
text/plain
|
Details |
This is a tracking bug for work needed in MachV to enable QuickLaunch (aka Turbo mode, aka The Mother of All Leaks) by default. To do this, we must first define the correct behavior (functional spec), describe how it works (design spec), and then fix a number of defects related to multiple profiles, mail accounts, PSM, memory usage, etc.
Reporter | ||
Updated•23 years ago
|
Reporter | ||
Comment 1•23 years ago
|
||
mass-reassigning pchen QuickLaunch bugs to blaker
Assignee: pchen → blaker
Comment 2•23 years ago
|
||
i think we need to set some criteria for making this decision, and set a date for when this decision needs to be made. propose we make the decision at the beginning of the 1.0 milestone.
Reporter | ||
Comment 3•23 years ago
|
||
What decision? This has already happened, and these are just the bugs we are tracking as a result. If milestone builds and the beta turn up problems, we may be forced to reconsider, but there is no need to plan now to reconsider at any point.
Comment 4•23 years ago
|
||
Keeping QuickLaunch on by default is important, but I don't need this tracking bug on my radar.
Target Milestone: --- → Future
Reporter | ||
Comment 5•23 years ago
|
||
Well then I do, we cannot afford to put out any more releases that have this turned off. taking.
Assignee: blaker → trudelle
Target Milestone: Future → mozilla0.9.9
Comment 6•23 years ago
|
||
Yes, I meant that I would just as soon have the actual bugs I'm responsible for targetted to this milestone.
Reporter | ||
Comment 7•23 years ago
|
||
I know, and I'd rather you had the actual bugs- I'll take the meta bugs. :-)
Keywords: meta
Comment 8•23 years ago
|
||
if mozilla is already installed quick launch should be set to the current setting. Set bug 125883
Reporter | ||
Comment 9•22 years ago
|
||
Mass-moving remaining Nav team 0.99 bugs to 1.0.
Target Milestone: mozilla0.9.9 → mozilla1.0
Reporter | ||
Updated•22 years ago
|
No longer depends on: MailNotification
Reporter | ||
Updated•22 years ago
|
Comment 10•22 years ago
|
||
Please update this bug with an [adt1] - [adt3] impact rating (or take it off the list if it doesn't even rate adt3.) Thanks!
Reporter | ||
Comment 11•22 years ago
|
||
not sure what list, and this is a meta bug, so ->1.0.1
Target Milestone: mozilla1.0 → mozilla1.0.1
Updated•22 years ago
|
Comment 12•22 years ago
|
||
Adding paul, evelyn and scott. What's the difference between this bug, and bug 75599? Is bug 75599 the superset, and this bug simply the top items we need to resolve to "Enable QuickLaunch by default for MachV"?
Reporter | ||
Comment 13•22 years ago
|
||
Basically. Bug 7599 was an old tracker from previous releases, a catch-all that is useless for MachV, IMO. I don't see any reason to maintain it. I am tracking similar NS commercial issues using http://bugscape.mcom.com/show_bug.cgi?id=12562
Updated•22 years ago
|
Comment 14•22 years ago
|
||
Dunno if this would work... If most of the turbo problems are due to switching profiles, is there some way to quit and restart turbo when a different profile is selected and before launching the browser? Worst case, we could throw up a dialog: "quit profile manager) and disable turbo before switching to a different profile"... Switching would take a performance (and maybe a usability) hit, but most users who rarely (or never) switch profiles would get the full benefit of turbo.
Reporter | ||
Comment 15•22 years ago
|
||
We are looking into some variations on this approach, and plan to implement one of them as a fallback option to use in beta if we can't get the real problems fixed in time.
Comment 16•22 years ago
|
||
In my opinion, bug 100846 belongs to this list too. Because of the bug, the QuickLaunch task bar icon is lost until Mozilla process is killed or computer is restarted. Absence of the icon is a major loss of QL functionality.
Reporter | ||
Comment 17•22 years ago
|
||
Thanks for keeping an eye out for QL issues Walter, but I'm not sure that it is major loss of functionality. Is the process still running? If so, then the main benefit of QL remains. The icon only provides the ability to exit, disable and incidental access to individual components, which is only lost until Mozilla restarts. Plus, this happens only after an Explorer crash, which is pretty infrequent.
Comment 18•22 years ago
|
||
Should this bug be blocked by 123633? Blake asked the same question in that bug report.
Comment 19•22 years ago
|
||
Updated•22 years ago
|
Reporter | ||
Updated•22 years ago
|
Summary: Enable QuickLaunch by default for MachV → Quicklaunch issues
Reporter | ||
Comment 20•22 years ago
|
||
Mass moving all of my open Nav/toolkit bugs to new owner.
Assignee: trudelle → sgehani
Comment 22•15 years ago
|
||
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: 15 years ago
Resolution: --- → WONTFIX
Updated•12 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•