Allow overwriting PageLoadStrategy in wasm tests
#1268
Merged
Conversation
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
This was referenced Sep 13, 2024
akoeplinger
reviewed
Sep 14, 2024
src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmTestBrowserCommand.cs
Show resolved
Hide resolved
3 tasks
Member
Author
|
/ba-g android is not connected |
akoeplinger
approved these changes
Sep 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Trying to fix the new chrome bump: dotnet/runtime#107504.
Till now we were running tests always with
PageLoadStrategywith default valueNormal. It is documented to have caused problems in testing with Selenium with older versions of chrome. This change does not change the default value, only provides an option to overwrite it.https://www.selenium.dev/documentation/webdriver/drivers/options/#pageloadstrategy