Project

General

Profile

Actions

Bug #53594

closed

No placeholder attribute in backend forms

Added by Oliver Hader over 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
Start date:
2013-11-13
Due date:
% Done:

100%

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

Description

The disposal of the placeholder feature in backend forms needs to be enabled using the mode setting "useOrOverridePlaceholder" in TCA. However, the implementation for checking this needs to be inverted, since it returns an empty string if it's enabled, but should be the opposite way instead.

How to reproduce:
  • enter a title for a file in the file backend module
  • create a new content element (text w/image) and assign that file
  • after enabling the override mode, the input field should show the placeholder (using the HTML5 placeholder attribute)

How it should look like (but does not currently):


Files

53594.png (8.59 KB) 53594.png Oliver Hader, 2013-11-13 10:43

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #53573: FormDataTraverser::getFieldValueRecursive() might return NULLClosed2013-11-12

Actions
Actions #1

Updated by Oliver Hader over 10 years ago

Actions #2

Updated by Gerrit Code Review over 10 years ago

  • Status changed from New 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/25365

Actions #3

Updated by Gerrit Code Review over 10 years ago

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

Actions #4

Updated by Gerrit Code Review about 10 years ago

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

Actions #5

Updated by Oliver Hader about 10 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #6

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF