Closed
Bug 482450
Opened 16 years ago
Closed 16 years ago
Fix workaround string for the "Open in a New Window" tab context menu item
Categories
(Firefox :: Tabbed Browser, defect, P1)
Firefox
Tabbed Browser
Tracking
()
VERIFIED
FIXED
Firefox 3.6a1
People
(Reporter: wladow, Assigned: wladow)
References
Details
(Keywords: access, late-l10n, verified1.9.1)
Attachments
(1 file)
1.79 KB,
patch
|
Gavin
:
review+
beltzner
:
ui-review+
|
Details | Diff | Splinter Review |
As no one has responded on my bug 225680 comment 144 so far, I'm filing a new bug for fixing the temporary workaround, where "Open in a New Window" tab context menu item is using the string taken from Places and has no accesskey. I think we should fix this in 1.9.1 as well, as this is one of the new features in Fx3.5, which we shouldn't introduce with a temporary string and an accessibility issue.
There's bug 455722 already filed for adding "Duplicate tab" or a similar item, currently with uiwanted keyword set. It seems we won't take it in consideration for 1.9.1 and will use the "Open in a New Window" instead, so this bug should not be a dup of bug 455722.
Attachment #366543 -
Flags: review?(gavin.sharp)
Comment 1•16 years ago
|
||
For the record, I don't really see us taking this patch any more than a working patch in bug 455722 for 3.5.
No idea how to mark up that we should make a call either or.
Comment 2•16 years ago
|
||
Axel, that bug is about duplicating the tab, not detaching the tab. I think this is quite possibly worthwhile, especially since I think "open in a new window" is a little different from what really happes here.
We should do this before string freeze, IMO, and double check that we want the current string.
Updated•16 years ago
|
Attachment #366543 -
Flags: review?(gavin.sharp) → review+
Comment 3•16 years ago
|
||
Comment on attachment 366543 [details] [diff] [review]
fix the menuitem, v1
r=me, thanks!
Comment 4•16 years ago
|
||
Workarounds suck, should definitely fix.
Flags: blocking-firefox3.1? → blocking-firefox3.1+
Priority: -- → P2
Assignee | ||
Comment 5•16 years ago
|
||
Comment on attachment 366543 [details] [diff] [review]
fix the menuitem, v1
(In reply to comment #2)
> We should do this before string freeze, IMO, and double check that we want the
> current string.
Mike, what do you think? Shall we take the "Open in a New Window" string, or should it be changed to let's say "Move to a New Window" or even something else?
Attachment #366543 -
Flags: ui-review?(beltzner)
Comment 6•16 years ago
|
||
--> P1, as this bug will require the wider feedback of a beta release or is of sufficient complexity that we should be looking at it sooner, not later.
Priority: P2 → P1
Updated•16 years ago
|
Attachment #366543 -
Flags: ui-review?(beltzner) → ui-review+
Assignee | ||
Updated•16 years ago
|
Keywords: checkin-needed
Comment 7•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.2a1
Comment 8•16 years ago
|
||
Keywords: checkin-needed → fixed1.9.1
Comment 9•16 years ago
|
||
Verified fixed with:
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090421 Minefield/3.6a1pre ID:20090421041537
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090420 Shiretoko/3.5b4pre ID:20090420044915
Status: RESOLVED → VERIFIED
Keywords: fixed1.9.1 → verified1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•