On Thu, Jun 16, 2011 at 5:29 AM, Gabriel Petrovay wrote:
> Chris (from Google) mentioned that he already files some internally. So,
> Chris, are there any that we still have to file?
>
Sure, please file them externally if you want to be notified of any related
changes (we'll update the external i
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
bug report anyone ?
On 15 Jun., 15:36, Clem wrote:
> Same issues !
>
> Sincerely,
> Clement.
>
> On 6 juin, 21:02, Miles 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
> > paramet
Same issues !
Sincerely,
Clement.
On 6 juin, 21:02, Miles 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
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 notic
good topic, i had / have the same problems with this, it would be nice
if the styles you gave to the input box just stay´s the same
On 6 Jun., 13:05, Gabriel Petrovay wrote:
> Thanks Chris for the answers. See inline.
>
>
>
>
>
>
>
>
>
> On Mon, Jun 6, 2011 at 3:06 AM, Chris Broadfoot wrote:
> >
And, is it safe to handle classes generated but such an API?
For example I want to remove the pac-input-default class myself. Can I repy
on such a name or is this error-prone since the names can change anytime?
Regards,
Gabriel
--
You received this message because you are subscribed to the Goo
Some more issues with the autocomplete feature:
- since the proposal div is absolutely positioned, the resizing of the
window keeps the div in place while the input field changes its position. (I
know this is not a very common behavior of the user: resizing the browser
during completion proposal
