Bug #43253
closed
CSC: figcaption problem IE <= 8
0%
Description
If I use the html 5 output and I have a content element text with images(, align the image right) and use a caption, the Internet Explorer <= 8 has a problem with the width of the figcaption element: the width goes wider than the image.
I fixed it using the following typoscript:
tt_content.image.20.rendering.singleCaption.caption.wrap.override >
tt_content.image.20.rendering.singleCaption.caption.dataWrap.override = <figcaption class="csc-textpic-caption###CLASSES###" style="width:{TSFE:lastImageInfo|0}px;"> | </figcaption>
Updated by Patrick Broens almost 12 years ago
- Status changed from New to Needs Feedback
Internet Explorer <=8 does not support HTML5 and CSS >= 2 fully. If you or your client need to have support for these browsers, you should not use HTML5. You can't expect support for new technologies in an old browser. Probably the browsers you're mentioning don't know the figcaption tag at all.
CSC in version 4.7 has been adapted to have no inline styles anymore, to comply with rules for governmental websites in for instance Germany and The Netherlands.
If the solution works for you, please use it on your own website(s), but I shouldn't reinstate the inline styles simply because we need support for older browsers. We don't, especially not with HTML5.
There is always the possibility to have your own rendering for CSC if needed.
Updated by Bernhard Eckl almost 12 years ago
Internet Explorer <=8 does not support HTML5 and CSS >= 2 fully. If you or your client need to have support for these browsers, you should not use HTML5. You can't expect support for new technologies in an old browser. Probably the browsers you're mentioning don't know the figcaption tag at all.
I (and I think most of the other web developers) use html5.js to support it for the older IEs.
If the solution works for you, please use it on your own website(s), but I shouldn't reinstate the inline styles simply because we need support for older browsers. We don't, especially not with HTML5.
How about a condition? If we would talk about IE6 I totally agree, but it affects also IE8! So just kick out all these stuff is not a good solution in my opinion.
Normally a big advantage of TYPO3 is the backwards compatibility but in this case it is not. I think the governments would not be happy if they can not use their installed browser (mostly they don’t have the actual browser installed) to view the sites correctly. So then this can never be a really out of the box running system. I think you also could not tell all your website surfers to just use the bleeding edge version of their browser…
There is always the possibility to have your own rendering for CSC if needed.
Right, in my opinion a custom rendering should be used for special needs, but this is no special need.
I would love to see a small condition and everybody would be happy.
I also don’t like inline styles (and I also don’t like the older IEs), but if there is no better solution, why not use a condition.
Updated by Andreas Keck almost 12 years ago
I agree with Bernhard, it would be better if it just works instead of telling the users to update their browser.
Updated by Alexander Opitz over 11 years ago
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1)?
Updated by Alexander Opitz almost 11 years ago
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback for over 90 days.
If you think, that this is the wrong decision, then please write to the mailing list typo3.teams.bugs with issue number and an explanation.
Updated by Bernhard Eckl almost 11 years ago
What kind of information do you need? It is just broken in IE <= 8 and I don’t know if it still exists on 6.1, if the output of css_styled_content is the same then yes. The project where the problem occured is already finished and I have no access to it anymore. In my opinion the browsers behaviour should be respected even if it is a bug in the browser. Normal things for web developers, think about times with IE 6…