Hi, >> One question: the “class org.w3c.dom.Window” line is commented out >> because it “conflicts with our Window class”. How does it conflict? > > If you uncommment it Rhino says: > org.mozilla.javascript.EvaluatorException: > Cannot import "Window" since a property by that name is already > defined. > > Which isn't strictly correct since we bind 'window' (little 'w').
Weird... Could this be a regression due of fixing bug 46072 [1] or a Rhino bug? >> (Also I might return iterators to the classes/packages lists wrapped >> with Collections.unmodifiableList so that calling code can’t remove >> items. That, or add removeClass()/removePackage() methods, if we want >> to allow removals.) > > So I did both the above. I was also going to add a 'getImportInfo()' > method to the bridge.UserAgent class (that defaults to getting the > default importInfo). That way developers can support different sets > of imports for different documents. This sounds like pretty useful and powerful enough to support the exotic use cases. :-) It it worth to file a RFE so this won't get lost? Regards, Helder [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=46072 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
