Hello and Thank you for this project!

I'm using jQuery-Tags-Input with jQuery 2.1.3 and I'm getting this error when hitting ,:

Uncaught TypeError: Cannot use 'in' operator to search for '0' in ,

It references this:

//Line 367
$.each(event.data.delimiter ,function(index, value){
    if(event.which == value.charCodeAt(0)){
        flag = true;
    }
});

Hey XOXCO,

I noticed that no one has committed to this project since 2013. Would there be any interest in transferring the repository over or be added as a collaborator? I would love to take care of some of the open issues and continue to add features to the plugin.

Best!

Can't locate why this is happening, but the little "x" and the anchor tag to manage delete of tags does not show up. Any clues as to where this is set?

1. minChars
2. maxChars Also fixed a bug (I hope so it was one) when using autocomplete, on pressing enter two tags were added: 1st : what we typed 2hnd : what autocomplete returned.

After a jquery append if I want to assign tagInput again to newly apended fields, it seems tagInput reassigns to old hidden fields also. So it creates multiple tag input fields for previous ones. For example check this fiddle http://jsfiddle.net/aRBkV/

What to do in this situation?

Hello,

When I set property autocomplete_url and put some text and lose focus the tag is not added. Without property autocomplete_url works correctly.

My code: $('#tags_3').tagsInput({ width: '99%', height: '23px', autocomplete_url: 'TagHandler.json', defaultText: 'Add one tag', minChars: 3 });

Thanks

Hi, we have a few which make use of tagsinput on our page. When there is a tag removed we fire a javascript function.

It seems that if there are multiple tagsinput inputs on the page, tags are only removed from the last input. The javascript function always seems to fire, but the tag remains in all but the final input.

Anyone else noticed this?

i've the following array:

[
    {'id':1,'name':'John'},
    {'id':2,'name':'Drew'},
    {'id':3,'name':'Alex'},
];

i need to get the names as suggestions and store them as objects in the input field so that i can later retrieve them by id. how can i do this?

jQuery-Tags-Input seems to break with jQuery 1.7.2 (it's fine on 1.7.1).

Specifically, clicking to add a tag raises the following error in the console:

Error: Syntax error, unrecognised expression: #[object Object]_addTag

And clicking to remove a tag raises the following:

Error: Syntax error, unrecognised expression: #[object Object]_tagsinput

I can't for the life of me, figure out how to get the autocomplete to work.

I use the example code as provided and no ajax request is fired (checked with firebug).

Any help would be appreciated.

Code used:

$('#content form input.tag-interface').tagsInput({
    autocomplete_url: APP_PATH + '/tags.json',
});

I am trying to use this plugin with angular but having few issues. I have created a directive to use it, but when changing the view, id on the input seems to be append with time like "tags1431552377968_tagsinput". Is there a reason for this and how can I avoid it??

I observed that jQuery-Tags-Input was not working on Safari for iOS. The following error is thrown:

TypeError: $('#phone').importTags is not a function. (In '$('#phone').importTags('')', '$('#phone').importTags' is undefined)

"phone" is the field when I'm applying them.

The code works flawlessly on Chrome and Firefox for iOS. Also, it works flawlessly on every desktop browser I've tried, including Safari (for Mac), Chrome, and Firefox. The problem was that safari for iOS with the ad block crystal is blocking the jquery.input.tags.js from loading.

Any idea why this is happening? I contacted the team of Crystal App.

Html:

<div class="col-sm-12">
   <div class="input-group m-b tooltip-demo">
      <span class="input-group-btn top-align">
         <a type="button" class="btn btn-letusgo" href=""  data-toggle="tooltip" data-placement="top" title="frontend_make_call" id="phonebutton">frontend_phone</a>
      </span>
      <input type="text" class="tags form-control" id="phone" name="phone">
   </div>
</div>

JS:

function prepareTags() {
    // Email, phone and tags
    $('#phone').importTags(''); // ======> Code fails right here, just when initializing 
    $('#phone').tagsInput(updateMultiFieldForCustomer('phone'))
}

function updateMultiFieldForCustomer(fieldName) {
    return {
        width:'100%',
        height:'auto',
        defaultText:'add ' + fieldName,
        onAddTag: function (tag) { multiFieldAddedTagAction(fieldName, tag) },
        onRemoveTag: function (tag) { multiFieldRemovedTagAction(fieldName, tag) }
    }
}

$(document).ready(function() {
    customerid = $.urlParam("id")
    customerAlias = $.urlParam("alias")
    prepareTags()
}

Message from Web Inspector:

Content blocker prevented frame displaying https://app.thetask.ninja/customer.html?id=xxxxxxxxxxxx from loading a resource from https://app.thetask.ninja/js/plugins/tagsinput/jquery.tagsinput.min.js

Steps to reproduce:

• Install Crystal Ad Block on your iPad
• Open Safari
• Include jQuery-Tags-Input on a website
• Load the page

$(data.fake_input).bind('keypress',无法监听到中文输入时自适应宽度 增加了一段change的监听 $(data.fake_input).bind('input propertychange', function(event) { if (event.data.autosize) { $(event.target).doAutosize(settings) } })

Please, declare the "i" variable, because it's causing error in babel-loader when using the component with webpack 4.0.

https://github.com/xoxco/jQuery-Tags-Input/blob/ae31b175fbfd0a0476822182ef52e76c2629e9c3/src/jquery.tagsinput.js#L354

Hey, guys! I have faced with an issue. When I run composer install/composer update on the first time I see that the version 1.3.2-17 was installed. We work... make test.. and after another "composer update" we saw that the version 1.3.2-17 was updated to 1.3.3. Ok. But the version 1.3.2-17 is pretty full reworked. Сomments in your code told me that this is the version 2.0 and have no compatibility with another versions in some cases. Can you fix it? Can you make another branch for 2.0 version or hide this version(due you do not support your package)? 1.3-* and 1.3.2-17 is not quite the same

When checking if a tag exists there is no "normalization" of the searched tag. Although the tags are trimmed in the function addTag, the searched tag in tagExist is not trimmed. This may cause a problem when adding new tags. I had this problem until I solved it.