Apologies in advance...
Issues sending to this list - using relay.plus.net has been failing, so
this is just to test if I can use my hosting provider's SMTP server to
do so instead.
"Fish - visionary genius, or just a big haddie?"
of hourglasses to get to http:/www.google.co.uk
Cam anyone shed any further light on the scope of the issue.
(Sent via webmail as list not accepting (Plusnet) emails.
I would have reported this on the bug tracker, but I've found it
impossible to access this, even after a change of password.
This is currently with 3.10 (Dev CI#4729) on RISC OS 5.25, RiscOS version
(24 Aug 18).
I have been using URI files so=red in Paul Vigay's NeXTBar app to launch
favourite files. I'm lazy, and this is easier than finding them from the
icon bar's Hot List. Fot the last three or so development builds this has
stopped working, and even if I save the location in a RISC OS URI file and
double-click on this it still doesn't work. Also, double-clicking on a URL
in a MPro email doesn't work.
I've just discovered that if I save a location as an ANT URL file and
double-click on this, it does work. However, this is the format NeXTBar
uses to store URLs, so I am not totally puzzled.
Does anyone know why this should happen?
Peter Young (zfc Hg) and family
Prestbury, Cheltenham, Glos. GL52, England
As those of you who follow every CI release may have noticed, in the past week
or so, the Login dialog, and the SSL issue alerts have changed to be
in-browser. This was done to simplify the frontend APIs a little, and to unify
the functionality into the core so that it is easier to amend/extend for all
fronends at once.
In addition, we have added code to tell you the basic reason why a certificate
was not acceptable to the browser and done our best to make the dialogs look
fairly obvious to work with.
There are some known issues with the dialogs right now.
First and foremost, the dialogs are not in necessarily in their final form in
will work even if JS is off; but in future we may *add* functionality by JS so
it may become necessary for all but the most basic features. Finally (for now)
there is no way outside of the content to know for sure that the page was
generated by NetSurf itself. We will be adding an indicator which will show this
among other status information in the near future. This will likely take the
form of the 'padlock' feature you see on most modern browsers.
That said, we need your help to get these features nailed down as they are, so that
a future release can include them...
We need translations for the various messages used in those dialogs. The login
dialog is pretty much translated already, but the new SSL dialog needs a number
of strings translating. Those of you who are able to translate messages, you can
find the current set of messages at:
The specific messages for the SSL dialog are around line 1070 in the "Privacy
error interface" section of the file. Translations for the certificate failure
reasons are most critical at this time. We may tweak the english text from
time to time, as we optimise how the dialog feels, and it goes with the
"PrivacyDescription" text which also needs translating for each supported
The "%s" in PrivacyDescription is for the server's hostname, so any translation
should take that into account and include such a marker where the server name
We are also anxious that if you encounter problems with the new login or privacy
problem interfaces, that you report them to our bug tracker. I would appreciate
such issues being raised because this is all using very new internal features
in the browser which we hope to use for other functionality in the future and so
we need it well tested.
Further discussion on the topic of these two dialogs may come in time.
Thank you all,
Daniel Silverstone http://www.netsurf-browser.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
The local history window has had a few updates.
* It will now open scrolled to show the current entry.
* It can now be navigated with the keyboard. (Cursor
Left, Right, Up, Down, and Return.)
* Thumbnails are now slightly larger, and their dimensions
take account of the screen DPI.
Michael Drake https://www.codethink.co.uk/