My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1343: Printing looks bad with Info Windows (in IE6 or IE7 (maybe in IE8 too)
110 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Dec 2010


Sign in to add a comment
 
Reported by [email protected], May 31, 2009
First, visit
https://code.google.com/apis/maps/documentation/v3/examples/infowindow-simple.html
in IE6 or IE7 (maybe in IE8 too).  Then, click on the marker.  Finally,
print this page.  Looks pretty bad!

This may not seem like a big deal at first but consider this common use of
the Google Map... for many of my clients, I use the Google Maps API for
their Contact Us pages.  These pages are basically the same as
https://code.google.com/apis/maps/documentation/v3/examples/infowindow-simple.html
except that I have the Info Window appear on page load.  Many users will
want to print this page.  So for this reason, I think this is an issue that
needs to be resolved.

Thank You
May 31, 2009
#1 pamela.fox
 Issue 1342  has been merged into this issue.
Jun 1, 2009
#2 pamela.fox
Replicated and reported to team, thanks!
Status: Confirmed
Labels: Internal-1890744
Jun 3, 2009
#4 [email protected]
This is a major bug. The V3 maps look different in IE and Chrome/Mozilla
- The animations in the maps (moving a marker to centre using JS) is sloppy and 
rough 
in IE but works smoothly in Chrome/Mozilla. Actually everything goes slow in IE, 
even 
manual zoom, moving the map using the hand cursor, etc.
- As reported by Larry, the shadow looks crap in IE, and the border of infoWindow 
looks very rough and patchy.
This is a major bug that's going to stop everyone from moving to V3 api.
Jun 4, 2009
#5 pamela.fox
Please report those issues as separate bugs, and reference links that demonstrate the 
issues. This issue is only about printing. Thanks!
Jul 27, 2009
#6 [email protected]
Same problem in Firefox 3.0.11... marker doesn't show up on printed page, only a
white rectangle
Jul 29, 2009
#7 [email protected]
White rectangle on printed page is only firefox issue. I tried Webkit based browsers
and they worked fine.
Nov 17, 2009
#8 [email protected]
I thought that part of the Terms of Use were that Google maps were for web use only
and not for printing?!
Nov 18, 2009
#9 [email protected]
With all due respect, who cares what the "Terms of Use" says. Just imagine how many
people are experiencing this inconvenience EVERY SINGLE DAY. It should be fixed.
Dec 21, 2009
#10 [email protected]
re: comment 9:  i was meaning if google state it is against their terms then why
would they 'fix' something to help people go against them?!
Jan 7, 2010
#11 [email protected]
 Issue 2061  has been merged into this issue.
Jan 28, 2010
#12 [email protected]
I'm not sure if this belongs here or in a separate issue, but I'm mainly interested in 
printable map markers, as mentioned by someone else in this Google Groups discussion: 
http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/d1713a8d4e307e51

I have a live example of the bug(?) at 
http://offcampusaccommodation.newcastle.edu.au/Listings/Detail/1746

On screen it looks like the attached screen.gif, but when printed it looks like print.gif, 
with the map markers replaced with white boxes, even the non-custom red pin marker. I 
believe this is because the markers use the background-image CSS rule to display the 
marker image, which most(?) browsers won't print by default.

As Pete mentions on the Google Groups thread above, it doesn't appear to make a difference 
if you use .gifs for the marker instead of .pngs.

Apparently Maps v2 solved this by allowing you to specify a separate printImage, as 
mentioned here: http://econym.org.uk/gmap/custom.htm

Thanks Googlers, and apologies for the long comment everyone.
screen.gif
46.0 KB   View   Download
print.gif
39.4 KB   View   Download
Apr 5, 2010
#13 [email protected]
I highly consider this as a major bug, locking the use of this API to build a 
commercial application.
Apr 23, 2010
#14 [email protected]
It's not just "printing looks bad".  Markers do not work at all, i.e. printing is broken in all the major browsers, 
including Chrome.
Apr 24, 2010
#15 [email protected]
I absolutely agree with [email protected]. Markers do not print in any well known 
browser. I've tested marker printing with no success in IE6, IE7, IE8, FF3.6, Opera 
10.5, Chrome 4.1 and Safari 4. No one of these browsers can print markers correctly.

This issue makes API V3 impossible to be used in commercial enviroments.

I know about Google policy on issues preferences and starring, but looking at the 
impact of this one, I would consider it a critical issue, no matter how many stars it 
has got.
May 24, 2010
#16 [email protected]
Can we change title to more accurately reflect real problem? See comment 12 & 14
May 25, 2010
#17 [email protected]
I absolutely agree with pholmstr. Issue title should be something like "Markers do not 
print at all"
Jun 14, 2010
#19 [email protected]
My first staps with the API took me directly to V3, which works very smooth onscreen, yet when I print, no markers... which makes it quite useless, and it seems I have to study on V2 now. 
Jun 17, 2010
#20 [email protected]
atm the map itself doesnt print, too (beside markers and zoomcontrol)
custom maps are printed

my map can be found here:
http://www.mario-baldauf.org/API_v3/routenplaner/index.html
- press 'Hilfe' - 'Hier klicken' - 'Route berrechnen' - 'Karte drucken'
Jun 23, 2010
#21 [email protected]
Agree with all the comments that this problem of markers not printing properly really degrades the usefulness of this API. Developers won't be able to use this because their users will only be confused and could likely contact the client regarding the problem (depending on the implementation). 

The problem of maps not printing at all when getting route directions is a separate major problem that should probably be reported separately.
Jun 24, 2010
#22 [email protected]
I discovered what may be a workaround to maps not printing right in IE, particularly maps for directions and markers. Many map DIV elements generated by Google Maps API3 contain an inline style of "filter: alpha(opacity=1);background-color: #000;".  Disabling these two properties when printing causes the map and markers to print correctly using IE. The printout looks good and markers don't have the white box around them. Tested other browsers too and see no ill effects from disabling these settings--not yet anyway. 
Jun 29, 2010
#23 [email protected]
Hi, on wich div do you disable the styles and how do you do yo disable the filter and the background ?
Thanks.
Jun 29, 2010
#24 [email protected]
Re: Comment 23

div#map_canvas div {
 filter: none !important ;
 background: transparent !important ;
}
Jun 29, 2010
#25 [email protected]
Thank you for the answer.
So I put these properties to my map div but I still have :
- blank instead of the map when printing in Firefox
- blank instead of the marker in safari

