Closed Bug 36418 Opened 25 years ago Closed 25 years ago

M16 pre's think they are M14 still

Categories

(SeaMonkey :: Build Config, defect, P3)

Product:
SeaMonkey
Component:
Build Config
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jmd, Assigned: granrosebugs)

References

(
URL
)

Details

help->about and the user-agent sent to servers identifies M16 builds (2000041911) as M14 still. User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.13 i686; en-US; m14) Gecko/20000419 Assuming all platform/OS, only PC/Linux tested.
Confirmed. This isn't unusual at this early stage of the milestone to have it reporting the correct version. I expect it to get fixed as M16 is getting ready to be released.
Severity: minor → trivial
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → M16
I have the fix for this in my tree, so I'll take it and leave cls to pursue the more interesting stuff.
Assignee: cls → granrose
adding leaf as QA since I can't own and QA the fix.
Status: NEW → ASSIGNED
QA Contact: granrose → leaf
See bug 36027. If some enterprising Build Config engineer wants to resolve this when the fix for this bug gets checked in... It only requires a ONE letter (number, actually) change and these two are related (in a way).
fix checked in. should show up in tomorrow's verification builds.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.