Project

General

Profile

Actions

Bug #70183

closed

CSH doesn't show on Backend User Settings fields

Added by Patrick Schriner over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2015-09-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

The headlines are "clickable" but will only lead to focus switching to the respective field (and checking / unchecking that field if is a checkbox)

Tested in IE 10 and Chrome 45


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #74333: Help texts in Backend User Settings do not appearClosedGianluigi Martino2016-03-05

Actions
Actions #1

Updated by Wouter Wolters over 8 years ago

  • Status changed from New to Needs Feedback

Can you retest this on current master?
It works here in FireFox.

Actions #2

Updated by Riccardo De Contardi over 8 years ago

I made a test with 7.6 (current master) and Chrome 46 on Mac

1) the CSH of the Backend User Settings works, except for these fields (I mean, it is absent):

- Avatar
- Current password
- Display debug messages in a new browser window

2) there is an annoying behavior: when you click on the title to show the CSH, it is shown, but the related field gains the focus, and the CSH for that field does not work anymore.
sometimes even the CSH of other fields cease to work.
I think it would then be better to show it on hover, maybe with a delay.

Actions #3

Updated by Patrick Schriner over 8 years ago

just tested on current master:

Doesn't work in Chrome or IE 11 for me. The ? is shown in some places, but neither hovering nor clicking will show the associated text.

In Chrome it doesn't work at all
In IE 11 double clicking will show the CSH (but trigger a click on the associated input field as well) (until "broken", where nothing opens)

Actions #4

Updated by Alexander Opitz over 8 years ago

Did you upgraded or installed a new environment? It sounds a bit like caching issues.

Actions #5

Updated by Alexander Opitz about 8 years ago

  • Status changed from Needs Feedback to Closed

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

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 #6

Updated by Patrick Schriner about 8 years ago

I'll take a look again on monday - as it was "master" it's an "ever-upgrading" environment.

Actions

Also available in: Atom PDF