RenderedFragment not detecting changes in render tree when component with changes is below a CascadingValue #43
Description
Credit to @FritzAndFriends for discovering this.
This problem shows up when a component changes that is a child component of a CascadingValue. Then the RenderedFragment does not think there is a change and keeps the existing DOM nodes/markup.
E.g.: CUT > CascadingValue > component that changed
Then CUT won't see the change.
The related commit fixes the issue.