Sam wrote: >The JavaScript was the problem >because it was calling for graphics to be loaded in some way not tolerable >to Arachne. But Arachne doesn't (yet) handle JavaScript. The problem was that instead of loading an image JavaScript was used (that JavaScript would then tell the JavaScript capable browser what image to load). Fixing https: and problems like it with images on pages (such as JavaScript, cid: also comes to mind) should be rather straightforward. However I kind of lack the latest source (hint hint). //Bernie
- Re: 1.70R3: Endless loop of "verifying images"... Samuel W. Heywood
- Re: 1.70R3: Endless loop of "verifying images"... L.D. Best
- Re: 1.70R3: Endless loop of "verifying images"... L.D. Best
- Re: 1.70R3: Endless loop of "verifying images"... Samuel W. Heywood
- Re: 1.70R3: Endless loop of "verifying images"... Glenn McCorkle
- Re: 1.70R3: Endless loop of "verifying images"... L.D. Best
- Re: 1.70R3: Endless loop of "verifying images"... Samuel W. Heywood
- Re: 1.70R3: Endless loop of "verifying images"... L.D. Best
- Re: 1.70R3: Endless loop of "verifying images"... Joerg Dietze
- Re: 1.70R3: Endless loop of "verifying images"... Glenn McCorkle
- Re: 1.70R3: Endless loop of "verifying images"... Bernie
- Re: 1.70R3: Endless loop of "verifying images"... Samuel W. Heywood
- Re: 1.70R3: Endless loop of "verifying image... Neil Parks
