Petar Ivanov"]After consulting with our developers regarding this matter it was determined that the behavior is most likely related to a development issue (as your requirement should be achievable by only setting EnableCustomValues to false which currently still allows editing through the delete and backspace buttons).  In order to ensure that the matter will receive attention I have logged this behaviors in our internal tracking system with a Development IDs 111865. The next step would be for a developer to research the issues and confirm my findings or offer some resolution.

Dear Petar,

Many thanks for you concern on the issue we are facing, Sure will update if i get any breakthrough.. Again thanks for the support, Good work and keep going Infragistics!!

Hi pavanpuligandla,

Thank you for your reply and apologies for the delayed response.

After consulting with our developers regarding this matter it was determined that the behavior is most likely related to a development issue (as your requirement should be achievable by only setting EnableCustomValues to false which currently still allows editing through the delete and backspace buttons).  In order to ensure that the matter will receive attention I have logged this behaviors in our internal tracking system with a Development IDs 111865. The next step would be for a developer to research the issues and confirm my findings or offer some resolution.

Your support ticket number regarding this matter is CAS-90055-MJ2XF6 . Please feel free to send us any updates in the meantime. You can view the status of the development issue connected to this case by going to the “My IG” tab on our website, hovering to the "My Support Activity" dropdown and selecting the "Development Issues" tab. 

Feel free to contact me if you have any questions.

Hi,

Thanks for the comeback..

This is working fine, But the items which are being selected are now deselected.. I got an idea here like,

after initialization event, we also need to write inputkeydown event like below as an example

function ddlSerLine_InputKeyDown(sender, eventArgs)

{
             var dropdown = $find('<%=ddlSerLine.ClientID %>');
             while (dropdown.get_selectedItems().length > 0)
             {
                 dropdown.get_selectedItems()[0].inactivate();
                 //dropdown.get_selectedItems()[0].unselect();
             }

             //set some default value in the dropdown's input field
             dropdown._elements["Input"].value = "-Please Select-";
         }

     function ddlSerLine_Initialize(sender, eventArgs)
         {
            sender._elements["Input"].readOnly = true;
         }

Once when the dropdown has been initialized, then the input box will be read only, when user tries to press the key then in InputKeyDown event we need to hold the selection, But in the above code, if the items are selected we are deselecting and deactiviting 'em, Instead of that i need to hold the selected values..

I hope you are clear on my issue..

Thanks

Hi pavanpuligandla,

Apologies for the delayed response.

I am unsure of the issue your are describing in your last, however after examining the matter further, in your scenario it may be more convenient to set the input element of the dropdown to be readonly upon  initializing the WebDropDown. This may be done using something similar to:

function WebDropDown1_Initialize(sender, eventArgs)
{
    sender._elements["Input"].readOnly = true;
}

Hope this is helpful.

Hi,

Any solution for this?? I just want to disable the INPUT TEXTBOX so that users can not even click on the textbox, But this hsould happen when DisplayMode is in DropDown not for DropDownList..

Thanks