Closed
Bug 63103
Opened 25 years ago
Closed 24 years ago
add "About Plug-ins" to the Help menu
Categories
(SeaMonkey :: Help Documentation, enhancement)
SeaMonkey
Help Documentation
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9
People
(Reporter: niko, Assigned: bzbarsky)
References
Details
Attachments
(7 files)
3.74 KB,
patch
|
Details | Diff | Splinter Review | |
3.13 KB,
patch
|
Details | Diff | Splinter Review | |
3.06 KB,
patch
|
Details | Diff | Splinter Review | |
3.25 KB,
patch
|
Details | Diff | Splinter Review | |
4.11 KB,
patch
|
Details | Diff | Splinter Review | |
4.12 KB,
patch
|
Details | Diff | Splinter Review | |
3.77 KB,
patch
|
Details | Diff | Splinter Review |
The description says all, there should be a menu-item which opens the
about:plugins page, because IMHO this feature is very unknown, and should be
accesable for the user without knowing any pseudo-URLs
Comment 1•25 years ago
|
||
I agree.
![]() |
Assignee | |
Comment 3•25 years ago
|
||
![]() |
Assignee | |
Comment 4•25 years ago
|
||
Comments on the patch:
1) I added the necessary entities to the utilityOverlay.dtd files in l10n (under
en-GB and en-DE). Should I be doing that?
2) The utilityOverlay.dtd file already has a AboutPluginsCmd.label entity
defined as ".About Plug-Ins". Note the leading ".". So I ended up making up a
new entity name (AboutCommPluginsCmd.label) for this patch. Should I just
modify the text for AboutPluginsCmd to kill the "."? Or is that reserved for
some sort of future use?
Comment 5•25 years ago
|
||
This has got a vote from me. Excellent idea.
![]() |
Assignee | |
Comment 6•25 years ago
|
||
Adding some keywords
Comment 7•25 years ago
|
||
This feature should also work with the "modal" help about window.
Comment 8•25 years ago
|
||
Two comments about the patch :
1) Does the patch need to define new accesskeys for the en-DE and en-GB dtd?
2) Why not put the oncommand directly on the menuitem (we could fix the way the
release notes menu item works too)
![]() |
Assignee | |
Comment 9•25 years ago
|
||
Actually, looks like release notes does it that way because the URL text needs
to be dynamic. There is no reason for the about:plugins to be dynamic, so moving
that to the xul.
Going to attach an updated patch that addresses Fabian's comments.
![]() |
Assignee | |
Comment 10•25 years ago
|
||
![]() |
Assignee | |
Comment 11•24 years ago
|
||
Comment 12•24 years ago
|
||
r=fabian. We could also remove the name= on the about menu item. Also I think
having dtd entities on name= is a bad mojo, but I'm not sure. Can anyone confirm
what I'm saying?
![]() |
Assignee | |
Comment 13•24 years ago
|
||
Alec, could you sr?
Comment 14•24 years ago
|
||
I think the menuitem text should be "Show Installed Plug-ins" instead of "About
installed plugins". Also, I don't think the command should be on the Help
menu. How about Tasks->Tools or Debug?
Should about:plugins eventually be integrated into the "Helper Applications"
prefs panel, and then changed to just refer/point to that panel?
Cc mpt.
![]() |
Assignee | |
Comment 15•24 years ago
|
||
Tasks->tools, perhaps. Debug, absolutely not. This should be in a menu that
will be included in commercial versions of Mozilla, in my opinion.
![]() |
Assignee | |
Comment 16•24 years ago
|
||
Jesse, just to comment further on the points you raise. There is I believe a
separate bug on improving about:plugins itself and maybe integrating it with the
helper app prefs.
This bug is just for a quick way to get to about:plugins. If about:plugins is
done away with, this will need to go away too. But since it's unlikely that
about:plugins will change form in the near future, it would be nice to have a
menu option for pulling it up instead of expecting users to know arcane urls to
type.
Comment 17•24 years ago
|
||
About Plugins is the right menu name.
However, in nc4 plugins is above About Communicator, and I think that's correct
for mozilla too.
I'm sorry i didn't look at the patch earlier. I was thinking about this feature
a while ago and thought that it should only be in the navigator menu [which you
can't currently do...], but after checking nc4 the menuitem does indeed appear
in mail.
in nc4 navigator about plug-ins changes the current window to about:plugins.
in messenger it finds an open navigator window and uses it. ie, new windows
are opened as a last resort.
verah is gone, reassigning. cc german/ben for opinions.
Assignee: verah → bzbarsky
Keywords: 4xp
Summary: add an "About installed plugins" entry to the help menu → add "About Plug-ins" to the Help menu
Comment 18•24 years ago
|
||
It makes no sense to me that going to a Help option in Mail should cause a
destructive action to take place in Navigator (re-using a window). But then
again I think it's evil that we do that for links in e-mail messages, too.
Comment 19•24 years ago
|
||
If it is in menus, it should be in the Help menu, like 4.x. The current patch has
three problems. Firstly it says `Plugins' when it should say `Plug-ins'. Secondly
it is below the main `About' item, when the main `About' item should always be
the last item in the `Help' menu (preceded by a separator), which means that
`About Plug-ins' should be above it. Thirdly, the current `About' item should be
renamed `About Mozilla' (or `About &suiteNameShort;', if there is such an entity)
to avoid confusion, and adding another `About' item just makes this more urgent.
However, items in the `Help' menu should be kept to an absolute minimum, because
generally those users who need to access help need as little confusion as
possible. So eventually about:plugins should be replaced by information in the
Helper Apps prefs panel.
Comment 20•24 years ago
|
||
> when the main `About' item should always be
> the last item in the `Help' menu
unless you are talking about Mac OS Classic where it is common practive to have
the app "About..." first and any other items underneath as the first items of the
Apple menu.
Comment 21•24 years ago
|
||
there already bugs for us doing useless stuff in the apple menu, and i'm sure
you can file a bug for About &shortSuiteName;. let's leave this bug for About
Plug-ins [I wrote it right 2 out of 3 times in my previous comment, which is a
passing grade].
Comment 22•24 years ago
|
||
Yes, I was talking about the `Help' menu rather than the Apple menu. See my
2000-11-22 comment in bug 43935 about how XP Toolkit should handle `About' items
in the Apple menu.
![]() |
Assignee | |
Comment 23•24 years ago
|
||
![]() |
Assignee | |
Comment 24•24 years ago
|
||
mpt, that last patch addresses the first two points you raise. As for the third
point, that menuitem currently has its value dynamically reset in
utilityOverlay.js to the value of aboutStrName in the brand.properties file. So
in the menu it says 'About Mozilla', not 'About'.
I'm not sure whether we should change the dtd given that it's not being used.
In fact, I would be in favor of eliminating that value= from the xul altogether;
that way people will notice if it's not being set properly in the js...
Comment 25•24 years ago
|
||
If the only time people will see it is if a JS error occurs, perhaps you could
change `About' to `[An error occurred while processing this directive]' ... :-)
No, leave it as `About' for error-resiliency, but (if you can be bothered doing
so) add a comment to the source code noting that it should never be seen.
Comment 26•24 years ago
|
||
if the design masters agree with the design, the coding part is ok too
Comment 27•24 years ago
|
||
Personally i'd prefer if we followed nc4's approach of putting all about items
into one group.
![]() |
Assignee | |
Comment 28•24 years ago
|
||
![]() |
Assignee | |
Comment 29•24 years ago
|
||
Added the comments mpt requested. Also per mpts request added class="about" to
the about menu items (for use in Apple menu stuff).
timeless, it seems that NS 4.x is inconsistent as to whether the separator is
there or not. On Unix/Win it is not, on Mac it is. I feel that having it there
is better in case we end up with yet another "about" menu item....
Comment 30•24 years ago
|
||
should you use class="about application" for "about" so that we can separate
it?
Comment 31•24 years ago
|
||
My thinking is that XP Toolkit will take the class="about" items, insert the
last one first in the Apple menu (since that will be the `About NameOfApp'
item), and then insert the rest in their original order.
![]() |
Assignee | |
Comment 32•24 years ago
|
||
I think class="about application" is more flexible since that way we can either
use the class or mpt's proposed solution. Attaching revised patch.
![]() |
Assignee | |
Comment 33•24 years ago
|
||
Comment 34•24 years ago
|
||
class="about application" specifies *two* classes for the item at once -- the
`about' class and the `application' class. Is that really what you want?
![]() |
Assignee | |
Comment 35•24 years ago
|
||
I thought that was the point. An "about" class for all the About items so we
can separate them from other menuitems and an "application" class in addition to
that for the global About so that we can separate it from other About items.
Comment 36•24 years ago
|
||
*** Bug 70007 has been marked as a duplicate of this bug. ***
![]() |
Assignee | |
Comment 37•24 years ago
|
||
So.... timeless? mpt? comments? I hear there is a localization freeze coming
soon and since I've added a new label....
![]() |
Assignee | |
Comment 38•24 years ago
|
||
Updated•24 years ago
|
Keywords: mozilla0.9
Comment 39•24 years ago
|
||
r=timeless. the stupid about nonsense does not belong in this bug, if/when mac
people or mpt care, they can file a new bug.
ben please a=
Comment 40•24 years ago
|
||
we don't need a separator between the about plugins and the regular about (see
4.x)... other than that, a=ben@netscape.com
Comment 41•24 years ago
|
||
fix checked in, thanks
Status: NEW → RESOLVED
Closed: 24 years ago
Keywords: mozilla0.9,
review
Resolution: --- → FIXED
Target Milestone: --- → mozilla0.9
Comment 42•24 years ago
|
||
Verified fixed windows 98 build 2001051404
Verified fixed mac build 2001051408
Verified fixed linux build 2001051412
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•