Support forums » Products » Cute Editor for .NET » Re: Unresponsive script in Firefox

Unresponsive script in Firefox

Last post 01-16-2007, 5:01 PM by stevehaffner. 8 replies.
Sort Posts: Previous Next

  •  01-15-2007, 3:30 PM 25802

    Unresponsive script in Firefox

    Reply Quote
    My application uses CuteEdit on many different pages. Some of these pages use a single instance of CuteEdit, some use two instances, and one of them even uses three instances. I have wrapped my CuteEdit controls inside a DIV with decorations, including an Edit button.
     
    When I load my "three instance page" in Firefox 1.5, and click on my Edit button, an unresponsive script error occurs on PostBack. I should point out that this page works just fine in IE 6.0. Also, the very similar "single instance page" and "two instance page" both work just fine in both browsers.
     
    I am investigating, but before I spend too much time on it, I was wondering if anyone had encountered a similar problem and had any advice.
     

  •  01-15-2007, 5:58 PM 25803 in reply to 25802

    Re: Unresponsive script in Firefox

    Reply Quote
    Which version of Cute Editor are you using?

    Can you reproduce the problems in the following example?
     
     
    This example contains 4 instances.
     
    Keep me posted
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  01-15-2007, 6:12 PM 25804 in reply to 25803

    Re: Unresponsive script in Firefox

    Reply Quote
    Version? CuteEditor_for_Net5
     
    Example? The problem does not reproduce in the Multiple.aspx sample. The sample is very slow in Firefox, but does not show the unresponsive script error.
     
    I am trying to strip away layers of code to find out whether the problem is occurring in CuteEditor or in my application layer. The problem occurs during a WebForm postback owned by a Button control that I have added. It may have nothing to do with CuteEditor. I'll let you know if my opinion changes.
     
    Thanks for the response.

  •  01-16-2007, 1:40 PM 25823 in reply to 25804

    Re: Unresponsive script in Firefox

    Reply Quote
    For what it's worth, I have found that the problem only occurs when I make one of the three CuteEditor controls visible. That doesn't mean the problem lies with CuteEditor, but CE is a required ingredient. I have not been able to repro the problem in a simpler application, just as the problem did not repro in the Multiple.aspx sample.
     
    Has anybody had this unresponsive script problem with Firefox 2.0 or 1.5? I did try running Firefox in Safe Mode, and that did not help. Looks like it's going to be a long day...

  •  01-16-2007, 1:58 PM 25825 in reply to 25823

    Re: Unresponsive script in Firefox

    Reply Quote
    >> have found that the problem only occurs when I make one of the three CuteEditor controls visible.

    How did you do that? Can you create a simple example and put it online?
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  01-16-2007, 2:56 PM 25827 in reply to 25825

    Re: Unresponsive script in Firefox

    Reply Quote
    Too much code to condense down to a simple example. Perhaps that is part of my problem.
     
    I did just try removing all of the control validators from the page, and the problem went away. It could be a problem with Firefox and Validators. I don't know what CuteEditor's Visible state would have to do with anything, though.
     
    Last year there was quite a bit of chit-chat on the boards about new unresponsive script errors that a lot of sites were observing with Firefox. The solution was always to increase the dom.max_script_run_time from 5 to 10 seconds. I tried increasing it to 30, and that didn't help. So I think I am getting into a loop or something.
     
    Anyway, thanks for your interest. If I can find a useful, simple example I'll share it with you and the forum.

  •  01-16-2007, 4:02 PM 25830 in reply to 25827

    Re: Unresponsive script in Firefox

    Reply Quote
    A little more info, still no code to share. Sorry.
     
    CuteEditor is still intruding itself into the mix of circumstances that cause the unresponsive script behavior. I'll explain how.
     
    On my three-CuteEditor page, I have found that removing my CustomValidator controls allows the page to function properly. I don't understand why. Now the mystery deepens, as all good mysteries do.
     
    I have another page that is very similar to my three-CE page, except it has only a single instance of CE. (Both the three-CE and the single-CE pages have input forms with custom validators.) The single-CE page functions fine, even with the CustomValidator, which cuts against some of my earlier discoveries. I thought maybe the problem was having multiple custom validators. On the three-CE page, I removed all but one of the custom validators, but no dice, the unresponsive script recurred. Next, I went back to my single-CE page, and added a second instance of CE, but no additional validators. The unresponsive script recurred. This suggests the necessary ingredients for the failure to be at least one Custom Validator, plus multiple instances of CE (or at least my user control that contains an embedded CE).
     
    So CE has not been totally eliminated as my culprit, tho' it is certainly not my prime suspect.
     
    I do notice many references to __doPostBack in the files cuteeditor_gecko.js.aspx, CuteEditor_Gecko.js.initialize.js, Cuteeditor_safari.js.aspx, and CuteEditor_Safari13.js.aspx. But I don't understand enough of what that code is doing to hazard a guess.
     
    I hope I can condense all this down into a small sample page that repros the problem. I am not at liberty to share the whole thing, unfortunately.

  •  01-16-2007, 4:16 PM 25832 in reply to 25830

    Re: Unresponsive script in Firefox

    Reply Quote
    I got some code. See if you can get the unresponsive error under Firefox 2.0 or 1.5?

     
    <%@ Page Language="C#" %>

    <%@ Register Assembly="CuteEditor" Namespace="CuteEditor" TagPrefix="CE" %>

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

    <script runat="server">

    public void ValidateCheckbox(object source, ServerValidateEventArgs arguments)

    {

    arguments.IsValid = true; // always true

    }

    </script>

    <html xmlns="http://www.w3.org/1999/xhtml" >

    <head runat="server">

    <title>Untitled Page</title>

    </head>

    <body>

    <form id="form1" runat="server">

    <div>

    <asp:LinkButton ID="LinkButton1" runat="server">Click To Test For Bug</asp:LinkButton>

    First of Two Instances of Cute Editor

    <br />

    <CE:Editor ID="Editor1" runat="server" Text="Contents should not matter" Width=300 Height=300>

    </CE:Editor>

    <br />

    <CE:Editor ID="Editor2" runat="server" Text="Contents should not matter" Width=300 Height=300>

    </CE:Editor>

    <asp:CheckBox ID="CheckBox1" runat="server" Text="A Checkbox To Validate" />

    <asp:CustomValidator ID="MyCustomValidator" runat="server" ErrorMessage="Not really important." OnServerValidate="ValidateCheckbox" Display="None"></asp:CustomValidator>

    </div>

    </form>

    </body>

    </html>

  •  01-16-2007, 5:01 PM 25834 in reply to 25832

    Re: Unresponsive script in Firefox

    Reply Quote
     
     
    PROBLEM SOLVED!
     
    I forgot to put EnableClientScript="False" on the CustomValidators. Apparently, Firefox was trying to do client-side validation by referring to non-existent client-size code, or some such thing.

    Adding the EnableClientScript="False" attribute seems to clear up the problem.
     
    CuteEditor is exonerated!
View as RSS news feed in XML