Hi guys,

I know that one of the major fixes done in the las version of CuteEditor (5.3), was the XHTML property. In the previous version in some cases it did not return XHTML Comliant html. There were some posts on the subject I think (including a couple from my colleague Stefan Dobrev). I want to congratulate you with the new release. I solves a lot of XHTML problems we had before.

Unfortunately, it appears that there is still some cases in whitch the editor returns not a valid XHTML. Here is an example that I used to test XHTML compliancy:

 

<div><input value=testInput></div>
<div><textarea>test text</textarea></div>
<div>
<div><input type=checkbox><label for=testBox>test</label></div>
</div>
<div><select>
<option value=1>1</option>
<option value=2 selected>2</option>
<option value=3>3</option>
<option value=4>4</option>
</select> </div>

At first I found the problem in my own application and thought that I'm missing some configuration, but later I tested the same example using the sample editor at: http://cutesoft.net/example/xmloutput.aspx

The result was the same.

I played a bit with the html and found that without the <select> part it all parses ok. E.g. the following html returns a correct XHTML:

 

<div><input value=testInput></div>
<div><textarea>test text</textarea></div>
<div>
<div><input type=checkbox><label for=testBox>test</label></div>
</div>

After adding the following html in the end and submitting the XHTML breaks down:

 

 

 I hope that my explanations of the problem were detailed enough and you will be able to repond me as soon as possible.

 

Also I have another problem with the editor that I explained in another post here:

 

I'll be very greatful if you are able tp give me an update on that also.

 

Thanks for taking time to answer :)

 

Thanks for the nice comments. We are working on improving XHTML support.

 

Please try the following code:

 

<option value=2 selected>2</option>

 

to:

 

<option value=2 selected="selected">2</option>

 

 

 

 

 

Hi Adam,

 

Thanks for the quick answer, I tried what you suggested and it worked fine. As it appears the XHTML is problematic only when there is a single attribute not followed by = and a value (such as CHECKED and selected). Unfortunately, these attributes are automatically added by the editor when a radio button or checkbox that is cheked is added by the user.

It is easy for me to change the html but not that easy for the end user. More over that even if I change to selected="selected the moment I switch from html to normal and then back to html the html is back to selected only.

I tested this with the old version (5.2) and it worked just fine. I suppose that changes made for the current version brought this regression and hope that very soon there will be a solution for it.

 

Thanks again and please keep me posted on the progress ofthis issue.

[email protected],

Please download the latest build (May 24, 2006).

 

Download:

 

http://cutesoft.net/ASP.NET+WYSIWYG+Editor/downloads/default.aspx

Demo:

 

http://cutesoft.net/example/general.aspx