Some blazor event tests failures seem to be related and will fail together

[HaoK]

From #31156
so there's something about the interaction between this set of quarantined tests that when they run will cause a large set of tests to fail. When we last unquarantined most of these we saw similar failures start in the CI, I really think our current system of only running the quarantined tests and not the full set of tests is not a good mechanism to verify that the tests well behave once unquarantined, we should be running the full set of normal tests + quarantined tests to accurately determine things are fixed

It looks like a bunch of the event tests failed together and caused more test to fail too:

The tests being unquarantined in events that seem to cause issues:
ServerEventTest.EventDuringBatchRendering_CanTriggerDOMEvents
EventBubblingTest.BubblingStandardEvent_FiredOnElementWithoutHandler
EventTest.PreventDefault_DotNotApplyByDefault
EventTest.InputEvent_RespondsOnKeystrokes
EventTest.InputEvent_RespondsOnKeystrokes_EvenIfUpdatesAreLaggy
RoutingTest.PreventDefault_CanBlockNavigation_ForInternalNavigation_PreventDefaultTarget
RoutingTest.PreventDefault_CanBlockNavigation_ForExternalNavigation_PreventDefaultAncestor
(also caused [Non]BubblingCustomEvent to all fail too which aren't currently quarantined and other preventdefault tests)

It would be good to figure out why there's cross test interaction in these event tests, I'm not sure these are definitely the culprits but something in that set of tests will cause massive failures when they are all enabled.

[ghost]

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.

[ghost]

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.