search

yenbao1340 / gmaps-utility-library-dev

Automatically exported from code.google.com/p/gmaps-utility-library-dev
0 stars 0 forks source link

TabbedMaxContent Windows are Oversized #139

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Open the maxtabs.html example
2. Display and maximize the info window

What is the expected output? What do you see instead?
I would expect the info window to be sized properly for its content, 
instead it's rendered at about 700x600px.

What version of the product are you using? On what operating system?
1.0 & dev on XP (multiple browsers)

Please provide any additional information below.
I tried adding the maxWidth and/or style properties when defining the info 
window, but haven't had any luck.  Is it possible to use these to control 
size?

Original issue reported on code.google.com by carpied...@gmail.com on 3 Aug 2009 at 7:58

GoogleCodeExporter commented 8 years ago

Original comment by pamela.fox on 4 Aug 2009 at 12:03

GoogleCodeExporter commented 8 years ago

Original comment by pamela.fox on 4 Aug 2009 at 12:03

GoogleCodeExporter commented 8 years ago 
The size of the max window is determined by the core API. I believe it is a
percentage of the map container with some max/min cap. This lib has no control 
over
it. The developer can have some limited control with style sheet. Changing the
underline DOM structure of the infowindow is not support, so I probably will 
mark
this as will not fix.

Original comment by nian...@gmail.com on 4 Aug 2009 at 10:42

GoogleCodeExporter commented 8 years ago 
Any advice as to how I can use the style sheet to solve this problem?

Original comment by carpied...@gmail.com on 4 Aug 2009 at 8:44

GoogleCodeExporter commented 8 years ago 
You might be able to use GInfoWindow.getContentNode() to gain access to the DOM 
node,
or used a named node in your content and use firebug to figure out the DOM 
structure
and travel up. Use JavaScript to modify each related node's size and hopefully 
you
can get what you want. Again, this is not supported, can be very tricky to do, 
and
you are at your own risk of break the code at future release of the core API. 
If you
want more control over your infowindow, maybe you can consider use 
ExtInfoWindow.

Original comment by nian...@gmail.com on 5 Aug 2009 at 8:56

GoogleCodeExporter commented 8 years ago 
Thanks!  And since I forgot to say to earlier, great work; I love the project.

Original comment by carpied...@gmail.com on 5 Aug 2009 at 9:28

GoogleCodeExporter commented 8 years ago

Original comment by nian...@gmail.com on 6 Aug 2009 at 12:37