changeset 10120:de0071f81192 jdk-9+144

8169204: Need to document JSObject Call and setSlot APIs to use weak references Reviewed-by: kcr
author mbilla
date Sat, 05 Nov 2016 21:55:53 +0530
parents 885450989240
children 1d2ba137d832 7da620ef965e
files modules/javafx.web/src/main/java/javafx/scene/web/WebEngine.java
diffstat 1 files changed, 3 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/modules/javafx.web/src/main/java/javafx/scene/web/WebEngine.java	Fri Nov 04 17:32:28 2016 -0700
+++ b/modules/javafx.web/src/main/java/javafx/scene/web/WebEngine.java	Sat Nov 05 21:55:53 2016 +0530
@@ -237,7 +237,9 @@
  * in that accessing properties of the {@code JavaRuntimeObject}
  * causes the Java field or method with the same name to be accessed.
  * <p> Note that the Java objects bound using
- * {@link netscape.javascript.JSObject#setMember JSObject.setMember}
+ * {@link netscape.javascript.JSObject#setMember JSObject.setMember},
+ * {@link netscape.javascript.JSObject#setSlot JSObject.setSlot}, and
+ * {@link netscape.javascript.JSObject#call JSObject.call}
  * are implemented using weak references. This means that the Java object
  * can be garbage collected, causing subsequent accesses to the JavaScript
  * objects to have no effect.