fix: replace NetworkIdle with Load + explicit element wait to fix Firefox integration test timeouts - #435
Draft
BenjaminMichaelis with Copilot wants to merge 2 commits into
Draft
Conversation
…tion tests Firefox's Blazor WASM runtime keeps background connections open, preventing WaitForLoadStateAsync(NetworkIdle) from ever resolving within the 90-second timeout. Replace it with the reliable WaitForLoadStateAsync(Load) paired with an explicit element-level wait that confirms the page is truly interactive: - EditorTests: new WaitForEditorLoadedAsync() helper waits for Load then for div[role="code"] to be visible (Monaco editor present = Blazor running) - WasmRunnerTests: Load + WaitFor(Attached) on wasmRunner-sentinel element - TryDotNetJsIntegrationTests: Load only (FindEditor() already waits for the editor element afterward) Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix issues found with Copilot
fix: replace NetworkIdle with Load + explicit element wait to fix Firefox integration test timeouts
Aug 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Firefox's Blazor WASM runtime keeps persistent background connections open, so
WaitForLoadStateAsync(LoadState.NetworkIdle)never resolves — the previous 90 s timeout increase just delayed the inevitable failure.Changes
PageExtensions.cs— newWaitForEditorLoadedAsync()helper: waits forLoadState.Loadthen polls fordiv[role="code"]visibility (Monaco rendering is a reliable Blazor-initialized signal)EditorTests.cs— allWaitForLoadStateAsync(NetworkIdle)calls replaced withWaitForEditorLoadedAsync()WasmRunnerTests.cs— replacedNetworkIdle+IsHiddenAsync()withLoad+WaitFor(Attached)on thewasmRunner-sentinelelement (sentinel is appended by JS only after WASM initializes)TryDotNetJsIntegrationTests.cs— replacedNetworkIdlewithLoad(subsequentFindEditor()already waits for the editor element)