Fixed
Status Update
Comments
ry...@gmail.com <ry...@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("
ma...@gmail.com <ma...@gmail.com> #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.
ar...@gmail.com <ar...@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
};
...
zw...@google.com <zw...@google.com>
ar...@gmail.com <ar...@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.
zw...@google.com <zw...@google.com> #7
Switched to Yandex Maps, it works well.
Thank you!
Thank you!
ar...@gmail.com <ar...@gmail.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.
Description