Comment 5 for bug 231487

Revision history for this message
In , Johannes-codeon (johannes-codeon) wrote :

The problem is typo3 uses a frameset which has a frame with the name = "content", and in js references that frame via top.content, which doesn't work - instead, top.frames[framenumber] works (in the case of typo3 std. install its top.frames[3]) - so this really isn't an issue of typo3 itself, but of the ff3 js engine - replacing this code parts of course "fixes" the problem, but i don't think that's the way to go, as i wouldn't love to add another browser to my list of "can't do x in js" for webdeveloping