[9-dev] RfR: JDK-8132743: Move netscape.javascript package from jdk.plugin to new module

David DeHaven david.dehaven at oracle.com
Fri Mar 4 15:31:05 UTC 2016


>>> Updated webrev:
>>> http://cr.openjdk.java.net/~ddehaven/8132743/webrev.1/
>>> 
>> Looks fine to me.  Thanks for the update.
>> 
> Just reading the javadoc again and I wonder about this statement in the package description:
> 
> "The classes in this package were initially specified by Netscape, and are the de facto standard mechanism for calling JavaScript from the Java runtime."
> 
> Does need to qualify the statement to say when in the web browser? Just thinking about the scripting API as a way to integrate with JavaScript.

The use with JavaScript engines goes beyond just browser use (it can be used by Nashorn) but HTML DOM access is only relevant when using with a browser or with WebKit in JavaFX. It's how JavaFX applications communicate with web sites being rendered in a WebView and, in theory (only because I haven't tried it myself), you should be able to manipulate the HTML DOM directly once you gain access to it. You can do the same from an applet running in an browser via Java plugin.

I don't know if that clarifies anything or makes it worse... caffeine hasn't kicked in yet this morning.

-DrD-




More information about the build-dev mailing list