and that's why it isn't working for you because obviously: 1) the events aren't bubbling or 2) your dom structure is incorrect.
I'd look first to see if your handlers aren't actually receiving the events and secondly I'd look at your dom structure to make sure that the elements you think should be able to receive the events are actually capable of doing so. You can use firefox or ie's built in developer tools to explore the dom. But seriously, if you have a composite which has numerous interface elements such as textboxes, labels, etc. and radio buttons what difference does it make where in the composite's dom structure the radiobuttons' click events are caught? On the other hand, if you want one composite which contains the radiobuttons to fire off events that other composites can process then why not use the publisher/subscriber design pattern to facilitate that level of communications? That's how I'd handle it in this case. Jeff On Tue, Dec 7, 2010 at 9:37 AM, Ed Bras <[email protected]> wrote: > Yes, but that's not very efficient, that's why you use event bubbling... > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- *Jeff Schwartz* -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
