[TYPO3-dev] domesticating t3lib_div::debug

Steffen Kamper steffen at sk-typo3.de
Mon May 19 10:15:55 CEST 2008


"Christopher Torgalson" <bedlamhotel at gmail.com> schrieb im Newsbeitrag 
news:mailman.1648.1211183509.4573.typo3-dev at lists.netfielders.de...
> Hi,
>
> On Mon, May 19, 2008 at 9:36 AM, Steffen Kamper <steffen at sk-typo3.de> 
> wrote:
>>
>> "Dmitry Dulepov [typo3]" <dmitry at typo3.org> schrieb im Newsbeitrag
>> news:mailman.1.1211182074.15588.typo3-dev at lists.netfielders.de...
>>> Steffen Kamper wrote:
>>>> no, also FF
>>>>
>>>> its like this:
>>>>
>>>> outer: position relative
>>>> docheader: position absolute
>>>> innerdiv (content): position static
>>>>
>>>> i know this normal behaviour with relative/absolute but i stumbled why
>>>> content disappeared. now i got it hopefully (i didn't checked all
>>>> browsers) and i'm happy that such a solution works :)
>>>
>>> Hm... So you can't make innerdiv absolute? Docheader has certain height, 
>>> I
>>> thought you can have innerdiv absolute as well, positioned after
>>> docheader. I am just curious, never bad to learn why something does not
>>> work.
>>>
>>> --
>>
>> me too - CSS seems not to be logic sometimes, and i don't know if this is 
>> a
>> browser problem or correct CSS behaviour ;-)
>
>
> This is only a wild guess, since I haven't looked at the source, but
> it sounds like the 'innerdiv' element that you've needed to assign
> "position:static;" to is probably implicitly set to position absolute
> or static somewhere else, and either a) has no explicit z-index set so
> it winds up under something else, or b) has no specific xy coordinates
> assigned so it's off in some unexpected location at the 0, 0 point of
> the parent element (and maybe simultaneously underneath something).
>
> Setting the position property to static is not usually necessary since
> that's the default. If it was necessary to do it for a fix in browsers
> with good rendering engines (e.g. Firefox, Safari and Opera) as well
> as IE, then it's likely that that default was somewhere overridden. If
> so, then the alternate fix would be to find the rule that's
> (undesirably) getting applied to the innerdiv element and make that
> rule more specific so that it only applies where it's intended.
>
> -- 
> Christopher Torgalson
> http://www.typo3apprentice.com/

Hi Christopher,

the inner div was set to position:absolute before. You're right that static 
is the default so set it to static should be the same like remove the 
position:absolute there. I played with the css in firebug to get this 
solution, that's why i modified it that way.

vg Steffen 






More information about the TYPO3-dev mailing list