-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LinkControl - initial search suggestions, first result is prematurely selected. #19630
Comments
Related discussions:
Technically, this issue appears to be fixed by the changes included in #19651, whereby: pressing Enter when entering a value in the LinkControl search field will not select any of the suggestions unless the user first navigates to one of those suggestions using the arrow key. It may be worth reformulating this issue to consider what we might want to be the ideal user interaction here. For example, it might be worth considering whether one of those suggestions should be shown to be selected by default. And if so, whether we should optimize that to select a search result vs. a raw URL, and whether we should be "smart" about considering raw URLs vs. search results.
|
The initial issue here has been fixed, but given the questions raised by @aduth above, I'm changing the labels and moving this back to Needs Design. FWIW, I'm quite happy with the current interaction 😄 |
I am not sure if I am understanding this right, this wouldn't be unexpected. Just to be super clear what I see is this: @aduth can you confirm this is me looking in right spot? |
@karmatosed Yes, if I recall correctly, one of the "open questions" here is whether any of those "Recently" or search-associated suggestions should be highlighted by default. I think this can have a pretty dramatic difference on what happens in a typical workflow of type, then press Enter. Consider:
In terms of how this is displayed to the user, and based on the text you quoted, we could show a suggestion as highlighted by default (presumably the first, which would have the behavior of 3a above). Seeing how this behaves in other link editing experiences (e.g. Google Docs), I'm inclined to think that we should require some user interaction (ArrowDown or mouse over) and never select/highlight a suggestion by default. If a user types a query and immediately presses enter, I think that value should be used verbatim. I expect this would be more aligned with their own expectations (especially in circumstances where they're pasting a complete URL in the input). |
To clarify, I believe this is the current behavior, and as such, if it's considered fine as-is (which would be my position), then we could consider this issue closed. |
I think also closing this, for now, makes sense, let's do that and we can always iterate. |
Originally posted by @WunderBart in #19458 (comment)
Description
When initial suggestions are present (see referenced PR) then the
input
has novalue
. However when you hit enter the first search suggestion is populated as the link. This shouldn't happen. The suggestion should only become "selected" if the user clicks it or uses the keyboard arrows to select it.The behaviour should be that hitting enter should show some kind of error indicating no value has been selected/entered and therefore no link can be created.
The text was updated successfully, but these errors were encountered: