Closed Bug 108795 Opened 18 years ago Closed 11 years ago

Quicklaunch issues

Categories

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

defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: trudelle, Assigned: samir_bugzilla)

References

()

Details

(Keywords: meta)

Attachments

(1 file)

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.
Depends on: 108797
Depends on: 108801
Blocks: 102472
Depends on: 101329
mass-reassigning pchen QuickLaunch bugs to blaker
Assignee: pchen → blaker
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.
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.
Keeping QuickLaunch on by default is important, but I don't need this tracking 
bug on my radar.
Target Milestone: --- → Future
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
Yes, I meant that I would just as soon have the actual bugs I'm responsible for
targetted to this milestone.
I know, and I'd rather you had the actual bugs- I'll take the meta bugs. :-)
Keywords: meta
Depends on: 119056
Depends on: 98673
if mozilla is already installed quick launch should be set to the current
setting. Set bug 125883
Depends on: 99848
Depends on: 128386
Mass-moving remaining Nav team 0.99 bugs to 1.0.
Target Milestone: mozilla0.9.9 → mozilla1.0
Depends on: 100516
No longer depends on: MailNotification
Depends on: 108475
Depends on: 128377
Depends on: 124009
Depends on: 86904
No longer depends on: 100319
No longer depends on: 124009
No longer depends on: 99848
Depends on: 99848
No longer depends on: 128386
No longer depends on: 99848
Depends on: 133120
Depends on: 128386
Depends on: 134039
Please update this bug with an [adt1] - [adt3] impact rating (or take it off the
list if it doesn't even rate adt3.)  Thanks!
not sure what list, and this is a meta bug, so ->1.0.1
Target Milestone: mozilla1.0 → mozilla1.0.1
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"?
Depends on: 136181
Depends on: 134897
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
Depends on: 125561, 133584
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.
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. 
Depends on: 136940
Depends on: 76831
Depends on: 137581
Depends on: 137881
Depends on: 137978
Depends on: 124278
Depends on: 138297
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.
Depends on: 138217
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.
Should this bug be blocked by 123633?  Blake asked the same question in that bug 
report.
Depends on: 123633
Depends on: 121100
Depends on: 115370
Depends on: 132076
Depends on: 141647
Depends on: 143848, 144559
No longer depends on: 121100
No longer depends on: 124278
Depends on: 139880
Depends on: 149176
Depends on: 147223
Depends on: 155679
Summary: Enable QuickLaunch by default for MachV → Quicklaunch issues
Mass moving all of my open Nav/toolkit bugs to new owner.
Assignee: trudelle → sgehani
Depends on: 146340
retargeting
Target Milestone: mozilla1.0.1 → Future
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: 11 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.