On 9/15/2011 2:04 PM, Philip TAYLOR (Webmaster, Ret'd) wrote:
cmcadams wrote:
Sorry about that. Maybe it is all bugs and angst. Check if there's a newer
video driver (direct from the chipset vendor, eg nVidia, not the card
manufacturer).
about:config webgl.force-enabled -> true appears to suffice :
I wonder why it is necessary ?
Its necessary because the driver/hardware combo you have is faulty in
one of possibly many ways.
It could be security flawed, allowing a code escalation at the driver
level in your driver. It could be graphic corruption level, causing your
screen display to misbehave (even outside of Firefox/SeaMonkey bounds).
It could be graphic escalation leakages, allowing SeaMonkey (and the
webpage) to send "back to server" information from other parts of your
screen and other open applications.
It could be simply crashy, causing many instability issues when coupled
with WebGL.
All of those reasons is why we block graphics/hardware. We do allow the
force_enabled for those cases where a developer/user wants to hack
around restrictions, or try to fix them at the Gecko Software Level. As
well as for when a website designer wants to utilize WebGL but his own
hardware wants to be blocked.
--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
