In article <20121214122314.GG15360@kyllikki.org>,
Vincent Sanders <vince@netsurf-browser.org> wrote:
> Thankyou for all your feedback.
> As some of you discovered there was no user interface to enable
> javascript so you would need to add:
> enable_javascript:1
> to your configuration manually.
While testing the various spidermonkey versions I added the user interface
to enable javascript. Here's a screen dump www.cgransden.co.uk/screen.png.
> It seems that the RISC OS edition of spidermonkey is failing to even
> initialise as can be seen within the log as:
> javascript/jsapi.c js_initialise 39: New runtime handle 0x0
With 1.85 on RISC OS this happens with the JIT turned on. If the JIT is
disabled it gets a bit further then gets stuck in a loop.
> which effectively means the javascript support is disabled and will not
> be able to use any script code on this platform (many of your examples
> work fine on the Linux platforms being used for development).
> If time permits I may look into this further but as I have limited
> access to RISC OS systems myself and the platform maintainer is
> currently not active I cannot promise progress in the immediate
> future.
> Sorry this was not more useful at this time but I do feel progress is
> being made albeit slowly.
Would it be an option to use Spidermonkey 1.7 on RISC OS temporarily? This
version seems stable and all the javascript tests work ok. They give the
same results as the gtk version which uses 1.85.
Chris.
No comments:
Post a Comment