Search

You searched for the word(s):
Showing page 1 of 2 (11 total posts) < 1 second(s)
  • Re: Unresponsive script in Firefox

    &nbsp; &nbsp; PROBLEM SOLVED! &nbsp; 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. &nbsp; CuteEditor is ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 16, 2007
  • Re: Unresponsive script in Firefox

    I got some code. See if you can get the unresponsive error under Firefox 2.0 or 1.5? &nbsp; &lt;%@ Page Language=''C#'' %&gt; &lt;%@ Register Assembly=''CuteEditor'' Namespace=''CuteEditor'' TagPrefix=''CE'' %&gt; &lt;!DOCTYPE html PUBLIC ''-//W3C//DTD XHTML 1.0 Transitional//EN'' ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 16, 2007
  • Re: Unresponsive script in Firefox

    A little more info, still no code to share. Sorry. &nbsp; CuteEditor is still intruding itself into the mix of circumstances that cause the unresponsive script behavior. I'll explain how. &nbsp; 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 ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 16, 2007
  • Re: Unresponsive script in Firefox

    Too much code to condense down to a simple example. Perhaps that is part of my problem. &nbsp; 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. &nbsp; Last year ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 16, 2007
  • Re: Unresponsive script in Firefox

    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. &nbsp; Has ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 16, 2007
  • Re: Unresponsive script in Firefox

    Version? CuteEditor_for_Net5 &nbsp; Example? The problem does not reproduce in the Multiple.aspx sample.&nbsp;The sample&nbsp;is very slow in Firefox, but does not show the unresponsive script error. &nbsp; I am trying to strip away layers of code to find out whether the problem is occurring in CuteEditor or in&nbsp;my application layer. The ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 15, 2007
  • Unresponsive script in Firefox

    My application uses CuteEdit on many different pages. Some of these pages use a single instance of CuteEdit, some use two instances, and&nbsp;one of them even uses&nbsp;three instances. I have wrapped my CuteEdit controls inside a DIV with decorations, including an Edit button. &nbsp; When I load&nbsp;my&nbsp;''three instance page''&nbsp;in ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 15, 2007
  • Re: FilesGalleryPath limitation

    Awesome. I had a little glitch in setting the path, but this should do me just fine. Thanks!
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 10, 2007
  • FilesGalleryPath limitation

    As I understand it, the FilesGalleryPath sets the root directory for the Downloadable Files function, as well as root directory of the Link Browser function. In my application, I need those to be different. I want my users to be able to browse to any file in the web tree (wwwroot), but I want to restrict where they can drop downloadable files to ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on January 10, 2007
  • Re: Global or default target= attribute for links

    Thanks, Adam. Your solution works for the case where editors enter&nbsp;links into their content&nbsp;using the CuteEditor link button, which covers the majority of uses in my situation. But I get the same undesired behavior for ''inherited'' HTML that does not have the target attribute set properly. My editors will still have the option of ...
    Posted to Cute Editor for .NET (Forum) by stevehaffner on December 18, 2006
1 2 Next >