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
{{ message }}
This repository has been archived by the owner on Nov 22, 2021. It is now read-only.
The problem seems to occur when either a, m or p is searched. I don't know why exactly this is happening, but I think it comes from an encodeHMTL call in the wrong place.
I'm encountering a weird escaping problem while using ngTagsInput 2.0.1 (with autocompletion enabled).
In the array I pass when I resolve the promise, one entry causes an issue:
The problem seems to occur when either
a
,m
orp
is searched. I don't know why exactly this is happening, but I think it comes from anencodeHMTL
call in the wrong place.Screenshots:
The text was updated successfully, but these errors were encountered: