Fixed
Status Update
Comments
ka...@gmail.com <ka...@gmail.com> #3
Example 1. Just trying to attach your gmaps script.
If you open the developer console, you will see that gmaps init script is loaded, but "getScript("https://maps.gstatic.com/intl/en_us/mapfiles/api-3/9/8/main.js ");" line isn't working, there is no new script in the document after document.write.
If you open the developer console, you will see that gmaps init script is loaded, but "getScript("
[Deleted User] <[Deleted User]> #4
Example 2. Trying to use callback parameter. Init is loaded, main javascript file is loaded too. But not working, exception screenshot is in attach.
de...@gmail.com <de...@gmail.com> #5
For example 2 - your code:
...
lf.main = function(a) {
eval(a); // <-- Uncaught Error: Code generation from strings disallowed for this context
};
...
...
lf.main = function(a) {
eval(a); // <-- Uncaught Error: Code generation from strings disallowed for this context
};
...
de...@gmail.com <de...@gmail.com> #6
Just to poke this bug, using the asynchronous loading method has no effect on this. The only workaround is to roll back to manifest version 1 which is actively being phased out.
en...@google.com <en...@google.com> #7
Switched to Yandex Maps, it works well.
Thank you!
Thank you!
cs...@google.com <cs...@google.com> #8
As manifest version 1 won't be accepted by the Chrome Webstore starting in mid August, we really do need a workaround/fix.
cs...@google.com <cs...@google.com> #9
As I discovered a few minutes ago, manifest version 1 is no longer accepted by the Chrome store *now*. So setting the manifest version to 1 and using 'unsafe-eval' in the CSP no longer works for new extensions.
Updating existing extensions may still be supported.
Updating existing extensions may still be supported.
[Deleted User] <[Deleted User]> #10
New packaged apps having manifest version 1 are no longer supported.
Please fix this issue as soon as possible.
Thanks
Please fix this issue as soon as possible.
Thanks
Description
I'm getting the below error <b><i>most of the times</i></b> on every attempt to drag the map, after displaying a dynamically constructed polygon.
Error : <em>"Uncaught TypeError: Cannot read property 'x' of undefined" </em>
To replicate my problem :
1. Disable the map's draggable attribute
2. Allow user to trace a shape on the map, use the coordinates to dynamically construct and show a polyline.
3. When the tracing is done, construct a polygon using the path set to the above polyline and remove the polyline
4. Enable the map's draggable attribute
5. Now try to drag the map
Error/Consequence : The above mentioned error is displayed on the browser console several times. The map is not draggable.
jsFiddle : <a rel="nofollow" href="
(If using this jsFiddle, click on "Start Drawing" and trace on the map to display the polyline followed by the polygon. Now try to drag the map)
On Android browser, the error points to line# 180 of my html file (irrespective of the html file length) (but I cant check what that line is)
On the iPad emulation of Chrome on desktop, the error points to the below line of a google maps API js file (whose name changes on every page load). The error line is :
<code>g("center");H.bh=cg("center");H.Gf=bg("latLngCenter");H.ph=bg("projectionBounds");H.Df=bg("projection");H.getLatLngBounds=md("k");H.Hm=bg("fixedPoint");function lx(a,b){this.min=a;this.max=b}function mx(a,b){return b<a.min?a.min:b>a.max?a.max:b};function nx(a){this.d=a}L(nx,P);nx[F].immutable_changed=function(){var a=this,b=a.get("immutable"),c=a.b;b!=c&&(Id(a.d,function(d){(c&&c[d])!==(b&&b[d])&&a.set(d,b&&b[d])}),a.b=b)};function ox(a,b,c){Bn(this,a);this.b=b;
Browser & OS used:
1) Android browser on Android phone/tablet
2) iPad emulation of Chrome browser on desktop (closest I could get to an iPad+Mac combination)
API version :
Latest google maps API version (3.exp)
Temporary fix :
Introducing a delay of 1500ms before performing step #4 above is helping eliminate the map freezing and the error in the console, but makes the appln feel slower than it truly is.
Thanks in advance.
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************