Bug 13405 - Poor user experience in completion tooltip
Summary: Poor user experience in completion tooltip
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Jason Smith [MSFT]
Depends on:
Reported: 2013-07-23 08:36 UTC by Marek Safar
Modified: 2017-07-21 09:49 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Marek Safar 2013-07-23 08:36:52 UTC
When there is only 1 available method overload completion experience is inconsistent and confusing.

XS sometimes shows up/down arrows which are misleading because pressing up/down keys in this case does hide completion window.

Comment 1 Marius Ungureanu 2013-09-02 19:33:12 UTC
This is somewhat a duplicate of #12114
Comment 2 Adam Hartley [MSFT] 2017-07-21 09:49:09 UTC
Thanks so much for taking the time to submit this report! I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 for Mac Preview version 7.1, and I was unable to hit the problem. It appears as if the up and down arrows are not present in this situation.

If this issue is still occurring for you, please reopen this report and attach a reproduction, ideally starting with a new template project and then adding just the code necessary to demonstrate the issue.