40914 - Major and minor attributes both show 5

Status: VERIFIED INVALID

(Core :: DOM: Core & HTML, defect, P3)

Description

[Daniel Roberts]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.3.49 i586; en-US; m16) Gecko/20000525
BuildID:    2000042708

The "major" and "minor" attributes in the "Netscape Client Sniffer" test at the
indicated URL both show "5."  I don't think Mozilla is currently == 5.5, is it?

Reproducible: Always
Steps to Reproduce:
1. Go to the given URL
2. Click on "Netscape Client Sniffer"
3. Notice that major and minor at the bottom of the page are both 5.

Actual Results:  major and minor both == 5.

Expected Results:  major should be 5 (or 6??), and minor should be 0.

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

In netscape 4.61, major is 4 and minor is 4.61.  Thus I suspect the current
results are correct.

If you agree, please mark INVALID.  (But changing to DOM Level 0 anyway.)

Comment 2

[Sean Richardson]

Actually, the results should be "5" and "5.0" (for NN 4.72, "4" and "4.72").
The line in the sniffer that sets the variable reported as the Minor is
   var is_minor = parseFloat(navigator.appVersion);

( I know that's not what most people think of when they hear "minor", but
  the comments at the top of the script make it clear that is_minor isn't
  just the part after the "." )

Depending on how parseFloat() works, it might report "5.0" as just "5",
in which case nothing is wrong with Mozilla or its navigator.appVersion.

The original sniffer page mentioned above is
http://www.gemal.dk/browserspy/netscapeis.html -- it's been displaced because
the URL for Netscape's Ultimate JavaScript Client Sniffer is too long 
to fit in 80 columns, and there is plenty of background info there. 

Look under PROFILE OF YOUR BROWSER to see the results.

BTW, http://www.gemal.dk/browserspy/basic.html correctly reports "5.0",
but it's probably parsing the UserAgent string.

Tested with the 2000-05-26-08-M16 nightly binaary on WinNT. Setting OS to All.

Comment 3

[Daniel Roberts]

Hmm...  As I think about it, this makes sense.  But if so, then is there not a
bug (or at the very least, some confusion) in BrowserSpy itself?

Comment 4

[Johnny Stenback (:jst)]

Eric Krock, what's your opinion about this?

Comment 5

[ekrock's old account (dead)]

Even in Nav4.73 on WinNT 4.0SP4, javascript:parseFloat("5.0"); in the location 
bar returns 5. So this is just a consequence of how parseFloat works. INVALID.

Comment 6

[Fabian Guisset]

VERIFIED invalid