Brave bottom address bar mismatching color with Android bottom navigation

Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.


Description of the issue:

When using both bottom toolbar and bottom addressbar, then the android bottom navigation buttons, get a background matching the website color instead of following the browser theme color.

How can this issue be reproduced?

  1. With android bottom navigation enabled, and Brave’s address bar on top and toolbar on bottom, the android bottom navigation matches Brave’s theme color

  2. Switch to also bottom address bar

  3. Now the bottom navigation has a background color matching that of the website, instead of matching Brave’s theme

Expected result: Android’s bottom navigation should match the browser’s theme, not the website one. Otherwise there is a strange color jump, even more obvious when one is light and the other dark.

Brave Version( check About Brave): Brave 1.87.190, Chromium 145.0.7632.109

Mobile Device details

Samsung Galaxy S21 Ultra

Additional Information:

Android bottom navigation enabled

Address bar on top, toolbar on bottom: navigation is dark, perfectly matching the browser theme

Both address bar and toolbar are on top: the bottom navigation perfectly matches the theme color

Both addresses bar and toolbar at bottom: the navigation bar is strangely matching the theme color, creating a strange visual jump, even more noticeable when the website has a light background

Example with a light background to show what I meant, this looks very off. I think it should just keep working like it does when just having the toolbar at the bottom.

I will revert to top address bar and toolbar for now. Let me know if I can help in any way, and thank you for looking into this :blush:

Should I send this bug report on github or is this the right place? :blush:

@fcole90 you are in the right place, although in the future you’re more than welcome to open an issue on our Github as well!

I went ahead and filed this one away for the devs to review: