Closed Bug 106588 Opened 23 years ago Closed 23 years ago

about: does not display build ID when javascript is disabled

Categories

(Core :: Security: CAPS, defect)

defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 91779

People

(Reporter: mozillaBugzilla, Assigned: security-bugs)

References

Details

I can't find out the build ID from the UI from the solaris trunk build obtained
from:
ftp://ftp.mozilla.org/pub/mozilla/nightly/latest-trunk/mozilla-sparc-sun-solaris2.6.tar.gz

It's not in the title bar, nor is it on the aobut page.

going to http://www.gemal.dk/browserspy/basic.html
gives me: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.5+) Gecko/20011024
you can add a bookmark with this URL : javascript:alert(navigator.userAgent)

Is there no Build Id at all or is the build id in the title=00000000 ?
FYI: that javascript URL doesn't work if all options in the tabbrowser are
enabled (Another bug perhaps)

I get the same result as was reported by browser spy.


I'm assuming the buildID is the Gecko/20011024 (or jsut 20011024) of the string
but it jsut doens't appear on teh title bar, nor does it appear in the about screen

Okay, after a bit more testing, it doesn't appear there *IF JavaScript is
disabled* -- Changing summary

Unfortuantly, that's how I do the majority of my browsing nowadays.
Summary: Can't find Build number via UI → about: does not display build ID when javascript is disabled
confirming with win2k build 20011023..

The about:mozilla page doesn't show the UA string if I disable JS.
(realted to bug 91779)

-> Security Caps
Assignee: asa → mstoltz
Status: UNCONFIRMED → NEW
Component: Browser-General → Security: CAPS
Ever confirmed: true
OS: SunOS → All
QA Contact: doronr → bsharma
Hardware: Sun → All
dup of 91779. Yes, I realize that one talks about "about:plugins", not "about:"
but believe me when I say this is the same bug, and don't reopen this one.

*** This bug has been marked as a duplicate of 91779 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Marking verified duplicate as per above developer comments.
Status: RESOLVED → VERIFIED
*** Bug 179090 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.