Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Feature Request: Case Sensitive Option On/Off #8

Closed
mmezzacca opened this Issue Jun 6, 2011 · 9 comments

Comments

Projects
None yet
2 participants

A case in-sensitive option for autocomplete (match existing entries regardless of case). Currently you can have any number of tags that are the same eg. "tennis", "TENNIS" and "Tennis".

Not sure if this was fixed in the latest release but I didn't see it.

Owner

webworka commented Jun 6, 2011

Do you mean for the autocompletion list or for the function that checks if an entry is a new one?

Hmm, I guess for the function that checks if it is a new entry... For example, if "Tennis" is in the auto complete list and already in the current list, if I type "tennis" the autocomplete works by showing "Tennis" but if I hit enter it thinks that "tennis" is a new entry. And so both "Tennis" and "tennis" appear on the list. Does that make sense?

Owner

webworka commented Jun 6, 2011

No, this does not make sense in most cases. I'll add an option for this. Default behaviour should be in-sensitive in my opinion.

@webworka webworka closed this Jun 6, 2011

@webworka webworka reopened this Jun 6, 2011

Ok, thanks. To clarify, currently it operates as case sensitive?

Owner

webworka commented Jun 6, 2011

Yes. That is the reason why you can put "merlin" in the first Input on the example page. "Merlin" does not work, as expected.

So are you saying you should change this default behavior to in-sensitive?

Owner

webworka commented Jun 6, 2011

Yes. in my opinion the in-sensitive behaviour is the one that is mostly needed. Don't you think?

Yes, I agree.

On Mon, Jun 6, 2011 at 6:38 PM, webworka <
reply@reply.github.com>wrote:

Yes. in my opinion the in-sensitive behaviour is the one that is mostly
needed. Don't you think?

Reply to this email directly or view it on GitHub:
#8 (comment)

@webworka webworka added a commit that referenced this issue Jun 8, 2011

@webworka webworka - Extension: Added Support for local data, remote url and function fo…
…r autocomplete. Thanks to garjitec (issue #9 and #7)

- Extension: Added option for breaking characters. Thanks to garjitec (issue #9)
- Extension: Added option for Case Sesnsitive check of new entries. (issue #8)
- Extension: Added support for pasting into input field. Thanks to garjitec (issue #9)
- Bugfix: Items where not marked as deleted when taking to much time for confirmation
- Merge: Cleaned up formatting. Thanks to garjitech (issue #9)
- Merge: Changed the way that autocompleteURL is used to overwrite autocompleteOptions.source. Thanks to garjitec (issue #9)
051e8ab
Owner

webworka commented Jun 8, 2011

Option added in version 1.2.0

@webworka webworka closed this Jun 8, 2011

@garjitech garjitech added a commit to garjitech/Tagedit that referenced this issue Jun 9, 2011

@webworka @garjitech webworka + garjitech - Extension: Added Support for local data, remote url and function fo…
…r autocomplete. Thanks to garjitec (issue #9 and #7)

- Extension: Added option for breaking characters. Thanks to garjitec (issue #9)
- Extension: Added option for Case Sesnsitive check of new entries. (issue #8)
- Extension: Added support for pasting into input field. Thanks to garjitec (issue #9)
- Bugfix: Items where not marked as deleted when taking to much time for confirmation
- Merge: Cleaned up formatting. Thanks to garjitech (issue #9)
- Merge: Changed the way that autocompleteURL is used to overwrite autocompleteOptions.source. Thanks to garjitec (issue #9)
7c567b2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment