I did not file any of the bugs. Chris (from Google) mentioned that he already files some internally. So, Chris, are there any that we still have to file?
Thanks! PS: In the meanwhile I do a lot of dirty tricks: enabling auto completion only from the 2 character (enabling it on keypress when the input field is empty still has some issues) Anyway this is much better because you might not need completion always and only on demand. Moreover, for 1 character is most probably irrelevant. And this way the showing of the control is decoupled from auto completion. On Wed, Jun 15, 2011 at 8:48 PM, en4ce <[email protected]> wrote: > bug report anyone ? > > On 15 Jun., 15:36, Clem <[email protected]> wrote: > > Same issues ! > > > > Sincerely, > > Clement. > > > > On 6 juin, 21:02, Miles <[email protected]> wrote: > > > > > > > > > > > > > > > > > I completely agree that the user of the API should be able to supply > > > the default text for the input box. Specifying it via the options > > > parameter would be great. Or perhaps the google API could respect what > > > I've set for the value attribute on my input element? > > > > > Another point of quirkiness I've noticed: > > > > > In my webapp, if the user clicks outside of the autocomplete text box > > > before selecting a location from the drop down, I need the text box to > > > clear out instead of leaving the text as is. I've tried clearing the > > > textbox manually via onchange and onblur events, but the somehow the > > > autocomplete logic magically repopulates it right after it clears. > > > > > Regards, > > > > > Miles > > > > > On Jun 6, 7:26 am, Gabriel Petrovay <[email protected]> wrote: > > > > > > And a few more things on usability: > > > > > > - an Enter or Tab selection. I know that both are already used in > form > > > > submission and navigation respectively. But it would be nice to let > the user > > > > choose what key he wants in the constructor. > > > > - once the user chooses something, this should be considered "chosen" > and > > > > the proposal div should not be displayed again if the user navigates > back > > > > and forth the controls, unless he changes again the text in the > autocomplete > > > > field. > > > > > > And one more test and proposal for the focus thing: > > > > - try autocomplete on an input with the autofocus attribute. "Enter a > > > > location" should not be displayed. The options arguments in the > Autocomplete > > > > contructor should say something like: > > > > var options = { > > > > emtyText: "Enter a location";} > > > > > > This for at least two reasons: > > > > 1. internationalization (correct me if I-'m wrong and this is handled > by an > > > > option in the maps API URL already, but not sure if that fits all > needs) > > > > 2. letting users write their own text, and possibly empty if someone > writes > > > > the text outside the field > > > > > > Regards, > > > > Gabriel > > -- > 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 > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- MSc Gabriel Petrovay Mobile: +41(0)787978034 www.28msec.com -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
