UI: Use custom HTML elements for the UI Tag Input#11715
Open
lscharmer wants to merge 1 commit into
Open
Conversation
lscharmer
force-pushed
the
11/hotfix/ui-tag-input
branch
from
2edf85d to
e3f8c43
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes Mantis Bugs:
The library
@yaireo/tagifywhich is used for the UI Tag Input uses non existing HTML tags (e.g.<tags>,<tag>). We already replaced these with<div>'s instead but this results in invalid attributes used for our replacement tags (as reported in the Mantis issues above).This PR replaces the
<div>'s with custom HTML elements, so that this won't result in invalid HTML attributes anymore (https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements).