Remove DNS resolver workaround from the test framework #17547
Merged
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.
The
if
statement is no longer necessary because the Node.js versions that didn't providedns.setDefaultResultOrder
are no longer supported, but looking into this a bit more it turns out that the entire workaround is no longer necessary because the issue got fixed in Firefox 105 in bug 1769994. Indeed, Firefox now starts nicely with the workaround removed.Reverts 60ed3cd.