2 Replies Latest reply on Sep 19, 2010 6:11 PM by Akaine Harga

    rich:dropDownMenu fails in Safari and Chrome

    Akaine Harga Novice



      Since the search gave nothing usefull I'll just ask:


      Does anyone know why rich:dropDownMenu fails to function (no menuitems, no onhover animation, etc.) in Chrome 6 (possibly Safari 4/5)?

      One correction: the menu on the rf demo page still works fine, so it must be something I have...


      JSF 1.2

      Facelets 1.1.15

      RF 3.3.3 GA

      (works fine in Firefox 3.6, Opera 10.62, IE 7/8 under Windows and Linux.


      Niether dynamic nor the static dropdownmenus are working. Even if I simplify the thing to this I get the same result:

      <html xmlns="http://www.w3.org/1999/xhtml"
          xmlns:a4j="http://richfaces.org/a4j" xml:lang="es-MX" lang="es-MX">
          <f:loadBundle basename="com.sacred.bundle.messages" var="msg"/>
          <a4j:keepAlive beanName="controller_sesion" />
          <a4j:form ajaxSubmit="true" ajaxSingle="true">
              <rich:toolBar styleClass="menuExit">
                  <rich:dropDownMenu direction="bottom-left" value="Salir">
                      <rich:menuItem submitMode="ajax" value="#{msg.cerrar_sesion}" action="#{controller_sesion.invalidarSesion}" />


      I've attached the rendered source screenshot to the post.


      Any ideas?

        • 1. Re: rich:dropDownMenu fails in Chrome 6
          Akaine Harga Novice

          Update: the issue does exist with Safari 4/5

          • 2. Re: rich:dropDownMenu fails in Chrome 6
            Akaine Harga Novice

            After a couple of tests I've reduced the "search zone":


            The issue occurs because of FORWARD dispatcher type set for a4j components and only because I use ajaxSubmit=true for the forms and a4j:commandButton instead of h:commandButton which helps me to maintain the application context. If I switch to JSF elements or change nav rules to redirect the issue disappears but in this case I lose the app context and each content page shows me its real context including all the subdirs.


            So the questions are:

            - How could I avoid losing app context without additional frameworks like Seam?

            - What else can be done to avoid the issue?