Fix scrolling issue in Flutter QS #10326
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.
Changes
Currently, the Flutter interactive QuickStarts for mobile and web have an issue when scrolling past the first "Getting Started" step, whereas the content of the following step remains dimmed:
Screen.Recording.2023-10-31.at.13.16.07.mov
Turns out that the step whose content remains dimmed is added through an include. This include contains a level 2 heading with the name of the step ("Configure Auth0"), and is being included after another level 2 heading ("Getting Started"). While this should result (and does result) in a new level 2 heading being appended, it trips up the scroll behavior of the docs app.
This PR simply removes the "Getting Started" heading so that the includes follow after a level 1 heading, which does not cause any issues when scrolling. This is intended as a stop-gap measure until the underlying issue is fixed on the docs app.