Might be more robust to just deliver console.html through jhs? Then again, if you are after educating people about current browser pitfalls, the way you have it might be good.
Thanks, -- Raul On Fri, Mar 21, 2014 at 1:00 PM, Brian Schott <[email protected]>wrote: > Raul, > > I had not thought of this perspective and it seems valid. In my recent > efforts regarding the turtle graphics app I have produced 2 different > 3-frame browser interfaces and one of them requires a browser accessing the > local file console.html . I wonder if I need to post some sort of warning. > > > On Fri, Mar 21, 2014 at 12:23 PM, Raul Miller <[email protected]> > wrote: > > > There's a problem with the concept of the browser accessing local files. > > > > Let's say you visit a page on the internet and the owner of that page > wants > > access to files on your computer. Just put a file url in there and you > can > > get some access to well known files. And this leads to a cascading chain > of > > security issues. So finally people just give up in disgust and turn of > file > > urls. > > > > A on this suggests people download a file and use it locally. So even > when > > file urls are enabled they often have constraints on what directories can > > be visited. > > > > People make mistakes and then get upset at the wrong people because of > the > > consequences, which tends to ruin things for everyone. > > > > Thanks, > > > > -- > > Raul > > > > > > > > > -- > (B=) > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
