Polylines invisible in Firefox and Chrome, polylines are present in map.

[kreditt]

I've got a problem with my polylines which are not showing up in firefox 4 or in chrome, they are working fine in internet explorer 7 and 8.
Link to the map is here: http://aventit.com/flight/mapajax.php

The problem suddenly appeared today, I've had no such problem earlier.

The polylines are actually present, the "mouseover" infobox pops up when I'm over the "invisible" line, and a div shows up when I click it.
I've gone through my code over and over without finding anything that could cause this.
You need to choose an airport or airline in the bottom to get the polylines and markers to show.

Any ideas

[Andrew Leach]

On 13 April 2011 11:22, kreditt <kredi...@gmail.com> wrote:
>
> Any ideas

Use a specific version (eg 3.3) instead of the nightly build. What
happens if you do that?

[kreditt]

It's actually working by using 3.3.

Thank you very much.

[Andrew Leach]

On 13 April 2011 11:40, kreditt <kredi...@gmail.com> wrote:
> It's actually working by using 3.3.
>
> Thank you very much.

You're very welcome :-) Actually you may consider raising an issue
against today's version of the API.

Include as much detail as possible (eg browser versions), and provide
a demonstrator page (doing that should be easy). Make sure your report
also includes the date!

[en4ce]

yeah because else you always have to stick to 3.3, so switching
version back is not the best solution

On 13 Apr., 12:53, Andrew Leach <andrew.leac...@gmail.com> wrote:

[geoco...@gmail.com]

On Apr 13, 6:51 am, en4ce <djen...@googlemail.com> wrote:
> yeah because else you always have to stick to 3.3, so switching
> version back is not the best solution

And eventually v3.3 will be "retired" (like Version 3.0 and 3.1 have
been retired)
http://code.google.com/apis/maps/documentation/javascript/basics.html#VersionTypes

-- Larry

[en4ce]

haha, thats the Cherie on top :-P

On 13 Apr., 16:13, "geocode...@gmail.com" <geocode...@gmail.com>
wrote:

> On Apr 13, 6:51 am, en4ce <djen...@googlemail.com> wrote:
>
> > yeah because else you always have to stick to 3.3, so switching
> > version back is not the best solution
>
> And eventually v3.3 will be "retired" (like Version 3.0 and 3.1 have

> been retired)http://code.google.com/apis/maps/documentation/javascript/basics.html...

[Andrew Leach]

On 13 April 2011 15:13, geoco...@gmail.com <geoco...@gmail.com> wrote:
>
> And eventually v3.3 will be "retired" (like Version 3.0 and 3.1 have
> been retired)
> http://code.google.com/apis/maps/documentation/javascript/basics.html#VersionTypes

Yes. That's why it's important to raise an issue, so it doesn't get
retired before the problem with the next version is fixed. For the
moment, though, to get the live site to work correctly it's necessary
to specify a version which works.

[Brad]

Hey was just alerted to this post - I had a similar issue with the PHP Google Maps API class that I'm managing (http://code.google.com/p/php-google-map-api/ ) and was alerted to a similar situation today with polylines no longer rendering in FF but working in IE.  Here's the post on our FB wall - http://www.facebook.com/permalink.php?story_fbid=208449602506084&id=121455857872126 , but in short, at least for my implementation, it was due to me using "css compliant" color names instead of the full hexadecimal values (AKA: color:"red" instead of color:"#FF0000")  - I checked out the page you linked in question, and I noticed that the color value you are passing is #000 - I have a sneaking suspicion that if you change that value to #000000 , you're polylines will start rendering again.  This is obviously an issue with the API as a css compliant color declaration shouldn't just stop working, but for some reason that appears to be the case.  Let us know if this helps at all, I'm certainly interested to know if that's the cause.

[kreditt]

Your suspicion was correct, I tried with a full hex color code and the polylines did show up, but not with the "css compliant" codes,
the "css compliant" color codes have been working the whole time I've been working on this project. (for about a week now).

My guess is there have been some change in the API affecting the color codings, the question is if there are other functions also affected by this?

[Carolyn Grabill]

I had the same experience today with disappearing polylines, and changing "blue" to "#0000ff" was the solution for me, too. Thanks for posting the solution.

[Chris Broadfoot]

Yes, polygons are now rendered in Canvas where possible.

As specified in documentation, full hex style is necessary.

--
http://twitter.com/broady

[Chris Broadfoot]

As I said in another thread, polys are now rendered in Canvas. I've filed a bug to support shorthand colors, though I'm not sure if we could support opacity when using color names like 'red' or 'blue'.

As per documentation, please use full hex notation (e.g. #ff0000) when specifying colors:

http://code.google.com/apis/maps/documentation/javascript/reference.html#PolylineOptions

Chris

--
http://twitter.com/broady