Closed
Bug 331414
Opened 20 years ago
Closed 20 years ago
Accelerate keys conflict in bookmark organizer window.
Categories
(Firefox :: Bookmarks & History, defect, P3)
Tracking
()
RESOLVED
FIXED
Firefox 2 beta1
People
(Reporter: tim.miao, Assigned: bugs)
Details
(Keywords: access)
Attachments
(2 files, 1 obsolete file)
|
739 bytes,
patch
|
Gavin
:
review-
|
Details | Diff | Splinter Review |
|
6.10 KB,
patch
|
bugs
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050607 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9a1) Gecko/20060322 Firefox/1.6a1
Accelerate keys conflict.
Reproducible: Always
Steps to Reproduce:
1. Launch firefox and expand Bookmarks menu.
2. Select Organize Bookmarks menu to open the bookmark manage window.
3. Press Alt+F to expand File menu in this popup window.
Actual Results:
New folder window will popup instead of expanding File menu. This leads to fail opening top menu File in this window.
Expected Results:
There should not be two command with same accelerate key.
This bug can be reproduced on Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9a1) Gecko/20060322 Firefox/1.6a1.
System info:
Sun Blade 100, SNV_35/Vermilion_07.
Updated•20 years ago
|
Component: Keyboard Navigation → Places
QA Contact: keyboard.navigation → places
Attachment #215984 -
Flags: review?(gavin.sharp)
Comment 2•20 years ago
|
||
Comment on attachment 215984 [details] [diff] [review]
Patch
Since this accesskey is used in multiple places (see http://lxr.mozilla.org/seamonkey/search?string=placesCmd_new%3Afolder ), this will cause conflicting accesskeys in the bookmark context menu ("O" for "Open" and "New Folder"). It's hard to tell which accesskeys are still available to be used, and even more difficult to tell which can conflict with each other given that they are all used in multiple places, so I don't have any suggestions on how to fix this properly.
Attachment #215984 -
Flags: review?(gavin.sharp) → review-
Comment 3•20 years ago
|
||
(In reply to comment #2)
> this will cause conflicting accesskeys in the bookmark context menu
Though I suppose having conflicting access keys in the context menu might be better than having them in the main window - so if all else fails, it might still be worth landing that patch.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•20 years ago
|
||
IMO Alt+F is universal in Windows for 'File' access, thus Places window should follow same, and move other accelerator keys that are in conflict.
Fairly common practice to use Alt+F Alt+C to close the window.
Comment 5•20 years ago
|
||
(In reply to comment #4)
> IMO Alt+F is universal in Windows for 'File' access, thus Places window should
> follow same, and move other accelerator keys that are in conflict.
No one is disagreeing with that statement, that's why this bug was filed.
(In reply to comment #3)
> (In reply to comment #2)
> > this will cause conflicting accesskeys in the bookmark context menu
>
> Though I suppose having conflicting access keys in the context menu might be
> better than having them in the main window - so if all else fails, it might
> still be worth landing that patch.
>
In bookmarks manager of firefox 1.5, the access keys of newfolder is different in different place. It's alt-o in file menu and main window, alt-f in context menu. Why not port all these key settings here. Also it is better for user to have the same user experience.
Comment 7•20 years ago
|
||
(In reply to comment #6)
> Why not port all these key settings here. Also it is better for user to
> have the same user experience.
Sure, that might be a good idea, but there are many new items that also need accesskeys, so I don't know how feasible that is.
Updated•20 years ago
|
Severity: major → normal
OS: Solaris → All
Hardware: Sun → All
Version: unspecified → 2.0 Branch
| Assignee | ||
Comment 8•20 years ago
|
||
A better solution might be to move the accesskey attribute off the <command> and onto each instance.
Assignee: nobody → bugs
Priority: -- → P3
Target Milestone: --- → Firefox 2 beta1
Comment 9•20 years ago
|
||
Attachment #217406 -
Flags: review?(bugs)
| Assignee | ||
Comment 10•20 years ago
|
||
Comment on attachment 217406 [details] [diff] [review]
change the accesskey to "o" ,just same as firefox 1.0.7
I don't think it's a good idea to add another command for a different command instantiation in the UI... I think it'd be better to remove the accesskey attribute from the <command> element entirely and place it on each of the pieces of UI that refer to the command.
e.g.:
> <command id="placesCmd_new:folder"
> label="&cmd.new_folder.label;"
> oncommand="PlacesController.newFolder()"/>
> <menuitem id="placesContext_new:folder" command="placesCmd_new:folder"
> accesskey="&foo;" selection="mutable"/>
Attachment #217406 -
Flags: review?(bugs) → review-
Updated•20 years ago
|
Attachment #217406 -
Attachment is obsolete: true
Comment 11•20 years ago
|
||
Attachment #217542 -
Flags: review?(bugs)
| Assignee | ||
Comment 12•20 years ago
|
||
Comment on attachment 217542 [details] [diff] [review]
patch(remove accesskey attribute from command)
r=ben@mozilla.org
Attachment #217542 -
Flags: review?(bugs) → review+
| Assignee | ||
Comment 13•20 years ago
|
||
fixed-on-trunk, fixed-1.8-branch
Thanks!
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 14•16 years ago
|
||
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".
In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body contains places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.
Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.
Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in
before you can comment on or make changes to this bug.
Description
•