Street View issue with Firefox 5

252 views
Skip to first unread message

Epizentrum

unread,
Jun 18, 2011, 6:03:30 AM6/18/11
to Google Maps JavaScript API v3
Hi, in http://www.dafmap.de, FF5 does not show the Street View tiles.
It throws the following exception for each tile it wants to load:

uncaught exception: [Exception... "Failure arg 5
[nsIDOMWebGLRenderingContext.texImage2D]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
http://maps.gstatic.com/intl/de_de/mapfiles/api-3/4/14/main.js ::
RD :: line 78" data: no]

Known issue with FF5? Is there a workaround? It works with Safari 5 on
Mac OS X. I haven't checked other browsers/OSes, yet.

en4ce

unread,
Jun 19, 2011, 8:29:11 AM6/19/11
to Google Maps JavaScript API v3
Firefox 5 is still in beta so this can happen, i suggest to make a bug
report

On 18 Jun., 12:03, Epizentrum <epizent...@googlemail.com> wrote:
> Hi, inhttp://www.dafmap.de, FF5 does not show the Street View tiles.

Epizentrum

unread,
Jun 19, 2011, 11:25:06 AM6/19/11
to google-map...@googlegroups.com
Problem solved. It works fine with the latest Maps API (v3.5). v3.4 still has the problem, so don't use it with FF5. Thanks for the feedback!

Scott Davis

unread,
Jun 21, 2011, 5:53:48 PM6/21/11
to Google Maps JavaScript API v3
I'm still getting essentially the same error message even after
upgrading to version 3.5 of the Google Map API. Any other ideas?

My error message:
uncaught exception: [Exception... "Failure arg 5
[nsIDOMWebGLRenderingContext.texImage2D]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
http://maps.gstatic.com/intl/en_us/mapfiles/api-3/5/6a/main.js ::
iG :: line 80" data: no]

I get all of the controls on the screen, just no images.

Stephan Bardubitzki

unread,
Jun 22, 2011, 12:24:05 AM6/22/11
to google-map...@googlegroups.com
Same here.

Reported to Mozilla as well.


--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.


msikma

unread,
Jun 22, 2011, 11:10:21 AM6/22/11
to google-map...@googlegroups.com
Could you link to your bug report to Mozilla? Would be useful to see what they have to say. I'm including the API through http://maps.google.com/maps/api/js?sensor=false which at this moment loads version 3.5.7 of the API: still no luck. Haven't figured out a workaround yet.

Grok Lobster

unread,
Jun 22, 2011, 8:16:46 PM6/22/11
to Google Maps JavaScript API v3
Works for me with this map.

http://greg-koppel.site88.net/maps/SBStyleMap.html

On Jun 22, 8:10 am, msikma <mich...@wedemandhtml.com> wrote:
> Could you link to your bug report to Mozilla? Would be useful to see what
> they have to say. I'm including the API throughhttp://maps.google.com/maps/api/js?sensor=falsewhich at this moment loads

Mike Robbins

unread,
Jun 23, 2011, 12:00:07 AM6/23/11
to google-map...@googlegroups.com
not for me, the map works but not the streetview

Mike Robbins

unread,
Jun 23, 2011, 12:30:45 AM6/23/11
to Google Maps JavaScript API v3
I thinkit has to do with webGL. disable webGL in ff5 and streetview
works, enable webGL and not so much. The little I know is that V3 api
will use webGL if available. and so, would it then follow that cross
domain restrictions would apply on images used for textures?

Luke Mahé

unread,
Jun 23, 2011, 1:02:07 AM6/23/11
to google-map...@googlegroups.com
Thanks for reporting this. We will be disable WebGL in FF5 soon.

-- Luke

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.

msikma

unread,
Jun 24, 2011, 4:31:34 AM6/24/11
to google-map...@googlegroups.com
Looks like it works again. Thanks!

Mike Robbins

unread,
Jul 18, 2011, 7:21:38 PM7/18/11
to Google Maps JavaScript API v3
Hey Luke or other Google folk. do you have any timeline on when (or
if!) webGL will be re-implemented for the V3 api. I'm taking a wild
guess that this might hinge around CORS adoption? will this happen?
are there any other factors that might play in happening or not?
Thanks.
Reply all
Reply to author
Forward
0 new messages