User tests: Successful: Unsuccessful:
Pull Request for pr #27712.
The accessible media form field doesn't support the class property. This pr fixes it.
testclass
joomla-field-media
element of the custom field in the dev tools of the browserNo testclass
is added to the element.
testclass
is added to the element.
Status | New | ⇒ | Pending |
Category | ⇒ | Layout Libraries |
Labels |
Added:
?
|
I have tested this item
I have tested this item
Tested successfully.
Status | Pending | ⇒ | Ready to Commit |
RTC
Labels |
Added:
?
|
This looks kinda weird because the class is already being set on the input element within the custom form field. Does it really make sense to have it in both places?
Did you actually test it? The class is not set, as it is not passed into the subform group. It is not rendered at all in any of the elements.
Yes I understand that the FormField layout is clearly correct. I'm asking specifically about the JLayout change as the class is also used here https://github.com/joomla/joomla-cms/pull/36593/files#diff-ffc48fe23d772f6461955e77801148ec01945822ae6574126b6cece7f7bccd26R54 and you're now adding it again on the custom element.
The class is only added to the custom element and nowhere else. The class is delegated to the element from the Formfield but never used there as you can see here https://github.com/joomla/joomla-cms/blob/4.1-dev/layouts/joomla/form/field/media/accessiblemedia.php. So where should then the class being used in your opinion?
Labels |
Added:
?
Removed: ? |
Title |
|
Status | Ready to Commit | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-02-23 05:00:14 |
Closed_By | ⇒ | laoneo |
Made another test and indeed you are right, the class is used on the input. So it would be wrong to render it two times.
@astridx can you have a look here if all is correct?