Version: 6.0

Our usage of the CuteEditor is as follows:

 

1) An underlying page has the html to be edited.
2) The CuteEditor is launched in a new browser window.
3) The new browser window calls javascript on the opening page to retrieve and populate the CuteEditor control (document.all.Editor1.value = "the html retrieved from the underlying page".
4) When editing is complete and the user closes the CuteEditor window, javascript writes the contents to the opening page.

 

 

 

Our problem is as follows:

The editor removes colors from inline styles.

Example:
1) The following html is entered into the CuteEditor:
 <p style="color: #800000">This is a test.</p>

3) The CuteEditor is reopened to edit this text and the following html is present:
 <p>This is a test.</p>

Notice the removal of the style tag.

 

I have verified that at step 3 in the example, the correct html is being set in the CuteEditor. It appears that the CuteEditor initialization that takes place when IE_Loader is executed is removing the style tag. I have also found that certain colors do not trigger the behaviour. For example, named colors (i.e. red) or various rgb values (i.e. c0c0c0) are unaffected.

Please let me know what we can do to prevent CuteEditor from removing certain colors from inline styles.

 

 

vc3_richard,

Adam,

 

I downloaded 6.1 and see the same behaviour.

 

A seemingly related symptom, we have also found that if there is a color set in a font tag, that for certain colors, each time the html is opened in the editor, one of the characters in the rgb string will be removed. This continues until there are only two charcters left in the rgb string at which point, the truncation will stop.

 

For example,

Initial text: <font color="#0000ff">Test</font>

Editor pass #1: <font color="#000ff">Test</font>

Editor pass #2: <font color="#00ff">Test</font>

Edtior pass #3: <font color="#0ff">Test</font>

Editor pass #9: <font color="#ff">Test</font>

 

Let me know what you think.

 

Thanks,

Richard

Our site is not accessible to you.

 

However, I have resolved the problem with a workaround. The populating code has been changed to allow the IE_Loader script to complete before placing the html from the underlying page into the CuteEditor control. This seems to have resolved the issue.

 

Thanks,

Richard