On Aug 22, 6:54 pm, Sefu <[email protected]> wrote: > ...that makes perfect sense, and that is no doubt the source of the > problem exactly. But who to send it to: carrier or Google? > I'm not certain that's the problem, but I think you should report the issue to google on the issue tracker, using a single styled url containing a hue, with a version of the map that has # and another version without the #. That would allow easy replication of the problem for google engineers.
http://code.google.com/p/gmaps-api-issues/issues/entry?template=Maps+API+v3+-+Bug It's difficult to report to the carrier because you saw different behaviour when you directly visited the url as a link on the browser, compared to the api usage of the url, as a background-image of a div style using the url("...") syntax. ... -- 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.
