Hi,
so it seems this problem is not gmap2 specific. It's just the way our
markup is structured, which seems no longer be supported by firefox 3.
The following simple example show the failure:
<div style="width: 200px; height: 200px">
<wicket:panel>
<div style="width: 100%; height: 100%; background: #ff0000">
</div>
</wicket:panel>
</div>
The nested div is no longer strechted to the full size of the containing
div.
I'll see how we can restructure our markup, but generally this change in
forefox's layout might effect other places too.
Sven
Ryan Sonnek schrieb:
On 6/26/08, Martin Funk <[EMAIL PROTECTED]> wrote:
Sven Meier wrote:
Hi,
I'm investigation the issue:
It seems that Google's css is being screwed up in FF3. When I let Wicket
strip all wicket tags *or* assign pixel width (instead of 100%) to the
element holding the map, everthing works fine in FF3.
btw. Sven,
I now can confirm the effect of stripping too.
so a quick solution would be running the app in deployment mode.
Can the "strip wicket tags" setting be declared at a component level, or
does it affect the entire server?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
