Re: Orpheus Home page
by Tony Moore
On 1 May 2013, Chris Young <chris.young(a)unsatisfactorysoftware.co.uk>
wrote:
> 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.
> >
> > http://javatester.org/javascript.html responds to NS 3.0 with a
> > 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
> JavaScript support.
[snip]
> The only bug here is that the "Disable JavaScript" choices option
> should not be available in builds that do not support JavaScript.
In that case, the ChangeLog, which says
Added early and primitive JavaScript support. (Disabled by default.)
needs to be changed.
Tony
9 years, 10 months
Re: Orpheus Home Page
by Gerald Dodson
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.
Gerald
9 years, 10 months
Re: Orpheus Home Page
by Tony Moore
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
<51815842.10509(a)unsatisfactorysoftware.co.uk>
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.
Tony
9 years, 10 months
Non-breaking space.
by Tim Hill
#1096
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
"we know"!
See the production crew near the foot of the page. All the names have
in them:
http://www.youngtheatre.co.uk/archive/199209_blithespirit/
(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!!)
9 years, 10 months
Re: Orpheus Home page
by Tony Moore
On 1 May 2013, "Learning Partners" <lp.books(a)argonet.co.uk> wrote:
> On Wed, 1 May, 2013 1:01 pm, Tony Moore wrote:
[snip]
> > JS setting in Choices to be lost when NS is quit/re-started. This
> > means that it is necessary to re-set 'Disable JavaScript' when NS
> > 3.0 is run.
>
> Yes am doing that. My problem is with Outlook Web Access where
> javascript:SetCmd(CmdSend);: Send does not seem to be supported yet.
> 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/
Tony
9 years, 10 months
Re: Orpheus Home page
by Tony Moore
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:
[snip]
> > Can't get javascript to work at all though (ticked on in choices
> > but....)
>
> Seems to work here. Have you made sure that you have a JavaScript
> version? :-)
>
> http://javatester.org/javascript.html will tell you whether JavaScript
> is working or not. Here I see:
>
> JavaScript IS WORKING in your web browser
>
> Your web browser supports JavaScript version 2.2
>
> 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
JavaScript IS WORKING in your web browser
Your web browser supports JavaScript version 2.2
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
that it is necessary to re-set 'Disable JavaScript' when NS 3.0 is run.
Tony
9 years, 10 months
netsurf 3.0 choices bug
by Tony Moore
The following has recently been discussed in csa.apps:
The NetSurf 3.0 Change Log says:
Added early and primitive JavaScript support. (Disabled by default.)
Unticking 'Disable Javascript' enables JS for the session but, if
NetSurf is quit/re-started, 'Disable Javascript' is again ticked, this
notwithstanding that the choices file contains enable_javascript:1
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.
Tony
9 years, 10 months
