maps version 3.17 and 3.18 exceptions

136 views
Skip to first unread message

Blaze

unread,
Dec 7, 2014, 7:39:41 AM12/7/14
to google-map...@googlegroups.com
Hi, 

Since 3.16 was retired and 3.17 become the frozen one, I experience some bugs in the maps js scripts.

I load my application usually with v=3.0 which is getting the oldest version. After nov 18 when v=3.0 started to serve 3.17 instead of 3.16 i see this in the console of chrome and firefox:

google.maps.version:     "3.17.18"

Uncaught TypeError: Cannot set property 'J' of undefined          VM6685:6 Uncaught TypeError: string is not a function                      VM6687:9 Uncaught TypeError: Cannot set property 'I' of undefined          VM6687:9 

or this

Uncaught TypeError: Cannot set property 'I' of undefined          VM10904:9  
Uncaught TypeError: string is not a function                      VM10976:6


same happens for 3.18


google.maps.version:     "3.18.16"

Uncaught TypeError: Cannot read property 'push' of undefined      VM6962:86 

or this

Uncaught ReferenceError: L is not defined                         VM7192:4 
Uncaught ReferenceError: So is not defined                        VM7194:6 
Uncaught ReferenceError: L is not defined                         VM7196:9


The outcome of the exceptions: sometimes the full map is not rendered, other time no markers or no polylines. Sometimes if a lot of page refreshes are done,all looks ok

Very strange...  


Just forgot to add that there is no exception and all works ok on version 1.19.2, but ofcourse I dont like to live on the edge....

Enoch Lau (Google Employee)

unread,
Dec 7, 2014, 10:39:36 PM12/7/14
to google-map...@googlegroups.com
Please link to a demo that illustrates the problem.

Nianwei Liu

unread,
Dec 8, 2014, 2:35:50 PM12/8/14
to google-map...@googlegroups.com
In my experience if you have used DOM tree access in your code, for example, get a DIV and look for it's children or parent to do something, you may have some issues because some of the version put in/took away additional DIV wrappers, in my case the there is an additional DIV put outside the infoWindow container in 3.18 causing some of position offset calc wrong.  

Blagoja Chavkoski

unread,
Dec 8, 2014, 7:24:33 PM12/8/14
to google-map...@googlegroups.com
Hi, tnx for the replay.

I use a lot of features, polylines markers, editable dragable custom overlays etc, and I havent touch the code since couple of years(Ill need to do some digging to see if back then I do some manipulation on the DOM itself also... ).
Dont know if I can narrow down to some small snippet of code, the problem for doing this is that I use gwt wrapper which I have written for this app. I havent had any problems till now, and also in the moment I run the app without problem on v1.19.2.
Really strange...

What has changed from 1.16 to 1.17 and 1.18 which is not changed in 1.19 ? there is way where u can narrow it down for me? Maybe to tell me where to search more eg iMarkers area or polylines or etc....? 

Tnx
Blaze

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-maps-js-a...@googlegroups.com.
To post to this group, send email to google-map...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-maps-js-api-v3.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages