I was having a problem this afternoon with some debugging. I typically disable
cache in the developer menu, and use private browsing. nevertheless, I would
make a change in my code and the change was not reflected in the browser
reload. In fact, I had a line that called on a nonexistent function. I
deleted the line, but it kept appearing in the error messages. Somehow, Safari
was caching when it was not supposed to be. I did not have time to explore it
further, but will tomorrow and see if I can reproduce it. I did not try
loading with Firefox and then again with Safari.
On Dec 30, 2013, at 7:48 PM, Otis Rothenberger <[email protected]> wrote:
> Phil,
>
> Exactly. That's what I'm thinking. Safari won't cache it, but it will pull it
> from cache.
>
> Otis
> --
> Otis Rothenberger
> [email protected]
> http://chemagic.com
>
>
>
>
> On Dec 30, 2013, at 7:28 PM, J. Philip Bays <[email protected]> wrote:
>
>> I would think that they both rely on the java console. I wonder what is
>> going on with that?
>>
>>
>> On Mon, Dec 30, 2013 at 4:27 PM, Robert Hanson <[email protected]> wrote:
>> It appears that Safari has a very strange "feature" -- at least on my
>> machine, everything works fine using http, but with file://, if I download
>> Jmol, open the zip file, extract the jsmol directory, and start simple2.htm,
>> and immediately clicking on the "Signed" link to get the signed version, the
>> applet fails to load.
>>
>> However, if I first open the applet in Firefox, then Safari will open it.
>> If Safari has opened the file, and I change the directory name, then the
>> next time I try this, Safari will not start the applet. However, if I then
>> open that local page in Firefox and then try again in Safari, all is good.
>>
>> What could possibly be going on? I don't know. But the fact that this is a
>> new problem suggested to me that it's something recent. I remembered that
>> recently I changed Safari settings to using the <applet> tag instead of
>> <object>. Well, guess what? When I switch back to using the <object> tag,
>> everything works normally. No directory problems; no load issues. Go figure.
>>
>> For whatever reason, it looks like we cannot use the <applet> tag in Safari.
>> I'm sure I had a reason for switching to that, but I can't remember that.
>>
>> Bob
>>
>>
>>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk_______________________________________________
> Jmol-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jmol-users
Philip Bays
Emeritus Professor of Chemistry
Saint Mary's College
Notre Dame, IN 46556
[email protected]
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
