Possible bug with multiple text inputs.

2 views
Skip to first unread message

Shawn Simister

unread,
Dec 3, 2008, 5:28:24 PM12/3/08
to freebase...@googlegroups.com
I'm using Freebase Suggest on five separate text inputs in my Freebase Sets web app and it works really well for the most part. But, if you type something really quickly into the first text field and then hit tab before the autocomplete is loaded your cursor moves to the next text field but the autocomplete eventually pops up for the first text field. This is pretty much what I would expect except that if you now choose a topic from the list, that topic's name gets entered in the second text field rather than the first. I think the topic name should at at least get entered in the first field but it would also be nice if the autocomplete list just appeared on the second text field.

Obviously, this is a pretty rare occurrence but I figured I'd check here to see if there's anything I can do to prevent this.

Shawn

Will Moffat

unread,
Dec 3, 2008, 6:16:32 PM12/3/08
to freebase...@googlegroups.com
Hi Shawn,

I can't reproduce this bug on a Mac using FF3 or Safari3. Which
browser + OS are you using?
If you're using the same as me, could take me step by step through
your problem.

cheers,
--Will

Dae Park

unread,
Dec 3, 2008, 6:59:22 PM12/3/08
to freebase...@googlegroups.com
Also, is this happening on trunk?

Shawn Simister

unread,
Dec 3, 2008, 8:40:00 PM12/3/08
to freebase...@googlegroups.com
I'm seeing this in both Firefox & Chrome on Vista. Safari + Vista works as expected. IE7 is a complete mess but thats nothing new. :-(

The basic steps I use are:
  1. Copy and paste some text into first text field and then immediately hit tab.
  2. Wait for autocomplete to load.
  3. Click on one of the topics from the drop-down list.

Shawn Simister

unread,
Dec 3, 2008, 8:43:12 PM12/3/08
to freebase...@googlegroups.com
This is happening with version 0.4 which I assume is the current stable stable release.

Dae Park

unread,
Dec 4, 2008, 11:12:21 AM12/4/08
to freebase...@googlegroups.com
Actually trunk is what we are using on production and has been stable
for a while. We just haven't gotten around cutting a branch.
Reply all
Reply to author
Forward
0 new messages