Repository navigation
Clearly document that CupertinoSlidingSegmentedControl's unselected segments are translucent #164073
Description
Steps to reproduce
Create a CupertinoSlidingSegmentedControl with content "below" it. The content below is visible in the unselected segments.
Expected results
Unselected segments should be opaque. Content below the unselected segment should not be visible.
Actual results
Unselected segments are translucent. Content below the unselected segment is visible.
Code sample
Code sample
import 'package:flutter/cupertino.dart';
void main() {
runApp(
CupertinoApp(
theme: CupertinoThemeData(
brightness: Brightness.light,
),
home: CupertinoPageScaffold(
child: Stack(
children: <Widget>[
Text('Hello world'),
CupertinoSlidingSegmentedControl<int>(
onValueChanged: (value) {},
children: {
0: Text('Foo'),
1: Text('Bar'),
}
),
],
),
),
),
);
}Screenshots or Video
Screenshots / Video demonstration
Logs
N/A
Flutter Doctor output
N/A
Activity
LongCatIsLooong commentedon Feb 25, 2025
This is because
UIColor.tertiarySystemFillis translucent (alpha = 0.12 in light mode). I think you'll get the same behavior with aUISegmentedControl.Yeah
UISegmentedControlis transparent. I put aUILabelbehind a segmented control:danagbemava-nc commentedon Feb 25, 2025
Hi @LongCatIsLooong, seeing as this occurs with the native components, is there any further action to be taken on this issue?
loic-sharma commentedon Mar 7, 2025
Removing the "waiting for customer" label as this is waiting for a response from triagers, not from me :)
I suspect this behavior should be kept as-is as
CupertinoSlidingSegmentedControl's transparency matchesUISegmentedControl's transparency. However, I'd suggest we document this behavior as it's surprising and can be easily mistaken as a bug in Flutter.[-]CupertinoSlidingSegmentedControl's unselected segments are translucent[/-][+]Clearly document that CupertinoSlidingSegmentedControl's unselected segments are translucent[/+][cupertino_ui] Document translucent default background of CupertinoSl…
github-actions commentedon Nov 11, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.