Bug 54796 - [VS-PropPage] Additional Supported Encodings dropdown menu is not left-aligned with other items
Summary: [VS-PropPage] Additional Supported Encodings dropdown menu is not left-aligne...
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 4.5.0 (15.2)
Hardware: PC Windows
: Normal trivial
Target Milestone: 15.2
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-04-07 19:22 UTC by Ben Beckley
Modified: 2017-04-11 21:37 UTC (History)
4 users (show)

Tags:
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 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:
Status:
VERIFIED FIXED

Description Ben Beckley 2017-04-07 19:22:44 UTC
Tested with XVS 4.5.0.322 (43f3cba)
Affects VS2013 and VS2015

Notice how the dropdown menu isn't aligned to the text field above it on the left. No functional issue here, it just doesn't look proper in my opinion.
https://www.screencast.com/t/IsApOcBQ6F

Reproduction Steps:
1) Create a new Android app from a template (WebView app in my case)
2) Go to project properties > Android options

env info: https://gist.github.com/BenBeckley/fdb4ba8ffab56c7a4027344eb8b558ea
Comment 1 Jose Gallardo 2017-04-11 16:08:19 UTC
Should be resolved in 4.5.0.341
Comment 2 Ben Beckley 2017-04-11 21:37:12 UTC
Verified fix in 4.5.0.341 (05b65c7/d15-2)