Skip to content

[wasm] Bump chrome for testing - linux: 145.0.7632.116, windows: 146.0.7680.31#125017

Merged
ilonatommy merged 3 commits intomainfrom
update-chrome-version-22531989897
Mar 9, 2026
Merged

[wasm] Bump chrome for testing - linux: 145.0.7632.116, windows: 146.0.7680.31#125017
ilonatommy merged 3 commits intomainfrom
update-chrome-version-22531989897

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 1, 2026

No description provided.

@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival
See info in area-owners.md if you want to be subscribed.

DOMContentLoaded fires when the initial HTML skeleton is parsed, but
Blazor WebAssembly still needs to download the runtime, managed
assemblies, and render the component tree. Tests that immediately try
to click elements after DOMContentLoaded can fail on slow CI machines
because the Blazor content hasn't replaced the loading spinner yet.

Add a wait for the Blazor-rendered '.page' element inside '#app' to
appear before executing any page interactions. This ensures Blazor
has fully initialized and the navigation links are actually present
and interactive.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@ilonatommy ilonatommy force-pushed the update-chrome-version-22531989897 branch from 635d910 to 5e210f7 Compare March 9, 2026 13:35
@ilonatommy
Copy link
Member

I added a WBT fix because I was not 100% sure if the timeout was not affected by the bump. It looks like it was not.

@ilonatommy ilonatommy merged commit 1709ae0 into main Mar 9, 2026
43 checks passed
@ilonatommy ilonatommy deleted the update-chrome-version-22531989897 branch March 9, 2026 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant