I have several different variations (controls on ascx, controls on pages, with and without master pages) of using the WebTextEditor, the numeric editors, and buttons and nothing is responding. The text editors accept focus, but keying into the control produces no text. The read-only is not set.
I even created a simple project just to see if it reproduces, and it does. I created an aspx page, no master page, added a ScriptManager and WebPageStyler. I set the theme to Carribean and EnableAppStyling to True. I drag and drop a WebTextEditor to the page and run the solution. I didn't change any properties at all on the WebTextEditor. The running page doesn't respond to input. Does anyone have any ideas? Thank you.
Hello inputoverload ,
Thank you for reporting this.
I used the latest service release of 10.3 version ( 10.3.20103.2120) and I was not able to reproduce the issue.
Below is the code snippet in the aspx markup:
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
<igmisc:WebPageStyler ID="WebPageStyler1" runat="server" EnableAppStyling="True"
StyleSetName="Caribbean" />
<ig:WebTextEditor ID="WebTextEditor1" runat="server">
</ig:WebTextEditor>
Can you please let us know what browser do you use in order to encounter the behavior?
What is the OS in your environment and what version of IG controls do you use?
Hope hearing from you.
I've been able to gain a little more information on this. It's not just the text editors that come up read only, the web image buttons also come essentially deactivated. And even the highlight effect when you mouse over doesn't happen. They're just dead buttons.
I'm using IE 8 on Windows XP. I've tried with compatability mode on and off. I've rereated the same problem using the latest build of 10.3, as well as 9.1 and 9.2. I've only been running the page from within Visual Studio, but I've tried it with VS 2005 and VS 2010 and it does the same thing. I'm using the .Net runtime 2.0 for all of this, though I tried a test in .Net 4.0 and it did exactly the same thing.
I've found I can post the code to my production server and the pages work correctly. But for some reason on my local machine the simplest pages (e.g just a plain aspx page with a text editor) fail no matter what I do.
So it seems I just need to figure out how and why the javascript is going wrong on my machine, but I don't know what to do or where to look. Any help would be appreciated. Thank you!
Hi,
I also have the same problem. i am not seeing readonly=true in .ascx file. but in view source it is showing readonly = true. i changed in .ascx.cs file to readonly-false. but still not able to edit WebDateTimeEdit control. please reply me...... thanks in advance.
Hi Abhishek,
The readOnly attribute should be removed when javascript are loaded and initialization of editor is run. If application is very large or it uses a lot of resources, then editor may remain not editable until browser loads page. If editor never becomes editable, then it means that application is too large and browser is not able to load all its resources, or there is a javascript exception which prevents running scripts, or editor failed to load its js files or register initialization script.
I have similar issue, though I don't know if there's a similar root cause.
I am using the NetAdvantage for ASP.NET 2011.1 WebTextEditor control - pointed at .NET 2.0. I simply drag the control to the page and am not setting any properties.
When the page renders, the resulting html input control has the following markup:
<input title="{0}" id="WebTextEditor1" readonly="readonly" name="WebTextEditor1" class="igte_Edit" type="text" style="text-align:notset;" />
Note the readonly. There are no javascript problems indicated in the browser. Also note that I don't have this problem when I point to .NET 3.5 or 4.0. Unfortunately I have to use 2.0 for this app.
Also note that I'm seeing similar issues with other controls. Almost as if they are javascript problems...but I don't know.
Any help is appreciated. Frustrating.
I just noticed the title="{0}" in the rendered markup. ?? I get the same thing with other NetAdvantage for ASP.NET 2011.1 controls such as WebDatePicker...which is also readonly whether I specify it or not.
Thanks in advance.
The title={0} comes from default value of ToolTip property. The {0} flag is replaced by current value in editor, so, that allows to dynamically adjust tool tip when value was modified. To disable that feature, application may useeditor.ToolTip=""
Note that what I was doing wrong was adding the controls to the Page rather than to the Form - once I added to the Form I was OK.
I am getting similar behavior as reported here (stuck in read-only, "{0}" as tooltip).
However, this is only for controls I create dynamically like
WebTextEditor t = new WebTextEditor();
t.ReadOnly = false;
t.Value = Value;
t.MaxLength = 20;
Controls.Add(t);
Controls I add to my page using the Designer work just fine.
Is there something special I have to do to get controls created dynamically to function correctly? The documentation for WebTextEditor really doesn't mention it (just "Understanding WebTextEditor", which has a list of features and a bit about the smart tag, and "Using WebTextEditor", which discusses
none of which seem relevant.