Skip to content
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

Option for sticky scroll to prioritize inner blocks #208406

Open
fnHoj opened this issue Mar 22, 2024 · 9 comments · May be fixed by #235949
Open

Option for sticky scroll to prioritize inner blocks #208406

fnHoj opened this issue Mar 22, 2024 · 9 comments · May be fixed by #235949
Assignees
Labels
editor-sticky-scroll feature-request Request for new features or functionality
Milestone

Comments

@fnHoj
Copy link

fnHoj commented Mar 22, 2024

Currently sticky scroll always stick the first lines, which may make it less useful in some situations.

Consider the following case:

<!DOCTYPE html>
<html>
    <body>
        <script>
            class SomeClass {
                constructor() {
                    // Long & complicated code
                    // Long & complicated code
                    // Long & complicated code
                }
            }
        </script>
    </body>
</html>

If we scroll to the comments with a max line count set to 3 for sticky scroll, <html>, <body> and <script> will stick around. However, we might not want to always stare at <html> whenever we write HTML, so it may be better to let <html> make room for inner code blocks.

Current Suggested alternative
"<html>", "<body>" and "<script>" stuck around, as they normally would It might be better if "<script>", "class SomeClass {", and "constructor() {" stuck around instead.

This problem also applies to other languages with a complicated program structure. Adding such an option can sometimes make it more efficient to work with these languages.

@aiday-mar aiday-mar added editor-sticky-scroll feature-request Request for new features or functionality labels Mar 22, 2024
@vscodenpa vscodenpa added this to the Backlog Candidates milestone Mar 22, 2024
@vscodenpa
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@Number-3434
Copy link

I would also find this useful when using Flutter, as it would show the nearest nested widget.

@vscodenpa
Copy link

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa
Copy link

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
@assyrus-favolo
Copy link

It's a pity that this has been closed, I feel like the request might not have been advertised enough since, for example, even Visual Studio has such an option https://learn.microsoft.com/en-us/visualstudio/ide/editor-sticky-scroll?view=vs-2022#inner-and-outer-scopes, so clearly there is an interest in general

@aiday-mar
Copy link
Contributor

Hi I will keep this feature request open

@aiday-mar aiday-mar reopened this Sep 5, 2024
@assyrus-favolo
Copy link

Thanks for considering this! :)

Copy link

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2024
@aiday-mar
Copy link
Contributor

Hi sorry all, I am not exactly sure what is happening with our bot. I believe it is because I placed the issue in the backlog candidate. I will reopen it and place it in the backlog directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor-sticky-scroll feature-request Request for new features or functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants