It will be included on release 1.0.13
gxleano → created an issue.
gxleano → created an issue.
After applying the change, everything looks better.
See:
It will be included on release 1.0.12
It will be included on release 1.2.27
It will be included on release 1.2.27
It will be included on release 1.2.27
Closing this issue because of it has been more than 2 month without activity and it can't be reproduced.
It will be included on release 1.2.27
It will be added to release 1.2.26
Thanks @adamzimmermann @alfthecat to report and work on this.
It will be included in release 1.2.26.
Thanks @bember!
@jovan1348 are you working on this issue?
Should it keeps assigned to you?
Hi @kopeboy
The token which you should use is [term:field_icon:icon], but it will only return the icon name, so in order to have the svg icon you should install a submodule (tagify_iconify_icons) which will be provided on this issue.
It will be included on release 1.2.25
It will be included on release 1.2.25
The Iconify Icons → module already includes integration with UI Icons, allowing it to be used as a provider by installing the Iconify Icons Provider submodule.
It will be included in release 1.0.10
BTW @shyam-sawhney, thanks for you comment in #7 💬 Span tags showing for Tagify User List Active it was very helpful to reproduce the issue.
Have you had a chance to test the solution?
In the meantime, I've implemented a temporary workaround to address the issue with the Select widget, as it currently does not function correctly when both limited and required.
You can find a brief demo here:
I've added a method to check if the label contains HTML, so if the label contains HTML it will be striped.
This is mostly happening when a custom Entity Reference Selection Plugin is used as reference method.
gxleano → changed the visibility of the branch 3477875-label-showing-html to active.
gxleano → changed the visibility of the branch 3477875-label-showing-html to hidden.
gxleano → changed the visibility of the branch 3477875-span-tags-showing-html to hidden.
Thanks @sunlix to report and fix the issue.
Moving to RTBC and Fix, it will be part of the next release 1.2.24
Hi @w01f!
I've been testing in a default set up (Drupal latest stable version and Tagify latest version) and I was not able to reproduce this problem.
See:
It will be included in release 1.2.23
It will be included in release 1.2.22.
When working with HTML custom elements (<tags>), native form validation—including the required attribute—won’t function automatically. The browser’s form validation system is built to work with standard HTML form elements, such as <input>, <textarea>, and <select>. Instead of using a hidden class to conceal the <input> or <select> elements, we can employ a subtle trick to keep the input element present but invisible. This allows us to benefit from the native required validation while maintaining the use of custom elements.