Recently I've noticed strange things happening when running NetSurf
(currently 3.1 #1108). When I load certain pages with a lot of
graphics/images the computer starts bleeping and the Organizer icon
starts alternating between black-on-cream and the reverse of that.
One such page is
I've recently upgraded to Organizer 2.20 which might be relevant.
Richard Porter http://www.minijem.plus.com/
I don't want a "user experience" - I just want stuff that works.
On 1 May 2013, Chris Young <chris.young(a)unsatisfactorysoftware.co.uk>
> On 01/05/13 17:45, Tony Moore wrote:
> > On 1 May 2013, Daniel Silverstone <dsilvers(a)netsurf-browser.org>
> > wrote:
> > > The JS support in the current builds is very likely to be
> > > identical to the 3.0 build.
> > blank Test Results window, whereas the response to the current 3.1
> > build is verbose. I took this to indicate JS progress. I'm sorry if
> > the assumtion was not correct.
> I think it is highly likely that NetSurf 3.0 has been built without
In that case, the ChangeLog, which says
needs to be changed.
The misunderstanding seems to persist: NS 3.0 does have JS built in.
As I understand things and, as already stated before, JS is disabled when
you load NS. Menu>Choices>Content takes you to the selection where you can
enable JS. With 3.0 you will always have to set what you want each time NS
is loaded, unlike the developemnt versions which will retain the choice
once selected whenever NS is subsequently reloaded.
On 6 May 2013, "Gerald Dodson" <gerald.dodson(a)argonet.co.uk> wrote:
> The misunderstanding seems to persist: NS 3.0 does have JS built in.
Chris Young, a NetSurf Developer, thinks that it is 'highly likely' that
NetSurf 3.0 was compiled without JS support. Please see message
The !RunImage size in NetSurf 3.0 is 3MB, which is the same as that of a
jsoff build. The !RunImage size in a json build is 5MB.
I included a list of names on a webpage the other day and my co-editor
doesn't like to see name split across a line. I agree: when lines are
long a split name looks silly when you can easily place a non-breaking
space between forename and surname. Browsers know not to split a line at
a non-breaking space, don't they? Except Netsurf?
I have not reported this as a bug (yet) because I expect a crescendo of
See the production crew near the foot of the page. All the names have
(One aspect of line endings I see does seem to be fixed and that was the
spurious line feeds which I saw in tables. Hurrah for that!!)
On 1 May 2013, "Learning Partners" <lp.books(a)argonet.co.uk> wrote:
> On Wed, 1 May, 2013 1:01 pm, Tony Moore wrote:
> > JS setting in Choices to be lost when NS is quit/re-started. This
> > 3.0 is run.
> Yes am doing that. My problem is with Outlook Web Access where
> Still I realise this is early days and it is a miracle anyway that I
> can read Outlook Web Access and Sharepoint pages in RISC OS!
If JS is important to you I would suggest downloading the latest
development build from http://ci.netsurf-browser.org/builds/riscos/ .
(choose json at the bottom of the page). The JS choices bug is absent,
and the JS support itself is more advanced than that in NS 3.0.
If you wish to keep up to date with the latest development build, Frank
de Bruijn's Fetch_NS is very useful http://aconet.org/tools/
On 1 May 2013, Peter Young <pnyoung(a)ormail.co.uk> wrote:
> On 1 May 2013 "Learning Partners" <lp.books(a)argonet.co.uk> wrote:
> > but....)
> version? :-)
> is working or not. Here I see:
> Every web browser identifies itself to websites with a character
> string called the "user agent". The User Agent string for your web
> browser is:
> NetSurf/3.0 (RISC OS)
John mentions the 'new release' which presumably means NS 3.0. Although
the javatester response above mentions NetSurf/3.0, the actual response
when using the NS 3.0 release, is a blank Test Results window, if JS is
working, and a fail notice if not.
The extended javatester response above presumably results from JS
improvements in NS #1096, as compared with NS 3.0. For comparison, the
javatester response to the earlier NS #1083 is
Your web browser was not detected as being either Opera, Firefox,
Internet Explorer, Chrome or a BlackBerry
so it seems that work is on-going in this area.
As mentioned in another post, there is a bug in NS 3.0 which causes the
JS setting in Choices to be lost when NS is quit/re-started. This means
The following has recently been discussed in csa.apps:
The NetSurf 3.0 Change Log says:
Subsequent development builds are not affected (the JS setting survives
quit/re-start) but the point has been made in csa.apps that it would be
helpful if the bug were to be fixed in 3.0, for the benefit of those who
rely on stable releases.