ICEfaces
  1. ICEfaces
  2. ICE-6629

Sometimes navigation only happens if button is clicked twice

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.1
    • Component/s: Bridge
    • Labels:
      None
    • Environment:
      ICEfaces 2.0.0/2.0.1-SNAPSHOT from 2. March 2011
      Mojarra 2.0.3/2.0.4/2.1.0-b5
      Firefox 3.6.14/Chrome (Iron) 9.0.600.2/Safari 5.0.3/Internet Explorer 8.0.7601
      Tomcat 7.0.6

      Description

      Sometimes, if I click on a button nothing seems to happen and I have to click a second time.
      • The Ajax request looks OK to me, the action in the backing bean is called and the Ajax response seems to be OK too. But the page in the browser doesn't change at all.
      • The bug is always reproducible using the same steps in the sample application. With Internet Explorer the bug happens later than in other browsers, it needs more clicks than the other browsers. With all other browsers I have tried, I was able to reproduce the problem using the same steps.
      • If I disable DOM diffing using org.icefaces.render.auto=false in web.xml the bug doesn't occur. But this is not a workaround for me because then I can't use the ICEfaces 1.8 components which I need to use.
      • The bug occurs with both h:commandButton and ace:pushButton.
      • I don't get a JavaScript error in the browser
      • Another guy has got the same problem in a totally different application.
      • For me this is a blocker issue

      I'll shortly provide a sample application and steps to reproduce via Micha Kiener as I can't make the sample public.

        Activity

        Adrian Gygax created issue -
        Adrian Gygax made changes -
        Field Original Value New Value
        Environment ICEfaces 2.0.0/2.0.1-SNAPSHOT from 2. March 2011
        Mojarra 2.0.3/2.0.4/2.1.0-b5
        Firefox 3.6.14/Chrome (Iron) 9.0.600.2/Safari 5.0.3/Internet Explorer 8.0.7601
        ICEfaces 2.0.0/2.0.1-SNAPSHOT from 2. March 2011
        Mojarra 2.0.3/2.0.4/2.1.0-b5
        Firefox 3.6.14/Chrome (Iron) 9.0.600.2/Safari 5.0.3/Internet Explorer 8.0.7601
        Tomcat 7.0.6
        Salesforce Case []
        Adrian Gygax made changes -
        Salesforce Case []
        Description Sometimes, if I click on a button nothing seems to happen and I have to click a second time.
        • The Ajax request looks OK to me, the action in the backing bean is called and the Ajax response seems to be OK too. But the page in the browser doesn't change at all.
        • The bug is always reproducible using the same steps in the sample application. With Internet Explorer the bug happens later than in other browsers, it needs more clicks than the other browsers. With all other browsers I have tried, I was able to reproduce the problem using the steps below.
        • If I disable DOM diffing using org.icefaces.render.auto=false in web.xml the bug doesn't occur. But this is not a workaround for me because then I can't use the ICEfaces 1.8 components which I need to use.
        • The bug occurs with both h:commandButton and ace:pushButton.
        • I don't get a JavaScript error in the browser
        • Another guy has got the same problem in a totally different application.
        • For me this is a blocker issue

        I'll shortly provide a sample application and steps to reproduce via Micha Kiener as I can't make the sample public.
        Sometimes, if I click on a button nothing seems to happen and I have to click a second time.
        • The Ajax request looks OK to me, the action in the backing bean is called and the Ajax response seems to be OK too. But the page in the browser doesn't change at all.
        • The bug is always reproducible using the same steps in the sample application. With Internet Explorer the bug happens later than in other browsers, it needs more clicks than the other browsers. With all other browsers I have tried, I was able to reproduce the problem using the same steps.
        • If I disable DOM diffing using org.icefaces.render.auto=false in web.xml the bug doesn't occur. But this is not a workaround for me because then I can't use the ICEfaces 1.8 components which I need to use.
        • The bug occurs with both h:commandButton and ace:pushButton.
        • I don't get a JavaScript error in the browser
        • Another guy has got the same problem in a totally different application.
        • For me this is a blocker issue

        I'll shortly provide a sample application and steps to reproduce via Micha Kiener as I can't make the sample public.
        Ken Fyten made changes -
        Salesforce Case []
        Fix Version/s 2.0.1 [ 10255 ]
        Assignee Ted Goddard [ ted.goddard ]
        Ted Goddard made changes -
        Attachment composition.zip [ 12928 ]
        Ted Goddard made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Ted Goddard
            Reporter:
            Adrian Gygax
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: