Move Blazor built-in components down in ToC #19917
Closed
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.
Scott ...
I'm still not getting the best behavior out of the ToC with the built-in component links embedded near the top of the Components node. The problem is still that when a reader selects one they end up with a highlighted ToC entry of the component in the Built-in components list and not the highlighted ToC entry of the topic where that link sent them.
I think what's happening is that it's matching the first
href
/uid
(URL) it comes to down the ToC. I think that by moving the whole node to the bottom of the Blazor ToC that it will start matching, thus highlighting, the topic where the component is described.If you think I'm right, let's give this PR shot. If you have a better plan to achieve the behavior I seek, I'm all 馃憘馃憘馃憘馃憘馃憘.
UPDATE: What about setting
topicHref
?... that sounds good if I'm interpreting it correctly as matching my goal (i.e., set it to the landing topic). 馃 Depends on what they mean by "it" ... pronouns ... they're great ... until they aren't. 馃槃