-
Notifications
You must be signed in to change notification settings - Fork 34.7k
Closed
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalityverification-neededVerification of issue is requestedVerification of issue is requestedverifiedVerification succeededVerification succeededwebIssues related to running VSCode in the webIssues related to running VSCode in the web
Milestone
Description
The web companion currently cannot load resources, like icons, because they are served from the remote extension host using the vscode-remote
-scheme. There are three potentials approaches to tackle this
- more uri-transforming. we already know that this is challenging because uris often come as css-rules and we don't look at those strings
- patch
document.createElement
and have special cases for style and img tags (and others) - use the mutation observer to know when a remote-resource is being requested
So, far option 1 seems tricky, option 2 seems pragmatic, and option 3 seems to be the browser way. There was also an attempt use service workers to serve such resources but only the https-scheme is supported...
cc @mjbvz who has a similar problem with webviews (and explored the service worker route)
Metadata
Metadata
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalityverification-neededVerification of issue is requestedVerification of issue is requestedverifiedVerification succeededVerification succeededwebIssues related to running VSCode in the webIssues related to running VSCode in the web