Project

General

Profile

Actions

Bug #55272

closed

TYPO3 4.5 HTML5 incompatibility fix

Added by Tizian Schmidlin almost 11 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
Must have
Assignee:
-
Category:
Content Rendering
Target version:
-
Start date:
2014-01-23
Due date:
% Done:

0%

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

Description

As many of you might know, TYPO3 4.5 does not support HTML5 properly.

For example, if you set config.doctype = html5, the base, meta and link tags that are generated by TYPO3 do not close properly (HTML 4 style).

This happens because of typo3/sysext/cms/tslib/class.tslib_pagegen.php at around line 220 to 248, where the html5 tag is not matched in the switch statement and thus "renderHtml" ist deactivated in t3lib_pageRenderer.

This could be solved as follows:
typo3/sysext/cms/tslib/class.tslib_pagegen.php at around line 241:

...
case 'xhtml_2':
    $GLOBALS['TSFE']->xhtmlVersion = 200;
break;
case 'html5':
break;
...

Actions #1

Updated by Markus Klein almost 11 years ago

  • Category set to Content Rendering
  • Status changed from New to Accepted
  • Target version set to next-patchlevel
  • Complexity set to easy
Actions #2

Updated by Gerrit Code Review almost 11 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/27029

Actions #3

Updated by Markus Klein almost 11 years ago

  • Status changed from Under Review to Needs Feedback
  • Target version deleted (next-patchlevel)

According to http://www.w3schools.com/tags/tag_link.asp this syntax is perfectly valid.
Neither base nor link nor meta needs to closed with a slash!

Actions #4

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Rejected

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF