I don't see how it can be anything else than the "%" character in the tile request URL - we've eliminated all other possibilities (the '|' causes no problems for sure). I think it may have something to do with mobile providers applying the same encoding protocols they use for SMS to all network traffic... a practice both lazy and cro-magnon by today's standards IMHO.
I've submitted an issue - please find it here: http://code.google.com/p/gmaps-api-issues/issues/list ...it has yet to be approved, but let's see how it goes ; P Thanks again for all your help. On Aug 22, 11:08 am, William <[email protected]> wrote: > 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+... > > 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.
