Android 11 notification bar background color is wrongly determined, causing unreadable result

[adam900710]

Steps to reproduce

0. Set "Dark" system theme (Lineage OS 18.1 in my case)
1. "Install" Twitter as PWA
2. Open Twitter PWA
3. Check the notification bar background

Expected behaviour

For the same "Dark" theme, weather.com results a much better background color:

Actual behaviour

The result for twitter.com can be seen here

Note the white notification bar, and since it's in dark mode, the text are also white, making things unreadable.

Device name

OnePlus 7t

Android version

Android 11 (lineage OS 18.1)

Firefox release type

Firefox

Firefox version

95.2.0

Device logs

No response

Additional information

It looks like the background color of the notification bar is determined by the main color used in the favicon.

Thus for weather.com it's blue, but unfortunately for twitter, the white bird makes the background to be white.

I'd say the behavior is completely unnecessary. Just use the default color is good enough.
The favicon never really indicate the main color of the web, not to mention users may use add-ons like the darkreader to change the look.

┆Issue is synchronized with this Jira Task

[sflorean]

Tested on Samsung A32 (Android 11) and the same behavior is displayed for both Firefox and Chrome.
@adam900710 can you please confirm this?

[adam900710]

@sflorean For chrome, it's not changing the notification bar color at all for both installed PWA twitter.com or weather.com.
(Aka, black notification bar)

So is this ROM related? Or maybe there is some lineageOS specific setting to prevent the background color change of notification bar?

[Tesseeaye]

I'm having this same issue with Twitter's PWA on a Samsung Galaxy S21 (Android 12) in Firefox Nightly 97.0a1 (Build #2015854347)

[stale]

See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[makotokato]

I can still reproduce this with Android 13 + Pixel 4a (See #27221 (comment) for Chrome behavior)

[cpeterso]

Moved to bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1807414

Change performed by the Move to Bugzilla add-on.