Bug 35391 - AppCompat Toolbar on pre Lollipop back button color changes to white
Summary: AppCompat Toolbar on pre Lollipop back button color changes to white
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 1.5.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-10-30 07:22 UTC by Caan Mee
Modified: 2015-12-11 16:05 UTC (History)
1 user (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 Caan Mee 2015-10-30 07:22:10 UTC
I currently tested the AppCompat using a Toolbar with the DrawerLayout.
We use a black back button on a white toolbar.

This works fine on >= Lollipop.

But on < API21 I noticed a strange behaviour:

1) Open the app (hamburger is shown)
2) Push any page on the Navigation stack (back button, black arrow is shown)
3) Push another arbitrary page on the stack (back button, white arrow is shown, but for sure you can't see a white backbutton on a white toolbar, but it's there)

I do not change the back button color programmatically.

See also: https://forums.xamarin.com/discussion/comment/162226
Comment 1 Rui Marinho 2015-12-11 16:05:51 UTC
User reported was fixed