[Seaside] Anchor seems confused

Jim Benson jb@speed.net
Thu, 6 Jun 2002 00:59:45 -0700


Avi,

Ah, it's the carriage return after the </img> and before the </a> that
causes the problem.

I had the prettify flag turned on in the Sexpr parser, when I turned it back
off it works correctly.

Treating the carriage return like that might just be an IE bug.

Jim



----- Original Message -----
From: "Avi Bryant" <avi@beta4.com>
To: "Jim Benson" <jb@speed.net>
Sent: Thursday, June 06, 2002 12:48 AM
Subject: Re: [Seaside] Anchor seems confused


> On Thu, 6 Jun 2002, Jim Benson wrote:
>
> > Avi,
> >
> > I've attached the generating class, and the HTML.
> >
> > It's hard coded to serve out of  'c:\RendevousWork'. I haven't gotten
far
> > enough along to give relative URLs yet :-)
> >
> > It only happens when you have two anchors together.
>
> Well, I don't see the effect (using Mozilla) - have you tried on anything
> other than Explorer?
>
> There aren't any spaces around the </a>.  There is a </img> tag, which
> could be confusing things, since <img> isn't usually closed.  This is an
> artifact of the s-expr parser, which doesn't know about unclosed tags
> (what it produces is more XML than HTML, I guess).
>
> Just to test this theory, you could try replacing the (img ...) with a
> '<img ...>' string?  I've done this before with '<br>' for similar reasons
> (maybe it's time to make that s-expr parser smarter).
>