[TYPO3-dev] css_styled_content makes wrong markup
Martin Kutschker
martin.kutschker-n0spam at no5pam-blackbox.net
Fri Feb 29 23:34:32 CET 2008
Steffen Kamper schrieb:
> Hi,
>
> with the no wrap options of Text/image the markup is semantical wrong.
>
> Here is the markup with text beside, right
>
> <!-- CONTENT ELEMENT, uid:22/textpic [begin] -->
> <a id="c22"></a>
> <!-- Image block: [begin] -->
> <div class="csc-textpic csc-textpic-intext-right-nowrap"><div
> class="csc-textpic-imagewrap"><dl class="csc-textpic-image
> csc-textpic-firstcol csc-textpic-lastcol" style="width:296px;"><dt><img
> src="uploads/pics/filter.png" width="296" height="97" border="0" alt=""
> /></dt></dl></div><div style="margin-right:306px;"><div
> class="csc-textpic-text">
> <!-- Header: [begin] -->
> <div class="csc-textpicHeader csc-textpicHeader-25"><h1
> class="csc-firstHeader">Test</h1></div>
Well, such things happen in CSS when you want to float stuff. Of course
if you want to make the header always stay on top you're right. it seems
that the intention of the code is different.
> The second is the anchor which is unnecessary and also can cause problems
> with css.
Could you give an example of such a problem?
>In this case it would be enough to have
> <div class="csc-textpic csc-textpic-intext-right-nowrap" id="c22">
> and all browsers are able to jump to this section instead of some dinosaurs
The anchor is done in the same way for all content elements. Depending
on the markup of the specific element it may be more elegant to move the
anchor id to another place, but it's more difficult.
Masi
PS: If you have really much time on your hand you could write a
replacement for CSC. IMHO it suffers from trying to be (in a way)
backwards compatible to the old "cotent (default)". This is not really
necessary.
More information about the TYPO3-dev
mailing list