2 Answers, 1 is accepted
0
Hello Martijn,
You can check the content that is sent to the server by toggling between Design and Html mode of the editor. If you do this you will see that the <noscript> preserves. Unfortunately the described behavior is another problem caused by the MOSS content filter. When you submit the page, MOSS will validate it and automatically make changes if the content is not valid. You can verify this by trying to enter the same content with the original SharePoint rich text editor.
We have not been able to find a workaround for this behavior yet.
Sincerely yours,
Stanimir
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
You can check the content that is sent to the server by toggling between Design and Html mode of the editor. If you do this you will see that the <noscript> preserves. Unfortunately the described behavior is another problem caused by the MOSS content filter. When you submit the page, MOSS will validate it and automatically make changes if the content is not valid. You can verify this by trying to enter the same content with the original SharePoint rich text editor.
We have not been able to find a workaround for this behavior yet.
Sincerely yours,
Stanimir
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Martijn
Top achievements
Rank 1
Rank 1
answered on 26 Jul 2010, 02:46 PM
thanx for the answer.
I think we have found a temporarily solution to the problem.
We're gonna use the MOSS content query webpart and add our script. It doesn't seem to strip the <noscript> tag, so I think this will help us out.
For the other content we still use the telerik editor of course ;-)
I think we have found a temporarily solution to the problem.
We're gonna use the MOSS content query webpart and add our script. It doesn't seem to strip the <noscript> tag, so I think this will help us out.
For the other content we still use the telerik editor of course ;-)