id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2500	Mac: Context menus always disabled with BrowserContextMenuOnCtrl	Josh Clark		"In Firefox 3, and likely in other browsers, too, it's not possible for Macs to access the context menu when FCKConfig.BrowserContextMenuOnCtrl is enabled.

Macs don't have two mouse buttons; without custom hardware, the way that context menus are triggered in OSX is by pressing the ctrl key. Unfortunately, this means that if the FCKConfig.BrowserContextMenuOnCtrl value is set, it *always* blocks the fck context menu on Mac, because e.ctrlKey is always true when the context menu is triggered:

{{{
( el._FCKContextMenu.CtrlDisable && ( e.ctrlKey || e.metaKey ) )
}}}

One fix is to replace the ( e.ctrlKey || e.metaKey ) condition with this:

{{{
( ( e.ctrlKey && !FCKBrowserInfo.IsMac  ) || e.metaKey )
}}}

That will offer the ctrl-key option for non-Mac systems while allowing the Command-key option for Macs.

My suggestion is to replace lines 101 and 129 (both identical) in fckcontextmenu.js:

{{{
if ( el._FCKContextMenu.CtrlDisable && ( e.ctrlKey || e.metaKey ) )
}}}

...with this:

{{{
if ( el._FCKContextMenu.CtrlDisable
     && ( e.ctrlKey && !FCKBrowserInfo.IsMac ) || e.metaKey ) )
}}}

And replace line 176 of fckcontextmenu.js:

{{{
if ( ( fckContextMenu.CtrlDisable && ( ev.ctrlKey || ev.metaKey ) ) || FCKConfig.BrowserContextMenu )
}}}

...with this:

{{{
if ( ( fckContextMenu.CtrlDisable
       && ( e.ctrlKey && !FCKBrowserInfo.IsMac ) || e.metaKey )
   || FCKConfig.BrowserContextMenu )
}}}

"	Bug	closed	Normal		UI : Context Menu	FCKeditor 2.4.3	fixed	HasPatch