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
code-server version: 1.31.1-100, also tested on 1.32.0-310
OS Version: Chrome OS
Description
When attempting to view an in-VSCode markdown preview, the following error appears:
command 'markdown.showPreview' not found
Steps to Reproduce
Open a Markdown (.md) file
Use the keyboard shortcut Ctrl-Shift-V to attempt to show Markdown preview
Error appears in the lower right corner of the screen
Reacted by John McCambridge, Yamamoto, Hirotaka, YONEDA Yūki, Muruloki, LucasBoisserie, Saikrishna Edupuganti, Loong, Patryk Gałczyński, Cocalus and Michael Doyle
Seems to be an IFRAME security issue. By opening the browser debugging tools,
On Firefox:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://v1.extapi.coder.com/extensionquery. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://v1.extapi.coder.com/extensionquery. (Reason: CORS request did not succeed).
Load denied by X-Frame-Options: “DENY” from “https://<redacted>.com/webview/index.html?id=<redacted>”, site does not permit any framing. Attempted to load into “https://<redacted>.com/?folder=vscode-remote%3A%2F%2Fcode-server%3A8080%2F<redacted>”.
On Chrome:
Refused to display 'https://<redacted>.com/webview/index.html?id=<redacted>' in a frame because it set 'X-Frame-Options' to 'deny'.
Activity
kylecarbs commentedon Mar 19, 2019
Will fix!
ViRb3 commentedon Mar 11, 2020
Markdown preview does not seem to work on latest release (2.1698-vsc1.41.1). There are no errors, but the preview window is empty.
ViRb3 commentedon Mar 11, 2020
@code-asher
ViRb3 commentedon Mar 11, 2020
Seems to be an IFRAME security issue. By opening the browser debugging tools,
On Firefox:
On Chrome:
nhooyr commentedon Mar 11, 2020
Opened #1409 for you @ViRb3
ViRb3 commentedon Mar 12, 2020
Apologies, the problem was in an inherited nginx config:
Everything works after I cleared those headers.