Ah, it looks like we ran into a similar issue internally and it did indeed to be separate from the issue fixed in that CL. We don’t have a resolution yet, but we’re seeing it when an SObjectWidget is collapsed via a WidgetSwitcher. Our current workaround is to force an invalidation pass by adding/removing the button from the hierarchy (rather than adjust it’s visibility), would that be doable until we have a proper fix?
Best,
Cody