-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm] browser http response stream could be seekable #54603
[wasm] browser http response stream could be seekable #54603
Conversation
An additional test for when runtime/src/libraries/System.Net.Http/src/System/Net/Http/BrowserHttpHandler/BrowserHttpHandler.cs Lines 275 to 283 in d1b5a34
|
src/libraries/Common/tests/System/Net/Http/HttpClientHandlerTest.cs
Outdated
Show resolved
Hide resolved
@@ -969,21 +968,24 @@ public async Task ReadAsStreamAsync_HandlerProducesWellBehavedResponseStream(boo | |||
// Boolean properties returning correct values | |||
Assert.True(responseStream.CanRead); | |||
Assert.False(responseStream.CanWrite); | |||
Assert.False(responseStream.CanSeek); | |||
Assert.Equal(PlatformDetection.IsBrowser, responseStream.CanSeek); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want this check after all? Hypothetically, when there's new platform with response stream that can seek as well, this line would need an update again. Or does it has some other purpose here?
@pavelsavara it seems that this PR has broken the full Framework build ( |
thanks Adam, I missed both the build failure and the #IF. |
Revert #54742 |
Next attempt in #54749 |
As discussed here, the unit test is too restrictive.
Fixes #54159