ICEfaces
  1. ICEfaces
  2. ICE-3063

wait cursor doesn't disappear after client-side action

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.7
    • Fix Version/s: 1.7.1
    • Component/s: Bridge
    • Labels:
      None
    • Environment:
      IE7, Firefox 2.0
      ICEfaces 1.7.x
      JSF1.2
      Facelets
      Tomcat 6

      Description

      A lot of forum users mentioned that after migrating to 1.7.0 the wait cursor doesn't disappear under certain circumstances when a client-side event has been triggered. sometimes the application doesn't even respond anymore. This is not happening in 1.6.2, so it might be a regression. See attached demo application.

        Activity

        Hide
        Michael Thiem added a comment -

        deploy on tomcat 6

        Show
        Michael Thiem added a comment - deploy on tomcat 6
        Hide
        Ken Fyten added a comment -

        Using the provided war file, I can reproduce the problem using FF2, IE7, IE6, Opera, Safari.

        • On any of the browsers, go to the menubar and select one of the options ('Edit Person' or 'List Person'). Let the page update, then select the other option in the menubar. After the page updates, the mouse cursor permanently becomes the hour glass. Sometimes you'll need to move the mouse a bit before it changes.
        • (Firefox specific) Load the page and do not do anything. Every few minutes the mouse becomes 'working in background' cursor (pointer + hour glass) for a few seconds, then changes back to a regular pointer.
        • (Safari specific) Go to the menubar and select one of the options, the page will update. Then after a few seconds, it will redirect to a page that says "Javascript is blocked. ICEfaces cannot run." I made sure that "Enable JavaScript" is checked in the preferences. And the data paginator still works.

        These problems are still reproducible when I use the trunk (rev 16637).

        Regards,
        Jacky

        Show
        Ken Fyten added a comment - Using the provided war file, I can reproduce the problem using FF2, IE7, IE6, Opera, Safari. On any of the browsers, go to the menubar and select one of the options ('Edit Person' or 'List Person'). Let the page update, then select the other option in the menubar. After the page updates, the mouse cursor permanently becomes the hour glass. Sometimes you'll need to move the mouse a bit before it changes. (Firefox specific) Load the page and do not do anything. Every few minutes the mouse becomes 'working in background' cursor (pointer + hour glass) for a few seconds, then changes back to a regular pointer. (Safari specific) Go to the menubar and select one of the options, the page will update. Then after a few seconds, it will redirect to a page that says "Javascript is blocked. ICEfaces cannot run." I made sure that "Enable JavaScript" is checked in the preferences. And the data paginator still works. These problems are still reproducible when I use the trunk (rev 16637). Regards, Jacky
        Hide
        Mircea Toma added a comment -

        An update for the 'body' element causes the evaluation of the 'script' element that is responsible for instantiating the bridge (feature introduced for ICE-1675). This in turn creates a lot of confusion since there are two bridge instances operating on common objects.
        The straight forward solution is to just send a reload command instead of the update, strategy already in place for the 'html' and 'head' elements.

        Show
        Mircea Toma added a comment - An update for the 'body' element causes the evaluation of the 'script' element that is responsible for instantiating the bridge (feature introduced for ICE-1675 ). This in turn creates a lot of confusion since there are two bridge instances operating on common objects. The straight forward solution is to just send a reload command instead of the update, strategy already in place for the 'html' and 'head' elements.
        Hide
        Mircea Toma added a comment -

        Implement better fix. Instead of sending 'reload' command when 'body' element is updated, shutdown previously associated bridge instance. Strip 'noscript' element from the update to avoid its execution in Safari.

        Show
        Mircea Toma added a comment - Implement better fix. Instead of sending 'reload' command when 'body' element is updated, shutdown previously associated bridge instance. Strip 'noscript' element from the update to avoid its execution in Safari.
        Hide
        Mircea Toma added a comment -

        Turn off all indicators on bridge shutdown.

        Show
        Mircea Toma added a comment - Turn off all indicators on bridge shutdown.
        Hide
        Mariana Popoviciu added a comment -

        It seems that this problem appears again in 1.8.2 in IE8, IE9 and Firefox5 (could be in other versions also).

        Show
        Mariana Popoviciu added a comment - It seems that this problem appears again in 1.8.2 in IE8, IE9 and Firefox5 (could be in other versions also).

          People

          • Assignee:
            Unassigned
            Reporter:
            Michael Thiem
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: