[Google Maps API v2] Re: GOpenInfoWindowHtml bug or feature?

On Mar 5, 3:32 am, Fairy <nonstopfa...@gmail.com> wrote about browsers
replacing &lt with <:

While you are right about the standard (a semi-colon is necessary),
you can't assume that browsers will always follow the HTML standard
within urls. This isn't an API thing, it's a browser thing.

However, while one could argue that the browser is at fault, you're
not helping. When including an ampersand in a url, you should encode
that. Urls should never have an unencoded ampersand in them, because
an ampersand should always be treated as starting an entity. Using
&amp;lt is *not* a workaround: it's what you should use.

The workaround would be to use a variable name which is not an entity.
&lat= would be interpreted in the way you want it to be.

--
You received this message because you are subscribed to the Google Groups "Google Maps API V2" group.
To post to this group, send email to google-maps-api@googlegroups.com.
To unsubscribe from this group, send email to google-maps-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.