Skip to content
This repository has been archived by the owner on Nov 22, 2021. It is now read-only.

Weird escaping behavior #200

Closed
aymericbeaumet opened this issue Jul 23, 2014 · 6 comments
Closed

Weird escaping behavior #200

aymericbeaumet opened this issue Jul 23, 2014 · 6 comments

Comments

@aymericbeaumet
Copy link

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:

var suggestions = [{
  text: 'Divers & projets spéciaux'
}];

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.

Screenshots:

@mbenford
Copy link
Owner

I fixed a bug somewhat related to that earlier today. Would you mind testing it again with the latest files? You can use this one.

@aymericbeaumet
Copy link
Author

I still encounter the bug with the latest file.

Do you need additional information to help you fix the issue?

@mbenford
Copy link
Owner

Could you provide a Plunker script that reproduces your issue?

@aymericbeaumet
Copy link
Author

Here you go!

@mbenford
Copy link
Owner

Thanks! I've identified the problem already. I'll convert this issue into a bug.

@aymericbeaumet
Copy link
Author

Ok great! 👍

@mbenford mbenford added this to the 2.2.0 milestone Mar 2, 2015
Bessonov pushed a commit to Bessonov/ngTagsInput.ie8 that referenced this issue May 3, 2015
Fix the highlight algorithm in order to take into account HTML entities
and correctly highlight them.

Closes mbenford#200
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants