Closed
Bug 465668
Opened 16 years ago
Closed 16 years ago
"Composition Toolbar" menuitem has wrong accesskey
Categories
(Thunderbird :: Message Compose Window, defect)
Thunderbird
Message Compose Window
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 3.0b2
People
(Reporter: dev-null, Assigned: dev-null)
References
Details
Attachments
(1 file)
2.10 KB,
patch
|
mkmelin
:
review+
|
Details | Diff | Splinter Review |
In composition window, the accesskey of View -> Toolbars -> Composition Toolbar is incorrect.
Attachment #348922 -
Flags: review?(mkmelin+mozilla)
Comment 1•16 years ago
|
||
confirmed. A _C_ is shown as the access key for both the Toolbar and Customize. Nominating Blocking Beta 1 since We are in String freeze.
Flags: blocking-thunderbird3.0b1?
Comment 2•16 years ago
|
||
Um, no. You don't nominate things as blockers because of the string freeze, you nominate them because you think they block the release, and if they really do block it, we might break the string freeze for them. However, something that nobody even noticed for five months doesn't amount to a b1 blocker, even without having to worry about a string.
Assignee: nobody → dev-null
Flags: wanted-thunderbird3+
Flags: blocking-thunderbird3.0b1?
Flags: blocking-thunderbird3.0b1-
Target Milestone: --- → Thunderbird 3.0b2
Version: unspecified → Trunk
Comment 3•16 years ago
|
||
I felt a decision needed to be made about the landing of the proposed patch because of the string freeze and not knowing if this fit that restriction.
Comment 4•16 years ago
|
||
Comment on attachment 348922 [details] [diff] [review] Patch v1.0 Nice catch, thx for the patch! r=mkmelin You'll have to wait until after the string freeze to get this landed.
Attachment #348922 -
Flags: review?(mkmelin+mozilla) → review+
Updated•16 years ago
|
Whiteboard: [land after tb3.0b1 string freeze]
Comment 5•16 years ago
|
||
http://hg.mozilla.org/comm-central/rev/6be1639196ad
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [land after tb3.0b1 string freeze]
You need to log in
before you can comment on or make changes to this bug.
Description
•