Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with "hidden" field on repititions and enabledControls "hide" enabled #518

Closed
nitori opened this issue Sep 23, 2022 · 1 comment
Closed

Comments

@nitori
Copy link
Contributor

nitori commented Sep 23, 2022

There seems to be a (related TYPO3 Core, a workaround is mentioned there as well) issue with the enabledControls "hide" on repetitions, if the hidden checkbox for the repetition table is configured with invertStateDisplay set to true.

Very simple mask element, just a repetition, with a single random field. No changes to any of the defaults. "hide" is set to true:

2022-09-23_152622

When using in backend and having the repetition opened up, using the top right hide toggle (1), switches the hidden input field (3) to he wrong value. The normal checkbox on the left (2) works as expected. Like said, only happens if invertStateDisplay is set to true for the hidden field of hat table.

image

This is obviously a TYPO3 bug, (as linked above), but it can probably be avoided in Mask by not using invertStateDisplay. Or at least not using it when "hide" enabledControls is set. Maybe doing it like sys_file_reference, by using a hidden palette with the hidden field could work, if the enabledControl is used.

At least until they fix the issue.

Greetings

@nhovratov
Copy link
Collaborator

Related: #514

nhovratov added a commit that referenced this issue Sep 25, 2022
A known TYPO3 bug causes the inline control hidden
toggle to set a wrong state when using
invertStateDisplay for the checkbox. Thus, this
option is removed and the label is changed
accordingly. This fix can be reverted, as soon as
TYPO3 core fixes this bug.

Fixes: #514
Fixes: #518
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants