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

Java Plug-In no longer supports 'javascript:' URLs after MS Hotfix 867801

    Details

    • Subcomponent:
    • Resolved In Build:
      b04
    • CPU:
      x86
    • OS:
      windows_xp

      Backports

        Description

        synopsis: Java Plug-In no longer supports 'javascript:' URLs after MS Hotfix 86780
        description: FULL PRODUCT VERSION :
        Applies to 1.4.2 and all recent (if not all period) JPIs.

        ADDITIONAL OS VERSION INFORMATION :
        Applies to any Microsoft OS to which the given hotfix has been applied

        EXTRA RELEVANT SYSTEM CONFIGURATION :
        See http://support.microsoft.com/?kbid=875345 for more information on Microsoft hotfix 86780.

        A DESCRIPTION OF THE PROBLEM :
        Microsoft's latest hot fix have broken any of out applets that use the 'javascript:' URL methodology to interact with the HTML document.

        We switched to this because of all the problems with the JSObject calls (most particularly in Internet Explorer). It now appears that we are dead in the water with this hotfix.

        The Hot fix mentions different calls can be made by the native code to as replacement functionality. It appears that this means the JRE must change its native code calls for Windows.

        STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
        Call a JavaScript function (in the enclosing page) from an applet via:

          appletContext.showDocument( 'javascript:...' )

        Note this approach does not allow a return value, but that is not an issue in many cases.

        EXPECTED VERSUS ACTUAL BEHAVIOR :
        EXPECTED -
        The given JavaScript function should be called successfully.
        ACTUAL -
        Call is prevented by MS hotfix.

        REPRODUCIBILITY :
        This bug can be reproduced always.

        CUSTOMER SUBMITTED WORKAROUND :
        One might argue that the workaround is to use JSObject, but:

        1) JSObject is far less stable than 'javascript:' URL usage and thus is best avoided except when one needs the return value of the JavaScript function.

        2) This defeats the generality of treating JavaScript calls as yet another URL type.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  djayaramsunw Devananda Jayaraman (Inactive)
                  Reporter:
                  jeffrtay Jeff Taylor (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Imported:
                    Indexed: