form button aren't disabled in firefox

I have found a different behavior clicking form buttons using Internet Explorer and Firefox.

While using Internet Explorer once the button has been clicked, it became disabled, using Firefox it remains enabled.

Could you help me?

Tagged:

Comments

  • Perhaps this may help? (from the web client configuration guide pdf)-

     

    6.1.8 Disable Field Access during Refill Requests
    Default behavior related to refill requests is to allow for user editing of form fields during the request operation.
    However, this can result in unexpected form field behavior following completion of the server request. To
    address this issue, ShowRefillProgress application setting has been added to the Web Client
    web.config file. This setting temporarily disables user access to form fields during the time that refill request
    processing is being performed.
    <add key="ShowRefillProgress="True"/>
    A Refill progress icon displays during processing of the refill request and all fields on the form are locked out.

  • I tried to add this 

     

     

    in Program Files (x86)\Metastorm\BPM\Web\we.config

     

    <?xml version="1.0"?>
    http://schemas.microsoft.com/.NetConfiguration/v2.0">

    ...

    ...

     

    it doesn't work .

    I've done something wrong?

  • Just a sanity check - which version are you using?

     

    This setting was introduced in versions 9.1.3 and above.

     


      
      
      
      
      
      
      
      
      
      
      
      
      
      
      
      
      
      <add key="FormOperationsTimeout" value="0">

     

    Also if a script is very quick quick the refill progress won't stay on for long,

     

    You can use a button with a System.Threading.Thread.Sleep(x) to test that it is working.

     

    Kind Regards

     

    Rich

  • I see that your "True" has an uppercase T...not sure if that matters, but if you look at all of the other tags, the "true" and "false" are all lowercase.

    You should also do an IISRESET and restart your browser after making this change. I tested it yesterday before posting my response and it worked fine for me.