[Mono-docs-list] Differences between generic names in the documentation.

Jonathan Pryor jonpryor at vt.edu
Wed Dec 12 08:01:08 EST 2007

On Wed, 2007-12-12 at 05:57 -0500, Jonathan Pryor wrote:
> On Sat, 2007-12-08 at 12:04 +0100, Valentin Sawadski wrote:
> > But then again it seems that the browser uses the Test<T>
> > everywhere. Sometimes it gets parsed and will be displayed as Test<T>
> > but other times not and some ugly HTML-Entities are being shown as the
> > class name.
> After looking into this further, I *think* this is a GTKHTML rendering
> bug.

Perfect test case:

1. Start Monodoc.
2. Click File -> Lookup URL, or type Ctrl+L.
3. Enter the URL: <a href="foo.bar&lt;T&gt;">foo.bar&lt;T&gt;</a>

It displays as "foo.bar&lt;T&gt;" (i.e. no escaping is occurring), and
if you hold your mouse over the link the target is "foo.bar&lt;T&gt;".

You can in fact change the URL to be:

	<a href="foo.bar<T>">foo.bar&lt;T&gt;</a>

Despite being invalid XML (is it even valid HTML?), GTKHTML displays it,
and shows the desired target when you mouse over it (foo.bar<T>), but it
still shows "foo.bar&lt;T&gt;" as the link text.  I can't find any way
to get "foo.bar<T>" as the link text. :-/

(Not that a href of "foo.bar<T>" helps anyway, as that's invalid XML,
and thus cannot be used within the documentation.)

So it's definitely a GTKHTML bug; no idea how to fix it.  This has also
been reported:


The latter two were opened in November of this year.  The first one also
seems applicable, and was opened in 2006.

Sounds like the actual solution is to get Gecko working again.  Anyone
know why it dies?

 - Jon

More information about the Mono-docs-list mailing list