It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

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.

Checking the value of clipBehaviour wouldn't really test anything since the change in state is further down the tree and an entire golden test for this small bug fix seems a little excessive IMO

I had to change an existing test because the "default" value for the SubMenuButton widget changed from Clip.none to Clip.hardEdge. However, since the original default value was never used in the widget tree and a hardcoded value of Clip.hardEdge was used instead, there is no change in functionality. I hope this is ok? :)

@gspencergoog I'm not really sure how to test this... Any thoughts?

This requires a test in order to land. You can get the material from _MenuPanel and check its clip behavior (you can find similar test in the framework)

@TahaTesser Ok, added a test to check the default clip of a ManuAnchor widget. PTAL!

@TahaTesser I think this is what you meant? :)

We need a second review from @gspencergoog to land this.