Question

Spun off from BrowserIssues.

Mozilla 0.9.1 (and probably all earlier versions) objects to non-standard HTML markup such as <foo>.

• One TWiki version (Dec 2000, can someone confirm this?) fixed Mozilla's objection to <nop> in the HTML it sees, by removing the <nop> tag from the rendered HTML. However, TWiki users can still put in random markup such as <oog>, which has the same effect as <nop> on most browsers, but upsets Mozilla - the symptom is that markup such as <code> may be continued to the end of the page if includes a non-standard markup element. See RenameTheMainWeb for an example - the first <nop> was an <oog> which messed up formatting in Mozilla but not IE5.
• With Mozilla 0.9.1 and the TWiki March 2001 beta, there is still a problem with syntax such as =bug<nop>:1234= (used with a DefaultPlugin extension): the <nop> causes the '=' formatting to carry on until the end of the bulleted item (actually to the </ul> below). The workaround is to use <b></b> instead of <nop>. This does not happen with IE5, which perhaps is more tolerant in what it accepts. The HTML generated was as follows (edited down a bit):

<p> <ul>
<li> ... just type <code>bug<nop>:7917</code> to link to ...
<ul>
<li> Documented in <a href="/bin/view/OTS/WikiEditing">WikiEditing</a> - .....
</ul>

I guess the question is whether this is a bug or not - I think that anything that generates <nop> in HTML output is a bug, and Mozilla is just being kind enough to pick this up for us

• TWiki version: TWiki 15 March 2001 Beta
• Web server: Apache 1.3.12
• Server OS: Red Hat Linux 6.2

-- RichardDonkin - 11 Jun 2001

Answer

Every <nop> tag should be filtered out by the TWiki scripts, it is a bug if not. I could not find the example you mention. Where is it?

-- PeterThoeny - 11 Jun 2001

The first example was in RenameTheMainWeb, but I edited out the problem by changing <oog> to <nop>. You can find it in HTML generated by preceding version.

The second example was on our intranet TWiki but can be recreated quite easily I think. Just enter =bug<nop>:1234= on a test page, e.g. bug:1234 - and check with Mozilla. (The NOP should be visible in the HTML here, and this text should render as fixed-width in Mozilla.)

(Note: the above test doesn't seem to show the bug on this TWiki, but it did in March beta.)

-- RichardDonkin - 12 Jun 2001