It still doesn't work correctly.  Here's my code:

 <form id="form1" runat="server">
    <div>
      <asp:ScriptManager ID="ScriptManager1" runat="server">
      </asp:ScriptManager>
      <ig:WebDropDown ID="WebDropDown1" runat="server" Width="200px"  TextField="Prod_Code" ValueField="Prod_ID"
        AutoSelectOnMatch="false"  EnableAutoFiltering="Client"
        OnSelectionChanged="WebDropDown1_SelectionChanged"
        DataSourceID="SqlDataSource1">
        <AutoPostBackFlags SelectionChanged="On" ValueChanged="Off" />
      </ig:WebDropDown>
   
      <asp:SqlDataSource ID="SqlDataSource1" runat="server"
        ConnectionString="<%$ ConnectionStrings:TravelerMakerGUIConnectionStringXXXX %>"
        SelectCommand="SELECT [Prod_Code], [Prod_ID] FROM [ProductCodes]">
      </asp:SqlDataSource>
   
    </div>
    </form>


The desired behavior is: A postback should only happen when:
1) an item is selected with the mouse (this works)
2) Only when the <enter> key is hit (not working) - postpacks also happen at other times.

If the list is a bunch of part numbers like:
abc-123
abc-124
abc-125
def-123
def-124

Now, using my code and part numbers from above, select abc-124 with the mouse.  a postback happens - this is correct.

Now, pretend that you made a mistake, and you really wanted one of the def-123 parts.  So, rather than use the mouse, you highlight the abc-123 item, and start typing 'D'.....     A postback happens.   I did not select a full partnumber, I just typed a 'D', and a postback happened.  This postback should not happen, I did not select a part number.   

A postback should only happen if an item is selected with the mouse, or if I hit the <enter> key. 

Thanks, Jim

@jdresser,

I respect your opinion and I would like to keep a proper language in the community. 

Thank you in advance!

Hi all,

I have investigated the issue, and I have asked our engineering staff to examine this further.  To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 108257. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution. I will update you with any new information after the review.

Please let me know if you need more information.

Hello,

since I ran into the same problem but could not try the 12.1 release yet - is this fixed in 12.1?

By the way: Someone mentioned to set AutoSelectOnMatch="false" and first I thought this would solve the problem. But it does only if the WebDropDown has no selection. In this case it works as expected. If it has a selected item it shows the unexpected behaviour again.

Hi bernhardus,

According to the bug, this was verified in a build of 12.1 prior to shipping, so it should be in the RTM.

regards,

David Young

I'm using Version 13.2, and this issue still exists. When I use the down arrow to navigate through the items it causes a postback. In my mind, it should only postback if I hit enter or click an item. Can someone please help me! This is an urgent issue. here is my code:

DropDownContainerHeight="0px"
DropDownContainerMaxHeight="200px"
DropDownContainerWidth="150px"
NullText="-- Select One --"
AutoSelectOnMatch="False"
KeepFocusOnSelection="false"
EnableAutoCompleteFirstMatch="false"
EnableAutoFiltering="Client"
EnableCustomValueSelection="false"
EnableCustomValues="false"
EnableMarkingMatchedText="True"
OnSelectionChanged="ddlSepCode_SelectionChanged">

Hi Lonnie,

Just try this dirty workaround, it did the trick for me:

<script type="text/javascript">

        var keyDown = null;

        function ddl_KeyDown(sender, eventArgs) {

            if (eventArgs._props[0].keyCode != 13)

                keyDown = true;

            else

                keyDown = false;

        }

        function ddl_SelectionChanging(sender, eventArgs) {

            if (keyDown !== null && keyDown)

                eventArgs.set_cancel(true);

        }

  </script>

I’m just left with the issue that a TAB doesn’t trigger selectionchanged-event.