Project

General

Profile

Actions

Bug #58167

closed

Meta-Tag http-equiv="Content-Type" content="text/html [...]"

Added by anybody no-lastname-given almost 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2014-04-24
Due date:
% Done:

0%

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

Description

For some versions of XHTML it would be usefull to change the Meta-Tag http-equiv="Content-Type" content="text/html [...]" for valide XHTML.

This problem was reported twice (see below), the solution was closing both issues reffering to the other. One was closed because of the other with the attribute "resolved", the other one closed because the first one was "resolved". But this is no solution.

The support of XHTML5 is till not included (target 6.1). If the Core Developement Team does only like to follow the hype of commercialization of the internet and the system of dictatorship of few oligopolist (WHATWG), then they should pronounce that the support of XHTML will be skipped or there should be again the possibility to produce valide XHTML without hacking all the PHP.

Recorded in two issues:

Bug #17534:
"Add a template-TS option (fx. config.renderContent) to set another content type for <meta http-equiv="Content-Type" [...]>.
Content-Type "text/html" is hardcoded but "application/xhtml+xml" is required for doctype xhtml_11 and above."

Bug #17561:
"When using config.doctype = xhtml_11 to specify that the content output is xhtml 1.1 a meta charset and ontent type tag is output that does not reflect this setting. How to reproduce: Set up a page as xhtml 1.1 and specify: config.doctype = xhtml_11

Expected result:
A meta tag saying:
<meta http-equiv="Content-Type" application/xhtml+xml; charset=utf-8"/>

Observed result:
A meta tag saying:
<meta http-equiv="Content-Type" text/html; charset=utf-8"/>

I propose to use an identical case stucture as is in use for the doctype switch itself.

I'm not a doctype guru, so I fixed this in our install for xhtml_11 only. The other meta tags are default.

(issue imported from #M6214)"


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #17534: Meta-Tag http-equiv="Content-Type" content="text/html [...]"ClosedChristian Kuhn2007-08-15

Actions
Related to TYPO3 Core - Bug #17561: meta http-equiv="Content-Type" should change along with config.doctypeClosed2007-08-27

Actions
Related to TYPO3 Core - Feature #22992: Pagerenderer - use better method for adding meta tagsClosed2010-06-25

Actions
Actions #1

Updated by Riccardo De Contardi almost 9 years ago

This is still present in 6.2.12

Actions #2

Updated by Riccardo De Contardi over 8 years ago

Confirmed also for v.7 (latest master)

Actions #3

Updated by Riccardo De Contardi over 8 years ago

  • Category set to Frontend
Actions #4

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from New to Closed

There has been no activity since a lot of time. Although the issue is still present, I close this one and ask everyone to continue on #22992.

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

Actions

Also available in: Atom PDF