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 erratic when more than one entries have the same "value". #1589

Closed
fabriciomurta opened this Issue Jun 15, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@fabriciomurta
Contributor

fabriciomurta commented Jun 15, 2018

In current TagField, if more than one entries have the same value (regardless of the text), the component loads correctly and the tags' adding and removing works erratically.

A simple test case exploring this issue would be:

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

<!DOCTYPE html>

<html>
<head runat="server">
    <title>TagField v4 - Ext.NET Examples</title>
</head>
<body>
    <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="Indicator Tip test.">
            <Tags>
            </Tags>
            <Items>
                <ext:Tag Value="0" Text="George (boc@nog.org)" />
                <ext:Tag Value="0" Text="Sang Lamie (boc-sang@nog.org)" />
                <ext:Tag Value="0" Text="Alhos Hostis (boc-alhos@nog.org)" />
                <ext:Tag Value="0" Text="Guildoval Boturici (boc-guild@nog.org)" />
            </Items>
        </ext:TagField>
    </form>
</body>
</html>

@fabriciomurta fabriciomurta added this to the 4.6.0 milestone Jun 15, 2018

@fabriciomurta fabriciomurta self-assigned this Jun 15, 2018

@fabriciomurta fabriciomurta changed the title from TagField support for handling entries with the same "value". to TagField erratic when more than one entries have the same "value". Jun 15, 2018

@fabriciomurta

This comment has been minimized.

Contributor

fabriciomurta commented Jun 15, 2018

Fixed! The fix will make it to the next Ext.NET release!

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