Bob,
I cleaned my FF problem out so that there would not be any confusion. My issue
was related to a known FF bug with document.execCommand. Easy solution was to
opt FF out on the commands that were related to object resizing. This was not a
Local Storage issue as I originally thought.
With the above problem removes, here is FF errors - not seen on Chrome of
Safari. The first is the familiar omnipresent FF depreciation warning:
MLHttpRequest on the main thread is deprecated because of its detrimental
effects to the end user's experience. For more help http://xhr.spec.whatwg.org/
jquery.min.js:4:0
not well-formed package.js:1:1
syntax error corejmol.z.js:1:1
syntax error UnknownServiceException.js:1:1
syntax error JmolBinary.js:1:1
syntax error PrecisionRenderer.js:1:1
JSmol exec jmolApplet0 start applet null -- OK JSmol.min.nojq.js:82:366
(not an error)
syntax error corescript.z.js:1:1
not well-formed methane.txt:1:6
syntax error coretext.z.js:1:1
syntax error PropertyManager.js:1:1
syntax error coreprop.z.js:1:1
Otis
--
Otis Rothenberger
o...@chemagic.com
http://chemagic.com
On Aug 25, 2015, at 3:30 PM, Otis Rothenberger osrot...@chemagic.com wrote:
Paul and Bob,
Chrome appears OK for me. Firefox is whining about a whole mess of syntax
errors in various Jmol .js files. I must admit that FF is becoming a real
pain for me. I haven’t checked for a while. I see it’s having problems with
my Local Storage error catching, but that’s unrelated to the various Jmol .js
syntax errors. I can fix that.
I show the Developer menu on Safari. That’s how I access the JavaScript
console. It’s also where I turn off local file restrictions. This Developer
menu item does not show by default.
Again, just to be clear. I am running double click .htm from my desktop - no
server. I run with an Internet connection because my locally run page
interacts with Internet data sources.
I guess I should also mention that I’m running JSmol.min.nojq.js
The Chrome that seems to be behaving for me is Version 44.0.2403.157
(64-bit). Since I’m running local files, I use a terminal start-up to allow
this.
Otis
--
Otis Rothenberger
o...@chemagic.com
http://chemagic.com
On Aug 25, 2015, at 2:46 PM, Paul PILLOT paulpil...@gmail.com wrote:
Thanks Otis,
I am also running pages from my local web server (localhost). I haven’t
spotted the setting you are referring to.
I have made further tests with firefox 40 and Chrome 44.
The three browsers give the same consistent error messages (that don’t
prevent jsmol from working).
Paul
Le 25-08-2015 à 14:34, Otis Rothenberger osrot...@chemagic.com a écrit :
Bob and Paul,
I’m not seeing this (below) in MacOS X 10.10.4 (Yosemite) and Safari 8.0.7.
I should mention that I’m running locally with internet connection - i.e.
all my AJAX remote calls working.
This means that I run Safari with “Disable Local File Restrictions” checked.
Otis
--
Otis Rothenberger
o...@chemagic.com
http://chemagic.com
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
