Repository navigation
[a11y] With maximum accessibility font size, action buttons in AlertDialogs cause rendering overflow exceptions #42696
Description
b/142592672
-
On iOS, go to Settings -> General -> Accessibility -> Larger Text and set to maximum.
-
Observe dialogs with actions can have rendering exceptions.
Full repro code:
import 'package:flutter/material.dart';
void main() => runApp(MyApp());
class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(primarySwatch: Colors.blue),
home: Scaffold(
appBar: AppBar(title: Text('Alert Dialog Test')),
body: Builder(
builder: (context) => Center(
child: RaisedButton(
child: Text('Show Alert'),
onPressed: () {
showDialog(
context: context,
builder: (context) {
return AlertDialog(
title: Text('Alert Dialog'),
content: Text('Alert text'),
actions: [
FlatButton(onPressed: () {}, child: Text('Decline')),
FlatButton(onPressed: () {}, child: Text('Accept')),
],
);
},
);
},
),
),
),
),
);
}
}
(We would like the text to show up fully, and we we would like them to be stacked vertically if they do not fit).
Activity
Hixie commentedon Oct 29, 2019
This has been fixed!
shihaohong commentedon Nov 7, 2019
Since #43226 was reverted, part of the problem has come back and we will need to re-design a solution that is less of a breaking change.
shihaohong commentedon Feb 19, 2020
Just posting an update here that I'm still actively working on this issue. It's been taking a long time due to unforeseen breaking changes and test failures in google3 that required fixes to the upstream framework before I could proceed:
Once these changes have been rolled into google3, I can continue with the migration
shihaohong commentedon Mar 4, 2020
The behavior in the repro code has already been fixed, so I'll now close the issue
github-actions commentedon Aug 22, 2021
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.