On Dec 17, 12:47 am, Ben Appleton <[email protected]> wrote: > I have just submitted fixes and automated tests to ensure that in future we > do not leak any obfuscated properties on non-final classes, ie. MVCObject > and OverlayView. These fixes should go out with the next release. However > the next scheduled release is 3 weeks away since many people are on > vacation, so let's consider workarounds for the meantime.
Thanks Ben, Actually, I fixed it yesterday. I am not using an obfuscator. "L" is the actual variable name. I have moved all single character variables to properties of the same parent object. "this.L" is "this._.L." Ditto for the others. I use "var _=this._;" to reduce the code size. I am assuming I can use "this._" safely. I must make similar changes to "sparsetile.js". You must have moved some of your code into an iframe. Otherwise, I do not understand the sudden appearance of the many security violations. I use "this.A" also. It receives an error message too. Thanks again for your help. -- 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 [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.
