Adam,

 

You mentioned that the main reason for the typing delay is because CE is cleaning the HTML code as the user types.

 

Why not consider this another way: Provide an option to use CE strictly as a text editor and when this option is set true, don't do any such cleaning or other actions on keydown that might delay the typing from appearing. For example, call it UseAsTextEditor. 

 

I assume that some of your customers buy CE so that their users can develop web pages, but I would suspect most of us buy it to use as a sophisticated text editor (at least that's why we bought it).

 

In the last couple days, we have tried several of the competitive products and they don't have typing delays in either IE or FF, and all of them also have an HTML mode, so they must be doing less than CE is doing. Maybe if CE's new property - UseAsTextEditor - is set true, CE would only do the minimum on keydown, so that there would be no typing delays.

 

We want to continue with CE because it is a superior product in many, many ways, but we have to resolve this issue in order to move ahead.

 

FredD

FredD,

 

We've changed the logic of cleaning HTML code on keydown.

Try this example again:

 

 

Keep me posted

 

 

Firefox: unfortunately, it's a bit worse than before. Instead of using the 1000 repeated lines, we tested with a 20 page cleaned Word doc that has several tables and image placeholders and formatting requirements:

 

We experienced many problems:

 

1. Scrolling delayed when using the mouse and scroll bar.

2. Focus not appearing for several seconds after clicking into the body.

3. Typing delays of 5 or more seconds quite frequently.

4. On some occassions, inability to click into the body after scrolling to the top or bottom - delays of more than 20 seconds before we could click into the content.

5. Click and type in the middle of the content produces:

 

   a. Delay before the cursor appears.

   b. Continual typing delays for several words, then no delays for a couple of sentences, then long delays again.

 

 

 

 

fredd,

You were right - clearing the cache totally changed the situation.  In a large (20+ pages) Word-based doc with image placeholders, lots of ordered and unordered lists, along with tables and font changes, there still is timing that kicks in and performs a background operation, but it's brief and, IMO, acceptable under the circumstances.

 

This can occur during typing or during scrolling. When typing and the background op kicks in (a few seconds only), my typing goes into a cache. When the background op is finished, my typing neatly displays and I can continue.

 

5 and 10 page docs don't exhibit any significant bg operations.

 

I think you've done a great job for us here, Adam. IE is perfect and FF is almost perfect.

 

I'll work with it over the weekend and report back with any problems.

 

Thanks, Adam, for looking into this serious problem and finding a solution for all of us. It will sure make our users happy.

 

FredD