DOM Inspector uses wrong (old) localeVersion

RESOLVED FIXED

Status

()

Core
Localization
RESOLVED FIXED
16 years ago
15 years ago

People

(Reporter: Karl Ove Hufthammer, Assigned: tao)

Tracking

Trunk
x86
Other
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Build ID: 2002080419

The 'localeVersion' for DOM Inspector is currently set to '0.9.4' instead of
'1.1b'. (See the two 'conrents.rdf' files in 'inspector.jar'.) This makes it
difficult to localize.

To fix: change 'chrome:localeVersion="0.9.4"' to 'chrome:localeVersion="1.1b"'
in the 'contents.rdf' files for DOM Inspector. This should be part of the build
process, so that the localeVersion is automatically updated when a new
localeVersion is used globally. I believe this already happens for all other
.jar files, as they are all up to date.
(Reporter)

Updated

16 years ago
Keywords: mozilla1.1
(Reporter)

Comment 1

16 years ago
Nominating for Mozilla 1.0.1, as this is an extremely low-risk bug to fix (it's
a simple one line fix), but makes localization of DOM Inspector ~impossible.
Keywords: mozilla1.0.1
(Reporter)

Updated

16 years ago
Blocks: 109891

Updated

16 years ago
QA Contact: ruixu → kasumi

Comment 2

16 years ago
->tao.
Assignee: rchen → tao
(Reporter)

Comment 3

16 years ago
I can confirm that this is still a bug in the latest version (2002-10-06-10).

Nominating for Mozilla 1.2, as this is an extremely low-risk bug to fix (it's
a simple one line fix), but makes localization of DOM Inspector impossible.
Keywords: mozilla1.0.1, mozilla1.1 → mozilla1.0.2, mozilla1.2
(Reporter)

Updated

16 years ago
Depends on: 174989

Comment 4

16 years ago
my patch for bug 174989 (just checked in) should have this fixed for current
trunk (nightlies), we have localeVersion="1.2b" there now, I hope we'll catch it
for the 1.2final change :)

FIXED on the trunk, not fixed on 1.0 branch.

Comment 5

15 years ago
marking FIXED
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.