[Seaside] HTML Encoding change -- why?
jacaetevha at gmail.com
Tue Feb 14 19:01:32 UTC 2006
If you want to write your own HTML you should send the #html: message.
On 2/14/06, Nevin Pratt <nevin at bountifulbaby.com> wrote:
> In Seaside 2.3, I developed a rather sloppy habit of occasionally typing
> html directly in the #text: or #bold: argument. Here is an example:
> html text: '<br>This is an example'.
> rather than
> html break.
> html text: 'This is an example'.
> Sometimes as I typed, the html would just kind of roll off my fingers,
> and I would take the above shortcut rather than typing separate lines.
> But, in Seaside 2.5, this no longer works. Instead, a text argument
> like the above will be transformed into:
> '<br>This is an example'
> Which isn't what I expected. If I had wanted '<' and '>', I would
> have typed it.
> Well, I guess I can see value in the automatic transformation, but I can
> also see value in *not* transforming it.
> Is there a thread somewhere that talks about the pros and cons of making
> this change? What was the rationale for making the change?
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
"Where there is no vision, the people perish..."
More information about the Seaside