Ext.Net.TagField issues on auto-completion and creating custom tags

[fabriciomurta]

Ext.NET's tag field component is not the same as ExtJS. The current Ext.NET implementation had some recent fixes in #1323 and #1324 but still has issues regarding auto-completion according to this forum thread: Incorrect operation of the TagField.

According to the user report, Sencha's version does not have this problem.

[fabriciomurta]

Seems the issues mentioned above fixes only for 4.x.

[DaniilVeriga]

Ext.NET's tag field component is not the same as ExtJS.

Yes, true. The component appeared in Ext.NET before it appeared in ExtJS. Ext.NET TagField has some functionality over ExtJS one and our TagField has been left.

According to the user report, Sencha's version does not have this problem.

Yes, but it has other issues which are not presented in Ext.NET TagField and, again, missing some functionality.

#1324 has been now fixed in v3 as well. The fix is available in the sources right away. It will be included into the next v3 public release if ever.

#1323 is not reproducible with v3, i.e. it doesn't trigger any JavaScript error. But yes, TagField's TypeAhead="true" functionality appears to be broken in v3. It correctly populates the remainder of the text, but it doesn't autoselect it. It is because of .selectText() method which is defined in TextField and doesn't work for TagField. Created a dedicated issue #1334 and fixed already.

As for the issue stated in this forum post, here are my conclusions after investigation

[DaniilVeriga]

I am closing this issue as it looks like all issues have been addressed.