57850 - Netcenter is identifing as current build as Preview 1

Status: VERIFIED FIXED

(Core :: Layout, defect, P3)

Description

[Chris Petersen]

Build: 2000102408
Platform: All
Expect result: Correct browser version should be displayed
What I got: Netcenter indicates I'm using Preview release 1.

Steps to reproduce:

1) Go to http://home.netscape.com/computing/download

2) Netcenter reports the current browser is Preview Release 1.

Comment 1

[Chris Petersen]

Netcenter will need to indentify it as Netscape 6 and not Preview 1-3.

Comment 2

[Chris Petersen]

Nominating RTM. Netcenter will need to identify N6 properly in the near future.

Comment 3

[lchiang]

Good catch!  I'll try to find out who the owner of this page may be.  dveditz or 
jar - do you know if Netcenter has to change their page and if so, who should be 
contacted?

Comment 4

[Daniel Veditz [:dveditz]]

The page code defaults to pr1, then looks for "6.0b2" or "6.0b3" in the user 
agent to update the version. The code isn't expecting the plain "6.0" recent 
releases are using.

This page is owned by greggl I believe.

Comment 5

[Gregg Landskov (gone)]

this will be fixed - no worries

Comment 6

[Gregg Landskov (gone)]

JavaScript Sniff has been updated, push will go out later tonight.  The results 
for now will say "You are using: Netscape 6  Congratulations! Please stay tuned 
for the next release..."  We will be updating this message for launch day, but 
not before.  So yes we know it is not ideal, it will be addressed for launch and 
only people using post-PR3 daily builds will be able to see it.

Comment 7

[lchiang]

this got fixed for rtm by Netcenter si de, so I will go ahead and put rtm++ in
status whiteboard to get this bug higher on our verification radar.

Comment 8

[Chris Petersen]

Fixed in the Oct 26th branch build. 

Comment 9

[Asa Dotzler [:asa]]

It's identifying mozilla builds (branch and trunk 10/27) as Netscape 5.0

Comment 10

[lchiang]

Is that what it's supposed to do, Gregg?

Comment 11

[Chris Petersen]

Verified fixed in the 2001010209 trunk build.