Bug 27023 - 'User Notification Interface controller' name appears cutoff in WatchKit designer
Summary: 'User Notification Interface controller' name appears cutoff in WatchKit desi...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 3.9
Hardware: PC Windows
: Low enhancement
Target Milestone: ---
Assignee: Bugzilla
: 32570 ()
Depends on:
Reported: 2015-02-13 01:07 UTC by Prashant manu
Modified: 2017-07-10 17:02 UTC (History)
8 users (show)

Tags: ac vs vsmac
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 for Bug 27023 on Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.
Related Links:

Comment 2 Alan McGovern 2015-02-13 07:07:15 UTC
We might need a smaller font. We can also shorten the name by removing the 'User' part
Comment 3 GouriKumari 2015-03-18 14:45:09 UTC
Since, this is an enhancement I am changing the milestone.
Comment 4 Alan McGovern 2015-07-29 09:12:48 UTC
*** Bug 32570 has been marked as a duplicate of this bug. ***
Comment 5 Pierce Boggan [MSFT] 2017-07-10 16:59:09 UTC
Thanks so much for taking the time to submit this report! I can confirm using the latest Visual Studio 2017 Preview version 15.3 I am able to still reproduce this issue.