fix!: Align WebView.NavigateWithHttpRequestMessage signature with UWP #11344
+10
−25
Conversation
This file contains 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
github-actions
bot
added
platform/android 🤖
|
@MartinZikmund FYI |
Youssef1313
force-pushed
the
webview-align
branch
2 times, most recently
from
f9150f5 to
0aa65a4
Compare
BREAKING CHANGE: WebView.NavigateWithHttpRequestMessage parameter type is now `Windows.Web.Http.HttpRequestMessage` instead of `System.Net.Http.HttpRequestMessage`
Youssef1313
force-pushed
the
webview-align
branch
from
0aa65a4 to
5870430
Compare
github-actions
bot
added
the
area/automation
jeromelaban
approved these changes
Feb 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
BREAKING CHANGE: WebView.NavigateWithHttpRequestMessage parameter type is now
Windows.Web.Http.HttpRequestMessageinstead ofSystem.Net.Http.HttpRequestMessageGitHub Issue (If applicable): #8339, closes #11099
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information
Internal Issue (If applicable):