[saurabh-mirajkar]

Fixes flutter/flutter#191556

This is the port of flutter/flutter#191721 following the Material/Cupertino decoupling.

Description

The Material 3 defaults documented in FilledButton.defaultStyleOf did not match the values used by _FilledButtonDefaultsM3.

The documentation described the tonal variant colors (secondaryContainer / onSecondaryContainer) and corresponding overlay colors, while the implementation uses primary / onPrimary.

This updates the Material 3 defaults documentation to match the existing implementation.

Tests

• Ran dart format packages/material_ui/lib/src/filled_button.dart.
• No tests added as this is a documentation-only change.

Original Flutter PR: flutter/flutter#191721

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[gemini-code-assist]

Code Review

This pull request updates the documentation for FilledButton in packages/material_ui/lib/src/filled_button.dart to correctly reflect its Material 3 default style implementation, changing references from secondaryContainer and onSecondaryContainer to primary and onPrimary respectively. Additionally, a pending changelog entry is added to document this fix. There are no review comments, and I have no feedback to provide.

[stuartmorgan-g]

test-exempt: comment-only change

[QuncCccccc]

LGTM. Thanks a lot for your contribution!