Does anyone found a solution for these bugs ?
Is there a google internal report for these bugs ? 

The internal problem report on the comment 2 looks to be for the problem of the title of this issue : IE7 and 8 ... Is it right ? 
I stand for the answer to know if I should open a new issue.
Jul 6, 2010
Project Member #26 [email protected]
 Issue 2433  has been merged into this issue.
Jul 12, 2010
#27 [email protected]
Re: Comment 25:
The only work around I found for the issue you are seeing in Firefox is to enable background printing on the page set-up of the browser. Most browsers do not enable background printing by default so you need to tell user to enable that option when printing.
Jul 15, 2010
Project Member #28 [email protected]
 Issue 2123  has been merged into this issue.
Jul 23, 2010
#29 [email protected]
(No comment was entered for this change.)
Labels: -Internal-1890744 Internal-1951146
Jul 28, 2010
#30 [email protected]
I have a work around for you folks who are looking for an (hopefully) acceptable alternative.  What I've found that works is to use the Google Static Maps API for printing purposes only.  You are severely limited in comparison to the dynamic maps but this may be just enough to get you over your own hurdle.

I definitely agree that not being able to print the map is an issue and severely reduces the value in using the API.  As for the TnC's on printing, Google has the following:

"10.10 print more than 5,000 copies of sales collateral materials containing a screenshot of Tele Atlas Content for purposes of commercial sales lead generation ("Direct Marketing") or incorporate Tele Atlas Content as a core part of printed matter (such as printed maps or guide books) that you redistribute for a fee (you must contact Tele Atlas to obtain a direct license if you desire to do either of the above);"

Allowing your end users to print copies of the map for their own navigational needs does not violate this condition.

Has anyone found this to be a Mac/PC only issue?  Is it limited to Firefox or does it affect all major browsers?

Jul 28, 2010
#31 [email protected]
I created a Google Wave for this for other developers who want to collaborate on possible work arounds:

https://wave.google.com/wave/waveref/googlewave.com/w+IRzfxGprA
Aug 3, 2010
#32 [email protected]
it's a critical issue!!
Aug 8, 2010
Project Member #34 [email protected]
 Issue 2605  has been merged into this issue.
Aug 28, 2010
#35 [email protected]
Why has Google not yet fixed this? Can we get an official statement please?

