Autocomplete issues: don't show results when backspacing to :

[niranjanb]

I noticed a couple of minor issues. I am entering these at Michael's behest.

If you enter type:person and delete person back so that only type: remains, we get a drop box with "Release track" as the first entry. Not sure if it makes any sense to have an auto-complete when there is not even a single character to begin with.

It appears that my browser auto-complete is competing with the interface's auto-complete.

If I typed type:Person and scrolled down the drop-down list but did not click on any and just came back to the text box, then the text I had originally entered gets replaced with the text of the drop-down list item that the cursor was last on.

[schmmd]

Thanks Niranjan. Niranjan is using firefox. Browser autocomplete seems appropriately disabled with chrome on my computer. The last point is a duplicate of #25.

[xdavidjung]

I've never run into the double-autocomplete problem myself, but I thought I'd solved the problem by setting the autocomplete attribute to off. Next time I'm around I'll have to ask you to show me.

The other issues, such as having a autocomplete dropbox with random entries when "type:" is all that's there, and using the keyboard to navigate the dropbox and having it replace what's in the box already, are issues inherent in the Freebase suggest module.

I'm thinking that instead of having the type queries be reliant on the user typing in "type:" or entity queries be reliant on "entity:" being appended to the front of queries, there could be some sort of visual switch (a radio button, perhaps) that would allow the user to execute type or entity queries.

An advantage would be that it would make users aware of these options; a disadvantage is having more options to learn about and how it would look on the page.

Michael, I could make a prototype of something that would do this if you were interested.

[schmmd]

Is it possible to make the autocomplete disappear when the user backspaces
to the colon? We don't pop up the autocomplete until a character is
entered after the colon, so this makes sense to me. That way we don't
display nonsense suggestions too.

I'm thinking that instead of having the type queries be reliant on the
user typing in "type:" or entity queries be reliant on "entity:" being
appended to the front of queries, there could be some sort of visual switch
(a radio button, perhaps) that would allow the user to execute type or
entity queries.

This is a great idea. I think we have more important work first though.

On Tue, Oct 9, 2012 at 6:01 PM, David Jung [email protected] wrote:

I've never run into the double-autocomplete problem myself, but I thought
I'd solved the problem by setting the autocomplete attribute to off. Next
time I'm around I'll have to ask you to show me.

The other issues, such as having a autocomplete dropbox with random
entries when "type:" is all that's there, and using the keyboard to
navigate the dropbox and having it replace what's in the box already, are
issues inherent in the Freebase suggest module.

I'm thinking that instead of having the type queries be reliant on the
user typing in "type:" or entity queries be reliant on "entity:" being
appended to the front of queries, there could be some sort of visual switch
(a radio button, perhaps) that would allow the user to execute type or
entity queries.

An advantage would be that it would make users aware of these options; a
disadvantage is having more options to learn about and how it would look on
the page.

Michael, I could make a prototype of something that would do this if you
were interested.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-9285789.