Open
Bug 466217
Opened 16 years ago
Updated 2 years ago
[Mac] Firefox does not display menu items from _any_ contextual menu plug-in in Mac OS
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: kelekonaken, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 As an OSX Power User, I use a variety of tools to speed my workflow. One such tool is "On My Command" that allows me to create context menu items relevant to my workflow. (http://www.abracode.com/free/cmworkshop/) Apparently Firefox is not using the standard OSX Menu Manager rendering the tool non-functional within Firefox. Developer comment is available here: http://abracode.com/pipermail/omc_abracode.com/2008-May/000329.html Setting up duplicate context menus within Firefox (something I have not attempted and I not sure if the power of OMC is available) should not be required as it creates work in maintaining consistency between the environments. Reproducible: Always Steps to Reproduce: 1. Setup OMC on Mac 2. Right-click to access context menu within Firefox Actual Results: OMC command options are not available for selection Expected Results: OMC menu items should be available for selection to perform the configured command on the selected object May be some relationship with Bug 429824 - User-defined shortcuts don't work
Updated•16 years ago
|
Assignee: nobody → joshmoz
Component: Menus → Widget: Cocoa
Product: Firefox → Core
QA Contact: menus → cocoa
Reporter | ||
Comment 1•16 years ago
|
||
I updated the summary to indicate this is a generic problem with context menu plugins and not specific to this one application.
Summary: [Mac] Firefox does not present context menu items generated by "On My Command" → [Mac] Firefox does not display menu items from _any_ contextual menu plug-in in Mac OS
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•