6297 - JS Navigator object returns bogus platform

Status: VERIFIED DUPLICATE of bug 10465

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

Description

[bobj]

Running xxx build on US NT4, and going to the URL
  http://rocknroll/users/nhotta/publish/html/nav_obj.html
it returns:

 navigator.appVersion=5
 navigator.platform=Win95
 navigator.language=en
 navigator.userAgent=Mozilla/5.0 [en] (Win95; I)
 screen.width=-1
 screen.height=-1
 screen.pixelDepth=-1 bits
 screen.colorDepth=-1 bits, 0.5 colors

but the platform is NT4, not Win95.

I tried this on 4.51 and it returns "Win32".  Better, but not
very precise...

Comment 1

[vidur (gone)]

I'm just getting this from the nsINetService interface. Reassigning to the
netlib guys.

Comment 2

[Warren Harris]

Verify in necko.

Comment 3

[Judson Valeski]

as it stands right now, necko will return null for all user agent components;
they aren't being initialized right now. How do we want to init them now that
they're in necko (pure xp code)? In the old world the FE would set the various
pieces as they are FE dependent. I suppose I should just have the code that is
setting them now grab an nsINetService and set them that way, but there are two
problems with that:

1. Before any urls are loaded we have to be sure that they get set via
nsINetService.
2. How do we protect ourselves from some rogue code grabbing the nsINetService
and changing the values? (there is a certain portion of the UA string that is
static and will act as our brand).

Comment 4

[Judson Valeski]

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

Comment 5

[Prashant Desale]

Maring verified.