Closed Bug 10805 Opened 25 years ago Closed 25 years ago

[BLOCKER]Build number is not correct in navigator-tes1.xul file

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: bsharma, Assigned: bsharma)

References

Details

Build number used to appear as Build ID in navigator.xul file. But, now there is no file with such in res/samples. I found Build ID field in navigator-test1.xul file but it is labeled as 99032911 which is wrong.
Severity: normal → blocker
Summary: Build number is not correct in navigator-tes1.xul file → [BLOCKER]Build number is not correct in navigator-tes1.xul file
This bug is blocking our QA auto scripts grabbing the right build number. Can this be fixed please?
i'm suprised you haven't gotten a response about this. navigator.xul got moved during M8 when matt fisher did his chrome work. the file lives in the /chrome directory now. so install today;s build, see where the navigator.xul is, and then change your test scripts accordingly.
Thanks...Bindu..this work for ya?
Blocks: 11349
Assignee: don → bsharma
over to bsharma to see if this works.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Status: VERIFIED → REOPENED
The navigator-test1.xul does not exists in res/samples directory. I need to get the Build number information for the Performance report. In which file can I find the Build number information and where that file is located?
look in the file navigator.dtd. It's in there.
Resolution: FIXED → ---
Clearing FIXED resolution due to reopen.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Found the Build number in the navigator.dtd.
Status: RESOLVED → VERIFIED
QA Contact: leger → bsharma
Marking Verified.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.