I have just noticed that when using IE 11, after changing the selection in a WebDropDown, an "X" appears next to the triangle selector thing.
If the user clicks the X, it clears the selected text from the dropdown, but when the page posts back, the value that was selected before clicking the X is still the selected value.
This X does not show up in other versions of IE or in Chrome or Firefox.
Ideally, I would like to know how to suppress the X so that it isn't there, becuase it is allowing user to clear a dropdown that I do not wish them to be able to clear.
Is there a way to disable or hide the X?
Thanks!
John
Hello jmakuch,
Thank you for your reply. Can you please make sure that the cache is cleared to ensure that no old styles are being loaded on the page. In addition to that, it would be helpful inspecting in the IE developer tools whether the style removing the clear X is applied on the dropdown input in this case. A small working sample demonstrating the issues would be greatly appreciated and would allow me to provide you with more specific feedback.
Please do not hesitate to contact me with any updates or questions.
My stylesheet is up to date and contains the section referenced by pellcomp, but the issue is still occurring.
Hello pellcomp,
Thank you for your reply. As you have rightly noted, after upgrading it is necessary to refresh or add anew the styleset as the fix for this issue is in the CSS.
Please do not hesitate to contact me if you need more information.
I have figured out why the upgrade doesn't work for us, and probably others too. Simply upgrading the control DLL and versions using the "upgrade tool" is not enough. You also have to upgrade the style sheets used by your application to the latest version from the app stylist. The following CSS rule has been added to *texteditor.css file:.igte_Edit::-ms-clear, .igte_EditInContainer::-ms-clear{display: none;}
This can, of course, be added manually to your existing files, but there is a good chance other changes are worth getting too.
We too are experiencing this problem with 13.1 and 13.2 builds in IE11.