[Seaside] escaped html
Ragnar Hojland Espinosa
ragnar at linalco.com
Sat Jun 21 01:44:05 CEST 2003
On Fri, Jun 20, 2003 at 08:33:49AM -0700, Julian Fitzell wrote:
> >Is there a reason for seaside not escaping the strings by default, as
> >it happened with seaEscapeHtml in 0.94b? Or am I missing something?
> >
>
> I assume you mean encoded with html entities? If so, there is already
> #encodedText:
Yes, thats what I mean. I didn't see any encodedText:, and a grep on
seaside2.3b2.st doesn't give out anything..
>
> #anchorWithAction:text: and similar don't encode the text because
> otherwise there is no way to give it HTML directly. But if it proves
> that giving text, not html, is the more common case, we may want to
> change it.
Hm.. now I know i shouldnt be posting past 0h with no caffeine in the
system.., but I don't get why would the text: in #nachorWithAction: be
commonly used to write raw HTML. Its something like:
self openAnchorWithAction: anActionBlock. "<a href=..>"
self text: aText.
self close. "</a>"
I do see its usefulness, but I'd say encoding the text would be orders
of magnitude more common. Of course maybe in some other similar
methods it'd be the other way..
--
Ragnar Hojland - Project Manager
Linalco "Especialistas Linux y en Software Libre"
http://www.linalco.com Tel: +34-91-5970074 Fax: +34-91-5970083
More information about the Seaside
mailing list