Closed Bug 6381 Opened 26 years ago Closed 26 years ago

nsSampleAppShellComponent.xul: non-localizable XUL file

Categories

(Core Graveyard :: Tracking, defect, P2)

Product:
Core Graveyard
Component:
Tracking
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: tao, Assigned: matt)

References

(
URL
)

Details

(Whiteboard: This is actually not used in the product and is only a sample.)

Please refer to the "XUL Coding Style Guidelines" in the URL above for how to make XUL localizable. Thanks!
Changing QA contact to myself
Assignee: law → matt
Priority: P3 → P2
Target Milestone: M6
Matt ...
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 6379 ***
Status: RESOLVED → REOPENED
Summary: downloadProgress.xul: non-localizable XUL file → nsSampleAppShellComponent.xul: non-localizable XUL file
Hi, matt: Sorry that there is a typo in the summary field. The target file was nsSampleAppShellComponent.xul. Changing summary field to reflect the intended target.
Status: REOPENED → ASSIGNED
Target Milestone: M6 → M7
This is actually not used in the product and is only a sample.
Resolution: DUPLICATE → ---
So is this bug Invalid?
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → INVALID
This is an invalid bug
Status: RESOLVED → VERIFIED
Whiteboard: This is actually not used in the product and is only a sample.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.