- 11 7月, 2019 2 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Benjamin Pasero 提交于
Also: let the theme service not change classes on document.body but the actual container of the workbench
-
- 10 7月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 05 7月, 2019 4 次提交
-
-
由 Benjamin Pasero 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
clean up user data provider
-
由 Sandeep Somavarapu 提交于
-
- 04 7月, 2019 2 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
- 02 7月, 2019 1 次提交
-
-
由 Johannes Rieken 提交于
-
- 01 7月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 24 6月, 2019 6 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
- 23 6月, 2019 1 次提交
-
-
由 Sandeep Somavarapu 提交于
-
- 21 6月, 2019 1 次提交
-
-
由 Peng Lyu 提交于
-
- 20 6月, 2019 4 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Peng Lyu 提交于
-
由 Sandeep Somavarapu 提交于
- get product configuration from server
-
- 19 6月, 2019 1 次提交
-
-
由 Peng Lyu 提交于
-
- 18 6月, 2019 2 次提交
-
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
Hello first commit from browser :)
-
- 17 6月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 16 6月, 2019 1 次提交
-
-
由 Matt Bierner 提交于
## Problem We use a custom `vscode-resource` protocol to control access to local resources inside of webviews. This will not work on the web, but we still would prefer a way to intercept webview requests from the main client ## Proposed solution Move webviews into their own origin and register a service worker on this origin. This service worker can talk with the outer iframe of our webview. When a request for a resource comes in to the service worker: * In the service worker, add the request to a map and post a message back to the client saying we want to load this resource * The outer iframe gets the message from the sercice worker and forwards it to our main process * This process handles the message and use the normal file system api to read the resource (also restricting which files can be read) * We post the result back into the inner iframe which fowards it back to the service worker * The service worker now resolves the pending request. The prototype version in this change works but does not correctly handle multiple clients existing at the same time (plus probably a lot of other edge cases too)
-
- 14 6月, 2019 2 次提交
-
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
- 13 6月, 2019 2 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Benjamin Pasero 提交于
-
- 12 6月, 2019 1 次提交
-
-
由 Sandeep Somavarapu 提交于
-
- 11 6月, 2019 3 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
- 10 6月, 2019 1 次提交
-
-
由 isidor 提交于
-
- 08 6月, 2019 2 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
- 07 6月, 2019 1 次提交
-
-
由 Johannes Rieken 提交于
-