fieldOfView | SPi-V devFIXED: SPi-V is instable in Safari (Mac OS X)
Submitted by Aldo on October 17, 2004 - 15:54.
Users using Safari (or any other browser based on Apple's WebKit) may experience instabilities with Shockwave.
When viewing content locally in said browsers, content may render too high (even over the browser user interface). The same content will display properly when played back from a webserver.
Depending on available system resources, Safari may crash after displaying the content for a while. The same content played back using the standalone viewer application or in a different browser such as the Mac OS X version of FireFox is stable.
These fenomena are due to an incompatibility between WebKit and Shockwave, which is unfortunately out of our hands.
Content in Safari
The fix I had in place to fix the content rendering too high bug was broken, but is fixed now. In all honesty, I hadn't had a chance to test the fix before, but I did now.
You should no longer see the content rendering over the browser ui. You will still see a strip of ~20 pixels at the bottom of the display where the viewer can not draw. That's an unfortunate sideeffect of the fix.
The fix unfortunately won't work on local content; if you open SPi-V content in Safari from your harddisk, the content will render too heigh.
Hmmm? No change?
Hi,
i tried to view the same page in thre Browsers (online - not from the harddisk):
Safari (1.2.4), Camino (2004051715 (v0.8b)) and IE (5.2.3) - from top to bottom.
(See the result under: http://www.360pixel.de/fov/browsers.jpg)
Test with your browser: http://www.360pixel.de/fov/ac-test2.html
The only Browser displaying the page correctly was IE.
In the others the content is still (much) too high...
Will this be changed in future versions?
some change...
The Safari one is 'the way it is supposed to look in Safari'. I know that kind of sucks, but it used to be worse. I fixed it so the content isn't rendering too heigh in the window (it used to draw over the Safari UI like Camino), but unfortunately I cannot make it fill the entire frame like IE and Firefox do. Macromedia are telling me it's a thing Apple has to fix, there's nothing I can do about that.
Never tried the engine in Camino. It used to look like that in Safari too. Is Camino used much at all? I'ld think people be dropping that for Firefox, if not for Safari. I could look into applying the same fix I applied to Safari to Camino,
but at this point I'ld rather focus my attention to some other issues. Unless you convince me Camino is the next big thingTurns out Camino isn't as dead as I thought it was ;-) I'll get back to this...BTW, Omniweb should work ok, since it uses the same HTML rendering engine as Safari.
No - STOP
Hi,
NO - that is not what i wanted to say: i just tried Camino because i had it on my harddisk... i was not using it since Safari came out.
Safari is alive - i do not know anything excact about Camino...
Offset problem fixed in SPi-V 1.3
The offset problem fixed in SPi-V 1.3 and the lastest version of Safari running on OS X 10.4 (Tiger).
The stability issues remain on Macs, but appear to be limited to those with low video memory capabilties (32 Mb)