Closed Bug 752797 Opened 12 years ago Closed 12 years ago

Build ID absent from about: page

Categories

(SeaMonkey :: UI Design, defect)

defect
Not set
normal

Tracking

(seamonkey2.11 unaffected, seamonkey2.12? verified)

VERIFIED FIXED
seamonkey2.12
Tracking Status
seamonkey2.11 --- unaffected
seamonkey2.12 ? verified

People

(Reporter: tonymec, Assigned: ewong)

References

()

Details

Attachments

(3 files, 3 obsolete files)

Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/15.0 Firefox/15.0a1 SeaMonkey/2.12a1 ID:20120507003035

Now that bug 588909 has landed, the build date is absent from the about: page (instead of Gecko/20120507 on the bottom line, I see Gecko/15.0). I suggest that the bottom line "Build ID: <user agent>" be replaced by two lines: "User Agent: <user agent>" and "Build ID: <build ID>" with the 14-digit build-ID YYYYMMDDhhmmss, e.g. today 20120507003035.

On SeaMonkey there is no separate About dialog (Help → About SeaMonkey opens the about: page, just as it did on Netscape) but IMHO Firefox and Thunderbird could benefit from this too.

I'm filing this against the General component because I can't figure where bugs for the (generic) about: page belong.

See also bug 588909 comment #128
We definitely don't need this for Firefox; removing tracking flags.
Product: Core → Toolkit
QA Contact: general → general
Hey Tony SeaMonkey forked the about: page in bug 555939. Perhaps you could either move this to SeaMonkey or file another bug in SeaMonkey.
(In reply to Philip Chee from comment #2)
> Hey Tony SeaMonkey forked the about: page in bug 555939. Perhaps you could
> either move this to SeaMonkey or file another bug in SeaMonkey.

If it's "not wanted fot Firefox" (see comment #1) I suppose I'll have to.
Component: General → UI Design
Product: Toolkit → SeaMonkey
QA Contact: general → ui-design
Yeah, Dão made clear in bug 589444 already that he doesn't want the Build ID anywhere, I didn't realize though that his opinion equals what Firefox wants.

Anyway, given that the page was forked already, look for suite/common/about.xhtml for a place to add the Build ID (either as another item in the list close to the UA string or more nicely formatted next to the version string in the upper part).
I think the toolkit about: page probably should have this as well as the forked SeaMonkey about: page - even though I fully agree with comment #1 in that Firefox doesn't *need* it (which doesn't mean that it wouldn't be good to be done in that general about: page as well).
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #5)
> I think the toolkit about: page probably should have this as well as the
> forked SeaMonkey about: page - even though I fully agree with comment #1 in
> that Firefox doesn't *need* it (which doesn't mean that it wouldn't be good
> to be done in that general about: page as well).

I agree in the abstract, though I don't much care about products other than SeaMonkey (I didn't know this page was forked). Maybe some Toolkit guy should open a parallel bug?
The general question raised by Callek in bug 752333 comment #3 was if we should keep maintaining different forks of those about: pages (e.g, Thunderbird forked about:support already with some extensions that are of interest for SeaMonkey but meaningless in the Firefox context) or if Toolkit would be willing to add some "hooks" for other applications to add features they consider important without having to fork the entire page (the other example may be about:buildconfig which should have some comm-central link in addition to mozilla-central for applications building from there). On the other hand, it is clear that the UX expectations differ at least between Firefox and SeaMonkey, thus favoring separate forks.
Let's keep this bug to about: and adding the build ID there and not convolute it with the question if other pages should be forked or not. This page was forked because of the low profile and importance it has on Firefox in contrast to SeaMonkey and an alleged security risk that nobody really could explain in the light of other about:xxx pages being around that seem to not have that problem. Maybe the non-overridden default page has different constraints due to different code paths. Anyhow, it is forked and therefore not too hard to change for adding the build ID.

Centerum censeo that we should redesign this page some time, but that's subject to yet another bug.
Attached patch Add buildID to about: page. (v1) (obsolete) — Splinter Review
Assignee: nobody → ewong
Status: NEW → ASSIGNED
Attachment #627445 - Flags: review?(neil)
Comment on attachment 627445 [details] [diff] [review]
Add buildID to about: page. (v1)

>+        //listItem.appendChild(document.createTextNode("&about.buildIdentifier;"));
Nit: remove comment before check in.

>+<!ENTITY about.userAgent            "User Agent: ">
Nit: lowercase a in "User Agent: " please.
Attachment #627445 - Flags: review?(neil) → review+
Attached patch Add buildID to about: page (v2) (obsolete) — Splinter Review
Attachment #627445 - Attachment is obsolete: true
Attachment #627481 - Flags: review+
Attachment #627481 - Attachment is obsolete: true
Attachment #627482 - Flags: review+
Pushed to comm-central:
http://hg.mozilla.org/comm-central/rev/6f776bf05c33
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/15.0 Firefox/15.0a1 SeaMonkey/2.12a1 ID:20120526213553

I VERIFY that the bug is fixed on this Linux64 hourly build, as shown by the screenshot in comment #14.
I assume that the fix is platform-agnostic. Feel free to REOPEN with specifics if you still see it in a SeaMonkey 2.12a1 build made *after* comment #13.
Status: RESOLVED → VERIFIED
Target Milestone: --- → seamonkey2.12
(In reply to neil@parkwaycc.co.uk from comment #10)
> >+<!ENTITY about.userAgent            "User Agent: ">
> Nit: lowercase a in "User Agent: " please.

This landed with the capital 'A' rather than "User agent: " as requested.
(In reply to rsx11m from comment #16)
> (In reply to comment #10)
> > >+<!ENTITY about.userAgent            "User Agent: ">
> > Nit: lowercase a in "User Agent: " please.
> This landed with the capital 'A' rather than "User agent: " as requested.
Possibly because my comment was confusing; I should have said '"User agent: " (lower case a) please' (showing the corrected spelling).
(In reply to rsx11m from comment #16)
> (In reply to neil@parkwaycc.co.uk from comment #10)
> > >+<!ENTITY about.userAgent            "User Agent: ">
> > Nit: lowercase a in "User Agent: " please.
> 
> This landed with the capital 'A' rather than "User agent: " as requested.

In my quality as reporter, I'm happy with either. You may want to land an incremental patch, or even open an additional bug of "trivial" severity (cosmetic problem, misspelling, etc.)
I'm sure ewong can push a quick follow-up patch for this, given that the original patch already received an r+ with the case change (i.e., no need for a new bug).
Attachment #627868 - Flags: review?(neil)
Comment on attachment 627868 [details] [diff] [review]
follow up patch to fix 'User agent'

Need to change line 108 of about.xhtml too?
Attachment #627868 - Attachment is obsolete: true
Attachment #627868 - Flags: review?(neil)
Attachment #627878 - Flags: review?(neil)
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → ASSIGNED
Attachment #627878 - Flags: review?(neil) → review+
Pushed to comm-central:
http://hg.mozilla.org/comm-central/rev/c94f0c7434e4
Status: ASSIGNED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
VERIFIED with lowercase a in "User agent".
Status: RESOLVED → VERIFIED
P.S. “Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/15.0 Firefox/15.0a1 SeaMonkey/2.12a1” ID:20120531003003
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: