Re-enable FormWithParentBindingContextTest.CanUseFormWithMethodGet
#63356
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.
Re-enable
FormWithParentBindingContextTest.CanUseFormWithMethodGet
Description
This pull request re-enables
FormWithParentBindingContextTest.CanUseFormWithMethodGet
by refactoring the test coverage for form handling with browser back/forward navigation by moving the relevant test fromFormWithParentBindingContextTest
to a new dedicated test class,FormWithNoBackForwardCacheTest
. Additionally, it introduces a new browser context and configuration to ensure correct browser behavior for these tests.Changes
CanUseFormWithMethodGet
test has been removed fromFormWithParentBindingContextTest
and added to a new file and class,FormWithNoBackForwardCacheTest
with different browser context.BackForwardCacheContext
, toBrowserFixture
for tests needing control over Chrome's back/forward cache.Reasoning behind changes:
In the recent changes in Chrome the Back/forward cache is now enabled by default. Due to this
autocomplete="off"
is not working correctly in the test. The new created ServerFixtureContext that disables this default behaviour in Chrome.Fixes #61882