Closed Bug 10523 Opened 25 years ago Closed 23 years ago

Mailnews in menus when component not installed

Categories

(SeaMonkey :: MailNews: Message Display, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.0

People

(Reporter: bfulgham, Assigned: timeless)

References

Details

(Keywords: helpwanted, polish, Whiteboard: [nsbeta3-])

I have build the Debian GNU/Linux version of Mozilla with mail-news support.
Due to the modular nature of the software, I attempted to factor out the editor
and mail-news components into separate binary packages, so that a user could
elect to install only the browser, or the browser and editor but not the mail,
etc.

If I install only the browser (meaning that none of the mail-news chrome or
components are on my system) the browser runs fine.  If I select the "Messenger"
menu item, I get a blank frame for the messenger, which hangs around until I
kill mozilla.  Obviously, with no mailnews support I should not expect to get a
messenger by making this selection.  However, I don't think that selection of
this menu item should create this blank frame.

This occurs under the M8 Milestone build under Debian GNU/Linux.  Glibx2.1,
compiled using egcs 1.1 on a Pentium II system.
Assignee: don → phil
Component: Browser-General → Back End
Product: Browser → MailNews
QA Contact: leger → lchiang
Summary: Mailnews Integration Issue → [PP]Mailnews Integration Issue
Forwarding to mail folks to answer.
Assignee: phil → dp
I would have thought Messenger would not be in the menu if it was not installed.
Reassigning to someone with a clue about the registry or apprunner - please
reassign appropriately.
Assignee: dp → hyatt
I heard XUL fragments being the solution for this.
Beth - do you guys test the menus to see what happens when Messenger is not
installed? Thanks.
Overlays will solve this problem.  Reassigning to don.
Assignee: hyatt → don
Overlays will not magically solve this problem. Note that it is not just the
task menu, it is also the file menu, prefs, the search menu, and taskbar. And it
is not just mail, it is also chat, conferencing,3270, and whatever other app
comes along that wants to integrate with the browser.
bug 11426 is pretty much a dup of this.
Severity: minor → normal
Priority: P3 → P1
Summary: [PP]Mailnews Integration Issue → [BETA][PP]Mailnews Integration Issue
Target Milestone: M11
Upgrading to a beta issue.
Blocks: 11091
(target milestone is M11 or M12 - add to mail beta tracking bug)
Target Milestone: M11 → M12
I don't think this is a M11 stopper.  To get this off the M11 list, I'm moving
out to M12. Don, if you disagree, pls change back. Thanks.
Move to M13.
Target Milestone: M13 → M15
Move to M15.
Summary: [BETA][PP]Mailnews Integration Issue → [PP]Mailnews Integration Issue
Hmmmm ...
Keywords: pp
Summary: [PP]Mailnews Integration Issue → Mailnews Integration Issue
Summary: Mailnews Integration Issue → Mailnews in menus when component not installed
Don, is this really M15?  Is this bug on your radar somewhere?  (It's in the
MailNews product which you may not look at regularly.)  Maybe the product should
be changed to browser?
Mass moving to M16 to get these off the M15 radar.  Please let me know if this
is really an M15 stopper.
Target Milestone: M15 → M16
Target Milestone: M16 → M18
I think this is a mail problem.  Reassigning to me.
Assignee: don → putterman
Are you sure this is a mail problem? If it's a xul problem, maybe i should try 
to figure this out... Reporter, if you could describe (in excrutiating detail) 
how I could reproduce your build on linux, I would appreciate it, then i'll 
look into this.  But there's a time window, I'm about to change lose my 
freelance status.

This is not a platform parity issue.  It is a product parity issue since 
Navigator 4 doesn't mention messenger unless you have communicator.
Keywords: pp4xp, b3mail, polish, ui
Adding nsbeta3 to b3mail bugs.
Keywords: nsbeta3
Removing b3mail keyword (these bugs have been promoted now.)
Keywords: b3mail
I think it's a mail problem because we need to make sure that these items only 
get added to other components when mail is installed. So we need to put them in 
dynamic overlays.  Some of this has already been done but I don't think all of 
it has.
Mail triage team is marking the remainder of this bug as nsbeta3-
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future
taking this as QA contact
QA Contact: lchiang → stephend
Can I change the status to assigned, since we seem to agree this occurs?
No.
a) only assignee can do that
b) this bug is in the wrong component [it really belongs in browser:user 
interface or mailnews:front end]
c) this assignee isn't likely to fix it, please read the bugzilla most doomed 
list, putterman and I are both doomed in mailnews.

To fix this requires extracting a few menus into overlays and then setting them 
up to be registered for overlay use by mailnews.

I did have an extraction mechanism for this, however the menus that we would 
dump into need a reorg so i will not do this until that is created.

Ask jag on irc for more info.

For accounting, i'll lump this into my pile.  Remember: Assigned bugs are no 
more or less likely to be fixed by overburdenned engineers.  If someone wants 
to commit my current work i'll gladly send it to that person. Marking 
helpwanted, setting milestone...
Assignee: putterman → timeless
Component: Mail Back End → Mail Window Front End
Keywords: nsbeta3helpwanted
OS: Linux → All
Hardware: PC → All
Target Milestone: Future → mozilla1.0
I have addressed (pun!) part of the problem with attachment 41186 [details] [diff] [review] to bug 89234.
IMHO this has been fixed. See bug 46596.
Yes, I only see Navigator and Composer on both the taskbar and the Tasks menu
item, when choosing a Custom install in the installer and unselecting mail/news.
 marking fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Verified FIXED using installer bits for:

Mac OS 9.1 - 2001-09-21-08
RedHat 7.1 - 2001-09-23-08
Windows 2K - 2001-09-23-06
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.