Replacing "#" with "%23" results in an url that passes successfully without modification (through the iPhone and carrier - still don't know where the urlEncoding is being done) to the Google maps API, but "%2300ff00" will break Google's RGB-to-HSL calculation.
This means that the tiles will appear if "%23" is used, but they will be tiles affected only by 'saturation', 'lightness' and 'gamma' style options. On Aug 25, 1:15 am, "Thor Mitchell (Google Employee)" <[email protected]> wrote: > Just out of curiosity, on the devices on which the styled map does not > work, what happens if instead of specifying your hue as '#00ff00' in > your app you specify it as '%2300ff00'? > > Just wondering if the devices concerned are not URL encoding the # as > they should, perhaps because the # character is permitted in URLs, but > only as the fragment separator. > > Thor. > > On Aug 23, 5:14 pm, William <[email protected]> wrote: > > > > > On Aug 23, 4:52 pm, Sefu <[email protected]> wrote: > > > > Using iPhone's Safari (after cleaning the > > > iPhone cache of course), when I follow the single-tile 'hue active' > > > links on the aforementioned 'issues' page (http://code.google.com/p/ > > > gmaps-api-issues/issues/detail?id=2657), I get a 'bad request' error. > > > just to confirm, this 'bad request' error is the http 400 error > > message from the google tile server, which looks like this? > > > Google Error > > Bad Request > > Your client has issued a malformed or illegal request. > > > ... -- 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.
