We seem to be having a slight issue with xhtml.

 

Changing the markup in html view to <p class="someClass">Hello world</p>

 

Then moving back to design view and again to html view, autoformatting seems to occur and this becomes

<p class=someClass>Hello world</p>

which is now not xhtml... (although for capture purposes editor.xhtml does give the correct output, it is confusing the hell out of our content editors who have been told to check for xhtml at all stages)

 

(this behaviour is shown in the http://cutesoft.net/example/xmloutput.aspx online demo)

 

Any pointers?

 

Mike

Mike,

 

To get better XHTML format code, CuteEditior For ASP.NET handles this job on the server side. After you click the submit/save button, CuteEditor will automatically convert <p class=someClass>Hello world</p> to <p class="someClass">Hello world</p>

 

Please check the following example:

Cheers for that Adam.

 

Can you just confirm the process.

 

Is is the case that xhtml loaded from a database into the cuteeditor interface is immediatly refomatted as html4.0, and only when we call the .xhtml property on the server side is it converted back.

 

Or does the autoformat to html4.0 occur when switching between design and html views?

 

In either of the above cases is there a way to show the xhtml markup in the html view?

 

Mike

 

Mike,

 

When load the HTML code, some HTML code will be changed depend on different browser behaviours.

 

>>In either of the above cases is there a way to show the xhtml markup in the html view?

 

In the earlier version, we tried to convert HTML to XHTML in the client side using JavaScript. But we ran into two problems:

 

1. It will take a lot of time when working on a long document.

 

2. The xhtml created is not good as server side XHTML code.

 

So in the current version, the only method to get XHTML code is calling the .xhtml property on the server side.