Multiple cascading parameters update from child component issue

[maryamhdr]

Describe the bug

I've an application which has one cascading parameter. In app's header component, I'm displaying some values based on the cascading parameter and in child parameter, I change properties of that cascading parameter object, and everything works like a charm. But when I add another cascading parameter, I face an issue when header component's UI which is dependent on both cascading parameters, doesn't update as expected.

To Reproduce

I've an app located at https://github.com/maryamhdr/BlazorMultipleCascadingParametersIssue.
The app's header shows title and subtitle which are cascading parameters.
In FirstPage's OnInitialized, I set title and subtitle to 1 and in SecondPage I set those cascading parameters to value 2.

I'd expect to see "1 - 1" in while I'm in FirstPage, and "2 - 2" while I'm in SecondPage but sometimes I see "1 - 1" in SecondPage and "2 - 2" in FirstPage which is not expected at all.

Note that If I merge props of both cascading parameters into one cascading parameter, everything works fine!

Further technical details

• ASP.NET Core version 5rc1
• Include the output of dotnet --info
  .NET SDK (reflecting any global.json):
  Version: 5.0.100-rc.1.20452.10
  Commit: 473d1b592e

Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\5.0.100-rc.1.20452.10\

Host (useful for support):
Version: 5.0.0-rc.1.20451.14
Commit: 38017c3935

.NET SDKs installed:
3.1.401 [C:\Program Files\dotnet\sdk]
5.0.100-preview.8.20417.9 [C:\Program Files\dotnet\sdk]
5.0.100-rc.1.20452.10 [C:\Program Files\dotnet\sdk]

• The IDE (VS / VS Code/ VS4Mac) you're running on, and it's version
  Microsoft Visual Studio Community 2019 Preview
  Version 16.8.0 Preview 3.0

https://github.com/maryamhdr/BlazorMultipleCascadingParametersIssue

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mkArtakMSFT]

Hi. Thanks for contacting us.
We're closing this issue as there was not much community interest in this ask for quite a while now.
You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.