1925219 - [Tab Strip Post Beta] Support status bar color for Android 15

Status: VERIFIED FIXED

(Firefox for Android :: Tabs, defect, P2)

Description

[Rahul Sainani [:rsainani]]

Attachment: Screenshot_20241016-212302.png

Note: This only happens on Android 15 when tab strip is enabled on nightly and beta 133 onwards.

Steps to reproduce

1. Open fenix on a large screen on nightly or beta 133+.
2. Observe that Tab Strip is visible

Expected behavior

Status bar color should match the tab strip

Actual behavior

Status bar color doesn't match

Device information

• Firefox version: Nighty - 132+ & Beta 133+
• Android device model: Pixel Tablet
• Android OS version: 15

Any additional information?

This is blocked till we add edge to edge support for Android 15.

Comment 1

[Kurt Felton]

This seems to have been fixed in latest nightly.

Comment 2

[Kurt Felton]

Attachment: Screenshot_20241020-235825.png

This is what I am seeing on build from 10-18.

Comment 3

[Rahul Sainani [:rsainani]]

Thanks for the info Kurt!

Comment 4

[Rahul Sainani [:rsainani]]

Now that [:mcarare] has fixed Bug 1925070 and Bug 1881685, we can verify this. Note that this can only be verified when both of them are present in the nightly build.

Comment 5

[Mira Lobontiu (Android QA)]

Verified as fixed on the latest Fenix Nightly 133.0a1 from 10/22 with:

• Lenovo TB X606X (Android 10), and
• Samsung Galaxy Tab S9 Ultra (Android 14), and
• on a Google Pixel tablet (Android 15) - emulator - please see the attached screenshot.

Comment 6

[Mira Lobontiu (Android QA)]

Attachment: Screenshot_20241022_162727.png

Comment 7

[Kurt Felton]

Is it possible to reduce the flickering when opening a new tab on the Tab Strip? The entire Tab Strip flickers when adding a new tab to the strip bar. I am using Pixel Tablet.

Comment 8

[Kurt Felton]

Attachment: screen-20241031-013654.mp4

Tab Strip is flickering when opening or close tabs due to animation

Comment 9

[Rahul Sainani [:rsainani]]

Thanks for the report Kurt! We're aware of this issue. Please keep an eye on Bug 1915815 for more updates about this. I'll close this issue as this specific issue was already resolved.