See the initial details on the bug item 4800:
- http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item4800?rev=2
- http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item4800?rev=3
In revision 2, I've surrounded the whole text with
<noautolink>
...
</noautolink>
to avoid linking of all those module and
Manager names. I *guess that CC has used TMCE to create revision 3, because I could reproduce the behaviour: As visible on TMCE editing, and goint permanent after save, the
<noautolink>
...
</noautolink>
is only applied to the first paragraph, instead of the whole list. For copypasting:
<noautolink>
A paragraph to show that
* NoAutoLink will no longer
* NoAutolink
</noautolink>
when editing with TMCE.
--
TWiki:Main/HaraldJoerg
- 13 Oct 2007
The problem is that the
TML2HTML translator uses a
span
to delimit
noautolink
sections. in this case, that span contains block HTML - P, UL etc. When the browser sees that, it decides to close the span before the first block element. At least, Firefox does, there's no guessing what other browsers do. The same problem is going to affect literal.
Because HTML has no generic contained, the translator need to generate a
div
if there are block-level elements within it. I have no idea how to do that at the moment (context-sensitivities are not the translator's strong point).
Confirmed and raised to Urgent.
--
TWiki:Main.CrawfordCurrie
- 14 Oct 2007
On
Item4831 you gave a clue:
noautolink
is different from
literal
because it is considered "palatable":
- ... we also consider NOAUTOLINK palatable, even though it isn't HTML, because it will be used later in the rendering process to generate a span
Simply removing it from the list has consequences on the UI, but maybe is acceptable: =<noautolink> tags will be shown in WYSIWYG edit, but it is still possible to mark
new noautolink section using the NOAUTOLINK style.
And hey, the translator will even join adjacent noautolink sections!
--
TWiki:Main.HaraldJoerg
- 16 Oct 2007
indeed, and that is exactly the solution I used.
CC