New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TagField with TypeAhead and HideSelected breaks when selecting tag from dropdown #1581

fabriciomurta opened this Issue Mar 20, 2018 · 1 comment


None yet
1 participant

fabriciomurta commented Mar 20, 2018

Found: 4.5.1
Ext.NET forum thread: TagField: addTags/addItems Error occurs

If a TagField is used with both TypeAhead="True" and HideSelected="True", then it will throw an exception while hovering the mouse over available entries thru the dropdown.

This happens because the component's createFilterFn() is not defined and no check is made against it during

Test case (user didn't provide one on forum thread):

<%@ Page Language="C#" %>

<script runat="server">
    protected void SubmitHandler(object sender, DirectEventArgs e)

<!DOCTYPE html>

<head runat="server">
    <title>TagField v4 - Ext.NET Examples</title>
    <form runat="server">
        <ext:ResourceManager runat="server" />
        <ext:TagField runat="server" ID="TFRecipient" TypeAhead="true" HideSelected="true" FieldLabel="An" Width="650" AllowBlank="false" Padding="5" IndicatorIcon="Help" IndicatorTip="Mehrere E-Mail-Empfänger durch Komma oder Leerzeichen getrennt eingeben">
                <ext:Tag Value="2" Text="George (" />

This probably isn't a Sencha issue as the TagField is a component exclusive to Ext.NET.

@fabriciomurta fabriciomurta added this to the 4.x milestone Mar 20, 2018

@fabriciomurta fabriciomurta self-assigned this Jun 14, 2018

@fabriciomurta fabriciomurta added the 4.x label Jun 15, 2018

@fabriciomurta fabriciomurta modified the milestones: 4.x, 4.6.0 Jun 15, 2018


This comment has been minimized.


fabriciomurta commented Jun 15, 2018

Fixed in a big overhaul with the TagField, improving several aspects of it that were annoying! The fix will be available next Ext.NET release -- see milestone bound to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment