Ok, I had a look at owaspantisami, and it's really good. However, some of the regular expressions in the example files are not correct - there are some issues about them in the bug tracker. Also, it may be a little bit too slow, because it uses DOM instead of SAX - there's an issue in the bug tracker though, indicating that this may change in the future.
Owaspantisami or not, the problem of restricting RichTextArea's input generally turns out to be harder than I expected - because every browser creates different HTML, e. g. for bold text: Firefox: <span style="font-weight: bold;">abc</span> IE: <STRONG>abc</STRONG> Chrome: <b>abc</b> This gets especially interesting, when using e. g. Firefox to edit a comment that was created by Chrome. So if you add italic style to <b>abc</b>, the result is: <b style="font-style: italic;">abc</b> etc. Maybe we'd be better off with a widget that provides the same kind of great user interaction as RichTextArea + RichTextToolbar, but creates BBCode, WikiText or something similar in the background, instead of HTML. I don't know, if this is possible, as RichTextArea relies on the browser's execCommand() function... -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
