Task #28015: Deprecate Content Object HTML - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Actions

Copy link

Task #28015

closed

Deprecate Content Object HTML

Added by Kai Ole Hartwig almost 13 years ago. Updated almost 11 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Xavier Perseguers

Category:

TypoScript

Target version:

Start date:

2011-07-09

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

4.6

PHP Version:

Tags:

Complexity:

Sprint Focus:

Description

Since TYPO3 4.5 TEXT and HTML behave the same way. HTML does not really make sense anymore and as such could be deprecated.

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Mr. Hudson almost 13 years ago

Patch set 1 of change I0080345efd881e273537db8797e31038d185c36c has been pushed to the review server.
It is available at http://review.typo3.org/3210

Actions

Copy link

Updated by Georg Ringer almost 13 years ago

sorry but this element really needs to stay. I agree that editors shouldnt see it but it can be very useful for doing stuff which is just not possible with e.g. content element "text" and its RTE

Actions

Copy link

Updated by Kai Ole Hartwig almost 13 years ago

You really mean the TypoScript-Object HTML? IMO this do completely the same like "TEXT"!

Georg Ringer wrote:

sorry but this element really needs to stay. I agree that editors shouldnt see it but it can be very useful for doing stuff which is just not possible with e.g. content element "text" and its RTE

Actions

Copy link