Hello,

I have been looking into your question and the information provided is not sufficient to determine exactly what your scenario is regarding the behavior described. I will need some additional information regarding your scenario. Could you please answer the following questions:

• What drop-down are you using in your grid? Is it igx-combo, igx-simple-combo, igx-select or igx-drop-down? Or are you using another component?
• Are you templating a column to use a dropdown. Which template do you use igxCellEditor or igxCell and how do you template the column that contains your dropdown?
• When you open the dropdown do you scroll to the far right in the grid or when you open the dropdown and select a value you scroll to the far right? What is the exact scenario and how is the described behavior reproduced?
• Could you provide more information, screenshots, code snippets or a sample with steps to reproduce?

This information is going to be highly appreciated and will help me in my further investigation.

However I have created a small sample trying to reproduce the described behavior. I am using igx-grid component with two columns templated with a dropdown component - one column with igx-combo and the other with igx-select. On my side everything works as expected and after entering the edit mode of one of the two columns and opening the drop-down of the component with which the column is edited, after selecting a value and scrolling to the far right of the grid and then returning to the cell from the column, the new value is selected. In the other scenario, I just open the dropdown, don't select anything, just scroll to the far right and come back and the component's dropdown has closed and remains the previous selection as expected. I am testing the sample in latest Ignite UI Angular version.

The described scenario could be observed here:       

Here you will find my sample for your reference. Please test it on your side and let me know how it behaves. If this is not an accurate demonstration of what you are trying to achieve, please feel free to modify it and send it back to me along with steps to reproduce. Alternatively, if the behavior cannot be replicated, please feel free to provide your own sample.

Having a working sample on my side, which I can debug, is going to be very helpful in finding the root cause of this behavior. 

Thank you for your cooperation.  

Regards,

Georgi Anastasov

Entry Level Software Developer

Infragistics

Hi @Georgi Anastasov,

Thanks for your reply. Issue happened due to our code issue, after corrected we fixed it now. Thanks.