I have just started noticing this after upgrading to version 11.2.20112.2086. Sometimes, when text is being entered into a WebTextEditor, the textbox appears to be in right-to-left mode and text appears in reverse.
Environment - VS 2008 .Net framework 2.5
I would appreciate it if someone could assist with this.
Edit
Environment - VS 2008 .Net framework 3.5
The reason we upgraded to version 11.2 was to get the Load-on-demand working for WebDataTree when there are throusands of tree nodes.
Were you able to resolve this issue with the text reversing? Can we be of any other assistance?
Hi Jason,
We have been able to replicate this consistently in IE 8 after the application moved into exe testing.
Environment - IE 8 and XP (IE 9- cannot replicate this error even after setting to IE 8 standards using developer tools)
Dot Net Framework - 3.5
These are steps that allows to consistently reproduce this issue in the application:
1. Select a node in the treeview to view details of the node in WebTextEditors, WebDatePicker etc controls placed in a WebTab control.
2. Select another node in the treeview to view details. The text editors and date picker controls appear with the cursor at the first character. The text cannot be selected and any text entered appears in reverse.
Switch to another tab or select another item from a dropdown list and the editors appear to be fine.
I would appreciate your assistance in this regard. Let me know if you need any further details.
Thanks!
Hi csggroup,
The steps to reproduce look good. However, it is hard to figure out how to use them if there is no sample.
Please, write a simple as possible sample (aspx file is enough), zip it and attach within Options.
Hi Viktor,
Please find the attached sample. I was able to replicate the issue by running the code in Visual Studio in IE 8 and Windows XP environment. I was using the default styleset. Steps to replicate:
1. Select a node in the tree to view details.
2. Select another node in the tree. Attempt to edit the company name. The cursor in the WebTextEditor behaves incorrectly.
I would appreciate your assistance with this issue. Let me know if you need any further details from my side.
Thank you for a sample. I created IIS web site with those codes, installed Virtual Machine with XP and IE8 and tested that sample.
I indeed was able to reproduce that strange behavior with caret in editor in about 1 attempts from 10-20.
If mouse is clicked outside of editor and then clicked back into editor, then editing works correctly.I noticed that failure happened only, when before start editing, caret jumped at the beginning of text. Click at the end of text or start typing-in sends caret to the very end of text, and it stays there regardless of other mouse clicks of keyboard entries. Entered characters go in front of text.
I tried to replace WebTextEditor by asp:TextBox. It also had strange failure with same probability: field could not be edited at all.
I was not able to find out (debug) why that ocasional failure happened.
The best I can suggest, is to experiment with focus/selection properties of WebTextEditor. For example:
<ig:WebTextEditor FocusOnInitialization="true" SelectionOnFocus="SelectAll" id="uxCompanyNameField" runat="server" width="430px" height="20" />
Hi,
Thank you for report.
There were already few reports related to that.
That happened, because IE11 dropped support for its old (private) selection model, which was used by WebTextEditor. That issue has been fixed by checking for IE11 and using standard selection model (Firefox, Chrome, etc,)
Updates will be available in service releases.
This issue has resurfaced with IE 11. If I set IE 11 to emulate 10 or lower, it works properly. If I set compatibility mode for my domain then the menus no longer display as IE's default compatibility mode is IE 7
Hello Leeny,
for a similar situation we found out that it is a IE focussing problem. A client side 'blur()' on the control in question before focussing the control again helped out.
Were you able to replicate this issue using version 11.2.20112.2086?
Thanks,
Leeny
I can consistently replicate this issue with version 11.2.20112.2086.
Could you please let me know if there anyways to get around with this?