The last example I'll review isn't very pretty, but it shows off some important points about both ViewLink and element behaviors. The document for a ViewLinked behavior can itself contain other Element Behaviors which are themselves ViewLinked. Events stop at ViewLink boundaries. Here's the demo . However, these events become even more important, as now they are the only way to get events out of a ViewLinked element behavior.
Lets take a look at how that's done.
When the onclick event of the button occurs, the behavior translates that into the firing of the synthetic click event. In this way, the implementation of your behaviors is truly separate from the properties, methods, and events that they expose to the outside world. Summary Having a powerful component model is a requirement for a full-fledged development platform. The component model delivered by Internet Explorer 5.5 has many features that allow the development of reusable components. Michael Wallent is Microsoft's group program manager for Internet Explorer.