Open GoogleCodeExporter opened 9 years ago
Hi,
I can see the globe in Firefox 4.0 and chrome 9+, It is not to be sceen in
Firefox 5.0
Regards,
Siddharth
Original comment by SIDS...@gmail.com
on 4 Jul 2011 at 11:32
It is probably due to the recent WebGL policy of not admitting textures from a
different domain. I think the security risk that triggered the policy is
exaggerated but the standard has imposed the limitation anyway (cross domain
images have been at the core of the Web almost always).
I guess systems like this one should add something like a tunneling mechanism
in the server side that redirects requests to map providers so that textures
seem to come from the same domain as the app. I don't think the standard method
for allowing cross-domain textures is not usable here.
Original comment by alvaro.s...@gmail.com
on 7 Aug 2011 at 12:00
Hi Alvaro,
Thanks for the reply
Regards,
Siddharth
Original comment by SIDS...@gmail.com
on 8 Aug 2011 at 12:17
See
http://hacks.mozilla.org/2011/06/cross-domain-webgl-textures-disabled-in-firefox
-5/
The cross-domain security restriction on WebGL textures also seems to apply in
the current Chrome release.
Very annoying!
Original comment by gerg.bowering
on 21 Aug 2011 at 11:03
I too can not see the globe.
I am using Win XP with Sp3 on Intel core 2 duo system with Intel GMA G31/33 chipset.
Graphics drivers are updated to the latest.
Other WebGL samples are running fine. But for this sample i don't see the globe.
The errors i see through inspect element in Chrome are:
uncaught error: could not initialize shaders - api.js : 1
failed to load resource
uncaught error: Cannot read property 'a' of null - api.js : 50
Thanks in advance.
Original comment by ramkumar...@gmail.com
on 27 Aug 2011 at 6:24
Original issue reported on code.google.com by
SIDS...@gmail.com
on 29 Jun 2011 at 4:13