Project

General

Profile

Actions

Bug #16097

closed

Sccessibility issue: XHTML compatibility of text with image content

Added by Martin Gratzer almost 18 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
Content Rendering
Target version:
-
Start date:
2006-04-27
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I found out that there is an error on the CSS Styled Content Extension when using an Text & Image content element. The generated XHTML Code looks like this:

<div class="...">
<dl class="...">
<dt><img .../></dt>
</dl>
<dd class="...">Caption...</dd>
</div>

but it should look like that to be XHTML valid:

<div class="...">
<dl class="...">
<dt><img .../></dt>
<dd class="...">Caption...</dd>
</dl>
</div>

I have solved the problem by changing the rednerMethod with adding

tt_content.textpic.20.renderMethod = div

to my template setup
(issue imported from #M3363)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #20438: Provide more flexible rendering for "text with image"ClosedErnesto Baschny2009-05-16

Actions
Actions #1

Updated by Ernesto Baschny almost 18 years ago

I can confirm this. It happens in 4.0-mode and setting styles.content.imgtext.imageTextSplit to "0" (default is "1"). I'll try to find a fix for it asap.

Actions #2

Updated by Martin Gratzer almost 18 years ago

Here the note regarding your message:

I could reproduce this error. It happens if you set
"styles.content.imgtext.imageTextSplit = 0" in the constants. Is this
your case? Could you give more informations on your system?

- did you upgrade from 3.8? if yes, did you choose compatMode = 4.0?
- what constants and other TS-setup do you have that are referring to
"imgtext"?

I have a fresh 4.0 installation, no upgrade.
Here is the list of my constants:

styles.content.links.extTarget = _self
styles.content.imgtext.maxW = 0
content.defaultHeaderType = 1
styles.content.imgtext.maxWInText = 0
styles.content.imgtext.linkWrap.width = 0
styles.content.imgtext.linkWrap.newWindow = 0
styles.content.imgtext.imageTextSplit = 0
styles.content.imgtext.emptyTitleHandling = rkeepEmpty
styles.content.imgtext.titleInLink = 1
styles.content.imgtext.titleInLinkAndImg = 1
styles.content.imgtext.colSpace = 0
styles.content.imgtext.textMargin = 0
styles.content.imgtext.borderColor = black
styles.content.imgtext.borderThick = 0
styles.content.imgtext.borderSpace = 0
styles.content.imgtext.borderSelector = DIV.csc-textpic-border DIV.csc-textpic-imagewrap .csc-textpic-image IMG
styles.content.mailform.badMess = Dieses Feld wird benötigt
styles.content.mailform.goodMess = Vielen Dank
styles.content.searchform.goodMess = Vielen Dank
styles.content.loginform.goodMess = Vielen Dank
styles.content.loginform.pid = 0
content.space = 0|0
PAGE_TARGET = _self
content.pageFrameObj = _self
styles.content.getNews.newsPid = 0

Actions #3

Updated by Chris topher about 14 years ago

The problem here was, that the dd-tag was rendered outside the dl-tag.
I just checked this issue with 4.3:

It is fixed.

Actions #4

Updated by Ernesto Baschny over 13 years ago

Fixed with new feature #11107 in 4.3

Actions #5

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF