Re: RISC OS Javascript support

2012-12-14 Thread Vincent Sanders
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.

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

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.

-- 
Regards Vincent
http://www.kyllikki.org/



Re: RISC OS Javascript support

2012-12-14 Thread george greenfield
In message 52fdf4eea8...@timil.com
  Tim Hill t...@timil.com wrote:

 In article 20121214122314.gg15...@kyllikki.org, Vincent Sanders
 vi...@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.
 
 Okay, that line added to top of Boot:Choices.WWW.NetSurf.Choices
 

?

I found that adding that line (enable_javascript:1) to my Choices file 
/dis/abled javascript: commenting it out restored the status quo 
(i.e., partial operation of js). I'm running the #727 build.

George

-- 
george greenfield