JDK-8239332 : LiveConnect netscape.javascript.JSException: No such property "outerWidthX" on JavaScript object
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 8u162
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-02-18
  • Updated: 2020-06-09
  • Resolved: 2020-03-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8u261 b01Fixed
Description
I have an applet that makes a JavaScript call via live connect.  I have the call surrounded by a try/catch.  Despite that, a stack trace like the
following is being printed in the Java console even though I do not print it.  

Error Codes
---------------------------------------------------
No such property "outerWidth" on JavaScript object

netscape.javascript.JSException: No such property "outerWidthX" on JavaScript object 
    at sun.plugin2.main.client.MessagePassingJSObject.newJSException(Unknown Source)
    at sun.plugin2.main.client.MessagePassingJSObject.waitForReply(Unknown Source)
    at sun.plugin2.main.client.MessagePassingJSObject.doMemberOp(Unknown Source)
    at sun.plugin2.main.client.MessagePassingJSObject.getMember(Unknown Source)
Comments
For the following files debug logs are printed out regardless debug settings: MessagePassingJSObject.java MessagePassingOneWayJSObject.java The root cause of such behaviour is incorrect interpretation of debug settings in these files.
03-03-2020

Some misunderstanding took place here. The problem is that the stack trace is printed out but it shouldn't (i.e. debug mode is OFF).
03-03-2020

I am not aware of ���outerWidthX��� property, but there is a slightly different one ���outerWidth���, (see https://www.w3schools.com/jsref/prop_win_outerheight.asp ). So I suspect there is some misconfiguration (most likely typo) here.
25-02-2020

The problem is reproducible on JDK 8u241, 8u162, 8u161, 8u152 and 8-b132. So it is NOT a regression introduced in 8u162.
25-02-2020