I think it's fairly obvious what the problem is:  There's an xml end-of-comment marker in the comments just before that lisp code, which is being taken into account even though it looks like this '--\>' .  Perhaps we need a double-backslash now ;-)


PS FWIW, the w3c validator says:

  1. Line 202, Column 14: invalid comment declaration: found character "\" outside comment but inside comment declaration.
    		; e.g. as --


    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

On Nov 6, 2007 5:37 AM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
Adrian Aichner writes:
 > "Stephen J. Turnbull" <stephen@xemacs.org> writes:
 > > QUERY
 > >
 > > The Lisp code that formats the new entry is showing through in my
 > > browser.  It's recent firefox, so we probably should do something
 > > about it. ;-)
 > Uh, oh, I was hoping this was a local issue for me.
 > It goes away in a reload for me in Firefox

On the Mac it *does not* go away with a reload.

I don't have time to work on it further today (that's why I so rudely
just dumped it on you, besides thinking that maybe you might have made
a typo you could find easily).

The page still works, so there's no huge hurry here.

XEmacs-Patches mailing list