<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WORKSFORME - Support: UNO for firefox JS engine - javascript document scripting" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122392#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WORKSFORME - Support: UNO for firefox JS engine - javascript document scripting" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122392">bug 122392</a> from <a class="email" href="mailto:todventtu@suomi24.fi" title="Buovjaga <todventtu@suomi24.fi>"> Buovjaga</a> <pre>(In reply to Tim from <a href="show_bug.cgi?id=122392#c4">comment #4</a>) > The intent of my bug was to suggest the enhancement that the firefox > integration (in the android version which i assumed was the same as the > core?), could re-use the firefox JS engine which it has to interact with > already, with a UNO interface support javascript in a cross platform way. I don't believe the Android version interacts with Firefox in any way. The current engine, Rhino, is provided by Mozilla: <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino">https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino</a> In <a class="bz_bug_link bz_status_NEW " title="NEW - Change the rhino engine for javascript macros for non Java alternative (spidermonkey/V8)" href="show_bug.cgi?id=97827">bug 97827</a>, I proposed that Duktape could be used as the engine. Michael Stahl commented: "SpiderMonkey and V8 are very large and complex C++ projects with unstable APIs so integrating them would be very painful"</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>