TYPO3 Core

This problem also occurs with a single RTE on a sheet that is not active when the page ist loaded.

I can reproduce this bug in 4.2.1.

I attached a simple test extension based on your flexform.

Maybe someone takes a look at this.

Using the test extension, I cannot reproduce the first part of this issue neither in 4.1.8-dev, nor in 4.3.0-dev using Firefox 3.

However, the layout is indeed awkward, but in different ways, in 4.1.8-dev and 4.3.0-dev.

To make sure that the first part of the issue is not related to incorrect installation, please delete all files in typo3temp/rtehtmlarea and all files with names starting with "rtehtmlarea_" in directory typo3temp.

Thanks Stan.

Part 1 (the focus issue) happens only in ff 2, I also can not reproduce this in ff 3, nor in Opera 9.50.

I can reproduce part1 with ff 2.0.0.14, on latest trunk and 4-2 branch: If I select the other tab after loading, click into the textarea and type in some text, then the "Quick find" bar in ff2 is opened with the typed text.

I think that this is due to the fact that the flexform tabs are not included in TCEform->getDynNestedStack

In version 4.2.6 and 4.2.8 the problem that the RTE overlaps other input fields with in flexforms still appears.
Saving problems or anything like that, we counld not reproduce.

I tried to understand what produce the bug and analysed the javascript code. There are many objects rendered with the attribut "display:none" and they have no height and width when calling the function sizeIframe in htmlarea.js. For this reason it is not possible to calculate the tool- and statusbar dimensions in auto mode.
At a be extension with multiple rtes in tabs i could fix this with a string replace for "DTM_activate" and an own function named "DTM_activate" calling the original function and sizeIframe. Because sizeIframe makes the rte smaller with every call, I switch from auto to fix dimension and the function is only executed once for each tab.
I used this code snippet at the extension:

$this->doc->JScode .=
// ... DynTabMenu-Kode mit modifiziertem Namen der Aktivierungsfunktion laden
str_replace('DTM_activate', 'DTM_activateOrig', $this->doc->getDynTabMenuJScode())
// ... Eingene Aktivierungsfunktion definieren, welche die Originalfunktion aufruft und
// einmalig Größenkorrekturen für alle RTEs vornimmt.
.'<script language="javascript" type="text/javascript">'
.'function DTM_activate(idBase,index,doToogle) {'
// ... Originalfunktion ausführen
.'DTM_activateOrig(idBase,index,doToogle);'
// ... Größenkorrekturen für alle bereits angelegten RTEs ausführen.
// (Die RTEs werden am Skriptende angelegt, weshalb bei der erstmaligen Ausführung am
// Skriptanfang nur das Objekt mit den Versionsinformationen existiert).
.'if( typeof(RTEarea) != "undefined" ) {'
.'try {'
// Die Namen aller Objekteigenschaften analysieren: init, initEditor, 0, data[tx_....
.'for(var eigenschaft in RTEarea) {'
// Objektfunktionen und Versionsinformationen ignorieren, ferner muss mit der
// Eigenschaft ein Editor verknüpft sein und die Höhe muss automatisch bestimmt
// werden.
.'if( eigenschaft != "0"'
.' && typeof(RTEarea[eigenschaft]) "object"'
.' && typeof(RTEarea[eigenschaft].editor) "object"'
.' && RTEarea[eigenschaft].editor.config.height == "auto"'
.' ) {'
// auto-Modus durch fixe Angabe deaktivieren, weil der RTE sonst durch wiederholte
// Berechnungen immer kleiner wird.
.'RTEarea[eigenschaft].editor.config.height = '
.'RTEarea[eigenschaft].editor._textArea.style.height;'
// Dimensionen berechnen.
.'RTEarea[eigenschaft].editor.sizeIframe(2);'
.'}'
.'}'
.'} catch(err) {'
.'}'
.'}'
.'}'
.'</script>'
;

The overlap issue was fixed in TYPO3 4.3 alpha2.

This issue is fixed in TYPO3 4.3 branch.