-
Notifications
You must be signed in to change notification settings - Fork 725
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
[droid] "Uri too long" in WebView.NavigateToString remediation #2023
Conversation
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.
Thanks for this contribution! A few tweaks and it's ready.
// step 1: generate long string | ||
_app.Tap(startButton); | ||
|
||
// _app.Wait(TimeSpan.FromSeconds(300)); // Android: 20 is sufficient |
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.
Delete the commented code
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.
Commented code is left by purpose - as for WASM (which is interpreter, not compiler) default timeout can be too short, and maybe adding _Wait would be necessary for this.
But OK, I will delete it (but it means that I have to re-create PR, as I was told that it had to be single commit in PR, and I don't know how to make changes without adding new commit to PR)
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.
There's no need to recreate the PR. It's fine to add additional commits that address PR feedback.
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.
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.
So, one commit per one changed file is ok?
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.
That's fine in this case.
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.
Also on the subject of commits - for the future please try to give each one a meaningful commit message. Don't just use the default 'Updated file.cs' when you're using the GitHub web interface.
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.
ok
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.
All corrections are made.
So, can this PR be approved/merged? :)
...SamplesApp.UITests/Windows_UI_Xaml_Controls/WebViewTests/UnoSamples_Test_NavigateToString.cs
Show resolved
Hide resolved
Changed variable name from _afterToString to _wasLoadedFromString
GitHub Issue (If applicable):
#1527
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When WebView.NavigateToString(long_string)
exception is thrown: "uri too long".
What is the new behavior?
no exception is thrown
PR Checklist
Please check if your PR fulfills the following requirements:
Other information
Recreated PR 1732 (as probably only of squashing way available to me).
Many thanks to Sébastien Goyette for helping me in creating tests for this PR.
CI is failing for WASM, as error I corrected on Android still exist on WASM.