Bug 56878 - [PlistEditor] Capabilities in Capabilities section show black text on dark mode (unreadable)
Summary: [PlistEditor] Capabilities in Capabilities section show black text on dark mo...
Status: RESOLVED DUPLICATE of bug 56623
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.5.0 (15.2)
Hardware: PC Mac OS
: Normal normal
Target Milestone: 15.3
Assignee: Bugzilla
Depends on:
Reported: 2017-05-26 15:34 UTC by Vincent Dondain [MSFT]
Modified: 2017-06-06 16:49 UTC (History)
5 users (show)

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

Plist Editor Capabilities (45.48 KB, image/png)
2017-05-26 15:34 UTC, Vincent Dondain [MSFT]

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:

Description Vincent Dondain [MSFT] 2017-05-26 15:34:02 UTC
Created attachment 22508 [details]
Plist Editor Capabilities

See attachement, the text for the capabilities should be white on dark mode otherwise it's unreadable (:

Used the following environment: https://gist.github.com/VincentDondain/9e54ad828c6bdb771488112a55412cb0
Comment 1 Emanuel 2017-06-06 13:56:54 UTC
Fixed on master and d15-3 branches: 280083265f955981a4bb17bc18699289ee3562af
Comment 2 Ben Beckley 2017-06-06 16:49:05 UTC

*** This bug has been marked as a duplicate of bug 56623 ***