Closed Bug 214267 Opened 21 years ago Closed 18 years ago

Review for Awkward UI Text

Categories

(Firefox :: General, defect, P2)

defect

Tracking

()

RESOLVED WORKSFORME
Firefox1.0

People

(Reporter: bugs, Unassigned)

References

Details

Review all UI text strings.
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → Firebird1.0
-> me
Assignee: bugs → blake
Status: ASSIGNED → NEW
Adding bug 210202 and bug 215737 to this bug
Depends on: 210292, 215737
QA Contact: asa
Depends on: 236586
Depends on: 236660
Depends on: 238571
Depends on: 234369
Depends on: 238190
Depends on: 241676
Flags: blocking1.0+
Depends on: 203720
I'm not sure if this applies, but adding bug 213186.
Depends on: 213186
Flags: blocking-aviary1.0RC1+
Would bug 246365 be a good candidate? It comprises an awkward text string and awkward button labels.
Sorry! I accidentally cleared the "depends" box on bug 214267 by hitting alt+d (the location bar shortcut). :( I just resurrected them from my browser history.
Does bug 248655 belong here (Arvid Axelsson still credited with default theme in Help->About->Credits)?
The text in bug 251062 could possibly use some love
need to start locking down on UI changes in the next week or so to stay on track.
Depends on: 253149
No longer depends on: 253149
Summary: Awkward UI Text Review → Review for Awkward UI Text
I've been knocking the dependencies off. When looking at the dependency tree, be sure to note which open ones are marked fixed-aviary1.0.
Depends on: 255113
I'm going to -minus- this tracking bug. if depenencies really need to get in on the branch at this point lets mark those blocking-aviary10.PR. I suspect we won't be able to take many more UI changes after that so any work needs to be wrapped up quickly.
Flags: blocking-aviary1.0PR-
Flags: blocking-aviary1.0PR+
Flags: blocking-aviary1.0-
Flags: blocking-aviary1.0+
Assignee: bross2 → nobody
QA Contact: general
Good night, long abandoned tracker.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.