Bug #15892
closed
Text with image misses the clearing DIV
0%
Description
Under certain circumstances, CSC causes a display error:
1. Have a web site with a DIV around the main content. Assign the content DIV a different background color than the rest of the page so that the container is clearly visibly.
2. Add a content element "text with image" (without the "no wrap" option".
3. Add an image.
4. Enter some text - only so much that the text is will be less tall than the image in the front end.
Expected result:
In the FE, the containing DIV will be resized so that the image is fully inside the DIV. For this, the clearer DIV should be added after the image container.
Actual result:
The image is partly out of the content container (because it is floated and there is no clearer DIV after the image/text block).
I will attach a screenshot of the problem on http://www.niesmann.de/news/jahr_2006.html?&MP=6235-6198%2C6282-7098 .
A workaround is to use "image in text (no wrap)" instead of just "image in text" (I will use this for that page so that it looks okay again). Yet, the standard "image in text" should prevent this, too.
(issue imported from #M2978)
Files
Updated by Oliver Klee over 18 years ago
Oh, the installation where the problems occurs uses TYPO3 3.8.0 with cron_cssstyledimgtext 0.4.1.
Updated by Ernesto Baschny over 18 years ago
This is an issue in cron_cssstyledimgtext. This has been integrated into css_styled_content, but only in TYPO3 4.0 (beta 2). I submitted some last changes today and plan to "back-port" all new features and bug fixes that went into the integration into my extension, so that it can also be used with TYPO3 3.8.x.
So tecnically this is not the place to submit this bug, since this is not a problem of css_styled_content.
As of this specific problem, this has been solved in the integration. Just open the pi1/class.tx_croncssstyledimgtext_pi1.php file and replace "<div class="csi-clear"></div>" with "<div class="csi-clear"></div>" (adding an empty comment inside this <div>).
So any moderator here, please close this bug.