Autocompleter UI component "ch" silently fails with more than a single character

[martyf]

When using the Autocompleter in a plugin, the docs require a trigger character ("ch") - and one would assume this to be a single character.

If you utilise the Autocompleter and provide a "ch" of more than 1 character, the Autocompleter fails to trigger - but does not report any errors - it simply never is able to be triggered.

Which is fine requiring a single trigger character - but given how tight the other error handling within v5 is, on instantiation of the plugin, would it (could it?) make sense to actually throw an error to the console to inform of the invalid "ch" string. The docs request "ch" be of type string - which technically could be multiple characters.

[TheSpyder]

We should at least warn in the console, yes. We are looking at supporting multiple characters (turns out : is a different character on some keyboards) but we're likely to do that with an array not multiple characters in one string. I'll make a note to deal with this warning at the same time.

[GitHubish]

It is true that it would be really practical if we could set up several triggers. Today I am using another product that offers this feature but I will be curious to be able to evaluate TinyMCE to replace our current product.

[TheSpyder]

@GitHubish you should be able to register the same autocomplete function multiple times with different triggers, would that cover what you need? This issue is regarding multi-character triggers.

[Mintenker]

I would really appreciate mutli-character triggers. Right now I am working on editor where the function to have autocomplete on writing {{. would be greatly appreciated. Any progress on this?

[ggsrivas]

I have the exact same requirement to trigger autoComplete when {{ is clicked.

[timsquires]

We also need to be able to trigger autocomplete on a multi-character trigger like {{, it would be great to not be limited to one character for triggering autocompletion.