Project

General

Profile

Actions
Copy link

Bug #59171

closed

Subheader visibility depends on doctype

Added by Torsten Crass over 10 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
TypoScript
Target version:
-
Start date:
2014-05-28
Due date:
% Done:

0%

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

Description

Hi,

if I am not mistaken, the decision for which content element types a subheader gets rendered depends on whether the doctype is html5 or not.

Assuming we have a non-empty subheader and we are not talking about an old-style mailform, if config.doctype is html5, then the condition in lib.stdheader.20.if turns true, and the HTML5 subheader gets rendered (and also wrapped by lib.stdheader.stdWrap.dataWrap).

On the other hand, when config.doctype does not equal html5, subheaders get only rendered for content elements of cType "header", since then tt_content.header.20.if becomes true.

I don't know if this is a bug or supposed to be a feature, but I'd expect the decision whether or not to render a subheader should be consistently made independently from the current doctype.

Regards --

-- Torsten

Actions
Copy link
 #1

Updated by Riccardo De Contardi about 9 years ago

  • Category set to TypoScript
Actions
Copy link
 #2

Updated by Riccardo De Contardi almost 8 years ago

  • Status changed from New to Closed

I am sorry that so much time has passed without a progress. I tend to close this one for now...

. CSC will be soon deprecated, and this kind of change is too dangerous and breaking for the existing installations to implement it now.
. Please use FSC where this dependency from the doctype is AFAIK absent.

If you think that this decision is wrong, please reopen it or open a new issue with a reference to this one.

Actions
Copy link

Also available in: Atom PDF