Framework Performance Opportunities
Some hand picked performance issues that can lead to decent improvements with just some framework changes without a big investment in many parts of the system.
No description
Currently, we only support general measurements of rich text (e.g. paragraph width/height, min/max intrinsic width), but granular measurements aren't supported yet.
Project to keep track to the necessary work to announce the stable release of platform views
No description
[local_auth] issue triage
No description
No description
[in_app_purchase] issue triage
No description
No description
No description
This project tracks a list of critical issues related to the gesture recognizers on iOS. The gesture recognizer handling on iOS is done with a ForwardingGestureRecognizer and DelayGestureReconizers. This mechanism fails in some scenarios. We should evaluate the scenarios and maybe find some different angles to solve the problems.
iOS 14 adoption engineering review
No description
No description
This project tracks a list of tasks that contributes to the new flutter create plugin command
Issues related to rendering fidelity including API incompatibility.
A set of issues we need to fix before removing the iOS platform view from technical preview.
Fixing these issues would reduce the friction in creating Flutter releases.
Migrates the devicelab from Cocoon to LUCI stack (http://go/flutter-devicelab-on-luci).
Tasks required to migrate the flutter sdk infrastructure to LUCI.
Engineer review of features missing or broken in some platforms
Bug fixes & enhancements for Fuchsia
Correctly use Vulkan validation layers in testing, with a white list for known failures.
Migrate supporting the Dart runner from the Flutter team to the Dart team
Add tests to the Flutter driver tests on Fuchsia.
Migrate the Flutter embedder on Fuchsia to use the Embedder API
Transfer the Flutter->Fuchsia GI roller to the Fuchsia team
A link widget that works everywhere and takes advantage of the web's element.
When this project was first created, Flutter apps were often quite janky (10x over single-frame budget) during the first run because of Skia shader compilations. A scalable and low-cost (which means as automatic as possible) solution is needed so whenever a new Flutter app has such an issue, its developers can easily solve it by following the tools/docs/APIs without incurring a significant amount of engineering cost from the Flutter team to debug and fix it.