[Seaside] Problem with WAScriptTag content escaping, when nestedinto a WAScriptTag

Boris Popov boris at deepcovelabs.com
Wed Oct 15 23:26:15 UTC 2008

In this case 'element' produces a little scriptaculous helper object and setting its 'id' indicates which actual dom element it should operate on.


DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

Thank you.

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Steve Aldred
Sent: Wednesday, October 15, 2008 4:19 PM
To: Seaside - general discussion
Subject: Re: [Seaside] Problem with WAScriptTag content escaping, when nestedinto a WAScriptTag

Balázs Kósi wrote:
> Hi!
> If you try this example:
> renderContentOn: html
>    html div
>       id: 'x';
>       with: 'foo'.
>    html script: (
>       html element
>          id: 'x';
>          update: [ :r | html script: 'alert(1)' ]

Haven't you given two different entities (div & element) the same id? 
Ids must be unique or browsers do weird things.

seaside mailing list
seaside at lists.squeakfoundation.org

More information about the seaside mailing list