Clarify Auto render mode behavior #31477
Merged
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
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.
Fixes #31228
Addresses #28161
Thanks @ghost! 🚀 ... I think the remarks that Mackinnon stated on general Auto mode rendering logic should be included. I'm not too keen at the moment on getting very deep into implementation details. After all, devs can't control those behaviors, and the timing of behaviors is somewhat arbitrary. Let's go with this for now, and we'll continue to work on the coverage as we go. Note that I can't use the
<head>content control example that he used because that coverage comes later in the doc set. That wouldn't make sense to include here and would confuse readers. It's best to just state the reason and not have an example.Internal previews