Hello,
I've just tried out the Prometeus version of Editor and have issues with embedded css resources. It applies to both Default and Vista skin.
The main problem is that you don't have specific class names/id's for editor styles, like UL,LI, etc tags.
We use css styles for all UL,LI elements in all websites we build. We have styles for margins, padding, liststyles etc. that are used in content pages globaly.
When RadEditor is used all ul/li elements in editor interface are affected and they look, well, crappy.
After disabling our ul/li styles it looks good in IE6, but still looks bad in Firefox. In Opera it looks OK, but width is wider than it should be (radedit is set to 100% width and that breaks the box model).
I suppose I'm not the only one with this problem...
Can't You make all elements in prometheus control specific with classes and id's so they don't break allready defined interface elements?
Good start is setting class="radedit" on all ul,li,table, etc. elements in skin files.
I've got screendumps for all tested browsers, too bad I can't upload those files with post here. Let me know if I can mail it over to someone if needed.
I've just tried out the Prometeus version of Editor and have issues with embedded css resources. It applies to both Default and Vista skin.
The main problem is that you don't have specific class names/id's for editor styles, like UL,LI, etc tags.
We use css styles for all UL,LI elements in all websites we build. We have styles for margins, padding, liststyles etc. that are used in content pages globaly.
When RadEditor is used all ul/li elements in editor interface are affected and they look, well, crappy.
After disabling our ul/li styles it looks good in IE6, but still looks bad in Firefox. In Opera it looks OK, but width is wider than it should be (radedit is set to 100% width and that breaks the box model).
I suppose I'm not the only one with this problem...
Can't You make all elements in prometheus control specific with classes and id's so they don't break allready defined interface elements?
Good start is setting class="radedit" on all ul,li,table, etc. elements in skin files.
I've got screendumps for all tested browsers, too bad I can't upload those files with post here. Let me know if I can mail it over to someone if needed.