TYPO3 Core

This is really an old bug that obviously never got fixed.
See http://typo3.org/1422+M570aa32c2d7.0.html for the resolution and someone please fix this in CVS.

That seems to be interesting. Have a look at Bug #0000486, I think this could be the solution why the remaining problems with TYPO3 on a Mac happen only with Opera.

To make it easier, I attach Karsten Dambekalns' patch here:

--- template.php 2003-02-11 17:29:53.000000000 0100
++ template.php-new 2003-05-20 17:14:39.000000000 +0200
(at)(at) -583,9 +583,8 (at)(at)

if (tempLayerObj && (level==0 || GLV_isVisible[level-1]))       {
                                        tempLayerObj.el.innerHTML = html;
-                                       tempLayerObj.height= (bw.ie4||bw.ie5||bw.ns6||bw.konq)?this.el.offsetHeight:bw.ns4?this.ref.height:bw.op?this.css.pixelHeight:0;
-                                       tempLayerObj.width= (bw.ie4||bw.ie5||bw.ns6||bw.konq)?this.el.offsetWidth:bw.ns4?this.ref.width:bw.op?this.css.pixelWidth:0;
-                               
+                                       tempLayerObj.height= (bw.ie4||bw.dom)?this.el.offsetHeight:bw.ns4?this.ref.height:0;
+                                       tempLayerObj.width= (bw.ie4||bw.dom)?this.el.offsetWidth:bw.ns4?this.ref.width:0;
                                        tempLayerObjCss.left = GLV_curLayerX[level] = GLV_x;
                                        tempLayerObjCss.top = GLV_curLayerY[level] = GLV_y;
                                        tempLayerObjCss.visibility = "visible";

Question: The specified TYPO3 version is 3.6.2 but I think the bug is still there in 3.7.0, right?

Yes, the problem is still in 3.7 and CVS, probably because it was never submitted here and Karsten's patch breaks Opera 5.
To make things more complicated, I uploaded Thomas Hering's patch from the same thread back then, which fixes stuff in two parts. I don't know what this is for, but Karsten's patch works for me as well and is less code ;)
And yes, the Mac patch should not bother with Opera, as this is a different phenomenon.

Kasper wrote:
- I wouild like the explode function to us ",2" as third parameter -
just to make sure it splits on only the first found "=". Only a
theoretical thing.

I agree with this. Changed it already on my local copy of the patch, so this is just for your information.

Stucki, does this mean stuff is (going to be) fixed now? I did not quite understand your comment.

Me, too ;-)
Obviously I pasted this information into the wrong window...

Yes I think we can fix it - I'm still waiting for Kaspers ok to ignore the Opera5 behaviour and simply enable it for all DOM-able browsers.

Fixed in CVS