Hi Adam, if you need any input or have any questions regarding that, let me know, my brother Huw is one of the authors. it's pretty straight forward to work with though, I've just integrated it with the Community Starter Kit.

Hi Adam, yes, that's fixed it. Thanks v much.

 Endys wrote:Thanks a lot for this idea... problem is in CSS .... something for developers of the great CuteEditor.   No worries

Hi Adam I came across this in my logs today too and have some further input. The 404s occur if you close the browser while on a page with the editor in it (and only then). It also only happens with Internet Explorer and not with Firefox. I spent a small amount of time trying to track it down and confirmed that the request for null appears to ...

Hi Adam, is the oncarriagereturn example using the latest build? Still seems to be giving the same result as before. Here's a series of snapshots to illustrate what I'm getting: Break element is set to Br and a paragraph style of heading 2 is applied to the first of the three lines. also notice that lines two and three have been inset by one ...

Hi Endys, is it possible that there's something in your style sheet that's causing this? What happens if you link to an empty style sheet (no style definitions) in the master page? I'm using master pages with style sheets and it seems to be working fine withe CuteEditor.

Hi Adam, I get the same behaviour using Br as the break element. If you go to the oncarriagereturn example you posted and set the break element to Br, then type: line 1 <carriage return> line 2 <carriage return> line 3 etc, then select line one and apply  a paragraph setting, eg Heading1, then all lines are converted, ...