miavir Reporter
	Description • 22 years ago

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

In trying to find the version of the installed Mozilla, it is natural to look at
the 'Help -> About Mozilla' Menu. The page that comes up however does *NOT*
contain the version info.

Reproducible: Always

Steps to Reproduce:
1. In Menu select 'Help -> About Mozilla'

Actual Results:  
Shows Mozilla Info, but doesn't contain Version Info.

Expected Results:  
Added the Version info to the page.

	Olivier Cahagne
	Comment 1 • 22 years ago

Did you install Mozilla 1.3 over a previous Mozilla with extensions ?

	miavir Reporter
	Comment 2 • 22 years ago

I installed 1.3 by moving the old directory where it had been residing away,
then installing the new version in the same place as the old was located. As
such, no data from the old installation remained, except such info as is in the
users own home directories.

	Daniel Wang
	Comment 3 • 22 years ago

multizilla problem? (bug 197693)

	Hermann Schwab
	Comment 4 • 22 years ago

'Help -> About Mozilla' needs Javascript enabled to display version info.
without Javascript it shows only 'Mozilla' linking to
http://www.mozilla.org/releases/

	Maarten Afman
	Comment 5 • 22 years ago

With me it shows the correct version info when I have enabled Javascript.
When I disable Javascript for Navigator it doesn't show the version info. 
Should we put a message between <noscript> tags? 
Like: "Enable JavaScript in the preferences to view version information."
?

	miavir Reporter
	Comment 6 • 22 years ago

Could this be made to work *without* having to have javascript on ? After all,
you generate that page yourself. And I really don't see why you have to turn on
javascript, with all the concommittant security risks that entails, just so that
you can see which Mozilla you're running.

	Hermann Schwab
	Comment 7 • 21 years ago

To repeat the good idea from comment #5:
The about: menue should contain a string in <noscript> tags, that suggests to
turn Javascript on to see the version info.

	Hermann Schwab
	Comment 8 • 21 years ago

Asking for a simple fix:
The about: menue should contain a string in <noscript> tags, that suggests to
turn Javascript on to see the version info.

	Hermann Schwab
	Comment 9 • 21 years ago

Firebird is displaying UserAgent info regardless of Javascript allowed or not.
Found in Firebirds aboutDialog.xul:
<script type="application/x-javascript">
      <![CDATA[
        function onLoad() {
          var userAgentField = document.getElementById("userAgent");
          userAgentField.value = navigator.userAgent;
        }
      ]]>
    </script>

	Ian Oeschger (gone)
	Comment 10 • 21 years ago

not a help bug. kicking up to browser-general

	Christophe Thalet
	Comment 11 • 21 years ago

Confirming this behaviour for Version 4.1

Implementating this via JavaScript is simply nuts.

It is so trivial to change this to pure HTML
that this issue is not even worth any character
that folks have typed here.

Don't tell me IE is unsafe. If you force users to enable JavaScript
just to see the version info, you are going the same direction.
Mozilla is not in any way more bulletproof against buffer overflows
etc. than IE is.

I couldn't believe this concept when I first saw it.

	jwq
	Comment 12 • 20 years ago

This bug may be a duplicate of Bug 91779.

	Kevin Brosnan
	Comment 13 • 20 years ago

Bug 91779 was morphed into an about: bug when it was origionlly an about:plugins
bug. In comment 30 of that bug amutch suggested seperating the bug to an
about:plugins bug and an about: bug.

	jwq
	Comment 14 • 20 years ago

 My reading of Bug 91779 is that it was intentionally expanded to
encompass both the about:plugins and about: problems. Bugs filed 
solely on the about: problem have been consistently marked as
duplicates of Bug 91779. See comment #21 of Bug 91779, comment #2 of
Bug 98169, comment #5 and comment #6 of Bug 179090, comment #1 of 
Bug 207801 and particularly comment #4 of Bug 106588.

 I believe that this bug should also be marked as a duplicate of
Bug 91779 and closed.

	jwq
	Comment 15 • 20 years ago

 OK, let's try again and write that reference list as: 
Bug 91779 comment #21; Bug 98169 comment #2; Bug 179090 comment #5 
and comment #6; Bug 207801 comment #1 and particularly 
Bug 106588 comment #4.

	Kevin Brosnan
	Comment 16 • 20 years ago

*** This bug has been marked as a duplicate of 91779 ***