Issue displaying Yellow Pushpins in Firefox 18

[GoogleCodeExporter]

Good afternoon.

The issue is as follows: Yellow pushpins are not being shown on map, although 
their shadows are.

I am currently using trunk version of all scripts, on the following urls:

This issue currently occurs with Firefox 18.0.2. Pushpins display correctly in 
IE 9 and Chrome 24.

Operating system is Windows 7 Home Edition, 64-bit.

See attached screenshot for example of issue.

Please advise.

Best regards,
Hugo Durana

Original issue reported on code.google.com by hugo.dur...@gmail.com on 12 Feb 2013 at 2:03

Attachments:

• [Sample Firefox 18.png](https://storage.googleapis.com/google-code-attachments/geoxml3/issue-80/comment-0/Sample Firefox 18.png)

[GoogleCodeExporter]

1. The trunk is old an not supported.  Please try either the polys or the kmz 
branch.
2. Where are your icons? 
3. What does your KML look like?  Can you either attach a sample file (that 
exhibits the problem) or provide a link to a file that is publicly available on 
the web.

Attaching your HTML or a live link to your map would be helpful also.

This map displays yellow pushpins:
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmltest_stylemap_marker.html?f
ilename=http://www.geocodezip.com/geoxml3_test/rollover_kml.xml

Original comment by geocodezip on 12 Feb 2013 at 2:43

[GoogleCodeExporter]

Original comment by geocodezip on 12 Feb 2013 at 2:44

• Changed state: NeedsMoreInfo
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Good afternoon and thank you for replying so fast.

1. The urls I am currently using are as follows:
<script type='text/javascript' 
src='http://geoxml3.googlecode.com/svn/branches/kmz/ZipFile.complete.js'></scrip
t>
<script type='text/javascript' 
src='http://geoxml3.googlecode.com/svn/trunk/ProjectedOverlay.js'></script>
<script type='text/javascript' 
src='http://geoxml3.googlecode.com/svn/branches/kmz/geoxml3.js'></script>

2. Regarding icons, the said icon I believe to be the one mention in the KML 
file (see attachment file.kml)

3. I am currently maintaining an app that uses KMZ files (see attachment 
file.kmz). The app displays markers correctly in IE9 and Chrome 24, but in 
Firefox 18.0.2 gives me that strange input.

I have no current public site for you to access.

Thanks once again for helping out.

Best regards,
Hugo.

Original comment by hugo.dur...@gmail.com on 12 Feb 2013 at 3:29

Attachments:

• file.kml
• file.kmz

[GoogleCodeExporter]

Looks to be an issue in how Firefox handles images and the kmz branch.

(tested with Firefox 11 on linux)
This works in (polys branch):
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmltest_linktoB.html?filename=
http://www.geocodezip.com/geoxml3_test/geoxml3_issue80_file.kml

This doesn't (kmz branch):
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_linktoB.html?filename=
http://www.geocodezip.com/geoxml3_test/geoxml3_issue80_file.kml

Original comment by geocodezip on 12 Feb 2013 at 4:26

• Changed state: Accepted

[GoogleCodeExporter]

Good afternoon,

Your KMZ Sample is exactly what happens to me. Any ideas on how can I fix this?

Best regards,
Hugo.

Original comment by hugo.dur...@gmail.com on 12 Feb 2013 at 4:34

[GoogleCodeExporter]

Looks like the problem is scaling (the kml works if I set scale to 1.0):

http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_linktoB.html?filename=
http://www.geocodezip.com/geoxml3_test/geoxml3_issue80_fileB.kml

might be an issue with the API.  

A possible workaround is to not use scaling.

Original comment by geocodezip on 12 Feb 2013 at 4:39

[GoogleCodeExporter]

Works with scaling set to 1.0 (at least in Firefox 11):

http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_linktoB.html?filename=
http://www.geocodezip.com/geoxml3_test/geoxml3_issue80_fileA.kmz

Original comment by geocodezip on 12 Feb 2013 at 5:01

[GoogleCodeExporter]

I confirm that the link in post #7 also works with Firefox 18.0.2 and in Opera 
12.14 (the latter also presented the same issue as before).

Well, thanks anyway for all the help. Guess I'll have to find an icon that 
doesn't look so bad :)

Original comment by hugo.dur...@gmail.com on 12 Feb 2013 at 5:14

[GoogleCodeExporter]

Possible fix (not checked in to the archive):

http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_linktoB_local.html?fil
ename=http://www.geocodezip.com/geoxml3_test/geoxml3_issue80_file.kml

Please test and advise on whether or not it works.

Original comment by geocodezip on 13 Feb 2013 at 4:58

[GoogleCodeExporter]

Good morning,

After a test with a clear cache, it seems that it is not working (see picture 
attached). I will however try to test it from home and give you feedback on 
that since my current workplace has a rather complex infrastructure and don't 
know whether something is filtering the request.

Thanks and best regards,
Hugo.

Original comment by hugo.dur...@gmail.com on 13 Feb 2013 at 11:30

Attachments:

• TestLoad.png

[GoogleCodeExporter]

Good evening,

Upon testing the link in post #10 at home, i get the same error (cache clean).
Browser: Firefox, v 18.0.2

Thanks for all your trouble (remind me to fedex you beer when this is fixed)  
and best regards,
Hugo.

Original comment by hugo.dur...@gmail.com on 13 Feb 2013 at 10:05

[GoogleCodeExporter]

Also seems to have something to do with <StyleMap>, if I remove that is works 
also:

http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_linktoB.html?filename=
http://www.geocodezip.com/geoxml3_test/geoxml3_issue80_file_NP.kml

Original comment by geocodezip on 14 Feb 2013 at 6:52

[GoogleCodeExporter]

Good morning,

I confirm that the change applied in post #12 works in Firefox.
What could it be, then?

Best regards,
Hugo.

Original comment by hugo.dur...@gmail.com on 14 Feb 2013 at 10:50

[GoogleCodeExporter]

> What could it be, then?

If I knew the answer to that it would be fixed.  I am currently investigating.  
Your thoughts and observations are welcome.

Can you remove the <StyleMap> as a workaround?

Original comment by geocodezip on 14 Feb 2013 at 1:42

[GoogleCodeExporter]

I am afraid I can't remove the StyleMap, otherwise the map will be filled with 
red dot markers where the yellow pushpins are.

Original comment by hugo.dur...@gmail.com on 14 Feb 2013 at 2:04

[GoogleCodeExporter]

Do you not know how to specify a custom icon without <StyleMap>? It isn't 
required for custom icons, my example does it for the single marker.  Or are 
you using some tool to create your KML that doesn't let you create custom 
markers without a <StyleMap>?

Original comment by geocodezip on 14 Feb 2013 at 2:39

[GoogleCodeExporter]

No, i actually don't know how to specify a custom icon without StyleMap.

The KML is being generated in code (C#) and then later zipped into KMZ.

-- 

Sem mais assunto de momento, subscrevo-me atentamente
Hugo Filipe Lopes Vieira Durana
hugo.durana@gmail.com
+351 962 444 867
Linkedin (EN <http://pt.linkedin.com/in/hugodurana>,
PT<http://pt.linkedin.com/in/hugodurana/pt>
)

A informação contida nesta mensagem destina-se exclusivamente para o
indivíduo a quem é original e especificamente dirigida. Esta mensagem e seu
conteúdo pode conter informação confidencial ou privilegiada. Se você não
for o destinatário pretendido, você está aqui notificado que qualquer
divulgação ou distribuição, ou tomar qualquer ação baseada no conteúdo
dessa informação, é estritamente proibido. Qualquer uso deste endereço de
e-mail para fins publicitários ou qualquer informação não solicitada também
é estritamente proibido.

The information contained in this message is intended solely for the
individual to whom it is specifically and originally addressed. This
message and its contents may contain confidential or priviledged
information. If you are not the intended recipient, you are hereby notified
that any disclosure or distribution, or taking any action in reliance on
the contents of this information, is strictly prohibited. Any use of this
e-mail address for publicitary purposes or any unsolicited information is
also strictly prohibited.

Original comment by hugo.dur...@gmail.com on 14 Feb 2013 at 2:42

[GoogleCodeExporter]

Good morning,

Yesterday i did find a workaround which was to take the original pushpin, 
resize it to 32x32px and place it as a resource in my app.

Did the trick just fine.

Best regards,
Hugo.

Original comment by hugo.dur...@gmail.com on 16 Feb 2013 at 10:51

[GoogleCodeExporter]

>  i did find a workaround
That is good to hear. This issue and the problem with my first cut fix to issue 
#66 both have issues related to the handling of dynamic sizing of images in 
Firefox.  Hopefully some day I will find a way to fix both for real.

Original comment by geocodezip on 16 Feb 2013 at 4:22

[GoogleCodeExporter]

Another example of the problem (may also be issue #66):

only shows one marker, there should be three:
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_stylemap_marker.html?f
ilename=http://www.geocodezip.com/geoxml3_test/rollover_kml.xml

polys branch, shows all three:
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmltest_stylemap_marker.html?f
ilename=http://www.geocodezip.com/geoxml3_test/rollover_kml.xml

Original comment by geocodezip on 16 Feb 2013 at 11:41

[GoogleCodeExporter]

A workaround that displays the markers for firefox:
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_stylemap_marker_201412
22.html?filename=http://www.geocodezip.com/geoxml3_test/rollover_kml.xml

calls setIcon on each marker once the map has become idle.

Original comment by geocodezip on 22 Dec 2014 at 5:53