Feature #14384
closed
Context-Menu on Mac-Browsers
Added by Ingo Schommer about 20 years ago.
Updated over 18 years ago.
Description
While the context-menu in the page-tree (left-click on yellow page-icons) gives a "real" dropdown-menu on IE/Win and Mozilla/Win, it fails to do so on every Mac-Browser. I suppose there's some browser-detection that completely excludes Mac-Browsers from getting this feature, although most of them would render it correctly. Pleaaaase change this for the next release, it's really nervewracking to use the horizontal context-menu on top (which is too long for most <1280-resolutions).
MacOS X 10.3.6
Safari 1.2
Firefox 1.0
Internet Explorer 5.5
(issue imported from #M486)
OK, solved this one myself: You just have to remove one check in /typo3/template.php:
"$GLOBALS['CLIENT']['SYSTEM']!='mac'" (diff-dump is attached below)
Tested it with nearly all Mac-Browsers, and only Opera complained (which has like 0.00001% marketshare). All others were fully functional with the new setup, except some rollover-error (past rollover-items stay highlighted). My results on MacOS X 10.3.6:
OmniWeb 5.0.1 (Rollover-Glitch)
Camino 0.8.1 (OK)
Safari 1.2.4 (Rollover-Glitch)
Internet Explorer 5.2.3 (OK)
Firefox 1.0 (OK)
Mozilla 1.7.3 (OK)
Opera 6.0.3 (Doesn't work)
Opera 7.5.0 (Dissapears on mouse-move)
--- template.php Thu Nov 11 19:57:51 2004
+++ template11-10-2004.php Thu Nov 11 19:57:21 2004
@ -346,7 +346,7
@
* @return boolean
*/
function isCMlayers() {
- return !$GLOBALS['BE_USER']->uc['disableCMlayers'] && $GLOBALS['CLIENT']['FORMSTYLE'] && $GLOBALS['CLIENT']['SYSTEM']!='mac';
+ return !$GLOBALS['BE_USER']->uc['disableCMlayers'] && $GLOBALS['CLIENT']['FORMSTYLE'];
}
/**
edited on: 11.11.04 20:02
thats not true. it loads in the top, like in every mozilla-based browser
thats not true. it loads in the top, like in every mozilla-based browser
I have now fixed that bug for all Mac browsers EXCEPT Opera which still seems to behave faulty in some cases. Can't check this since I have no Mac, however it seems that bug #0000675 contains a solution for the problem.
Also available in: Atom
PDF