On 11/16/06, Karl Guertin <[EMAIL PROTECTED]> wrote:
>
> This came up when I was doing the MochiKit.Animator demo, but I've
> been putting off because I wanted to do a smaller test case:
>
> <html>
> <head>
> <title>Mochikit Signal Bug Test</title>
> <script type="text/javascript" src="mochikit/MochiKit.js"></script>
> <script type="text/javascript">
> var randomObj = {};
> addLoadEvent(function(){
> connect('bad_example','onclick',
> function(e){signal('bad_example','showvalue',"explicit_value")});
> connect('bad_example','showvalue',window,'alert');
>
> connect('good_example','onclick',
> function(e){signal(randomObj,'showvalue',"explicit_value")});
> connect(randomObj,'showvalue',window,'alert');
> });
> </script>
> </head>
>
> <body>
> <h1>Signal Bug Test</h1>
> <button id="bad_example">Alert "explicit_value" (broken)</button>
> <button id="good_example">Alert "explicit_value"</button>
> </body>
> </html>
>
> This is running against SVN head (r1199). The behavior I've marked as
> 'broken' occurs on any DOM node when a custom signal is used. I would
> expect both buttons to produce the same results.
Custom signals definitely do not work on DOM nodes at this point. I'm
not sure that should be a goal, either. connect works very differently
for DOM nodes.
We should at least clearly document this.
-bob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~----------~----~----~----~------~----~------~--~---
