[TYPO3-content-rendering] Problem with figure element

Jordi Mueters jordimueters at hotmail.com
Fri Oct 26 12:03:43 CEST 2012


I think something went wrong with pasting. The syntax is correct, on the 
page there is a space between img and class.

It seems to be in HTML5 syntax, there are no "display: none" rules on 
any of the objects, yet in firebug it shows as grayed out (see-through) 
instead of a solid color. Normally see-through html code would mean it's 
invisible, but I can't find out why it would be invisible.

Weirdly enough, in Internet Explorer (9) it shows the image correctly. 
This is the first time I see Internet Explorer doing something I want 
that Firefox does not haha.

The difference, which I did not make, between IE and Firefox is that in 
Firefox the img element get's a moz-binding:
-moz-binding: 
url("chrome://global/content/bindings/general.xml#foobarbazdummy") 
!important;

When I remove this temporarily using Firebug the image does not show, 
though.

The console does not display any errors during the load of the page.
Using Tamper Data I can not see the image getting loaded, weird too 
isn't it?

On 26-10-2012 11:52, Kay Strobach wrote:
> <imgclass=
>      ^
> Syntax ;D
>
> Am 25.10.2012 20:26, schrieb Jordi Mueters:
>> I never really had this problem before, but suddenly I got the following:
>>
>> I simply create a content element in the BE, Text and Images, and insert
>> my lipsum text and just a simple picture.
>> The text shows up fine, but it seems like typo3 inserts the following in
>> the FE:
>>
>> <divclass="csc-textpic-imagewrap">
>> <figureclass="csc-textpic-image csc-textpic-last">
>> <imgclass="bowidnnbjwnneiesfmfv"width="240"height="400"alt=""src="uploads/pics/black_240x400_1_.gif">
>>
>> </figure>
>> </div>
>>
>> So inside the, for me unknown, figure element (html5 element or such?)
>> it inserts an img element which should show up just like that.
>>
>> It doesn't. In fact, it doesn't display anything at all, not even a
>> spacer for the image which would be 240 x 400.
>>
>> Does this sound like a familiar problem to any of you?
>



More information about the TYPO3-project-content-rendering mailing list