You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
trusktr commentedon Jul 19, 2020
Hi @playgithub! Thanks for opening the issue!
Not sure I understand.
I go there, and I'm at the top of the page.
When I click on that, it takes me to that page, at the top, as expected.
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.
What are you expecting here?
playgithub commentedon Jul 20, 2020
trusktr commentedon Jul 20, 2020
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:
trusktr commentedon Jul 20, 2020
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 commentedon Jul 20, 2020
thanks
Anilople commentedon Dec 19, 2020
Same problem.
In wiki page Apollo性能测试's link 分布式部署指南中的缓存配置
expect
but get
Platform information:
Docs information:
.mdfile: distributed-deployment-guide.md