Re: RISC OS NetSurf no longer responding to URI files
On 14 Aug 2019 David Higton wrote: > In message <52d17fe357.pnyo...@pnyoung.ormail.co.uk> > Peter Young wrote: >>On 4 Aug 2019 Peter Young wrote: >> >>> 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 stored 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. >> >>Just to report that I can again run NetSurf URLs from NeXTBar and from >>MPro. Many thanks to whoever fixed this. I've been too busy to access the >>bug tracker, I'm afraid. > I'd appreciate knowing whether you can access the bug tracker now, > Peter, if you can make the time available. I have to say that at > no time has access to Mantis stopped working for me. I shall try, but at the moment, at age eighty, I'm rather busy and tired. Watch this space! Best wishes, Peter. -- Peter Young (zfc Hg) and family Prestbury, Cheltenham, Glos. GL52, England http://pnyoung.orpheusweb.co.uk pnyo...@ormail.co.uk
Re: RISC OS NetSurf no longer responding to URI files
In message <52d17fe357.pnyo...@pnyoung.ormail.co.uk> Peter Young wrote: >On 4 Aug 2019 Peter Young wrote: > >> 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 stored 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. > >Just to report that I can again run NetSurf URLs from NeXTBar and from >MPro. Many thanks to whoever fixed this. I've been too busy to access the >bug tracker, I'm afraid. I'd appreciate knowing whether you can access the bug tracker now, Peter, if you can make the time available. I have to say that at no time has access to Mantis stopped working for me. David
Re: RISC OS NetSurf no longer responding to URI files
In article <929902e457.pnyo...@pnyoung.ormail.co.uk>, Peter Young wrote: > Many thanks, Tim, for putting me on the right road. My pleasure. -- Tim Hill Webmaster, www.timil.com websites : php : RISC OS
Re: RISC OS NetSurf no longer responding to URI files
On 15 Aug 2019 Tim Hill wrote: > In article , Peter Young > wrote: >> On 14 Aug 2019 Daniel Silverstone wrote: >>> On Wed, Aug 14, 2019 at 17:39:54 +0100, Peter Young wrote: Just to report that I can again run NetSurf URLs from NeXTBar and from MPro. Many thanks to whoever fixed this. I've been too busy to access the bug tracker, I'm afraid. >>> Unless I am very much mistaken, we have done literally nothing to >>> make that be fixed. I imagine it must have been a local hiccough on >>> your system. >> I think it must be, and it's now back to not launching URLs from >> NeXTBar and MPro. However, nothing has changed in my system. It >> remains a mystery, and I have a work-round anyway. > AIUI when URI files are run, the URI module sends a wimp message so a > loaded app can intercept it and do with the file as it wishes or the > module uses the Open_URI system variables to determine what to do. > In the case of URL files the filer does something similar. If no app has > intercepted a wimp message saying the file has been run (perhaps because > the application is not on the iconbar) the "run type" for that filetype > is examined and the appropriate action taken from that. > You can check the current settings in a command window (ctrl+f12); yours > will likely be slightly different. [snip lots of interesting stuff.] > Cure with: > 1. Trial and error. Try quitting programs and retrying. > 2. Find out which variable(s) is/are being 'broken' and use !Locate to > find the culprit obey file which is (un/re)setting it. I trialled and found the error, but didn't have time to go further with it till today. Yesterday was a long, busy but excellent day, and in the evening in spite of being tired I had a strange rush of blood to the brain. I had a VRPC laptop connected by ShareFS, and found that URLs were launched through UniServer, so this seemed to be the suspect app. I've just been experimenting, and if UniServer is quit, NetSurf launches URLs as it should do, and also used to. I now have two Obey files which I can launch from StrongMen, one to quite UniServer and one to run it, so I can switch between launching between using NetSurf and Chrome on the W10 machine. Problem more or less solved, but I still don't understand why this should have suddenly happened a few weeks ago. Something I'll never know. Many thanks, Tim, for putting me on the right road. Best wishes, Peter. -- Peter Young (zfc Hg) and family Prestbury, Cheltenham, Glos. GL52, England http://pnyoung.orpheusweb.co.uk pnyo...@ormail.co.uk
Re: RISC OS NetSurf no longer responding to URI files
In article , Peter Young wrote: > On 14 Aug 2019 Daniel Silverstone wrote: > > On Wed, Aug 14, 2019 at 17:39:54 +0100, Peter Young wrote: > >> Just to report that I can again run NetSurf URLs from NeXTBar and > >> from MPro. Many thanks to whoever fixed this. I've been too busy to > >> access the bug tracker, I'm afraid. > > Unless I am very much mistaken, we have done literally nothing to > > make that be fixed. I imagine it must have been a local hiccough on > > your system. > I think it must be, and it's now back to not launching URLs from > NeXTBar and MPro. However, nothing has changed in my system. It > remains a mystery, and I have a work-round anyway. AIUI when URI files are run, the URI module sends a wimp message so a loaded app can intercept it and do with the file as it wishes or the module uses the Open_URI system variables to determine what to do. In the case of URL files the filer does something similar. If no app has intercepted a wimp message saying the file has been run (perhaps because the application is not on the iconbar) the "run type" for that filetype is examined and the appropriate action taken from that. You can check the current settings in a command window (ctrl+f12); yours will likely be slightly different. *show *file* ... File$Type_B28 : URL ... File$Type_F91 : URI ... *show *run* ... Alias$@RunType_B28 : /SCSI::HardDisc4.$.Apps.!NetSurf.!Run -urlf %*0 ... *show *uri* Alias$Open_URI_file : /SCSI::HardDisc4.$.Apps.!NetSurf.!Run -nowin Alias$Open_URI_geo : SCSI::HardDisc4.$.Apps.!RiscOSM.!Run Alias$Open_URI_http : /SCSI::HardDisc4.$.Apps.!NetSurf.!Run -nowin Alias$Open_URI_https : /SCSI::HardDisc4.$.Apps.!NetSurf.!Run -nowin Alias$Open_URI_x-stronghelp : Run SCSI::HardDisc4.$.Apps.!StrongHlp.!Run (Some apps "wrongly" set a run type for URI files. Apparently that's not the way they should be handled) If the system isn't working there are two possible problems. 1. something loaded is discarding the wimp messages, or 2. something which may not be loaded has (un-)set the system variables Cure with: 1. Trial and error. Try quitting programs and retrying. 2. Find out which variable(s) is/are being 'broken' and use !Locate to find the culprit obey file which is (un/re)setting it. HTH -- Tim Hill Find an event to attend at: http://timil.com/riscos/calendar/ Mimemap and other stuff: http://timil.com/riscos/
Re: RISC OS NetSurf no longer responding to URI files
On 14 Aug 2019 Daniel Silverstone wrote: > On Wed, Aug 14, 2019 at 17:39:54 +0100, Peter Young wrote: >> Just to report that I can again run NetSurf URLs from NeXTBar and from >> MPro. Many thanks to whoever fixed this. I've been too busy to access the >> bug tracker, I'm afraid. > Unless I am very much mistaken, we have done literally nothing to make that > be fixed. I imagine it must have been a local hiccough on your system. I think it must be, and it's now back to not launching URLs from NeXTBar and MPro. However, nothing has changed in my system. It remains a mystery, and I have a work-round anyway. Best wishes, Peter. -- Peter Young (zfc Hg) and family Prestbury, Cheltenham, Glos. GL52, England http://pnyoung.orpheusweb.co.uk pnyo...@ormail.co.uk
New SSL alert and Login features [Help Wanted]
Hi all, 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 terms of visuals. Secondly they currently make no use of JavaScript and so 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: https://git.netsurf-browser.org/netsurf.git/tree/resources/FatMessages 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 language. 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 should go. 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. -- Daniel Silverstone http://www.netsurf-browser.org/ PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69