Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3885

VS Code's webview functionality should work when the browser is behind the proxy

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = Fixed webviews in Microsoft Visual Studio Code - Open Source for restricted environments

      Before this update, link:https://code.visualstudio.com/api/ux-guidelines/webviews[webviews] in Microsoft Visual Studio Code - Open Source did not render correctly in restricted environments. This issue occurred because the browser could not download static resources from the public Internet behind a proxy. With this update, the {prod-short} build of Microsoft Visual Studio Code - Open Source serves those resources directly from its server, which is usually accessible through proxies.
      Show
      = Fixed webviews in Microsoft Visual Studio Code - Open Source for restricted environments Before this update, link: https://code.visualstudio.com/api/ux-guidelines/webviews [webviews] in Microsoft Visual Studio Code - Open Source did not render correctly in restricted environments. This issue occurred because the browser could not download static resources from the public Internet behind a proxy. With this update, the {prod-short} build of Microsoft Visual Studio Code - Open Source serves those resources directly from its server, which is usually accessible through proxies.
    • Bug Fix
    • Done

      VS Code client (on the browser side) tries to fetch the common static resources for the WebView from the "https://uuid.vscode-cdn.net/insider/ef65ac1ba57f57f2a3961bfe94aa20481caca4c6/out/vs/workbench/contrib/webview/browser/pre/".

      As the resources can't be downloaded, any WebView functionality does not work. E.g.: markdown preview, the extension details page, etc.

      We can solve that problem by reworking the functionality on our (Che-Code) side to fetch the WebView-related static resources from the DevSpaces backend.
      As the same resources should be available on VS Code backend running in the cluster.

       

        1. Preview.png
          30 kB
          Artem Zatsarynnyi
        2. Screenshot_2023-01-03_at_15.42.37.png
          102 kB
          Artem Zatsarynnyi
        3. Selection_001.png
          49 kB
          Maksym Musienko
        4. Selection_002.png
          58 kB
          Maksym Musienko

              vgulyy Vitaliy Gulyy
              azatsary Artem Zatsarynnyi
              Maksym Musienko Maksym Musienko
              Max Leonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: