... which is all EL-accessible, so fun things like:
rendered="#{adfFacesContext.agent.agentName == 'gecko'}"
or
rendered="#{adfFacesContext.agent.capabilities.dom == 'level2'}"
rendered="#{adfFacesContext.agent.capabilities.accessKeys}"
... all work.
-- Adam
On 4/4/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > friendly to have the component do its own check on user agent, and emit the
>
> The incoming stuff from ADF Faces donation contains more comfortable
> stuff regarding UserAgent.
>
> AdfFacesContext afc = AdfFacesContext.getCurrentInstance();
> Agent agent = afc.getAgent();
>
>
> You may take a look ;-)
>
> -Matthias
>
>
> > correct kind of markup accordingly. If you don't have control over the
> > components, then what you describe will work -- but you don't need separate
> > panelGroup elements:
> >
> > <h:panelGroup>
> > <rw:inputSlider rendered="#{browser.coolComponentCapable}" .../>
> > <h:selectOneRadio rendered="#{not browser.coolComponentCapable}"
> > .../>
> > </h:panelGroup>
> >
> > Or, if you don't need the parent to think this is a single component, just
> > dispense with the panel group entirely.
> >
> >
> > > Thanks,
> > > Rich
> > >
> >
> >
> > Craig
> >
> >
>
>
> --
> Matthias Wessendorf
> Zülpicher Wall 12, 239
> 50674 Köln
> http://www.wessendorf.net
> mwessendorf-at-gmail-dot-com
>
