Anyone who can deal with the new manifest ver. 2 of Google extensions especially for Google Maps App? The problem is with the new policy you need to use HTTPS for the hosts that you use javascript code from like Jquery.com. In addition you need to write the names of the sites on manifest file asindicated<http://developer.chrome.com/stable/extensions/contentSecurityPolicy.html> .
These are all good but when you type the google map addresses you get the JS code and the map images on manifest file as script-src 'self' https://maps.googleapis.com; connect-src https://maps.googleapis.com; img-src 'self' https://maps.google.com";, (this is the format that is in use Google's example extension), another problem is occuring. The extension cannot connect to https://maps.gstatic.com/intl/en_us/mapfiles/api-3/9/13b/main.js because of the CSP. However if I also include *https://maps.gstatic.com* in manifest file as well then it gives another problem about the *main.js* comes from the address. "I try to use a Google product in a Google product but I guess there is a flaw about Google in it self" If you have any suggestion or any think you know might be useful for me. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/EKSlYJTR_xMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
