Closed
Bug 305910
Opened 19 years ago
Closed 18 years ago
Open in tabs should have more intuitive title
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
FIXED
Firefox 2 beta2
People
(Reporter: ivan.icin, Assigned: beltzner)
Details
(Keywords: fixed1.8.1, polish)
Attachments
(1 file)
3.95 KB,
patch
|
mconnor
:
review+
mconnor
:
approval1.8.1+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050824 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050824 Firefox/1.0+
Open in tabs is very useful option, but I think that its title may confuse
users. Now that "Bookmark all Tabs" is added to menu, it should be probably
called "Open All in Tabs".
Reproducible: Always
Updated•19 years ago
|
Assignee: nobody → mike
Assignee | ||
Comment 1•19 years ago
|
||
I don't think that this is so important as to block FFx 1.5, but if someone can
whip up a simple patch, it'd be worth looking at.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [ui polish]
Version: unspecified → Trunk
Assignee | ||
Updated•18 years ago
|
Whiteboard: [ui polish] → [ui polish] [swag: 0.5d]
Assignee | ||
Comment 2•18 years ago
|
||
Trivial change to the command label (and update to the comments). This only changes the code in the bookmarks component, not the places component. Let me know if you want me to make a patch that changes it there, too.
Attachment #225383 -
Flags: review?
Assignee | ||
Updated•18 years ago
|
Whiteboard: [ui polish] [swag: 0.5d]
Assignee | ||
Updated•18 years ago
|
Attachment #225383 -
Flags: review? → review?(mconnor)
Updated•18 years ago
|
Attachment #225383 -
Flags: review?(mconnor) → review+
Comment 3•18 years ago
|
||
mozilla/browser/components/bookmarks/content/bookmarksMenu.js 1.56
mozilla/browser/locales/en-US/chrome/browser/bookmarks/bookmarks.properties 1.15
Status: NEW → RESOLVED
Closed: 18 years ago
OS: Windows XP → All
Hardware: PC → All
Resolution: --- → FIXED
Version: Trunk → 2.0 Branch
Comment 4•18 years ago
|
||
Is this something that we want to land for b2?
Target Milestone: Firefox 2 beta1 → Firefox 2 beta2
Updated•18 years ago
|
Flags: blocking-firefox2?
Comment 5•18 years ago
|
||
not a blocker, but we'll likely take the patch
Flags: blocking-firefox2? → blocking-firefox2-
Updated•18 years ago
|
Attachment #225383 -
Flags: approval1.8.1?
Comment 6•18 years ago
|
||
This change isn't reflected in a key change, is that intentional? I think that this is a UI-consistency issue that localizers have hardly done themselves.
Comment 7•18 years ago
|
||
Comment on attachment 225383 [details] [diff] [review]
makes changes in command label and comments
a=mconnor on behalf of drivers for checkin by Wednesday, July 19th
Attachment #225383 -
Flags: approval1.8.1? → approval1.8.1+
Updated•18 years ago
|
Whiteboard: [checkin needed (1.8 branch)]
Comment 8•18 years ago
|
||
How do we know whether localizers have or have not done things with consistent phrasing? This doesn't look like a semantic change to me, since its just using clearer language. Hopefully localizers have already done that...
Comment 9•18 years ago
|
||
mozilla/browser/components/bookmarks/content/bookmarksMenu.js 1.48.2.9
mozilla/browser/locales/en-US/chrome/browser/bookmarks/bookmarks.properties 1.12.2.3
Keywords: fixed1.8.1
Whiteboard: [checkin needed (1.8 branch)]
Comment 10•18 years ago
|
||
(In reply to comment #8)
> How do we know whether localizers have or have not done things with consistent
> phrasing? This doesn't look like a semantic change to me, since its just using
> clearer language. Hopefully localizers have already done that...
>
Guessing roughly from an l10n checkout from before this landing on the 1.8 branch, your chances are 2-3 out of 54. Post to .l10n at least?
You need to log in
before you can comment on or make changes to this bug.
Description
•