Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: EE-4.2.0.GA
    • Fix Version/s: None
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      All

      Description

      The fix of issue ICE-10518 seems unneccacery.

      The fix causes the problem that it isn't possible to disable blockUI for a specific form, if the context parameter 'org.icefaces.blockUIOnSubmit' is set to true.

      Because ace:submitMonitor can be placed on every form, it should overwrite the context parameter org.icefaces.blockUIOnSubmit, which only can be disabled for specific pages.

      Another way to fix the bug ICE-10518, is to not use the attribute blockUI="@none" on the element ace:submitMonitor, if you want the blockUI to appear. If you want an blockUI to appear then you don't even have to use the element ace:submitMonitor, or you don't need to specify the attribute 'blockUI'.

      The one who posted the question said the fix already in his description: "Removing the ace:submitMonitor from the page allows the ui blocker to work correctly. ". He should have just removed the ace:submitMonitor, and the ui blocker allways worked correctly, the use of ace:submitMonitor was only faulty used.

      I've posted a question also on StackOverflow regarding this: https://stackoverflow.com/questions/54180650/setting-blockuionsubmit-for-a-specific-form

      And added a comment on the bug ICE-10518: http://jira.icesoft.org/browse/ICE-10518

        Activity

        There are no subversion log entries for this issue yet.

          People

          • Assignee:
            Unassigned
            Reporter:
            Oscar Stigzelius
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: