[TYPO3-core] RFC: #5835: Make clear.gif configurable

[Franz Koch]

Hi Steffen,

>>> can we not wrap the whole content element with one div that
>>> a) holds the id of the ce and
>>> b) has style="margin-top:??px; margin-bottom:??px"
>>
>> wasn't that exactly my proposal (including a working code snippet) 
>> from monday? ;)
>>
> 
> sry, i overseen the example you posted.
> Just a little remark - i wouldn't use cbox but as it is CSC (or should 
> be) something like csc-content-element.

it was just copy'n'paste from a live website - so not generalized for 
CSC. For a general version I'd not use a default class - I only needed 
that for the special layout of the website.

> Secondly i don't see need of using important, imho inline styles always 
> overriding heneral definitions.

well - you never know what strange ideas IE might come up with :). I 
just wanted to make absolutely sure that even "!important" definitions 
in regular stylesheet get overridden by the inline style in IE.

> Could you make a patch for CSC using compat version 4.3? Would be great 
> so we all can test. 

Sure. But maybe we should first discuss if "padding" should be used for 
spacing or margin. Following situation:

- CE 1 (space below 20px)
- CE 2 (space above 30px)

When using "margin" FF will show a space of 30px between the two CEs 
(using the higher of the two values), wheres IE might come up with 50px. 
I at least think it was like that - or maybe the other way around. I at 
least got different spaces in IE and the rest of the world or noticed 
some other issue when using margins.

Using "padding" will in both cases have a space of 50px between both 
elements, which would be backwards compatible. But the downside of using 
padding is, that you get problems if you apply some styling class from 
the section_frame dropdown (maybe for highlighting with a background).

So which way to go?


 > I would prefer such solution much more than the
> coded one from Susanne (sry)

You still need Susannes patch to get rid of the clear.gif on other 
places then default tt_content rendering.

-- 
kind regards,
Franz Koch