ngx-chips
ngx-chips copied to clipboard
Error editing tag with custom template
PLEASE MAKE SURE THAT:
- you searched similar issues online (9/10 issues in this repo are solved by googling, so please...do it)
- you provide an online demo I can see without having to replicate your environment
- you help me by debugging your issue, and if you can't, do go on filling out this form
I'm submitting a ... (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
[ ] support request/question
Notice: feature requests will be ignored, submit a PR if you'd like
Current behavior
When using a custom template with [editable]="true" it requires multiple clicks to manage to edit a tag. Two clicks gets you to the edit mode but the cursor dissapears and you need to click again to activate it. You can see in the gif bellow.

Expected behavior
It should require only two click to enter the editable mode and start modifying
Minimal reproduction of the problem with instructions (if applicable)
<tag-input
[(ngModel)]="myModel"
[editable]="true"
>
<ng-template let-item="item" let-index="index">
{{ item.display }}
</ng-template>
</tag-input>
What do you use to build your app?. Please specify the version
ng-cli 6.1.4
Angular version:
6.1.0
ngx-chips version:
1.9.7
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
- Chrome 68.0.3440
Hi, does it only happen with custom templates?
Angular version: 6.1.9 ngx-chips version: 1.9.8
i have the same problem.
@Gbuomprisco Yes, only happens on custom templates. Even if the custom template doesn't have nested tags inside it
<ng-template let-item="item" let-index="index">
{{ item.display }}
</ng-template>
@angular/[email protected] [email protected]
Same problem found when using ng-template and the attribute [editable]="true". Is there any workaround for this?
Having the same problem here. Found out that hitting tab after entering edit mode when using template shifted the focus to the input, but its an ugly workaround.
Any workaround for this issue?
Issue is still there