We're using the Telerik RadEditor as part of a CMS and while this is working nicely on the PC (IE7 & FF3) there are some major issues with the Mac implementation. While I understand there are some differences with the way each of the browsers deals with Rich Text, any help would be much appreciated. On our implementation we've set NewLineBr="false".
A couple of the more frustrating issues we've come across (I believe these can be replicated on the Telerik online demos):
1) If the user enters some text and formats this as a heading1 using the format dropdown (<h1>) they then can't start a new paragraph. Pressing 'enter' creates a new line (or rather inserts the <p>) but this is still encased within the heading tag. The only way around this seems to be to never apply any formatting until you've finished editing the document which isn't really a viable solution.
In addition, placing the cursor at the end of the line and pressing the 'new paragraph' button simply makes the current formatted header block a paragraph rather than creating a new paragraph as expected.
2) Often pressing 'enter' to break text into a new paragraph adds an additional set of <p></p> tags.
3) Highlighting text to apply or remove a class often deletes the text.
I can appreciate that there are differences between the browsers and that all features may not work in all iterations but we really need to allow our clients to do basic formatting without the frustration caused by the above.
I'm afraid I can't link directly to our implementation as this is still in development but as noted above, these should be reproducable on the Telerik Demo's.
Thanks in advance for any help.
Tim
A couple of the more frustrating issues we've come across (I believe these can be replicated on the Telerik online demos):
1) If the user enters some text and formats this as a heading1 using the format dropdown (<h1>) they then can't start a new paragraph. Pressing 'enter' creates a new line (or rather inserts the <p>) but this is still encased within the heading tag. The only way around this seems to be to never apply any formatting until you've finished editing the document which isn't really a viable solution.
In addition, placing the cursor at the end of the line and pressing the 'new paragraph' button simply makes the current formatted header block a paragraph rather than creating a new paragraph as expected.
2) Often pressing 'enter' to break text into a new paragraph adds an additional set of <p></p> tags.
3) Highlighting text to apply or remove a class often deletes the text.
I can appreciate that there are differences between the browsers and that all features may not work in all iterations but we really need to allow our clients to do basic formatting without the frustration caused by the above.
I'm afraid I can't link directly to our implementation as this is still in development but as noted above, these should be reproducable on the Telerik Demo's.
Thanks in advance for any help.
Tim
2 Answers, 1 is accepted
0
Tim
Top achievements
Rank 1
Rank 1
answered on 26 Jun 2008, 04:24 PM
I wanted to add that issue (1) also seems to be affecting both IE7 & FF2 on the PC. I've created a new demo instance of this using the editor simply dropped straight from the toolbox and into a new project and still get the same issue.
I'm sure this used to work however, (although I can't proove this) & as I can replicate the same issue on the Telerik online demo I'm not sure if I just imagined this working. I'm assuming there must be a workaround for this though - as the way it currently stands, once you've entered a heading formatting then it's impossible to add a new paragraph.
I'm sure this used to work however, (although I can't proove this) & as I can replicate the same issue on the Telerik online demo I'm not sure if I just imagined this working. I'm assuming there must be a workaround for this though - as the way it currently stands, once you've entered a heading formatting then it's impossible to add a new paragraph.
0
Hi Tim,
Thank you for reporting these problems.
The default behavior of the Enter command in Mozilla (Gecko) editors is to insert a <br> tag. In order to provide support for paragraph insertion under Firefox we made a custom implementation (NewLineBr="false") which has its limitations because of the different browser problems and behaviors. The observed first and second problems are side effects of our code and it is not an easy task to fix them. Both problems are logged in our ToDo list and if possible we will fix it in one of the future versions of RadEditor.
In the meantime our suggestion is to set NewLineBr="true" which will insert default <br> tags instead of <p> tags.
In regards to the third issue: Unfortunately, I was not able to reproduce it. Is it possible to send a video demonstrating how to replicate this problem on our end along with sample HTML content and steps. Thank you very much in advance.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thank you for reporting these problems.
The default behavior of the Enter command in Mozilla (Gecko) editors is to insert a <br> tag. In order to provide support for paragraph insertion under Firefox we made a custom implementation (NewLineBr="false") which has its limitations because of the different browser problems and behaviors. The observed first and second problems are side effects of our code and it is not an easy task to fix them. Both problems are logged in our ToDo list and if possible we will fix it in one of the future versions of RadEditor.
In the meantime our suggestion is to set NewLineBr="true" which will insert default <br> tags instead of <p> tags.
In regards to the third issue: Unfortunately, I was not able to reproduce it. Is it possible to send a video demonstrating how to replicate this problem on our end along with sample HTML content and steps. Thank you very much in advance.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center