Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4838960

Javascript event handlers becoming asynchronous

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 1.4.1_07
    • 1.4.1, 1.4.1_04, 5.0
    • deploy
    • 07
    • x86
    • windows_2000, windows_xp
    • Verified



        Name: gm110360 Date: 03/27/2003


        FULL PRODUCT VERSION :
        Plug-in Java(TM): Version 1.4.0_02
        Utilisation de la version JRE 1.4.0_02 Java HotSpot(TM) Client VM

        FULL OPERATING SYSTEM VERSION :
        Microsoft Windows 2000 [Version 5.00.2195]

        EXTRA RELEVANT SYSTEM CONFIGURATION :
        Internet Explorer 5.50.4807.2300

        A DESCRIPTION OF THE PROBLEM :
        Calling an applet's method inside a javascript event handler
        makes this handler asynchronous: other event handlers are
        called before the first handler has finished his work.
        Some events are even lost, their event handler being never
        called.

        The problem occurs when using recent versions of the plug-in
        (for instance 1.3.1_04 or 1.4.0_02 or 1.4.1) and Internet
        Explorer 5.5 or 6.0.

        It works as expected with IE and an older plug-in (1.3.1) or
        with Mozilla 1.1 and any plug-in.

        REGRESSION. Last worked in version 1.3.1

        STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
        1. Compile the following applet
        -------------------------------
        public class BugJRE extends javax.swing.JApplet{
            public void wait2s(){
          int i=0;
          long time = System.currentTimeMillis();
          while( (time + 2000) > System.currentTimeMillis() ){
           i = i + 1;
          }
            }
        }
        -------------------------------

        2. Save the following HTML page
        -------------------------------
        <html>
        <script language="javascript">
        function callJavaOnChange(){
         var t = document.getElementById("debug");
         var JsTime1 = new String(new Date().getTime());
         JsTime1 = JsTime1.substring(JsTime1.length-5);
         t.value = t.value + "\nBegin event("+JsTime1+") onChange";
         document.javaApplet.wait2s();
         t.value = t.value + "\nEnd event("+JsTime1+") onChange";
        }
        function callJavaOnMouseUp(){
         var t = document.getElementById("debug");
         var JsTime2 = new String(new Date().getTime());
         JsTime2 = JsTime2.substring(JsTime2.length-5);
         t.value = t.value + "\nBegin event("+JsTime2+") onMouseUp";
         document.javaApplet.wait2s();
         t.value = t.value + "\nEnd event("+JsTime2+") onMouseUp";
        }
        </script>
        <body>

        <object classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
        width="500"
        height="50" align="baseline"

        codebase="http://java.sun.com/products/plugin/1.3/jinstall-13-win32.cab#Vers
        ion=1,3,0,0"
            name="javaApplet">
        <param name="code" value="BugJRE.class">
        <param name="type"
        value="application/x-java-applet;version=1.3">
        <param name="MAYSCRIPT" value="true">
        </object>

        <br/>
        <select size="5" onchange="callJavaOnChange();"
        onmouseup="callJavaOnMouseUp();">
         <option value="option1" selected>option1</option>
         <option value="option2">option2</option>
         <option value="option3">option3</option>
         <option value="option4">option4</option>
         <option value="option5">option5</option>
        </select>
        <br/>
        <textarea id="debug" rows="20" cols="50"></textarea>
        </body>
        </html>
        -------------------------------

        3. Launch Internet Explorer with a recent version of the
        plug-in (1.4.0_02), and view the page described in step 2.

        4. Put the mouse cursor over option2, click, *do not wait*,
        move the cursor over option3, click.

        5. After a few seconds with the CPU at 100%, a log of which
        event handlers where called will appear in the textarea.


        EXPECTED VERSUS ACTUAL BEHAVIOR :
        The expected log should be something like this:
        Begin event(63014) onMouseUp
        End event(63014) onMouseUp
        Begin event(65016) onChange
        End event(65016) onChange
        Begin event(67039) onMouseUp
        End event(67039) onMouseUp
        Begin event(69042) onChange
        End event(69042) onChange

        This output means that handlers are called in the same order
        as the events are generated:
        1st: the onMouseUp for option2
        2nd: the onChange for option2
        3rd: the onMouseUp for option3
        4th: the onChange for option3

        The actual log is:
        Begin event(31923) onMouseUp
        Begin event(32433) onMouseUp
        End event(32433) onMouseUp
        Begin event(34506) onChange
        End event(34506) onChange
        End event(31923) onMouseUp

        This means that both handlers for the 2 mouseUp run in
        parallel, while the event handler for onChange is called
        only once instead of twice.

        REPRODUCIBILITY :
        This bug can be reproduced always.

        CUSTOMER WORKAROUND :
        Use an older plug-in or Mozilla 1.1 (replacing tag <object>
        by <applet>)
        (Review ID: 178721)
        ======================================================================

              djayaramsunw Devananda Jayaraman (Inactive)
              gmanwanisunw Girish Manwani (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: