Html <span> elements can have onClick, onBlur, and lots of other events, as well. People will probably end up having to attach this behavior manually.<br><br>This makes me wonder: Do we have a mechanism for attaching behaviors to "snippits" of HTML (more than links and buttons, say, divs / spans) on the output page, or do we need to address that as well? I see a use for being able to attach behaviors to any element on the HTML page.<br>
<br>The next question is: Do we need such a mechanism? That's, for the most part, the kind of behavior that a library like JQuery would provide, though we lose the hooks into JSF that come with behaviors.<br><br>--Lincoln<br>
<br><div class="gmail_quote">On Mon, Jan 11, 2010 at 2:24 PM, Andy Schwartz <span dir="ltr"><<a href="mailto:andy.schwartz@oracle.com">andy.schwartz@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hey Matthias -<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Why is HtmlOutputText not a ClientBehaviorHolder ?<br>
</blockquote>
<br></div>
I believe that the answer is that we only exposed ClientBehavior events/attach points for cases where components already exposed DOM event handlers. Since h:outputText does not expose any DOM event handlers (eg. no "onMouseover" attribute), we didn't surface any ClientBehavior attach points either. So, a related question is whether h:outputText should expose attributes for all of the relevant DOM event handlers. Personally I don't see much value in this - would prefer to keep h:outputText small/simple - but I am open to discussion on this point.<br>
<font color="#888888">
<br>
Andy<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>