-
Notifications
You must be signed in to change notification settings - Fork 509
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
Add note on NavigateToString limit and common error #3236
Conversation
There's a few conversations on Twitter about the size limit of `NavigateToString` not being obvious, and the error being hard to understand. This replaces a redundant "Additional web resources" section with one calling out the size limit, and including the error string in hopes of improving discoverability.
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.
Approved PR after pushed commit for writer/editor review.
Learn Build status updates of commit dbf1880: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit 9226f5e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit 5410b1b: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Rendered article section for review:
There's a few conversations on Twitter about the size limit of
NavigateToString
not being obvious, and the error being hard to understand.This PR replaces a redundant "Additional web resources" section with one calling out the size limit, and including the error string in hopes of improving discoverability.
Outline of headings
AB#52734029