User tests: Successful: Unsuccessful:
Pull Request for Issue #33210 .
~~Actually, yes! The PR #19789 from 2018 introduced the property
realName which basically is the untranslated string for the button and this is a B/C break and although buttons without it should still work the J4 implementation of the buttons should dictate for it for a11y and also to ensure proper functionality of the multiple instances of a browser. ~~
Rework the code so it should be B/C although J4 XTD Buttons should have a property
name and another
icon to ensure there won't be accidental conflicts
NPM Resource Changed
|Status||Pending||⇒||Ready to Commit|
@dgrammatiko Is the "Documentation Changes Required" still up to date, i.e. it needs documentation changes? Or has that become obsolete after your recent changes? I ask because if it needs documentation changes, I have to set the corresponding label before merging, so it later won't be forgotten.
Or has that become obsolete after your recent changes?
It should be B/C unless I got totally wrong. Let me explain: I introduce here a new property
icon but the fallback is the property name (as it was before):
$icon = ($button->get('icon')) ? $button->get('icon') : $button->get('name');
That said, it should be communicated that ALL the J4 xtd-button SHOULD use these properties not only for the error reported with the debug language strings but mainly because the button MIGHT NOT work as expected when there are multiple instances of editors in a page (eg using custom fields)
So does it need doc changes or not? That's still not clear to me. A simple "yes" or "no" is sufficient for me, any answer will not block RTC.
So does it need doc changes or not?
Yes, If https://docs.joomla.org/Special:MyLanguage/Editors_form_field_type this is all the docs about the editor field someone should totally rewrite that and include also the xtd-buttons and the expected properties for the button.
|Status||Ready to Commit||⇒||Fixed in Code Base|
|Closed_Date||0000-00-00 00:00:00||⇒||2021-04-22 17:00:49|