OK, I've made a bug.

http://code.google.com/p/gmaps-api-issues/issues/detail?id=1473

Thanks for looking into it.

On Jul 9, 3:18 pm, Adam Feldman <adam.feld...@google.com> wrote:
> We've talked this over and traced the problem to HTML's prohibition
> against nested <form> elements, which results in weird behavior in the
> situation you've found.
>
> Fixing this is on our radar, but it seems to be a pretty rare
> situation that you'd need to put a map in aform, so I admit that it's
> not high priority.  I recommend adding it to our issue tracker and
> then if a lot of people vote it up (by starring it), it is more likely
> to receive attention sooner.
>
> In the mean time, you'll have to move the map's div outside theform.
>
> Thanks,
> Adam
>
> On Jul 9, 4:14 am, John  Murphy <jcmur...@gmail.com> wrote:
>
>
>
> > Thanks for looking into this.  I actually posted a thread in the maps
> > group already.  It's here.
>
> >http://groups.google.com/group/Google-Maps-API/browse_thread/thread/0...
>
> > Would it be useful if I file a bug with the Maps API people as well?
> > I can't find a public bug database for thelocalsearchelement itself.
>
> > On Jul 9, 12:24 am, Adam Feldman <adam.feld...@google.com> wrote:
>
> > > Yes, you're correct, Jeremy.  I merely thought that folks on that list
> > > may have run into this one before.
>
> > > In any case, we're looking into it and I'll report back here when we
> > > find something.
>
> > > Adam
>
> > > On Jul 8, 7:50 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote:
>
> > > > If I'm not mistaken, google.elements.LocalSearchwas originally  
> > > > produced by the AJAX APIs team.  And while I certainly respect the  
> > > > experts in theMapsAPI group, I can tell you that they will likely  
> > > > decline to help because the relevant code is obfuscated.  I've been  
> > > > tinkering with this a little bit as time allows.  I will strive to get  
> > > > back to it again in the next day or two.  I know that, as has been  
> > > > pointed out, theproblemis related to the nestedformelements in the  
> > > > buggy example.  I am trying to find a workaround.
>
> > > > Jeremy R. Geerdes
> > > > Effective website design & development
> > > > Des Moines, IA
>
> > > > For more information or a project 
> > > > quote:http://jgeerdes.home.mchsi.comhttp://jgeerdes.blogspot.comhttp://jgee...
> > > > jgeer...@mchsi.com
>
> > > > Unless otherwise noted, any price quotes contained within this  
> > > > communication are given in US dollars.
>
> > > > If you're in the Des Moines, IA, area, check out Debra Heights  
> > > > Wesleyan Church!
>
> > > > And check out my blog, Adventures in Web Development, 
> > > > athttp://jgeerdes.blogspot.com
> > > >   !
>
> > > > On Jul 8, 2009, at 9:40 PM, Adam Feldman wrote:
>
> > > > > Hi John,
>
> > > > > The new Bar will become the default in the near future.  Can you go to
> > > > > theMapsAPI group and pose yourproblemthere:
> > > > >http://groups.google.com/group/Google-Maps-API
>
> > > > > There are a lot of folks over there who work with theMapsAPI, and
> > > > > they should be able to help you out.  Plus, everyone will benefit from
> > > > > the discussion.
>
> > > > > Thanks,
> > > > > Adam
>
> > > > > On Jul 8, 8:26 am, John Murphy <jcmur...@gmail.com> wrote:
> > > > >> Thanks for the reply.  I found I can work around it by using the  
> > > > >> old style bar:
>
> > > > >> var mapOptions =
> > > > >>             {
> > > > >>                 googleBarOptions :
> > > > >>                 {
> > > > >>                     showOnLoad : "true",
> > > > >>                     adsOptions:
> > > > >>                     {
> > > > >>                         client: "pub-XXX",
> > > > >>                         adsafe: "high",
> > > > >>                         language: "en"
> > > > >>                     }
> > > > >>                 }
> > > > >>             }
>
> > > > >> Hopefully Google will fix it before they make the new one the  
> > > > >> default.
>
> > > > >> On Wed, Jul 8, 2009 at 9:42 AM, Darius<darius...@gmail.com> wrote:
>
> > > > >>> I just put map outsideform. Possible workaround are positioning div
> > > > >>> with css. Real solution I didn't found.
>
> > > > >>> On 7 Lie, 20:36, John  Murphy <jcmur...@gmail.com> wrote:
> > > > >>>> Did you ever find a solution to thisproblem?  I've run into the  
> > > > >>>> same
> > > > >>>> issue.
>
> > > > >>>> On Jun 18, 1:51 pm, Darius <darius...@gmail.com> wrote:
>
> > > > >>>>> My real application require authorization, then I wrote two simple
> > > > >>>>> exampleshttp://bug.onrails.lt/. With Chrome any differences, with
> > > > >>>>> firefox or another gecko base browserlocalsearchdoesn't work.
>
> > > > >>>>> On Jun 17, 11:09 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote:
>
> > > > >>>>>> Can you provide a link to your page, wprkibg or not, so we can  
> > > > >>>>>> see what's
> > > > >>>>>> going on?
>
> > > > >>>>>> On Jun 17, 2009 10:32 AM, "Darius" <darius...@gmail.com> wrote:
>
> > > > >>>>>> I setuplocalsearchon mymaps, and its work fine with chrome
> > > > >>>>>> browser. But with firefox i get javascript error, andlocal 
> > > > >>>>>>searchnot
> > > > >>>>>> work.Problemoccurs only if i put  div container toform, e.x.
> > > > >>>>>> in html:
>
> > > > >>>>>> <form>
> > > > >>>>>>    <div id="map"><!-- --></div>
> > > > >>>>>> </form>
>
> > > > >>>>>> if i remove <form></form> tag all works good, but i can't submit
> > > > >>>>>>form...
>
> > > > >>>>>> firebug show javascript error:
> > > > >>>>>> this.c.formIdisnullonhttp://www.google.com/uds/api/elements/1.0/d188c3699cfb7ddb5c10fdeb86
> > > > >>>>>> ...
> > > > >>>>>> (line 102)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google AJAX APIs" group.
To post to this group, send email to Google-AJAX-Search-API@googlegroups.com
To unsubscribe from this group, send email to 
google-ajax-search-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-AJAX-Search-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to