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
markdown files preview does not save scroll position #63690
Comments
(Experimental duplicate detection)
|
@mjbvz , looking into this :) |
@AbdullahWali and @mjbvz , It seems to retain the scroll position when i am trying. |
@AbdullahWali Can you please share a markdown file that has this issue |
I could reproduce the bug with any md file (on macOS and windows). The scroll position is not saved for the Mardown Preview (which you can get by pressing ⇧⌘V or Ctrl+Shift+V in a md file). The side-by-side preview is working fine. I'm looking at this issue right now to fix it |
@Robhox , Thanks for the update. |
@skprabhanjan I'm already looking into it and would love to solve it if it's ok for you |
@Robhox , sure go ahead , seems like your first contribution , so will leave this to you :) |
@skprabhanjan Did you had any ideas how to fix this issue? I'm struggling to find where the position is saved when you switch tabs. |
@Robhox , Need to check it , Will get back to you after checking it :) |
Also, the markdown preview seems to be reloaded/regenerated when the user switches back to a preview tab, so during ~800ms there's a blank area which I find quite annoying too. |
Reproducible on 1.38.1, sample file inside ZIP: |
This is another variation of the same situation: if you open a side-by-side preview, then open another tab in the preview sub-window, then switch back to the preview tab, the scroll position in the preview will have been lost. |
Want to report that this issue seems to reproduce for the case of using the following experimental setting as found via issue #84520: "workbench.experimental.editorAssociations": [
{
"viewType": "vscode.markdown.preview.editor",
"filenamePattern": "*.md"
}
] Whereby, I find it convenient to be able to open Note, I have built the VSCode application from the latest git, and out-of-box the issue does not reproduce without the experimental setting. Hence, it seems that using preview viewtype as default for md files contributes to the loss of scroll position when switching between tasks. Given the |
I've had this problem with VSCode as long as I can remember. I just installed version 1.44.0 on my Thinkpad, and it's still definitely happening. As I read through the release notes, I like to try out the new features as I read. With a document this long, it definitely causes some frustration having to keep finding my place again after each try. Hoping someone can figure out what's causing this 🙏 |
See also #27498 |
This is very annoying and distracting especially when there is a new VS Code release, the descriptions are very long. So I'll try any new feature and when I go back to the release notes are reloads from the top and I have to scroll down again. Please take a look at it whenever possible. |
This comment has been minimized.
This comment has been minimized.
Hi @mjbvz, Thanks for the feedback. However I'm not sure why it was closed, VS Code release notes still do not retain the scroll position. Instead they jump to a random point each time they get the focus back, while the scroll bar goes crazy. IMHO this is even worse than the previous situation when at least the wrong position was predictable (i.e. the start of the page) :) Best regards, |
Issue Type: Bug
=> Scroll position is reset to top
VS Code version: Code 1.28.2 (7f3ce96, 2018-10-17T00:23:51.859Z)
OS version: Windows_NT x64 10.0.17134
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Extensions (4)
The text was updated successfully, but these errors were encountered: