You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the overall feedback we often need more characters than the currently allowed 255. We would like to replace the text field with the HTML editor to make it easier for the authors to create appropriate feedback.
UX:
The other feedback fields use the HTML editor, only for the overall feedback a simple text field is used, see gif below. It would be more consistent to use the HTML editor there as well. In addition, the authors have more opportunities to provide meaningful feedback.
Accessibility:
Not relevant
Technical solution:
For the implementation I plan to add the HTML widget to the semantic.json and update the minor version.
The text was updated successfully, but these errors were encountered:
@chhch , did you ever get this working? I made the edit in my semantics.json file in the drupal/sites/all/files/h5p/libraries/multchoice folder, but its not picking up the changes, not sure if there are any other caches i'm missing.
Hi @bartonmike, I think I had made a copy of the h5p-multi-choice element for testing. I named it something like h5p-multi-choice-html-widget and made the additional changes there. I used Drupal 7 in developer mode.
I believe changes in drupal/sites/all/files/h5p/libraries/multchoice would be overwritten the next time the H5P element was updated.
User story:
For the overall feedback we often need more characters than the currently allowed 255. We would like to replace the text field with the HTML editor to make it easier for the authors to create appropriate feedback.
UX:
The other feedback fields use the HTML editor, only for the overall feedback a simple text field is used, see gif below. It would be more consistent to use the HTML editor there as well. In addition, the authors have more opportunities to provide meaningful feedback.
Accessibility:
Not relevant
Technical solution:
For the implementation I plan to add the HTML widget to the semantic.json and update the minor version.
The text was updated successfully, but these errors were encountered: