Re: Gmap2 problem with Firefox 3.0
Murat Yücel wrote: I am not able to see the examples in IE 7 either. Could you confirm this? Yeah, can soemone confirm this. I currently don't have access to a windows machine. There also seems to be a problem with using png images as a marker. Found this fix which seems to solve the problem. http://homepage.ntlworld.com/bobosola/pnghowto.htm Same on this issue. Also could someone give some feedback if stripping the wicket tags makes a difference for IE too? mf /Murat 2008/6/27 Sven Meier <[EMAIL PROTECTED]>: 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: 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gmap2 problem with Firefox 3.0
Rafa? Jaskó?ka wrote: Yes, I didn't updated example sources for few days. And realized that I should do it, after sending previous post :) yeah:-) sorry for the arrogant tone in my mail. I just added a little logging message too. So if the programmer doesn't notice the sysadmin will tell him. mf 2008/7/3 Martin Funk <[EMAIL PROTECTED]>: Rafa? Jaskó?ka wrote: Hi, It seams that main problem for FF3 are custom wicket tags, in this case. The most simple solution will be adding line you meant: was, didn't you? https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-gmap2-examples/src/main/java/wicket/contrib/examples/GMapExampleApplication.java mf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gmap2 problem with Firefox 3.0
Yes, I didn't updated example sources for few days. And realized that I should do it, after sending previous post :) 2008/7/3 Martin Funk <[EMAIL PROTECTED]>: > Rafa? Jaskó?ka wrote: > >> Hi, >> >> It seams that main problem for FF3 are custom wicket tags, >> in >> this case. >> The most simple solution will be adding line >> >> > you meant: was, didn't you? > > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-gmap2-examples/src/main/java/wicket/contrib/examples/GMapExampleApplication.java > mf > >
Re: Gmap2 problem with Firefox 3.0
Rafa? Jaskó?ka wrote:
Hi,
It seams that main problem for FF3 are custom wicket tags, in
this case.
The most simple solution will be adding line
you meant: was, didn't you?
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-gmap2-examples/src/main/java/wicket/contrib/examples/GMapExampleApplication.java
mf
getMarkupSettings().setStripWicketTags(true);
in init() method of application class.
After adding:
@Override
protected void init() {
getMarkupSettings().setStripWicketTags(true);
}
in GMapExampleApplication,
and super.init();
in init() methods of all classes extending GMapExampleApplication, maps in
examples are visible.
It works on trunk and 1.3 branch.
rj
2008/6/27 Sven Meier <[EMAIL PROTECTED]>:
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:
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.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gmap2 problem with Firefox 3.0
Hi,
It seams that main problem for FF3 are custom wicket tags, in
this case.
The most simple solution will be adding line
getMarkupSettings().setStripWicketTags(true);
in init() method of application class.
After adding:
@Override
protected void init() {
getMarkupSettings().setStripWicketTags(true);
}
in GMapExampleApplication,
and super.init();
in init() methods of all classes extending GMapExampleApplication, maps in
examples are visible.
It works on trunk and 1.3 branch.
rj
2008/6/27 Sven Meier <[EMAIL PROTECTED]>:
> 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:
>
>
>
>
>
>
>
>
> 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.
>
>
Re: Gmap2 problem with Firefox 3.0
I am not able to see the examples in IE 7 either. Could you confirm this? There also seems to be a problem with using png images as a marker. Found this fix which seems to solve the problem. http://homepage.ntlworld.com/bobosola/pnghowto.htm /Murat 2008/6/27 Sven Meier <[EMAIL PROTECTED]>: > 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: > > > > > > > > > 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] > >
Re: Gmap2 problem with Firefox 3.0
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: 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]
Re: Gmap2 problem with Firefox 3.0
Ryan Sonnek wrote:
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?
As I read the code it is declared on application level.
Is there a chance to implement something like:
public IMarkupSettings getMarkupSettings() {
return Application.get().getMarkupSettings();
}
in Component? Of cource replacing all occurrences of
'Application.get().getMarkupSettings()' in Component with
'getMarkupSettings()' ?
That way subclassed Components could overwrite the getMarkupSettings and
roll their own settings.
I'm not sure though, if the settings have implications that go beyond
the Component?
mf
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gmap2 problem with Firefox 3.0
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?
Re: Gmap2 problem with Firefox 3.0
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. mf Sven kiot schrieb: Hello, i have a problem with gmap2 example application under the Firefox 3.0 . Maps are loaded, but are not shown correctly. I tried the same app in FF2, Opera 9, IE 7 and it works fine. Firebug shown any error so i don't where the problem can be. Is there anybody with the solution? Thanks, Tomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gmap2 problem with Firefox 3.0
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. Sven kiot schrieb: Hello, i have a problem with gmap2 example application under the Firefox 3.0 . Maps are loaded, but are not shown correctly. I tried the same app in FF2, Opera 9, IE 7 and it works fine. Firebug shown any error so i don't where the problem can be. Is there anybody with the solution? Thanks, Tomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Gmap2 problem with Firefox 3.0
Hello, i have a problem with gmap2 example application under the Firefox 3.0 . Maps are loaded, but are not shown correctly. I tried the same app in FF2, Opera 9, IE 7 and it works fine. Firebug shown any error so i don't where the problem can be. Is there anybody with the solution? Thanks, Tomas -- View this message in context: http://www.nabble.com/Gmap2-problem-with-Firefox-3.0-tp18137475p18137475.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
