-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
svgs not rendering in Markdown preview since update #68033
Comments
Marking as important since this might still be broken under Mac. |
I also can't repo on mac for bitmap images. @onewhitey Does this only happen for svgs? |
I'm also seeing this (or not seeing it, rather) on SVGs on linux |
I'm on Linux (Ubuntu 18.04) and seeing the "Some content has been disabled in this document" when in Markdown preview mode even though I have explicitly set it to "Disable". This happened since I updated VSCode today: Version: 1.31.0 |
Yes, this happens on my Mac (high Sierra) for svgs.
It appears to still render png and jpg, but am away from my computer at the
moment so I can’t check.
I’ll check it when I get to work.
…On Fri, 8 Feb 2019 at 6:38 am, Benjamin Watson ***@***.***> wrote:
I'm on Linux (Ubuntu 18.04) and seeing the "Some content has been disabled
in this document" when in Markdown preview mode even though I have
explicitly set it to "Disable". This happened since I updated VSCode today:
Version: 1.31.0
Commit: 7c66f58
<7c66f58>
Date: 2019-02-06T08:51:24.856Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.15.0-45-generic
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68033 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQSbHGYJQjtsvN7tk4YIu0vbiGtqViL8ks5vLICbgaJpZM4amjG3>
.
|
@mjbvz I have just tested locally: |
Fixes microsoft#68033 `allowSvgs` was already set as the default value after the webview was created. Due to an unrelated refactoring, the initial default value did not include `allowSvgs`
Reverts f98d248 since it caused unexpected side effects. Instead, lazily look up the value for `allowSvgs`. This emulates the behavior before the refactoring that broke svgs in the first place
Hello, Thanks a lot, |
VS Code 1.31.0 cannot render SVG in Markdown preview pane. We thought that was a default behavior of 1.31 from security reason, but it seems to be just a bug and fixed it at v1.31.1. See: microsoft/vscode#68033
Issue Type: Bug
Before the update, I am sure I was able to render images as such:

WarningViewing the same markdown file today, this renders as a "broken image".
VS Code version: Code 1.31.0 (7c66f58, 2019-02-05T22:32:14.164Z)
OS version: Darwin x64 17.7.0
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: enabled
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (13)
(1 theme extensions excluded)
The text was updated successfully, but these errors were encountered: