Skip to content

Problem preview css not properly loaded in WSL #883

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

Open
Sam0523 opened this issue May 28, 2023 · 2 comments
Open

Problem preview css not properly loaded in WSL #883

Sam0523 opened this issue May 28, 2023 · 2 comments

Comments

@Sam0523
Copy link

Sam0523 commented May 28, 2023

🐛 Bug Report

When using via WSL, problem preivew page did not load markdown.css properly, which leads to incorrect font settings.

图片

Left side is the problem preview of this extension. It is obvious that the monospace font is ugly NSimSun.
Right side is a markdown preview, which is rendered as expected.

To Reproduce

  1. Connect VSCode to WSL.
  2. Install extension for WSL.
  3. Login and open arbitrary problem preivew.

Expected behavior

Problem preview page renders with same CSS of markdown.

Your Environment

  • os: Win11 + WSL2
  • extension settings: Mostly defaults
  • nodejs version: v20.2.0
  • vscode version: 1.78.2
  • extension version: v0.18.1
@Sam0523
Copy link
Author

Sam0523 commented May 28, 2023

FYI:

It seems that the extension load the css from a wrong domain:
图片

图片

It seems that the extension tries to load a file in WSL by a host domain (file%2B.vscode-resource.vscode-cdn.net).

The correct domain in my case is vscode-remote%2Bwsl-002bopensuse-002dtumbleweed.vscode-resource.vscode-cdn.net, which is obviously related to the WSL configuration.

@lycpan233
Copy link

我也遇到了同样的问题,定位了一下发现确实是拓展有问题。目前这个问题你解决了吗? 或者是否有什么替代方案??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants