MatrixTransition.filterQuality doesn't outline performance implications if it is provided or null

Open Beginner friendly
#192,071 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
dart
Domain
documentation

Research direction

Start at the MatrixTransition.filterQuality API documentation and inspect the related implementation to establish what happens when the value is null versus provided. Update the documentation to explain when the child is re-rendered, the performance implications, and how the setting affects layer structure; done means readers can tell when to use each option.

Written by the indexing model from the issue text.

Description

a: animation d: api docs framework P2 team-framework triaged-framework

The documentation for MatrixTransition.filterQuality says:

The transform will be applied by re-rendering the child if filterQuality is null, otherwise it controls the quality of an ImageFilter.matrix applied to a bitmap rendering of the child.

But it is not clear when/how often the child is re-rendered if null, or what the performance implications of that are, or how setting it affects the layer structure. So it can be non-obvious to a reader when to set it and when not to.

This came up in reviewing this PR which sets it to null for platform views.

Dominant language
Dart
Stars
179k
Forks
31.7k
Avg merge
1d 21h
Merged PRs (30d)
413

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flutter/flutter

All issues in flutter/flutter

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.