Skip to content

scroll problem #1202

Open
Open
@playgithub

Description

@playgithub

To reproduce the problem:

  1. Open https://xmake.io/#/getting_started
  2. Locate to "Getting Started / Project Examples", and make sure it's expanded
  3. Locate to the next section, i.e. "Getting Started / Configuration"
  4. It doen't scroll properly

Activity

trusktr

trusktr commented on Jul 19, 2020

@trusktr
Member

Hi @playgithub! Thanks for opening the issue!

Not sure I understand.

  1. Open https://xmake.io/#/getting_started

I go there, and I'm at the top of the page.

  1. Locate to "Getting Started / Project Examples", and make sure it's expanded

When I click on that, it takes me to that page, at the top, as expected.

  1. Locate to the next section, i.e. "Getting Started / Configuration"

Then when I click on that, it goes to that page, and I am at the top, as expected. When we go to a new page, it should be at the top.

  1. It doen't scroll properly

What are you expecting here?

playgithub

playgithub commented on Jul 20, 2020

@playgithub
Author
  1. Locate to "Getting Started / Project Examples"
    1
  2. Locate to "Getting Started / Configuration"
    2
  3. unexpected scroll position
    3
  4. expected scroll position
    should_be
trusktr

trusktr commented on Jul 20, 2020

@trusktr
Member

Ah, got it. Your expecting the sidebar to scroll. I don't think this has been implemented (at least not during the time I've been working with the project).

This would be great to have. It's a problem that is exacerbated when the sidebar has long sub-lists. With smaller amounts of items on each page, then the problem isn't so noticeable because when the menu expands usually all items can fit on screen.

Two possible workarounds for now:

  • split the page into smaller pages, so that each expander opens to show less amount of items.
  • perhaps with a Docsify plugin it is possible to scroll the sidebar after a page change, by detecting which item is active.
trusktr

trusktr commented on Jul 20, 2020

@trusktr
Member

As for an official solution, we can modify the code at the same location where the current code is for scrolling the main content. We can make this an option so it is a semver-minor non-breaking change, then in v5 we can change the default to enabled.

playgithub

playgithub commented on Jul 20, 2020

@playgithub
Author

thanks

Anilople

Anilople commented on Dec 19, 2020

@Anilople
Contributor

Same problem.

In wiki page Apollo性能测试's link 分布式部署指南中的缓存配置

expect

image

but get

image


Platform information:

  • OS: Win10 home version 1909
  • Browser: Google Chrome 87.0.4280.88

Docs information:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @trusktr@playgithub@Anilople@sy-records

        Issue actions

          scroll problem · Issue #1202 · docsifyjs/docsify