I converted my V2 real estate map to V3 this week. I'm all done now, but I can't print the map & markers (as I can with the V2 map) to hand to my clients when we go on a property tour.


Sep 17, 2010
#36 [email protected]
This is a really serious issue. Basically it renders an otherwise complete system unusable for me.

Either fix this issue, or provide a method om map to generate a static map automatically, without the silly limit in querystring length.
Sep 25, 2010
#37 [email protected]
Still no solution for this??
I can get the map to print in every browser except for Firefox where I only see the controls. Mine has no markers though only Polygon.
Oct 5, 2010
#38 [email protected]
I just ran across this today and yesterday. Doing some experiments with firefox 3.6.10, chrome 6.0.472.62 and ie 8.0.6001 gives the following results (note, i've limited the map_canvas div size to 700px by 800 px. Also I'm running windows XP, SP2):

Firefox: Comment 27 above is a solution. the page prints correctly with the info box displayed or not displayed.

Chrome: With the info box displayed, the info box shadow results in white space on the map where the shadow was. The marker does not print
With the info box not displayed, the marker does not print. There is a white rectangle where the marker and it's shadow were.

IE: The info box is poorly formatted. The info box shadow causes the map details to be removed (not white space, but the gray background color obscures the details)
The marker is not printed.
With the info box removed, there is a smudge where the marker shadow was. The marker is not printed.

IMHO, this is a major problem with the version 3 API.

Oct 5, 2010
#39 [email protected]
An extension of comment 38.

As an example of the map i'm using to test, put this following url into your browser:

http://www.ayso11k.org/cgi-bin/wsa.pl?funct=maps_req

All, except the last, of the entries on this page use V2 of the API.

The last entry, ztest, uses V3 of the api.

regards

Oct 19, 2010
#40 [email protected]
Please, solve this problem. This is a major issue of Google Map API v3. Thanks to developpers.
Oct 19, 2010
#41 [email protected]
Perhaps this solution is good enough for you while googlers implement a real solution for this problem:

http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/3b1c5e69bfe809ce/b03412abfc8f8c19?lnk=gst&q=garito#b03412abfc8f8c19

Cheers
Oct 20, 2010
#42 [email protected]
Hi Garito
Thanks for your answer and solution, but like we say in French "c'est du bricolage".
I prefer this bug to be corrected.

Dom
Nov 2, 2010
#43 [email protected]
Google: This could be fixed in IE by removing the filter:alpha(opacity=1) style from the markers. It causes IE to print grey boxes instead of the markers. The link above from garito explains.
Nov 4, 2010
#44 [email protected]
(No comment was entered for this change.)
Labels: -Internal-1951146 Internal-1890744 Browser-IE6 Browser-IE7 Browser-IE8
Nov 4, 2010
#45 [email protected]
(No comment was entered for this change.)
Labels: -Internal-1890744 Internal-1951146
Nov 28, 2010
Project Member #46 [email protected]
 Issue 2823  has been merged into this issue.
Dec 8, 2010
#47 [email protected]
Hi everyone,

This was fixed in v3.3.3 of the API.

Cheers
Chris
Status: Fixed
Labels: Fixed-3.3.3
Dec 8, 2010
#49 [email protected]
Thanks Chris!

I have been waiting patiently for this fix, and it wasn't until recently I was given a deadline to go live with my coupon / map print out. This is perfect timing. I can go live with it proudly!

Thanks again!
Dec 10, 2010
#50 [email protected]
I've just tried printing https://code.google.com/apis/maps/documentation/javascript/examples/polyline-complex.html using internet explorer 8 and have the markers but I don't see the map. See attached file.
test.xps
421 KB   Download
Dec 10, 2010
#51 [email protected]
Thanksss! :)
Jan 6, 2011
#52 [email protected]
comment 50 confirmed... the map tiles are no longer printing!!!!! 
Mar 8, 2011
#53 [email protected]
Hi guys, I'm facing the same problem with v3.4, 
Mar 24, 2011
#55 [email protected]
Thanks Chris,
I have changed the used version to 3.3 and it worked.
Cheers !
Apr 19, 2011
#56 [email protected]
Hi guys,

recently i modified the code to use version 3.3.3 to print the info-window from version 2. Im able to print the info-window content & markers, but back side map is disappeared. 

Please help... 
3.xps
235 KB   Download
Sign in to add a comment

Powered by Google Project Hosting