You need to add one line to your CSS code:
#map_canvas div { line-height: normal ! important; }
where map_canvas is your div, where you're inserting your map.
If you encountered this issue, you have probably specified line-height to 1 em
or less. This caused that issue.
--
You received this m
jquery method -
add this line to your click function for the infoWindow:
//remove overflow scrollbars
$('#myDiv').parent().css('overflow','');
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" group.
To view this discussion
somebody came up with a much simpler solution which worked for me.
maybe it will work for you, too:
content='whatever you want'
var div = document.createElement('div');
div.innerHTML = content;
infowindow.setContent(div);
--
You received this message because you are subscribed to the Google Grou
Glad I stumbled up the solutions of this page, especially the
simple genius of setting the parent/parent-parent to *overflow:none*.
Brilliant.
In my attempts to figure out what was happening, I stumbled up the following
*in my context (only?)*: adjusting the font-size of the last line affected
Thanks for all the great discussion on this topic.
My variation on the problem was in Firefox (3 and 4-beta) the infoWindow
appeared correctly until the link was clicked.
On the click, Firefox would create the scroll bars and not follow the link.
Cause? Firefox would put that little dotted outlin
After marking this down as a solved problem, I was perusing my map and
realized that this fix does not work if the content div of the
infoWindow is larger than ~70% of the map_canvas. When this is the
case I actually did need the Y-scroll bars. Here was my final fix in
prototype (1.6.1):
//My i
I seem to have pasted incorrectly, The working listener for Prototype
was actually:
google.maps.event.addListener(infowindow, 'domready', function(){
$('infoWindow').parentNode.setStyle({
overflow: ''
});
$('infoWindow').parentNode.parentNode.setStyle({
Pete,
Thanks for grabbing my attention, I had indeed stopped watching this
thread, but would rather not close then reopen the infowindow.
Something odd came up while applying the change.
I am using prototype 1.6.1--though I usually translate back to normal
js when posting short bits. When using
Many thanks.
Ended up doing the same thing in jQuery - and hugely grateful to you
for sorting this out...
Gave every box the same class ('') and used their class selected
to solve the problem.
infoWindow.open(map, marker);
jQuery('.').parent().parent().css
Hi Josh
Have you seen the rest of the thread? Franky found a bug in my original
code, which probably explains why you were having to close and open the
infowindow to get the fix to work.
See the rest of the thread for the fix. Trouble is I still think in UCSD
Pascal where things happed in sequenc
Peter,
you tha man! This is a really great working solution. Took me some time
implementing it (big javascript, lots of maps and loops) but now it rocks.
Thanks a lot for the "final" solution.
Franky
On Mon, Sep 6, 2010 at 7:35 PM, Peter Lawless wrote:
> Hi Franky
>
> Good spot when you are op
I forgot to mention that my content div's id is also infowindow, as
you probably figured out..
--
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 google-maps-js-api...@googlegroups.com.
To unsub
Hi Franky
Good spot when you are opening the infowindow as you are so you come into
the map with the infowindow open it shows up my badly designed code!
What I should have done is wait for the 'domready' event to fire, before
trying to access the div.
google.maps.event.addListener(infowindow, 'd
On Thu, 26 Aug 2010 22:46:02 +0100
Peter Lawless wrote:
> Hi Brad & Franky et al
>
> Over a glass this evening I thought it would be a better approach to
> use a bit of JS and work out from my own content div to fix the
> overflow:auto issue rather than in via about 6 divs with CSS.
>
> I gave
Greetings,
I was having the same problem with about 12 lines of text. After
adding this to my marker click listener:
//infowindow is an instance of google.maps.InfoWindow
infowindow.close();
document.getElementById('infoWindow').parentNode.style.overflow = '';
document
Franky - my development infowindow contains a which includes an
and tags and up to 3 tags in a positioned horizontally, hence
the need to use clearing. Seems to work fine - after all the div I am
tweaking does not have an overflow style in V2 api and my infowindow has
always worked in that v
On Thu, 26 Aug 2010 22:46:02 +0100
Peter Lawless wrote:
> Hi Brad & Franky et al
>
> Over a glass this evening I thought it would be a better approach to
> use a bit of JS and work out from my own content div to fix the
> overflow:auto issue rather than in via about 6 divs with CSS.
>
> I gave
On Fri, 27 Aug 2010 19:35:13 -0700 (PDT)
William wrote:
> On Aug 27, 7:46 am, Peter Lawless wrote:
> > I gave my content div an id of '' thinking it might attract the
> > attention of the Australian development team!
> > Then document.getElementById('').parentNode.style.overflow='';
> >
On Aug 27, 7:46 am, Peter Lawless wrote:
> I gave my content div an id of '' thinking it might attract the
> attention of the Australian development team!
> Then document.getElementById('').parentNode.style.overflow=''; added
> immediately after the infowindow.open removes the overflow sty
Nice work Pete, I can't think of a reason off hand not to use it
myself. I may even try it out since I discovered that I still need to
spruce up my infowindows. Generally mine are ok... Until I click a
link inside it. When I do 2 vertical scroll bars appear out of
nowhere. Ugh!
--
You recei
Hi Brad & Franky et al
Over a glass this evening I thought it would be a better approach to use a
bit of JS and work out from my own content div to fix the overflow:auto
issue rather than in via about 6 divs with CSS.
I gave my content div an id of '' thinking it might attract the
attention o
I did something similar to yours Franky. On mine I removed the
default margin which took care of the scroll bars using . I also noticed that adding a 1px right padding
helped in some cases; .
Oh and I don't use my own divs.
http://www.darkmatters.org/Map/Test2/MakeMarkers2.html
--
You receive
On Thu, Aug 26, 2010 at 5:22 PM, Peter Lawless wrote:
> Hi Brad
>
> I have tried using h2 in fact we tried them all though to h7 yesterday.
> All with no luck.
>
> The problem is the overflow:auto on the containing div. The reference says
> you should be able to put a size on your content div s
Hi Brad
I have tried using h2 in fact we tried them all though to h7 yesterday. All
with no luck.
The problem is the overflow:auto on the containing div. The reference says
you should be able to put a size on your content div so it really should
work straight out of the box.
I tried not puttin
Better yet... Use instead. It's nearly as effective and seems
to resolve the random scroll bar issue on my maps. I'll probably
switch to on my maps. is just a bit over the type in terms
of title size.
--
You received this message because you are subscribed to the Google Groups
"Google Map
Hey there Peter
I've noticed this problem on my v3 maps as well and it's a real
nuisance. Now that you've brought it up I decided to see if there was
a way to squash this one and I think I may have an alternative
solution. I haven't tried this yet on my map but after poking around
on yours it se
Sorry left a space in the url! Try this one.
http://www.lawless.info/gmaps/bubble_test.html
On Wed, Aug 25, 2010 at 7:20 PM, Joseph Elfelt wrote:
> Please check your link
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Maps JavaScript API v3" group.
Please check your link
--
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 google-maps-js-api...@googlegroups.com.
To unsubscribe from this group, send email to
google-maps-js-api-v3+unsubscr...
28 matches
Mail list logo
