Original text before edit:
<!-- to change the organizational tree, edit 'OrgTree' in the Main web -->
%INCLUDE{"Main.OrgTreeHeader"}%
%RENDERLIST{ theme="org" focus="%WEB%.%TOPIC%" depth="2" }%
%INCLUDE{"Main.OrgTree"}%
Edit with
WysiwygPlugin in FF 1.0 to make text red, resulting in:
<!-- to change the organizational tree, edit 'OrgTree' in the Main web --><SPAN style="color: red;">
%INCLUDE{"Main.OrgTreeHeader"}%
%RENDERLIST{ theme="org" focus="%WEB%.%TOPIC%" depth="2" }%
%INCLUDE{"Main.OrgTree"}%</SPAN>
Edit with
WysiwygPlugin in IE 6.0 on original text, same operation, resulting in:
<!-- to change the organizational tree, edit 'OrgTree' in the Main web --><FONT color="#ff0000">%INCLUDE{"Main.OrgTreeHeader"}% %RENDERLIST{ theme="org" focus="%WEB%.%TOPIC%" depth="2" }% %INCLUDE{"Main.OrgTree"}% </FONT>
Two differences:
- span vs. font tag (no problem)
- Newlines are replaced by spaces (breaks the renderlist)
Also, for XHTML compatibility, tags should be lowercase.
--
PTh
I was actually going to report the same thing today as I see Peter did.
This is actually a very annoying thing. People have twiki variables followed by HTML comments on the next line changed to be on the same line making the twiki variable not work.
Also EDITTABLE and TABLE tags are put on the same line so they do not work as they should. All the same root cause: Wysiwyg stripping new lines away from the topic.
KJL
Sorry about this, but Wysiwyg takes great care
not to strip newlines from topics. However IE is not so careful. I really don't know what I can do about this; asking M$ to fix their browser is unlikely to work
CC
I believe this is fixed now (see
Item4435), but only testing will tell.
CC