Closed
Bug 359840
Opened 19 years ago
Closed 19 years ago
Overwrite install from 1.5.x to 2.0 for Korean locale display errors
Categories
(Mozilla Localizations :: ko / Korean, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: baz, Assigned: channy)
Details
(Keywords: fixed1.8.1.1)
Attachments
(2 files)
|
66.43 KB,
image/jpeg
|
Details | |
|
751 bytes,
patch
|
Pike
:
approval1.8.1.1+
|
Details | Diff | Splinter Review |
1. Start with a Firefox 1.5.x Korean locale install in Directory A
2. Ensure Firefox 1.5.x is shutdown
3. Attempt to install Firefox 2.0.0.0 Korean locale into Directory A
4. Installation will present a warning dialog (see attachment)
| Reporter | ||
Comment 1•19 years ago
|
||
The extensions compatibility dialog is broken due to a typo in the adminDisabled.warning.label entity. "&brandShortNmae;" should be "&brandShortName;".
Status: NEW → ASSIGNED
Component: Installer → ko-KR / Korean
Product: Firefox → Mozilla Localizations
Version: 2.0 Branch → unspecified
| Assignee | ||
Comment 3•19 years ago
|
||
Attachment #245321 -
Flags: approval1.8.1.1?
Comment 4•19 years ago
|
||
Comment on attachment 245321 [details] [diff] [review]
update.dtd patch
[ko] approval to land fix for updater for Firefox 2.0.0.1.
Please use the fixed1.8.1.1 and verified1.8.1.1 keywords to track landing and testing.
Attachment #245321 -
Flags: approval1.8.1.1? → approval1.8.1.1+
Comment 5•19 years ago
|
||
[mass-verified1.8.1.1 message, filter on this if you need to]
This bug has an approved patch, but not the verified1.8.1.1 keyword.
Please make sure that the approved patch is landed (add the fixed1.8.1.1 keyword then) and tested. If you verified that the bug in question is indeed fixed on the 1.8 branch nightlies, please add the verified1.8.1.1 keyword.
We need to get the QA activities around Firefox 2.0.0.1 up to speed so that we can feel good about releasing this update.
| Assignee | ||
Updated•19 years ago
|
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Keywords: fixed1.8.1.1
You need to log in
before you can comment on or make changes to this bug.
Description
•