Not sure what is the plan on this one - looks like FullTextQueryStringQueryBuilder has quite extensive handing for quotes with regard to fuzzy/phrase queries, and we probably don't want to break it. So I wonder what we are going to do here - do we remove quotes only in some specific cases? In which cases?

@TJones do you have more context on this?

Unlike the question mark situation, where we jump in before the query is run, in this case we want to wait for it to "fail" (0 results? < 3 results?), and then try an alternate query, without quotes.

This gets into the same problem you mentioned in T138958: we have to figure out how to order and control the flow of the alternatives for dealing with failed/poorly-performing queries.

I could put together a straw man proposal for how to deal with suggestions, quotes, "wrong keyboard", and language ID, and have a more co-ordinated conversation about all this.

Yes, I think it's time we had some orderly discussion and proper design on how to handle such things, we start having more and more of these and we need to introduce some order into the madness :)

I have put together a straw man proposal for how to deal with suggestions, quotes, "wrong keyboard", and language ID, and have a more co-ordinated conversation about all this. Please direct comments about the bigger picture to the talk page of the link above.